So interesting that Baltimore’s very subpar public transit system made it into the first batch of systems — not complaining at all I love that city & love to see it in random places on the internet :)
Show HN: Public transit systems as data – lines, stations, railcars, and history
21–26 of 26 posts
Re: Show HN: Public transit systems as data – lines, stations, railcars, and history
#22> Tokyo Metro is one of two rapid transit operators in Tokyo, Japan (the other being Toei Subway) I'm assuming this text is an AI hallucination because there are dozens of rail operators in Tokyo. Tokyo Metro is not even the largest and basically only operates an underground subway. JR (Japan Rail) operates above-ground and is much larger (and nation-wide). https://en.wikipedia.org/wiki/List_of_urban_rail_systems_in_…
Re: Show HN: Public transit systems as data – lines, stations, railcars, and history
#23This is interesting! However, can't it switch the unit to meters, not miles? From the link you provided, it appears the API doesn't include information about its unit in the responses. So, it's confusing.
theres a button in the top right to switch from miles to kilometers, that does it globally and handles the calculation gracefully! Edit: I've had my coffee now, and see what you mean. the API exposes it at /api/systems/{system}/lines/{line}, as well as aggregate for the system at /api/systems/{system}, working on supplying distance unit in api response now.
Re: Show HN: Public transit systems as data – lines, stations, railcars, and history
#24Re: Show HN: Public transit systems as data – lines, stations, railcars, and history
#25Earlier quoted context omitted.
theres a button in the top right to switch from miles to kilometers, that does it globally and handles the calculation gracefully! Edit: I've had my coffee now, and see what you mean. the API exposes it at /api/systems/{system}/lines/{line}, as well as aggregate for the system at /api/systems/{system}, working on supplying distance unit in api response now.
added unit type to those endpoints now.
Re: Show HN: Public transit systems as data – lines, stations, railcars, and history
#26For example, Tokyo Metro has many out-of-gate transfers, where the user taps out of special gates (Ikebukuro M/F) and into another paid area (Ikebukuro Y) on the same fare, as long as it's within 30 minutes. There are also out-of-gate transfers between different stations, such as Shintomicho and Tsukiji. Beijing has transfers within the same paid area that are notorious for being long and/or congested, so much so that some believe it's an intentional traffic control mechanism. These all have significant implications on actual experienced commute time and fare.
So if the end goal includes human navigation or commute statistics, it's incomplete without such considerations. Those government APIs you're using are only concerned with ridership and not these details. Short of visiting these places, you could watch vlogs (there's probably 5 for every Tokyo Metro station), and you could perhaps simulate some routes on existing navigation systems.