Theme 1 – Data sources and open standards
Many commenters note that the live maps rely on open transit data feeds, most commonly GTFS/GTFS‑RT in the U.S. and NeTEx/SIRI in Europe, often accessed through national open‑data portals.
- “In USA that is mostly GTFS and GFTS‑RT… In EU I believe its NeTEx and SIRI.” – ap‑andersson
- “For reference all of these generally use the gtfs standard.” – twelvechairs
- “All data is open data… GTFS for timetables and route geometry, GTFS‑RT for delays, alerts and positions where available.” – mci‑1 (author)
Theme 2 – Accuracy and transparency of live vs. estimated positions
Users frequently discuss whether a vehicle’s marker shows a real GPS position or a schedule‑based estimate corrected with delays, and they point out inconsistencies.
- “When you hover over a dot you can see whether it's the real position or whether the position is computed from the timetable with delay applied. The transparent yellow dots are computed, the opaque yellow dots are real position.” – tmtvl
- “Lots of systems have some sort of real location data, but it can be… shaky.” – rsynnott
- “Transit telemetry is inherently spotty on these public‑facing applications… it will resort to transit schedule estimations when data is missing.” – crispyambulance
Theme 3 – Practical usefulness and the desire for a global live map
Commenters value the maps for seeing actual vehicle locations (helping with unreliable stop timers) and express interest in aggregating such maps worldwide.
- “Absolutely, the official apps are lacking… This kind of map lets you check where the bus actually is.” – edarchis
- “You stop planning. You decide you want to go to X… and as you walk, it takes all of about 5 seconds… to know if you should walk briskly or have time for a detour.” – rzwitserloot (describing the Dutch OVInfo app)
- “This thread is full of people linking similar projects for different locations. The next step must be to combine it all to a global live map.” – ostacke