norway-roads_skill

This skill checks real-time road closures and conditions in Norway to help plan safer routes and avoid disruptions.
  • Python

2.6k

GitHub Stars

2

Bundled Files

3 weeks ago

Catalog Refreshed

2 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstart where the catalogue uses aiagentskills.

npx veilstart add skill openclaw/skills --skill norway-roads

  • _meta.json286 B
  • SKILL.md3.2 KB

Overview

This skill queries real-time road closures and condition data for Norway from the Statens Vegvesen NVDB API. It returns registered road closures, physical barriers, causes, locations, and closure periods to help plan travel or check specific routes. The data is drawn from the official NVDB v3 endpoint and requires no API key.

How this skill works

The skill calls NVDB object types for Vegstengning (road closures) and Vegsperring (physical barriers) and aggregates entries by location, county, municipality, cause, and from/to dates. It can filter by origin/destination, specific road names or sections, and output results as human-readable text or JSON. Responses reflect registered database entries; live traffic incidents may not be included.

When to use it

  • Checking whether a planned route between two Norwegian cities is affected by closures.
  • Verifying seasonal mountain pass closures or maintenance windows before travel.
  • Confirming whether a specific road (e.g., E6, E16, E39, Strynefjell) is closed or physically blocked.
  • Planning winter travel to understand snow, ice, or rock hazards on a route.
  • Getting official closure periods and causes for logistics, transport planning, or emergency responses.

Best practices

  • Query routes using --from and --to to get route-wide closure summaries rather than single-point checks.
  • Specify road names or known sections for targeted results when you only need local status (e.g., --road "Strynefjell" or --road "E6").
  • Use JSON output for programmatic integrations or automation; use human-readable mode for manual planning.
  • Treat NVDB entries as authoritative for registered closures but complement with live traffic sources (mobile app, traffic hotlines) for incidents not yet registered.
  • Check closure from/to dates to distinguish seasonal or scheduled closures from short-term incidents.

Example use cases

  • Are there road closures between Oslo and Bergen today? — returns closures along E16 and related segments with dates and causes.
  • Road condition on E6 near Trondheim — filters closures/barriers on E6 within Trøndelag county and lists active entries.
  • Driving to Tromsø in winter — checks for seasonal closures and avalanche/landslide risks on northern routes.
  • Logistics planning for freight — get closure windows and physical barriers to adjust delivery schedules.
  • Local authority or rescue coordination — retrieve official closure records and locations for incident response planning.

FAQ

No. The skill returns registered closures and physical barriers from NVDB. For live traffic incidents, use Vegvesen mobile services or local traffic updates.

Do I need an API key to use the data?

No. NVDB v3 is public and the skill accesses the endpoint without requiring an API key.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational