Position of transport stops and lines

Open data API in a single place

Provided by Point d'Accès National transport.data.gouv.fr

Get early access to Position of transport stops and lines API!

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

Dataset information

Country of origin
Updated
2025.05.28 02:24
Created
2020.07.22
Available languages
English
Keywords
traces, transport-public, position
Quality scoring

Dataset description

Position of stops and lines of all public transport datasets available on the platform transport.data.gouv.fr. This dataset is a fusion of GeoJSON generated from GTFS files and published in community resources on data.gouv.fr. GeoJSON is an extract of the position of the transport stops as well as the layout of the lines, when these are available in the GTFS (via the file shapes.txt). GeoJSONs are generated with the https://gitlab.com/CodeursEnLiberte/gtfs-to-GeoJSON/ tool. Merged files are updated regularly automatically (with this [script](https://github.com/etalab/gtfs_converter/blob/master/gtfs_converter/merge_all_geojson.py), contributions are welcome), and published in several formats to simplify reuse: — a [GeoJSON](https://fr.wikipedia.org/wiki/GeoJSON), zipped; — one [GeoJSON per line](http://jsonlines.org/), zipped. Each line is a GeoJSON with geometry. This file may be easier to use due to the size of the GeoJSON file; — a file [GeoPackage](https://www.geopackage.org/). Note: These files are a simple aggregation of GeoJSON available on transport.data.gouv.fr. There will therefore be duplicates in the positions of stops/trace lines since some (notably the major Parisian stations) are present in several data sets.
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