-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use data from github.com/nagix/mini-tokyo-3d #2
Comments
Is there any other open data source for any of the other agencies? Any OSM editor will work, I use JOSM, but it has a pretty steep learning curve. |
When you do the query to ODPT to get trains information, it seems that there is some ye, but for example the Den Toshi line is not present on your GTFS, the agency for that one should be Tokyu. |
There's partial information for other operators, but not schedules. Schedules are only available for Toei, Tokyo Metro, Yokohama Municipal, TWR (Rinkai Line), MIR (Tsukuba Express) and Tama Monorail: https://ckan.odpt.org/dataset/?_tags_limit=0&tags=%E5%88%97%E8%BB%8A%E6%99%82%E5%88%BB%E8%A1%A8-train_timetable. |
That would be interesting if we can link these timetables (took from mini metro 3d repository) on the GTFS ? https://github.com/nagix/mini-tokyo-3d/tree/master/data%2Ftrain-timetables |
Sure, why not? Looks like the data is up-to-date and available under an open license. I'm curious where they in turn get the data from. The data looks similar enough to the ODPT, so preparing a Provider wouldn't be too hard; however the routes seem to be a bit of a mess (e.g. |
Cool! |
Oh and also for names of station, it is possible to also select them in latin letters when we create the GTFS? |
Feel free to contribute, I probably won't have time to look into this for quite some time. Romanization is provided in translations.txt, as per the GTFS spec. |
Switched to mini-toyko-3d with the recent rewrite |
Hello,
I'm currently trying to port every lines that were forgotten on TokyoGTFS (for example the Den Toshi Line), but somehow it needs that rail_geo.osm need to be updated.
How did you made it?
The text was updated successfully, but these errors were encountered: