Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
95% Positive
Analyzed from 1582 words in the discussion.
Trending Topics
#live#map#data#https#transport#public#where#gtfs#bus#position
Discussion Sentiment
Analyzed from 1582 words in the discussion.
Trending Topics
Discussion (49 Comments)Read Original on HackerNews
https://www.iamexpat.de/lifestyle/lifestyle-news/new-site-al...
https://greggman.github.io/tokyo-trains
I think the live map is cool but (1) I don't know where to get that data and (2) seeing things at 100x speed is, IMO, more interesting as a visual
It's based off schedules but only Toei's schedules are easy to get (AFAICT). I got permission for the most of the others, but I thought the visual was good as is ... mostly. Maube I'll revisit.
Platinum - Real Live Location
Gold - Live as Estimated Where It Should Be From Last Observation
Silver - Live as Estimated According to Published Schedule
You Kidding Me? - Animated JavaScript...
Normally when I want to get somewhere I just use local public transport navigation app which calculates the route and shows me estimated time of when my tram or bus arrives (taking into account its GPS data). Why would I need to know live position of every vehicle in the city?
Nevertheless, cool project!
In an public transport heavy region (lots of The Netherlands is PT heavy) this changes how you interact with public transport. You stop planning. You decide you want to go to X, so you walk to the nearest stop you know will take you to X (in contrast to someone who rarely uses PT or lives in a PT light area: They either don't know the routes and thus don't know which stop to walk to, or there is only one stop within walking distance if that), and as you walk, it takes all of about 5 seconds, literally, to know if you should walk briskly or have time for a detour or whatever. Or even check if a different stop would be more efficient.
It's powered by the same data. 'look, a map!' is visually the most interesting, and thus perhaps appropriate here, where I would assume most readers don't even live in Belgium.
Delete that feature and you suddenly get a horde of angry users
(I'm joking. Local trains in Tokyo area are late quite often. Doesn't matter much when there's one every <5 minutes though.)
https://truetime.rideprt.org/map
There are a bunch of different protocols used to exchange scheduled and live transit information out there. And there are also a lot of different companies actually operating the vehicles (Transport Authorities). Sometimes several within one large city. But even if they have different systems underneath often they expose one of the popular protocols. Often there are even rules/law about certain protocols that you HAVE to support.
In USA that is mostly GTFS and GFTS-RT. I dod not think its a law but something about what you have to do to get funds maybe? I'm in Europe so my memory is foggy.
In EU I believe its NeTEx and SIRI. And every member nation needs a national hub where all transport authorities shares its data openly.
GTFS + GTFS-RT is very popular among consumer apps since its both pretty simple and pull-based. Static data is in CSV-files in a ZIP-file and the realtime data comes via Protobuf. If you check sources on the page this post is about you will se many GTFS sources. Ofc even transit systems built for the european standards can expose GTFS via a translation layer to support a broader range of consumers easily.
When it comes to signs at bus-stops there are those that are fed with this kind of data and can show both timetable data and realtime data based on the vehicles position. Here those signs are everywhere (Sweden) and I know there are plenty in the rest of Europe aswell. Outside of that I don't know if they are used as much.
> "vlive is an independent app and not an official app of any government, public authority or transport operator. It is not affiliated with, nor does it represent, NMBS/SNCB, De Lijn, STIB-MIVB or TEC. All data comes from their open data; where it matters, the official sources below are authoritative."
From: https://openbaarvervoerbelgie.be/over-ons/
* For companies publishing real time positions (STIB-MIVB, TEC), live position will be shown. For companies that don't (De Lijn, NMBS/SNBC), we calculate the position based on the schedule (GTFS), corrected with published delays (GTFS-RT).
Every vehicle on the map is labeled with realtime / calculated position.
Two notes on what you are looking at:
Not every vehicle is a live position. STIB-MIVB and TEC publish vehicle positions and those are shown as received. De Lijn and NMBS/SNCB do not, so their vehicles are computed from the timetable and corrected with the delays they do publish (GTFS-RT). Each marker is tagged live, computed with delay, or computed, and the computed ones are drawn dimmer.
All data is open data. The four operators publish through one federal portal (data.belgianmobility.io) under CC BY 4.0: GTFS for timetables and route geometry, GTFS-RT for delays, alerts and positions where available. NMBS ships no route geometry, so train paths are routed over Infrabel's open track network.
This is not specific to Belgium. Nearly every country publishes public-transport open data in the same formats, and I was able to locate feeds for most European countries. A map like this can be built for almost any of them!
Happy to answer questions on the data or the simulation :)
Those who don’t bookmark but write url by memory get extra points /s
Ptm.be is for rent btw (public transport map)