-
Notifications
You must be signed in to change notification settings - Fork 64
Description
Are you sure this is not a data issue?
- Yes, this is a Traewelling software bug (not a data issue).
Affected URL (if any)
No response
Describe the problem
I’ve noticed an issue with the geodata of my long-distance trips over the last two days that did not occur before.
Until recently, each trip had precise geoinformation of the real route stored and displayed.
Since around two weeks ago, I’ve observed the following behavior:
For long-distance check-ins that are at least one month in the past, no detailed geodata is shown anymore.
Instead of the previous detailed route shapes, I now only see highly simplified lines:
Either a straight line between the origin and destination station
Or straight segments between the individual stops
As a result, it is no longer possible to see the actual route of past long-distance trips.
This is quite frustrating for me, because I specifically use Traewelling for these detailed route visualizations.
Questions / Request:
Is this a known issue or an change?
If it is an intentional change:
Is there any way to still access the detailed geodata of older trips (e.g. via an opt-in setting, an export feature, etc.)?
If this is a bug:
Could you check whether the original detailed geodata is still available and whether the previous display can be restored?
Observed behavior:
Platform: Web / API
Affected trips: Long-distance trips, check-ins older than ~1 month
Previously: detailed route shapes with many points along the track
Now: only straight lines between origin/destination or between stops
The map data is from 08.01.2026
The web view is form today (14.01.2026)
https://github.com/user-attachments/assets/bd967b2e-c1ae-47df-ac83-5301991b50da
Thanks a lot for looking into this!
Steps to reproduce
Click on any old National Express check-in or request polyline via API.
Expected behavior
Even for older long-distance trips, the detailed geodata of the actual route traveled should be displayed, as it used to be.
If you need additional information (e.g. example links to affected trips, screenshots, time ranges), I’m happy to provide them.
Environment
No response
Browser console / error messages (optional)
Additional info (optional)
No response