Train: Green Travel Pledge Is Now Green Travel Data

The Rail Delivery Group renamed Green Travel Pledge to Green Travel Data (GTD), and SQUAKE's methodology follows: use "methodology": "GREEN-TRAVEL-DATA". The former name GREEN-TRAVEL-PLEDGE is still accepted and calculates the same way.

What's New?Copy Anchor Link

Every Station Pair, per TimetableCopy Anchor Link

The release for the timetable starting 14 December 2025 covers every pair of GB National Rail stations, whether the journey is direct or has changes. The earlier releases covered direct journeys only. SQUAKE keeps every release and calculates each journey with the release whose timetable covers its departure_date, or the latest release when none does. algorithm_specifics in the response names the release used.

Distance-Based Figure Only on RequestCopy Anchor Link

When a release has no figure for a station pair, SQUAKE now multiplies RDG's GB-wide figure per passenger-kilometre by the distance_in_km you send. Without distance_in_km, the calculation fails with green_travel_data_emission_not_found instead of returning a figure.

Changes to Responses and AuditsCopy Anchor Link

• origin and destination must be CRS codes of GB National Rail stations, such as KGX. The response no longer reports a distance derived from them; it reports distance_in_km when you send it.
• Audits no longer store car and air comparison values (co2_diesel_car, co2_plug_in_hybrid_electric_car, co2_battery_electric_car, co2_air).
• The error code green_travel_pledge_emission_not_found is now green_travel_data_emission_not_found.
• Client methodology configuration and reports list the methodology as GREEN-TRAVEL-DATA.

What This Means for YouCopy Anchor Link

Switch to "methodology": "GREEN-TRAVEL-DATA" and keep sending CRS codes and departure_date. Send distance_in_km if you want a figure for station pairs a release does not cover. See Train: Green Travel Data.