Describe the problem
When trying to implement a driver facing app that works for multiple agencies, it takes a little extra effort to scan through the data to categorize how an agency is using stop_times
Proposed solution
It would be useful to have more granular labeling of features used in the stop times file. Some possible ideas:
- uses arrival time (i think some feeds just copy departure time into arrival time)
- some classification of how timepoint is used - are the exact points meant for publishing to official timetables or only for internal performance observation or some other scheme
Alternatives you've considered
Keep manually scanning individual feeds and building my own taxonomy
Additional context
Been mostly focused on small agencies that arent using a cad/avl or scheduling software
Describe the problem
When trying to implement a driver facing app that works for multiple agencies, it takes a little extra effort to scan through the data to categorize how an agency is using stop_times
Proposed solution
It would be useful to have more granular labeling of features used in the stop times file. Some possible ideas:
Alternatives you've considered
Keep manually scanning individual feeds and building my own taxonomy
Additional context
Been mostly focused on small agencies that arent using a cad/avl or scheduling software