\n
![\"GTFS-to-GeoJSON\"](\"docs/images/gtfs-to-geojson-logo.svg\"){kind=logo}
\n \n
![](\"https://img.shields.io/npm/v/gtfs-to-geojson.svg?style=flat\")
\n ![](\"https://img.shields.io/npm/dm/gtfs-to-geojson.svg?style=flat\")
\n ![](\"https://img.shields.io/badge/License-MIT-yellow.svg\"){kind=icon}
\n \n Generate geoJSON of transit route data from a GTFS file.\n
\n
![\"NPM\"](\"https://nodei.co/npm/gtfs-to-geojson.png?downloads=true\")
\n\n ➡️\n Web Version |\n Installation |\n Quick Start |\n Configuration\n ⬅️\n
\n \n
\n \n \n \n
\n Generate geoJSON of transit route data from a GTFS file.\n
\n \n
![](\"https://user-images.githubusercontent.com/96217/81493949-96532f00-9259-11ea-9e09-d0399b59bf30.png\")
\n\n![](\"https://user-images.githubusercontent.com/96217/101810511-1da99f00-3ad6-11eb-90e7-cb2b6919a77f.jpg\")
\n\n`gtfs-to-geojson` uses the [`node-gtfs`](https://github.com/blinktaginc/node-gtfs) library to handle importing and querying GTFS data. If you are looking to generate HTML timetables in addition to maps, check out the [gtfs-to-html](https://github.com/BlinkTagInc/gtfs-to-html) project. If you'd like to make a cool stringline chart of all trips on a route throughout the day, check out the [gtfs-to-chart](https://github.com/BlinkTagInc/gtfs-to-chart) project.\n\n### GTFS-to-geojson on the web\n\nYou can now use gtfs-to-geojson without actually downloading any code or doing any configuration. geojson.gtfstohtml.com provides a web based interface for generating GeoJSON from GTFS. It allows uploading a zipped GTFS file or specifying a URL to a GTFS file.\n\n## Current Usage\n\nMany transit agencies use `gtfs-to-geojson` to generate the maps for their websites, including:\n\n- [511 Contra Costa](https://511contracosta.org/public-transit/contra-costa-transit-map/)\n- [County Connection](https://countyconnection.com/)\n- [Kings Area Rural Transit (KART)](https://www.kartbus.org/)\n- [Marin Transit](https://marintransit.org/)\n- [MVgo](https://mvgo.org/)\n- [Mountain View Community Shuttle](https://mvcommunityshuttle.com/)\n\nAre you using `gtfs-to-geojson`? Let us know via email (![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/envelope.png\")
| [envelope.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/envelope.geojson) |\n| `convex` | Polygon | A convex polygon around route endpoints. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/convex.png\")
| [convex.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/convex.geojson) |\n| `stops` | Points | Stops as points. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/stops.png\")
| [stops.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/stops.geojson) |\n| `stops-buffer` | Polygons | A buffer around stops. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/stops-buffer.png\")
| [stops-buffer.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/stops-buffer.geojson) |\n| `stops-dissolved` | Polygons | A dissolved buffer around stops. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/stops-dissolved.png\")
| [stops-dissolved.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/stops-dissolved.geojson) |\n| `lines` | MultiLineStrings | Routes as lines. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/lines.png\")
| [lines.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/lines.geojson) |\n| `lines-buffer` | Polygons | A buffer around route lines. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/lines-buffer.png\")
| [lines-buffer.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/lines-buffer.geojson) |\n| `lines-dissolved` | Polygons | A dissolved buffer around route lines. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/lines-dissolved.png\")
| [lines-dissolved.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/lines-dissolved.geojson) |\n| `lines-and-stops` | Points and MultiLineStrings | Both points and lines for stops and routes. | ![](\"https://raw.githubusercontent.com/BlinkTagInc/gtfs-to-geojson/master/examples/lines-and-stops.png\")
| [lines-and-stops.geojson](https://github.com/BlinkTagInc/gtfs-to-geojson/blob/master/examples/lines-and-stops.geojson) |\n\n```\n \"outputFormat\": \"lines-and-stops\"\n```\n\n### sqlitePath\n\n{String} A path to an SQLite database. Optional, defaults to using an in-memory database with a value of `:memory:`. If you want the data imported to persist, you need to specify a value for `sqlitePath`. Supports tilde as part of the path, like `~/Downloads/gtfs`.\n\n```\n \"sqlitePath\": \"/tmp/gtfs\"\n```\n\n### startDate\n\n{String} A date in YYYYMMDD format to use to filter service_ids in calendar.txt. Useful in combination with `endDate` configuration option. Optional, if not specified, all services in GTFS will be used.\n\n```\n \"startDate\": \"20240301\"\n```\n\n### zipOutput\n\n{Boolean} Whether or not to zip the output into one zip file named `geojson.zip`. Defaults to `false`.\n\n```\n \"zipOutput\": false\n```\n\n## Running\n\nTo generate geoJSON, run `gtfs-to-geojson`.\n\n gtfs-to-geojson\n\nBy default, `gtfs-to-geojson` will look for a `config.json` file in the project root. To specify a different path for the configuration file:\n\n gtfs-to-geojson --configPath /path/to/your/custom-config.json\n\nThis will download the GTFS file specified in `config.js` . Then, `gtfs-to-geojson` will create geoJSON and save it to `geojson/:agencyKey`.\n\n### Options\n\n`configPath`\n\n gtfs-to-geojson --configPath /path/to/your/custom-config.json\n\n`skipImport`\n\nSkips importing GTFS into SQLite. Useful if you are rerunning with an unchanged GTFS file. If you use this option and the GTFS file hasn't been imported or you don't have an `sqlitePath` to a non-in-memory database, you'll get an error.\n\n gtfs-to-geojson --skipImport\n\n## Processing very large GTFS files\n\nBy default, node has a memory limit of 512 MB or 1 GB. If you have a very large GTFS file, use the `max-old-space-size` option. For example to allocate 12 GB:\n\n export NODE_OPTIONS=\"--max-old-space-size=30000\"\n gtfs-to-geojson\n\n### Credits\n\nIdeas for including buffers, envelopes and convex service-area polygons came from [gtfs-service-area](https://github.com/cal-itp/gtfs-service-area).\n\n## Contributing\n\nPull requests are welcome, as is feedback and [reporting issues](https://github.com/blinktaginc/gtfs-to-geojson/issues).\n","readmeFilename":"README.md"}