CO2e emissions - usage perimeter

Open data API in a single place

Provided by SNCF Voyageurs

Get early access to CO2e emissions - usage perimeter API!

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

Dataset information

Country of origin
Updated
2025.12.05 13:27
Created
2025.12.05
Available languages
English
Keywords
ter, tgv, co2, environnement, developpement-durable, intercites, pollution
Quality scoring

Dataset description

CO2e emissions* (kgCO2e/traveller) on the main TGV, Intercity, TER and international routes (use perimeter). The scope of use for calculating CO2e emissions is defined as the accounting of the emissions of the scope of use, i.e. the emissions produced during the use of the vehicle (fuel or electricity consumption). Estimate calculated as follows: travel distance x CO2 emissions per kilometre of a passenger. All the data and calculation methodologies are detailed in the information document on the amount of greenhouse gases emitted during a transport service, available here: <https://ressources.data.sncf.com/explore/dataset/info-ges/information/>. The sources of the distance data are as follows: * For the train: SNCF source data; * For long-distance coaches: data from the results of several bus companies (Flixbus, Blablabus and local companies); * For the car: data from Mappy results. When the same journey is operated by several carriers (TGV, TER, Intercités), it must be considered that the TGV carbon footprint is displayed; * For aircraft: data from Google Maps, from distances as the crow flies. For the aircraft, condensation and cirrus trails are not taken into account. The names of stations and the distances between stations are given for information purposes only, and may vary depending on the planned date of travel and the route chosen. _*CO2e: CO2 equivalent_
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