TIL, thank you for the reference! I completely missed that while building out Tokyo Metro, I've never been to japan (though I want to) and as such, I'm not familiar with the vast systems. It took long enough to get data to build tokyo's metro, and I based that title off several articles I had read. When I have some time this week, I'll work to add the rest of the subway systems in region and update the title. ty!
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.
Thank you for your effort and apologise for confusing you.
English is my second language, so it might not be clear to native speakers.
Thank you for adding the unit type to those endpoints!
I'll enjoy your tool!
Could track length include sidings and double-tracks and extensions and other maintenance track needs that aren't useful for the passengers themselves?
yep, its still and will always be WIP, every system exposes their data a bit differently, so it's not completely plug and play. you're welcome to contribute to the existing system data however! https://github.com/WaffleThief123/publictransit-systems/
tysm! Yeah I've got a bit of a backlog, as each set of data for each system needs a deep-dive on how the system exposes it programmatically, then need to do tests and some studying on each to build cars,timelines, etc. Toronto is on the list, if there's any in particular you want, file an issue on gh, and I'll do my best to get it added in a timely manner. https://github.com/wafflethief123/publictransit-systems/issu...
Working in the industry: this is a can of worms that you might regret opening, because of simply how completely insane so many of the systems there are. I've seen cities repurpose text fields in otherwise perfectly standard formats because they needed a way to indicate that the bus was {insert any absolutely insane situation}, and not parsing that field means that the data doesn't make sense.
Your best bet for most of Europe are the open data platforms. Example for France: https://transport.data.gouv.fr/. There's soooome standardisation around a few formats:
GTFS, Netex, SIRI along with their various extensions (like GTFS-RT for realtime data), etc. Just parsing these (which is already a large undertaking in and of itself) should get you covered for a bunch of networks.
Oh, also, much of the data you'll find, especially from smaller cities or regions, is awful. You're going to be told that the line icon is white, on white text, and that's actually perfectly normal because actually their bus header is from an obscure system from former Yugoslavia that actually interprets "0xFFFFFF" as black when on layer 1. Good luck!
OVH aren't nice in that regard, and have trolled competitors to "leave it to the pros" before when there were serious incidents ( of which OVH have had their fair share), so it's not surprising.
/shrug/ We have our infrastructure partially in OVH, I see it as a friendly jab at them and a way to get updates without having to navigate to twitter.
