Creates GTFS and feed for Tokyo from various data, mainly the Public Transportation Open Data Center.
You need to have both the ODPT apikey.
Create a file called apikeys.json with the following content:
{
"odpt": "YOUR_ODPT_APIKEY_HERE"
}Alternatively, the script can read the apikey from APIKEY_ODPT environment variable.
It's also possible to put the apikeys.json file in a different place - if path to that
file is provided via the APIKEYS_FILE environment variable.
TokyoGTFS is written in Python 3 and depends on several external modules:
Before launching install those using pip3 install -r requirements.txt, or e.g. from your package manager.
Here's a list of all the scripts.
python3 -m static.rail
Options: -h/--help, -v/--verbose.
After those flags, one has to specify what action to take:
create-gtfs (python3 -m static.rail create-gtfs):
Creates the GTFS file. See python -m static.rail create-gtfs --help for all the options.
dump-provider (python3 -m static.rail dump-provider <provider_name>):
Dumps all train of a provider into data_cached (which can be later re-used in create-gtfs --from-cache).
Used to debug problems with a specific provider.
check-geo (python3 -m static.rail check-geo [agency-or-line]):
Used internally to check and verify the structure of the curated rail_geo.osm.
check-names (python3 -m static.rail check-names):
Used internally to check the structure of the curated station_names.csv file.
python3 -m static.bus
Options: -h/--help, -v/--verbose.
After those flags, one has to specify what action to take:
create-gtfs (python3 -m static.rail create-gtfs):
Creates the GTFS file. See python -m static.rail create-gtfs --help for all the options.
count-stops (python3 -m static.rail count-stops):
Writes out the proportion of valid stops per agency, per provider.
Always use the data in compliance with sources' terms and conditions.
See
TokyoGTFS is shared under the MIT License license, included in the file license.md.