Street information in Schleswig-Holstein

Open data API in a single place

Provided by Landesbetrieb Straßenbau und Verkehr Schleswig-Holstein

Get early access to Street information in Schleswig-Holstein API!

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

Dataset information

Country of origin
Updated
2025.11.13 23:00
Created
2009.12.31
Available languages
English
Keywords
bundesfernstraßen, opendata, netzknoten, kreisstraßen, kreisstraße, bundesfernstraße, schleswig-holstein, strasseninformationen, straßeninformationen, landesstraße, strassen, straßen, landesstraßen, netzknotenkarte, lbv, verkehrsnetze, sh
Quality scoring

Dataset description

In Schleswig-Holstein, the overland roads (Bundesfern-, Landes- and Kreisstrassen) are stationed. This stationing of the roads takes place in sections. Each section begins and ends at a network node (intersection or junction) of the inter-urban road network. The record section numbers of the interurban roads with the exception of the numbers in the cities. The Landesbetrieb Straßenbau und Verkehr Schleswig-Holstein assumes no liability for the correctness, completeness and up-to-dateness of the road data. The Landesbetrieb Straßenbau und Verkehr Schleswig-Holstein assumes no liability for material and financial losses incurred by the user as a result of the use of the data.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
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.

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

Copyright © 2026. Made by Apitalks