Intersections of the streets and roads of France

Open data API in a single place

Provided by OpenStreetMap

Get early access to Intersections of the streets and roads of France API!

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

Dataset information

Catalog

OpenStreetMap catalog

Country of origin

France

Updated

2021.11.11 16:21

Created

2021.11.11

Available languages

English

Keywords

carrefours, poi, voirie, routes, intersections, voirie-communale, rues, voirie-departementale, localisants, croisements

Datasource

Official portal for European data link

Quality scoring

Dataset description

This dataset lists intersections between named or numbered tracks in OpenStreetMap data covering the French territory. The data is generated in the streamed json format expected by the addok geocoder as well as in the geojson format. Example: {"type":"inter","name":"Chemin de la Carronnière / Route de Thoissey D64","context":"L'Abergement-Clémenciat, Ain","citycode":"01001","depcode":"01","lon":4.906772,"lat":46.163201} name: contains the name and/or route number (e.g. D40, A6) of each track separated by " / " context: contains the name of the municipality, followed by the name of the department citycode: contains the INSEE code of the municipality depcode: contains the INSEE code of the department The code used to generate the file is available at https://github.com/cquest/osm-intersections

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