NVDB C-Recommended road for cycling

Open data API in a single place

Provided by Lantmäteriet

Get early access to NVDB C-Recommended road for cycling 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

2007.08.13

Available languages

English

Keywords

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

Datasource

Official portal for European data link

Quality scoring

Dataset description

The data product consists of the phenomenon type C-Recommended road for bicycle traffic belonging to the product group NVDB-GCM.The data product includes data on recommended road for bicycle traffic that creates continuity of the cycle network by identifying suitable roads in the car network for bicycle traffic. The data product can only be linked to the car network, i.e. the road sections where the road traffic network is designated as “car network”, see reference #5 in DPS — data product specification — “The Swedish road network”. The purpose of the data product is to, for example, in a bicycle travel planner lead bicycle traffic to the streets that are most suitable for cycling traffic from a road safety point of view or for other reasons.

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