gtfs-to-html 2.7.2 → 2.8.0

package/www/docs/logging-sql-queries.md

@@ -1,12 +0,0 @@
----
-id: logging-sql-queries
-title: Logging SQL Queries
----
-
-## Logging SQL Queries
-
-You can add the option `debug` to your `config.json` file with the value of `true` to log all SQLite queries.
-
-```json
-"debug": true
-```

package/www/docs/previewing-html-output.md

@@ -1,24 +0,0 @@
----
-id: previewing-html-output
-title: Previewing HTML output
----
-
-## Previewing HTML output
-
-It can be useful to run the example Express application included in the `app` folder as a way to quickly preview all routes or see changes you are making to custom template.
-
-After an initial run of `gtfs-to-html`, the GTFS data will be downloaded and loaded into SQLite.
-
-You can view an individual route HTML on demand by running the included Express app:
-
-```bash
-    node app
-```
-
-By default, `gtfs-to-html` will look for a `config.json` file in the project root. To specify a different path for the configuration file:
-
-```bash
-    node app --configPath /path/to/your/custom-config.json
-```
-
-Once running, you can view the HTML in your browser at [localhost:3000](http://localhost:3000)

package/www/docs/processing-large-gtfs.md

@@ -1,10 +0,0 @@
----
-id: processing-large-gtfs
-title: Processing very large GTFS files
----
-
-By default, node has a memory limit of 512 MB or 1 GB. If you have a very large GTFS file and want to use the option `showOnlyTimepoint` = `false` you may need to allocate more memory. Use the `max-old-space-size` option. For example to allocate 4 GB:
-
-```
-    NODE_OPTIONS=--max_old_space_size=4096 gtfs-to-html
-```

package/www/docs/quick-start.md

@@ -1,136 +0,0 @@
----
-id: quick-start
-title: Quick Start
----
-
-## Command Line Usage
-
-The `gtfs-to-html` command-line utility will download the GTFS file specified in `config.js` and then build the HTML timetables and save them in `html/:agency_key`.
-
-If you would like to use this library as a command-line utility, you can install it globally directly from [npm](https://npmjs.org):
-```bash
-npm install gtfs-to-html -g
-```
-Then you can run `gtfs-to-html`.
-```bash
-gtfs-to-html
-```
-### Command-line options
-
-`configPath`
-
-Allows specifying a path to a configuration json file. By default, `gtfs-to-html` will look for a `config.json` file in the directory it is being run from. [See all configuration options](https://gtfstohtml.com/docs/configuration)
-```bash
-gtfs-to-html --configPath /path/to/your/custom-config.json
-```
-`skipImport`
-
-Skips 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, you'll get an error.
-```bash
-gtfs-to-html --skipImport
-```
-### Customizing the output
-
-You can create your own template to completely customize the HTML output using [custom templates](https://gtfstohtml.com/docs/custom-templates).
-
-### Processing very large GTFS files.
-
-By default, node has a memory limit of 512 MB or 1 GB. If you have a very large GTFS file and want to use the option `showOnlyTimepoint` = `false` you may need to allocate more memory. Use the `max-old-space-size` option. For example to allocate 4 GB:
-```bash
-NODE_OPTIONS=--max_old_space_size=4096 gtfs-to-html
-```
-## Docker Usage
-
-You can use both [`docker`](https://docker.com) and [`docker-compose`](https://docs.docker.com/compose/) to run GTFS-to-HTML.
-
-### Dockerfile
-
-A `Dockerfile` is available in the `docker` directory.
-
-- Create a `config.json` file and save in the same directory as your `Dockerfile`. You can use `config-sample.json` from the project root as a starting point. For Docker usage, remove any `sqlitePath` and `templatePath` values from the config.json.
-
-- Build the docker image:
-```bash
-docker build -t gtfs-to-html .
-```
-- Run the docker image:
-```bash
-docker run gtfs-to-html
-```
-- Copy the generated HTML out of the docker container
-
-```bash
-// Figure out what your container ID is
-docker container ls -a
-
-// Then copy the html folder from that container
-docker cp <YOUR IMAGE CONTAINER ID>:/html .
-
-// For example:
-docker cp ca45a38963d9:/html .
-```
-
-### Docker Compose
-
-Docker compose is used for multi-container Docker applications. In this context, it is just a convenient way to manage volumes. This allows (_i_) to get the generated HTML out of the docker container without explicitly copying with `docker cp`, and (_ii_) to tweak and run a new configuration without rebuilding the container from scratch.
-
-- Create a `config.json` file and save in the same directory as your `Dockerfile` and `docker-compose.yml`;
-
-- build and run the container:
-```bash
-docker-compose up
-```
-- the generated HTML will be available in the folder `html` next to docker files.
-
-Do you want to change something? Just delete the old HTML, change your `config.json`, and finally run `docker-compose up` again.
-
-## Usage as a node module
-
-If you are using this as a node module as part of an application, you can include it in your project's `package.json` file.
-
-### Code example
-
-```javascript
-import gtfsToHtml from 'gtfs-to-html';
-import { readFile } from 'fs/promises';
-const config = JSON.parse(
-  await readFile(new URL('./config.json', import.meta.url))
-);
-
-gtfsToHtml(config)
-  .then(() => {
-    console.log('HTML Generation Successful');
-    process.exit();
-  })
-  .catch((err) => {
-    console.error(err);
-    process.exit(1);
-  });
-```
-
-### Example Application
-
-An example Express application that uses `gtfs-to-html` is included in the `app` folder. After an initial run of `gtfs-to-html`, the GTFS data will be downloaded and loaded into SQLite.
-
-You can view an individual route HTML on demand by running the included Express app:
-```bash
-node app
-```
-By default, `gtfs-to-html` will look for a `config.json` file in the project root. To specify a different path for the configuration file:
-```bash
-node app --configPath /path/to/your/custom-config.json
-```
-Once running, you can view the HTML in your browser at [localhost:3000](http://localhost:3000)
-
-## Usage as a hosted web app
-
-A [hosted version of GTFS-to-HTML as a service](https://run.gtfstohtml.com) allows you to use it entirely within your browser - no downloads or command line necessary. Currently, it is limited to relatively small GTFS files and doesn't offer support for [Custom Templates](/docs/custom-templates).
-
-It provides:
-
-- a web-based interface for finding GTFS feeds or ability to enter your own URL
-- support for adding [custom configuration](/docs/configuration) as JSON
-- creation of HTML or PDF timetables as a downloadable .zip file
-- a preview of all timetables generated directly in your browser
-
-[run.gtfstohtml.com](https://run.gtfstohtml.com)

package/www/docs/related-libraries.md

@@ -1,54 +0,0 @@
----
-id: related-libraries
-title: Related Libraries
----
-
-## `node-gtfs`
-[`https://github.com/blinktaginc/node-gtfs`](https://github.com/blinktaginc/node-gtfs)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/node-gtfs/raw/master/docs/images/node-gtfs-logo.svg" alt="node-gtfs" width="100" /></div>
-  <div><code>gtfs-to-html</code> uses the <a href="https://github.com/blinktaginc/node-gtfs">node-gtfs</a> library to handle importing and querying GTFS data. It provides methods for loading transit data in GTFS format into a SQLite database and methods to query for agencies, routes, stops, times, fares, calendars and other GTFS data. It also offers spatial queries to find nearby stops, routes and agencies and can convert stops and shapes to geoJSON format.</div>
-</div>
-
-## `gtfs-to-geojson`
-[`https://github.com/blinktaginc/gtfs-to-geojson`](https://github.com/blinktaginc/gtfs-to-geojson)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/gtfs-to-geojson/raw/master/docs/images/gtfs-to-geojson-logo.svg" alt="gtfs-to-geojson" width="100" /></div>
-  <div><a href="https://github.com/blinktaginc/gtfs-to-geojson"><code>gtfs-to-geojson</code></a> converts transit data in GTFS format into geoJSON. This includes both shapes and stops. It can be configured to generate one geoJSON file per route or a single file which contains all routes for an agency. This is useful for creating maps of transit routes.</div>
-</div>
-
-## `gtfs-to-chart`
-[`https://github.com/blinktaginc/gtfs-to-chart`](https://github.com/blinktaginc/gtfs-to-chart)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/gtfs-to-chart/raw/master/docs/images/gtfs-to-chart-logo.svg" alt="gtfs-to-chart" width="100" /></div>
-  <div><a href="https://github.com/blinktaginc/gtfs-to-chart"><code>gtfs-to-chart</code></a> generates a stringline chart in D3 using data from an agency's GTFS. This chart shows all trips for a specific route as they travel through space over a single day.</div>
-</div>
-
-## Transit Departures Widget
-[`https://github.com/BlinkTagInc/transit-departures-widget`](https://github.com/BlinkTagInc/transit-departures-widget)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/transit-departures-widget/raw/main/docs/images/transit-departures-widget-logo.svg" alt="Transit Departures Widget" width="100" /></div>
-  <div>The <a href="https://github.com/BlinkTagInc/transit-departures-widget">Transit Departures Widget</a> generates a user-friendly transit realtime departures widget in HTML format directly from GTFS and GTFS-RT transit data. Most transit agencies have schedule data in GTFS format and many publish realtime departure information using GTFS-RT. This project generates HTML, JS and CSS for use on a transit agency website to allow users to see when the next vehicle is departing from a specific stop and includes features like caching, auto-refresh, url parameters and custom templates.</div>
-</div>
-
-## GTFS Accessibility Validator
-[`https://github.com/BlinkTagInc/gtfs-accessibility-validator`](https://github.com/BlinkTagInc/gtfs-accessibility-validator)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/gtfs-accessibility-validator/raw/main/docs/images/gtfs-accessibility-validator-logo.svg" alt="Transit Departures Widget" width="100" /></div>
-  <div>The <a href="https://github.com/BlinkTagInc/gtfs-accessibility-validator">GTFS Accessibility Validator</a> checks transit data in GTFS format for fields and files related to accessibility. The accessibility guidelines are taken from the <a href="https://dot.ca.gov/cal-itp/california-transit-data-guidelines-v3_0#section-checklist">California Transit Data Guidelines</a> published by Caltrans.</div>
-</div>
-
-## GTFS Text-to-Speech Tester
-[`https://github.com/BlinkTagInc/node-gtfs-tts`](https://github.com/BlinkTagInc/node-gtfs-tts)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/node-gtfs-tts/raw/main/docs/images/gtfs-tts-logo.svg" alt="Transit Departures Widget" width="100" /></div>
-  <div>The <a href="https://github.com/BlinkTagInc/node-gtfs-tts">GTFS Text-to-Speech Tester</a> is a command-line tool that will read all GTFS stop names using Text-to-Speech and allow flagging which names need Text-to-Speech values for tts_stop_name in stops.txt. Using this tool is the quickest way to determine which stops need phonetic spellings, abbreviations written out, large digits written as words, ordinals written out or other changes so that they can be read.</div>
-</div>
-
-## `node-gtfs-realtime`
-[`https://github.com/BlinkTagInc/node-gtfs-realtime`](https://github.com/BlinkTagInc/node-gtfs-realtime)
-<div style={{ display: 'flex', gap: 20 }}>
-  <div style={{ width: 100, flexShrink: 0 }}><img src="https://github.com/BlinkTagInc/node-gtfs-realtime/raw/main/docs/images/node-gtfs-realtime-logo.svg
-  " alt="Transit Departures Widget" width="100" /></div>
-  <div>GTFS-realtime transit data is in <a href="https://developers.google.com/protocol-buffers">protobuf format</a> which means its not human-readable by default. <code>node-GTFS-Realtime</code> aims to make it fast and easy to inspect GTFS-realtime data by providing a one-line command for downloading GTFS-realtime format data and converting to JSON. Try it out by running <code>npx gtfs-realtime http://api.bart.gov/gtfsrt/tripupdate.aspx</code> in your terminal.</div>
-</div>

package/www/docs/reviewing-changes.md

@@ -1,29 +0,0 @@
----
-id: reviewing-changes
-title: Reviewing changes between schedule updates
----
-
-When an agency updates their schedule and releases an updated GTFS file, it can be useful to review what has changed when generating HTML timetables. There are two ways to review what has changed:
-
-## Use `git`
-
-Use git to version control the output of GTFS-to-HTML. Make a git repository for this purpose and check in a set of timetable HTML files. Then, when generating updated timetables overwrite the old timetables and review the changes using your favorite git tool, such as [Github Desktop](https://desktop.github.com).
-
-
-## Use `diff2html`
-
-`diff2html` is a command line tool to easily compare two folders of html timetables.
-
-First generate two folders of GTFS-to-HTML output to compare. To make it easy to see what has changed, set the `beautify` option to `true` in the config file for both sets of output.
-
-Then, install diff2html:
-
-```bash
-    npm install -g diff2html-cli
-```
-
-Use the `diff` command and pipe the output to `diff2html` to get a nicely formatted list of the differences between two folders of html files.
-
-```bash
-    diff -bur html/folder1 html/folder2 |  diff2html -i stdin
-```

package/www/docs/stop-attributes.md

@@ -1,30 +0,0 @@
----
-id: stop-attributes
-title: stop_attributes.txt
----
-
-This is an optional, non-standard file called `stop_attributes.txt` which can be included in an agency's GTFS. This can be used to add additional useful information not included in GTFS, such as the city of each stop.
-
-### Column Definitions
-
-| column name | description |
-| ----------- | ----------- |
-| `stop_id` | A `stop_id` from `stops.txt` |
-| `stop_city` | The name of the city or region that the stop is in. |
-
-### Example
-
-```csv
-stop_id,stop_city
-1001,"Fresno, CA"
-1002,"Fresno, CA"
-1003,"Hanford, CA"
-1004,"Hanford, CA"
-1005,"Lemoore, CA"
-```
-
-An example of this file is located in [examples/stop_attributes.txt](https://github.com/BlinkTagInc/gtfs-to-html/blob/master/examples/stop_attributes.txt). 
-
-:::note
-This feature is in development. Fields may be added or changed in the future.
-:::

package/www/docs/support.md

@@ -1,12 +0,0 @@
----
-id: contact
-title: Questions, Feedback and Support
----
-
-## Issues
-
-GTFS-to-HTML is an open source project. If you encounter an issue when using it, please [open an issue on github](https://github.com/BlinkTagInc/gtfs-to-html/issues). Pull requests are welcome!
-
-# Questions, Feedback and Support
-
-Have questions about GTFS-to-HTML or need help integrating it into your agency's website? Email us at brendan@blinktag.com.

package/www/docs/timetable-notes-references.md

@@ -1,44 +0,0 @@
----
-id: timetable-notes-references
-title: timetable_notes_references.txt
----
-
-This is an optional, non-standard file called `timetable_notes_references.txt` which can be included in an agency's GTFS. This file specifies where notes that are defined in [`timetable_notes.txt`](/docs/timetable-notes) should be placed. Using `timetable_notes_references.txt` notes can be placed on specific stops, trips, stoptimes, routes or timetables.
-
-### Column Definitions
-
-| column name | description |
-| ----------- | ----------- |
-| `note_id` | The `note_id` that this reference refers to. |
-| `timetable_id` | Use to attach a note to an entire timetable, or in combination with `stop_id` to restrict which timetable a a note should show up on. Optional. |
-| `route_id` | Use to attach a note to all timetables for a specific route, or in combination with `stop_id` to restrict which timetable a a note should show up on. Optional. |
-| `trip_id` | Use to attach a note to a specific trip row or column, or in combination with `stop_id` to restrict to a specific stoptime. Optional. |
-| `stop_id` | Use to attach a note to a specific stop row or column, or in combination with `trip_id` to restrict to a specific stoptime. Optional. |
-| `stop_sequence` | Use along with a `stop_id` to attach a note to a specific stop and stop_sequence. Useful for routes that serve the same stop more than once in a trip such as circular routes. Optional. |
-| `show_on_stoptime` | A binary value that indicates whether this note should show up on all stoptimes of a trip or stop that it applies to. Valid options are `0` and `1`.  Optional, defaults to `0`. |
-
-### Example
-
-```csv
-note_id,timetable_id,route_id,trip_id,stop_id,stop_sequence,show_on_stoptime
-1,131,,,,,
-2,,17,,,,
-3,,,17010,,,1
-4,,,,254514,,
-5,,,,254514,11,
-6,,,17010,235269,,
-```
-
-Note `1` applies to only a specific timetable and it applies to the entire timetable. No other timetables will have this note.
-
-Note `2` applies only to a specific route. All timetables for that route will have this note.
-
-Note `3` applies only to a specific trip. Because it has `show_on_stoptime` set to `1` it shows up in the trip header and also for each timepoint of that trip in all timetables that have that trip.
-
-Note `4` applies only to a specific stop. It shows up by the stop name in all timetables that use that stop.
-
-Note `5` applies only to a specific stop and stop_sequence. It shows up by the stop name only if that stop has that stop_sequence value `11` for any trip in that timetable.
-
-Note `6` applies only to a specific stop and trip. It only shows up by the timepoint that matches the specific trip_id and stop_id.
-
-An example of this file is located in [examples/timetable_notes_references.txt](https://github.com/BlinkTagInc/gtfs-to-html/blob/master/examples/timetable_notes_references.txt).

package/www/docs/timetable-notes.md

@@ -1,33 +0,0 @@
----
-id: timetable-notes
-title: timetable_notes.txt
----
-
-This is an optional, non-standard file called `timetable_notes.txt` which can be included in an agency's GTFS. This file specifies notes about specific stops, trips, stoptimes, routes or timetables that should be included in the HTML output of a timetable.
-
-The symbol and text of each note is defined in this file while the locations that each note should be placed is defined in [`timetable_notes_references.txt`](/docs/timetable-notes-references). This allows one note to be used in multiple places, such as two different trips, without having to duplicate the text of the note multiple times.
-
-Notes can have a `symbol` specified or can be left blank and GTFS-to-HTML will assign a letter a-z to each note (falling back to using integers if more than 26 symbols are needed).
-
-### Column Definitions
-
-| column name | description |
-| ----------- | ----------- |
-| `note_id` | A unique ID for the timetable note |
-| `symbol` | The symbol used to indicate the note, such as `§`. Optional, if omitted a letter of the alphabet starting with `a` will be used. |
-| `note` | The text of the note, such as "This stop is sometimes underwater". [Markdown syntax](https://daringfireball.net/projects/markdown/syntax) is supported which allows including links and formatting. |
-
-### Example
-
-```csv
-note_id,symbol,note
-1,,"No service during baseball games"
-2,,"No express service during a full moon"
-3,,"Trip is cancelled if drawbridge is up"
-4,,"This stop is sometimes underwater"
-5,,"Driver will only stop if prearranged by fax"
-6,§,"Vehicle can arrive early if leap second is added during trip and *will not wait*"
-7,,"[See list of holidays](http://transitagency.org/holidays)"
-```
-
-An example of this file is located in [examples/timetable_notes.txt](https://github.com/BlinkTagInc/gtfs-to-html/blob/master/examples/timetable_notes.txt).

package/www/docs/timetable-pages.md

@@ -1,37 +0,0 @@
----
-id: timetable-pages
-title: timetable_pages.txt
----
-
-This is an optional, non-standard file called `timetable_pages.txt` which can be included in an agency's GTFS. This file specifies which HTML timetable to group together into a single HTML page.
-
-If you'd like to show timetables both directions of a route on the same HTML page or show timetables for weekdays and weekends on the same HTML page then you'll need `timetable_pages.txt`.
-
-### Column Definitions
-
-| column name | description |
-| ----------- | ----------- |
-| `timetable_page_id` | A unique ID for the timetable page |
-| `timetable_page_label` | A label that will show up on the top of the page. Optional, defaults to using route name. |
-| `filename` | The filename to use for the generated HTML file. Optional, defaults to `timetable_page_id` with file extension `.html`, for example `1.html`. |
-
-### Example
-
-```csv
-timetable_page_id,timetable_page_label,filename
-1,"Cloverdale, Healdsburg, Windsor, Santa Rosa","60.html"
-2,"Sebastopol, Rohnert Park, Cotati","26.html"
-```
-
-### Simple Example
-
-This example just lists `timetable_page_id` and will default to creating `1.html`, `2.html` and `3.html`.
-
-```csv
-timetable_page_id,timetable_page_label,filename
-1,,
-2,,
-3,,
-```
-
-An example of this file is located in [examples/timetable_pages.txt](https://github.com/BlinkTagInc/gtfs-to-html/blob/master/examples/timetable_pages.txt).

package/www/docs/timetable-stop-order.md

@@ -1,63 +0,0 @@
----
-id: timetable-stop-order
-title: timetable_stop_order.txt
----
-
-This is an optional, non-standard file called `timetable_stop_order.txt` which can be included in an agency's GTFS. It is used to specify stop order for a particular timetable. It is useful when generating combined timetables for multiple overlapping routes, or exerting fine-grained control on stop order.
-
-This file is often not needed. If all trips for a route serve the same set of stops, or all trips stop order is topologically sortable, there is no need to use `timetable_stop_order.txt` for that route. `timetable_stop_order.txt` is only needed for routes where some trips serve completely different stops than other trips and where the order can not be determined using a directed graph.
-
-GTFS-to-HTML uses [toposort](https://www.npmjs.com/package/toposort) to sort stops for each trip topologically iin a directed graph to determine a valid stop order for use in a timetable. If stop order across trips is cyclic or disjointed (i.e. not all trips have a common stop) then the stop order from trip with most number of stops is used as a fallback.
-
-| column name | description |
-| ----------- | ----------- |
-| `timetable_id` | The ID of the timetable from `timetables.txt` |
-| `stop_id` | The ID of the stop from `stops.txt`. |
-| `stop_sequence` | An assigned integer identifying the order of stops to be presented in the timetable. The values for `stop_sequence` must be non-negative integers, and they must increase along the trip. This value does not need to match the `stop_sequence` found in `stop_times.txt`. |
-
-### Example
-
-Route 1, trip 1 stops:
-
-    _____/‾‾‾\___
-    A B C D E H I
-
-Route 2, trip 2 stops:
-
-    ‾‾‾‾‾\___/‾‾‾
-    A B C F G H I
-
-The `timetable_stop_order.txt` for this route would be:
-
-```csv
-timetable_id,stop_id,stop_sequence
-1,A,0
-1,B,1
-1,C,2
-1,D,3
-1,E,4
-1,F,5
-1,G,6
-1,H,7
-1,I,8
-```
-
-Or, if you'd like to show stops `F` and `G` before stops `D` and `E` on the timetable:
-```csv
-timetable_id,stop_id,stop_sequence
-1,A,0
-1,B,1
-1,C,2
-1,F,3
-1,G,4
-1,D,5
-1,E,6
-1,H,7
-1,I,8
-```
-
-An example of this file is located in [examples/timetable_stop_order.txt](https://github.com/BlinkTagInc/gtfs-to-html/blob/master/examples/timetable_stop_order.txt).
-
-## Stops with different arrival and departure times
-
-Stoptimes with different arrival and departure times will be shown twice in a row and labeled as "(arrival)" and "(departure)". There is no need to put the same stop in timetable_stop_order twice in a row.

package/www/docs/timetables.md

@@ -1,64 +0,0 @@
----
-id: timetables
-title: timetables.txt
----
-
-This is an optional, non-standard file called `timetables.txt` which can be included in an agency's GTFS. This file specifies to GTFS-to-HTML which HTML timetables should be built. Often, this is the only additional file you need to create to use GTFS-to-HTML.
-
-### Column Definitions
-
-| column name              | description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `timetable_id`           | A unique ID for the timetable                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
-| `route_id`               | The ID of the route the timetable is for from `routes.txt`. For timetables that should include more than one route, see [Multi-route timetables](#multi-route-timetables)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `direction_id`           | The `direction_id` from `trips.txt` for the timetable. This can be blank.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `start_date`             | The start date for this timetable in `YYYYMMDD` format.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `end_date`               | The end date for this timetable in `YYYYMMDD` format.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `monday`                 | A binary value that indicates whether this timetable should include service on Mondays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `tuesday`                | A binary value that indicates whether this timetable should include service on Tuesdays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `wednesday`              | A binary value that indicates whether this timetable should include service on Wednesdays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
-| `thursday`               | A binary value that indicates whether this timetable should include service on Thursdays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `friday`                 | A binary value that indicates whether this timetable should include service on Fridays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `saturday`               | A binary value that indicates whether this timetable should include service on Saturdays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
-| `sunday`                 | A binary value that indicates whether this timetable should include service on Sundays. Valid options are `0` and `1`.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
-| `start_time`             | A time in HH:MM:SS format used exclude all trips that start before this time. Optional, default is to use all trips throughout the day.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
-| `end_time`               | A time in HH:MM:SS format used exclude all trips that start on or after this time. Optional, default is to use all trips throughout the day.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `include_exceptions`     | A binary value that indicates whether or not to include exceptions of type `1` from `calendar_dates.txt`, such as holiday service on a weekday. Valid options are `0` and `1`. Optional, defaults to `0` (exceptions are not included by default).                                                                                                                                                                                                                                                                                                                                                                                                                                   |
-| `timetable_label`        | A short text label describing the timetable, for instance "Route 4 Northbound Mon-Fri". Optional, defaults to route name and first and last stops. Optional.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `service_notes`          | Text shown on the timetable about the service represented. Optional.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
-| `orientation`            | Determines if the top row should be a list of trips or stops. Valid options are `vertical`, `horizontal` or `hourly`. `vertical` shows stops across the top row with each row being a list of stop times for each trip. `horizontal` shows trips across the top row with each row being stop times for a specific stop. `hourly` is for routes that run the same time each hour and will print a simplified schedule showing minutes after the hour for each stop. `horizontal` orientation is best for routes with lots of stops and fewer trips while `vertical` orientation is best for routes with lots of trips and a smaller number of stops. Optional, default is `vertical`. |
-| `timetable_page_id`      | The timetable page that should include this timetable. Optional.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
-| `timetable_sequence`     | The order that this timetable should appear on the timetable page. Optional.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
-| `direction_name`         | The human readable name of the direction of the timetable, such as "Southbound". Optional.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
-| `show_trip_continuation` | A binary value that indicates whether this timetable should show an additional column(s) or row(s) indicating which trips continue from a different route or continue on as a different route. This is calculated by trips that share the same `block_id` in `trips.txt`. Valid options are `0` and `1`. Optional, defaults to `0`.                                                                                                                                                                                                                                                                                                                                                  |
-
-### Example
-
-```csv
-timetable_id,route_id,direction_id,start_date,end_date,monday,tuesday,wednesday,thursday,friday,saturday,sunday,start_time,end_time,include_exceptions,timetable_label,service_notes,orientation,timetable_page_id,timetable_sequence,direction_name,show_trip_continuation
-0,2034,0,20150101,20151122,1,1,1,1,1,1,0,00:00:00,13:00:00,0,101 Northbound,Mon-Sat AM,horizontal,1,0,Northbound,0
-1,2034,0,20150101,20151122,1,1,1,1,1,1,0,13:00:00,24:00:00,0,101 Northbound,Mon-Sat PM,horizontal,1,1,Northbound,0
-2,2035,1,20150819,20151122,1,1,0,1,1,0,0,,,0,101T Northbound,"Mon,Tue,Thur,Fri",horizontal,1,0,Northbound,0
-3,2035,0,20150819,20151122,0,0,1,0,0,0,0,,,0,101T Southbound,Wednesday,horizontal,1,0,Southbound,0
-4,2036,1,20150101,20151122,0,0,0,0,0,0,1,,,0,102 Eastbound,Sunday,horizontal,1,0,Eastbound,0
-5,2036,0,20150101,20151122,1,1,1,1,1,0,0,,,0,102 Westbound,Mon-Fri,horizontal,1,0,Westbound,0
-6,2036,1,20150101,20151122,0,0,0,0,0,1,0,,,0,102 Eastbound,Saturday,horizontal,1,0,Eastbound,0
-7,2037,0,20150101,20151122,1,1,1,1,1,0,0,,,0,103 Westbound,Mon-Fri,horizontal,1,0,Westbound,0
-```
-
-An example of this file is located in [examples/timetables.txt](https://github.com/BlinkTagInc/gtfs-to-html/blob/master/examples/timetables.txt).
-
-## Multi-route Timetables
-
-To allow creating a single timetable for multiple routes that overlap, you can have multiple entries in `timetables.txt` for the same `timetable_id`. All fields should be the same for each row in `timetables.txt` for a combined route timetable except `route_id`.
-
-### Multi-route example
-
-In this example, only one timetable will be generated that will include trips from route_ids `2034`, `2035` and `2036`.
-
-```csv
-timetable_id,route_id,direction_id,start_date,end_date,monday,tuesday,wednesday,thursday,friday,saturday,sunday,start_time,end_time,include_exceptions,timetable_label,service_notes,orientation,timetable_page_id,timetable_sequence,direction_name,show_trip_continuation
-0,2034,0,20150101,20151122,1,1,1,1,1,1,0,,,0,101 Northbound,Mon-Sat AM,horizontal,1,0,Northbound,0
-0,2035,0,20150101,20151122,1,1,1,1,1,1,0,,,0,101 Northbound,Mon-Sat AM,horizontal,1,0,Northbound,0
-0,2036,0,20150101,20151122,1,1,1,1,1,1,0,,,0,101 Northbound,Mon-Sat AM,horizontal,1,0,Northbound,0
-```