GTFS Transport Types
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 24
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
The original GTFS format specifies 7 transport types.
For ingesting multiple sources, we should implement a lookup for the extended transport type list proposed over at https://developers.google.com/transit/gtfs/reference/extended-route-types.
This list is already used in different sources (e.g. Berlin).
- [ ] implement look-up table for mode-id to mode string
- [ ] annotate responses appropriately with the modes (this might include a dedicated look-up by city / network, since modes might be used differently)
- [ ] remove references from source (`gtfs/route.hpp`)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the extended route types reference linked in the issue, then inspect gtfs/route.hpp and the existing GTFS ingestion and response handling. Define the mode-id lookup, determine how city or network-specific usage affects annotations, and remove obsolete source references; done means extended modes are represented correctly for the supported sources.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100