search

cal-itp / operational-data-standard

The Transit Operational Data Standard is an open standard for representing the transit schedules used by drivers, dispatchers, and planners to carry out transit operations.
https://ods.calitp.org
Apache License 2.0
27 stars 6 forks source link

Separate HASTUS vehicle and crew schedules in run_events.txt? #72

Closed skyqrose closed 3 months ago

skyqrose commented 3 months ago

An issue that @jeffkessler-keolis raised that may affect #66 : HASTUS has separate schedule_ids for vehicle schedules and crew schedules, while #66 only has a single service_id, which corresponds to a HASTUS vehicle schedule id. If a producer who uses HASTUS has crew schedules that aren't aligned to vehicle schedules (e.g. vehicle schedules and GTFS use a service_id for "Weekday", while crew schedules have separate schedules_ids and duties for "Monday" and "Tuesday"), then it may be difficult to find a way to translate crew schedules into run_events.txt.

Jeff, can you write up a specific example?

Other producers: If you use HASTUS, do you have crew and vehicle schedules that don't line up with each other? Would this be a problem for you?

This issue won't delay #66. If this is a problem, we'd look for a workaround or an optional/backwards compatible addition on top of #66 for 2.1.

skyqrose commented 3 months ago

Jeff wrote up a more detailed description in #76 . Closing this issue in favor of that one.