NVDB Prohibited Direction of Travel

Open data API in a single place

Provided by Lantmäteriet

Get early access to NVDB Prohibited Direction of Travel API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Lantmäteriet catalog

Country of origin

Sweden

Updated

2024.11.12 00:00

Created

2001.04.01

Available languages

English

Keywords

område: transport, NVDB, trafikslag: väg, väghållare: statlig, vägtrafiknät: cykelnät, väghållare: kommunal, väghållare: enskild, vägtrafiknät: bilnät

Datasource

Official portal for European data link

Quality scoring

Dataset description

The type of activity includes a traffic rule on the prohibited direction of travel or the prohibition of entry by regulation or as a result of physical road design. The data product is registered on both the car network and the bicycle network. The data product consists of the phenomenon type Prohibited direction of travel belonging to the product group NVDB and the product subgroup Traffic Regulation Types in NVDB. The purpose of the data product is to provide information on where there is regulation of traffic by prohibited direction of travel. This affects traffic accessibility by closing connections between certain points. The data product creates, among other things, the right conditions for navigation on the road network.

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service