Create GTFS data for Tokyo trains and buses.
Written in Python and with the Impuls framework.
- Make sure you have a recent Python installation
- Create a new virtual environment for dependency management:
python -m venv --upgrade-deps .venv - Activate the venv:
. .venv/bin/activate - Install dependencies:
pip install -Ur requirements.txt - Provide API keys
- Run the desired script, e.g.
python -m tokyo_gtfs.rail
The railway GTFS contains schedule and through-service (block_id) data for all urban railways in the greater metropolitan area. The data is made available by the excellent mini-tokyo-3d project, with some minor tweaks applied.
Note that through-running occurs between multiple route types; that is a single block_id might join both rail and metro trips. This is intentional and must be supported by the consuming software.
Beware that the data is licensed under the MIT License,
and with the following copyright: Copyright (c) 2019-2025 Akihiko Kusanagi.
Most operators in the greater Tokyo area already share a GTFS and a GTFS-Realtime feeds, see https://ckan.odpt.org/dataset/?tags=%E3%83%90%E3%82%B9-bus&res_format=GTFS%2FGTFS-JP.
The script only creates GTFS for operators without GTFS feeds, but with ODPT JSON data; that is:
Tobu Bus(missing stop positions),Kanachu(missing stop positions),Kokusai Kogyo Bus(missing stop positions),- Tokyu Bus,
Odakyu Bus(missing stop positions),- Sotetsu Bus.
The data for those operators is very bare-bone, and thus the resulting GTFS is also quite bare-bone. None of these operators share realtime data.
As of now, API keys are only required for creating the bus GTFS. One must register at https://developer.odpt.org/
and obtain the "standard"/ODPT center apikey and the "challenge" apikey. Those keys must then be set
in the TOKYO_ODPT_APIKEY and TOKYO_CHALLENGE_APIKEY environment variables, e.g.:
$ export TOKYO_ODPT_APIKEY=apikey1
$ export TOKYO_CHALLENGE_APIKEY=apikey2
$ python -m tokyo_gtfs.bus
Most IDEs will have some support for .env files – use them to avoid having to export environment variables when running the scripts.
As an alternative, TokyoGTFS also accepts Docker-style secret passing. Instead of setting
TOKYO_ODPT_APIKEY or TOKYO_CHALLENGE_APIKEY directly, the apikeys can be saved in files,
and paths to those files can be set through the TOKYO_ODPT_APIKEY_FILE or
TOKYO_CHALLENGE_APIKEY_FILE environment variables. Beware that the direct/non-file env variables
take precedence.
TokyoGTFS is distributed under GNU GPL v3 (or any later version).
© Copyright 2025 Mikołaj Kuranowski
TokyoGTFS is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
TokyoGTFS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with TokyoGTFS. If not, see http://www.gnu.org/licenses/.
Except for files under the data directory, which are under the CC0 license;
released to the public domain.
The resulting railway GTFS is licensed under the MIT License,
with the following attribution: Copyright (c) 2019-2025 Akihiko Kusanagi.
The resulting bus GTFS uses data from the Public Transportation Open Data Center, under its Public Transportation Open Data Basic License and Public Transportation Open Data Challenge Limited License. This requires an attribution to the ODPT and a statement that accuracy and integrity of the data is not guaranteed and that users shall not contact ODPT and the operators about the data.