Best Practices: Reasonable lengths in unique ids
Open
Change type: Non-Functional
Discussion Period
GTFS Schedule
Support: Needs Feedback
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 225
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 3
Description
### Describe the problem
Today, I was confronted with a GTFS feed that used 100+ character IDs for individual trip_ids. You may guess what the size of the feed looked like. Their old feeds used only 8 digits as trip_id.
### Use cases
Efficient resource usage.
### Proposed solution
I want to propose a 36 byte soft limit as best practice for any identifier used in GTFS. A UUID would fit, I would say even a NeTEx ServiceJourney or ScheduledStopPoint identifier would fit as whole. If a value exceeds 36 bytes, a _nice_ warning can and should be presented.
Contributor guide
Assessment
This issue has not been assessed yet.