feat: Add support for timeframes.txt #158
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WMATA here in DC started including the optional
timeframes.txt
to their GTFS datasets. Currently,node-gtfs
doesn't importtimeframes.txt
into SQLite.timeframes.txt
appears to be part of the standard GTFS Schedule dataset.WMATA Rail GTFS Static details: https://developer.wmata.com/docs/services/gtfs/operations/5cdc5367acb52c9350f69753
Dataset with
timeframes.txt
included: wmata-gtfs-rail-static.zipNote: When using VSCode, I had a bit of trouble getting linting and formatting to work. Apologies if there are any formatting mistakes here. It looks like the
npm run lint
command from the README doesn't work.