An import tool for the British rail fares, routeing and timetable feeds into a database.
Although both the timetable and fares feed are open data you will need to obtain the fares feed via the ATOC website. The formal specification for the data inside the feed also available on the ATOC website.
At the moment only MySQL compatible databases are supported but it could be extended to support other data stores. PRs are very welcome.
Download / Install
You don't have to install it globally but it makes it easier if you are not going to use it as part of another project. The
-g option usually requires
sudo. It is not necessary to git clone this repository unless you would like to contribute.
npm install -g dtd2mysql
Each of these commands relies on the database settings being set in the environment variables. For example
DATABASE_USERNAME=root DATABASE_NAME=fares dtd2mysql --fares-clean.
Import the fares into a database, creating the schema if necessary. This operation is destructive and will remove any existing data.
dtd2mysql --fares /path/to/RJFAFxxx.ZIP
Removes expired data and invalid fares, corrects railcard passenger quantities, adds full date entries to restriction date records. This command will occasionally fail due to a MySQL timeout (depending on hardware), re-running the command should correct the problem.
Import the timetable information into a database, creating the schema if necessary. This operation is destructive and will remove any existing data.
dtd2mysql --timetable /path/to/RJTTFxxx.ZIP
Convert to GTFS
Convert the DTD/TTIS version of the timetable (up to 3 months into the future) to GTFS.
dtd2mysql --timetable /path/to/RJTTFxxx.ZIP dtd2mysql --gtfs-zip filename-of-gtfs.zip
dtd2mysql --routeing /path/to/RJRGxxxx.ZIP # optional dtd2mysql --nfm64 /path/to/nfm64.zip
Download from SFTP server
The download commands will take the latest full refresh from an SFTP server (by default the DTD server).
Requires the following environment variables:
SFTP_USERNAME=dtd_username SFTP_PASSWORD=dtd_password SFTP_HOSTNAME=dtd_hostname (this will default to dtd.atocrsp.org)
There is a command for each feed
dtd2mysql --download-fares /path/ dtd2mysql --download-timetable /path/ dtd2mysql --download-routeing /path/ dtd2mysql --download-nfm64 /path/
Or download and process in one command
dtd2mysql --get-fares dtd2mysql --get-timetable dtd2mysql --get-routeing dtd2mysql --get-nfm64
Values marked as all asterisks, empty spaces, or in the case of dates - zeros, are set to null. This is to preverse the integrity of the column type. For instance a route code is numerical although the data feed often uses ***** to signify any so this value is converted to null.
Although every record format has a composite key defined in the specification an
id field is added as the fields in the composite key are sometimes null. This is no longer supported in modern versions of MariaDB or MySQL.
At present journey segments, class legends, rounding rules, print formats and the fares data feed meta data are not imported. They are either deprecated or irrelevant. Raise an issue or PR if you would like them added.
The timetable data does not map to a relational database in a very logical fashion so all LO, LI and LT records map to a single
GTFS feed cutoff date
Only schedule records that start up to 3 months into the future (using date of import as a reference point) are exported to GTFS for performance reasons. This will cause any data after that point to be either incomplete or incorrect, as override/cancellation records after that will be ignored as well.
Issues and PRs are very welcome. To get the project set up run
git clone firstname.lastname@example.org:planarnetwork/dtd2mysql npm install --dev npm test
If you would like to send a pull request please write your contribution in TypeScript and if possible, add a test.
This software is licensed under GNU GPLv3.
Copyright 2017 Linus Norton.