MobilityData/GTFS_Schedule_Best-Practices
Best Practices for structuring General Transit Feed Specification Schedule data
NOASSERTION
Issues
- 1
- 15
- 8
Best Practice and spec alignment
#45 opened by scmcca - 1
- 5
Versioning cadence
#41 opened by scmcca - 5
- 2
Proposed best practice: Include tts_stop_name when stop name is potentially unintelligible using TTS technology
#34 opened by e-lo - 3
Reliable wheelchair accessibility
#32 opened by e-lo - 1
calendar.txt and stop_id as stop_code
#7 opened by RideSchedules - 2
- 1
- 2
Remove best practices now merged into the spec
#57 opened by emmambd - 0
- 0
Versioning
#35 opened by scmcca - 0
- 0
Revert to original introduction.md text
#16 opened by lionel-nj - 0
- 0
Prepare .md files to be fetched: add metadata
#23 opened by lionel-nj - 0
Change the gtfs@rmi.org to a MobilityData email
#25 opened by antrim