geojson-to-gtfs v0.3.0

geojson-to-gtfs

A library for Node.js to generate public transit feeds in the GTFS format from GeoJSON Feature Collections.

Motivation

This project is part of a set of tools to provide travel data in countries where public transport works on demand and neither bus stops nor timetables exist. Check out https://github.com/trufi-app to see more of our work.

Installation

$ npm install geojson-to-gtfs

Usage

Minimal example (using defaults):

const geojsonToGtfs = require('geojson-to-gtfs');

// Reads GeoJSON file, writes GTFS file
geojsonToGtfs('./routes.geojson', './gtfs.zip');

Customize transformation:

geojsonToGtfs('./routes.geojson', './gtfs.zip', {
  agencyUrl: "https://www.example.org", // Static value
  routeShortName: (feature) => feature.properties.line, // Callback
});

Usage without files:

const geojson = {
  type: "FeatureCollection",
  features: [{
    type: "Feature",
    geometry: {
      type: "LineString",
      coordinates: [[-66.2806316, -17.394221], [-66.2788024, -17.3940565], /* ... */]
    }
  }
};

const userConfig = {
  // ...
};

// Pass in GeoJSON as object. Output path is omitted and GTFS data is returned.
const gtfs = geojsonToGtfs(geojson, userConfig);

/*
{
  agency: [ ... ],
  calendar: [ ... ],
  frequencies: [ ... ],
  routes: [ ... ],
  stop_times: [ ... ],
  stops: [ ... ],
  trips: [ ... ],
  shapes: [ ... ]
}
*/

Handling missing information

As GeoJSON files describe geographic data structures and not public transit feeds, they lack a lot of crucial information. That is why this library was designed to give you lots of flexibility to fill in the gaps while transforming the data by defining static values or callbacks or overriding parts of the mapping altogether.

Stop times

By default, stop times are generated based on vehicle speed and the duration between stops. The time spent at a stop can be defined with the stopDuration config value. If you need more control you can override the mapStopTimes function.

Configuration

When transforming the GeoJSON to GTFS, field values will be determined by some default behaviour. You can change this behaviour for each field separately by overriding the respective key in the configuration or, when you need more flexibility, by overriding the respective mapping function.

Field values in the configuration can be either

• a primitive value that will be used for all generated rows or
• a callback that returns a primitive value. The callback arguments can be found in the listing below.

GTFS values

Special values

Service dates

Service windows are defined ahead of time. Default:

serviceWindows: [{
  serviceId: "mon-sun",
  monday: true,
  tuesday: true,
  wednesday: true,
  thursday: true,
  friday: true,
  saturday: true,
  sunday: true,
  startDate: "20000101",
  endDate: "21000101",
}]

Mapping functions

These can be overridden to customize the GTFS output.

Hooks

These can be used to pre- or post-process data. Hooks do not expect any return value. Passed in objects can be modified directly.

Constants

Some GTFS fields expect a magic number(https://en.wikipedia.org/wiki/Magicnumber(programming) that conveys certain information, e.g. to specify the route type. Instead of using the numbers directly, you can use the pre-defined contants for better readability. These are set as properties on the geojsonToGtfs function and can be used like this:

geojsonToGtfs.routeType.BUS

You can find all available constants in the src/constants.js file.

Todo

• Implement missing GTFS files: calendar_dates.txt, fare_rules.txt, transfers.txt, feed_info.txt
• Add missing GTFS fields for the existing files
• Allow different stop times strategies
• Allow multiple frequencies per trip
• Improve how calendar data is defined