GTFS to Aquius

This tool converts GTFS (General Transit Feed Specification) data into an Aquius dataset file. Unzip the GTFS (General Transit Feed Specification) archive, select (above) all the .txt files that were within the archive, and wait for the output to appear. Processing will normally take a few seconds for every 10 Megabytes of raw text data. Processing requires operating system memory of up to 10 times the total size of the raw text data. If processing takes more than a minute, it is highly likely that the machine has run out of free physical memory, and processing should be aborted. Merge Aquius can be used to work around any memory limitation by dividing stop_times.txt, running two or more GTFS conversions, and merging the result - as documented.

Optionally, also add a GeoJSON file (ending .json or .geojson) to the selection, which contains Polygon or MultiPolygon geographic boundaries which have their numeric population attached as the property population (or a custom field which has been specified in config.json as populationProperty). Population data allows Aquius to summarise the people served by a network. To improve processing speed, first limit the geographic area to broadly that of the GTFS archive and reduce the node complexity of the boundaries.

Optionally, also add a file called config.json to the selection, which contains bespoke criteria for generating the output. This can be used to control processing conditions such as date ranges, define product filters, and integrate attributions or translations. To produce a basic config.json file, process the data once and save the resulting config.json file. Edit that file in a text editor, then add the edited config.json to the selection above and re-process.

See documentation for configuration details and how to use of the output file. For routine or repeat usage, the conversion script can incorporated into a bespoke application which imports the javascript and calls the function gtfsToAquius.process(gtfs, options), as documented.