You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
real-time information on map (per each vehicle visible on map)
historical information in reports
Both would significantly (especially during panedmic times) help dispatchers react both instantly and planners react more efficient in deploying suitable vehicles based on the data.
Since the data could come from APC or other external systems (that would i.e. include vehicle id and enum value of occupancy status), it would need to be stored in TC database and be included in the produced vehicle_positions in GTFS-RT (there are already consumers of that data, including Google Maps and OneBusAway).
The text was updated successfully, but these errors were encountered:
Following adoption of Occupancy status in GTRS-RT v2 (details here: (https://gtfs.org/reference/realtime/v2/#enum-occupancystatus it would be important to include this in TransitClock for a number of reasons:
Both would significantly (especially during panedmic times) help dispatchers react both instantly and planners react more efficient in deploying suitable vehicles based on the data.
Since the data could come from APC or other external systems (that would i.e. include vehicle id and enum value of occupancy status), it would need to be stored in TC database and be included in the produced vehicle_positions in GTFS-RT (there are already consumers of that data, including Google Maps and OneBusAway).
The text was updated successfully, but these errors were encountered: