Consider management-side trip identification #51

Open
opened 2026-03-13 04:32:03 +00:00 by maxtkc · 1 comment
Owner

How can we make it so drivers don't have to specify their trip?

We could have a rule based setup.

Rule: If driver = bob, if time matches MWF 8-10am, set trip_id bobs_big_trip

We can suggest trip_id's (but NO FK) based on the GTFS static.

We can also consider having trip_id in the rule, which, if set, requires the driver to be set to something like "auto" to receive the remote trip id. We could also hardcode this, because maybe it's too complicated to have multiple anyways.

If we don't match a rule, we ignore them. If they are not set to auto, we use whatever they are set to (overriding settings here), I think this is simplest.

How can we make it so drivers don't have to specify their trip? We could have a rule based setup. ``` Rule: If driver = bob, if time matches MWF 8-10am, set trip_id bobs_big_trip ``` We can suggest trip_id's (but NO FK) based on the GTFS static. We can also consider having trip_id in the rule, which, if set, requires the driver to be set to something like "auto" to receive the remote trip id. We could also hardcode this, because maybe it's too complicated to have multiple anyways. If we don't match a rule, we ignore them. If they are not set to auto, we use whatever they are set to (overriding settings here), I think this is simplest.
maxtkc added this to the GTFS Realtime project 2026-03-17 18:19:01 +00:00
maxtkc self-assigned this 2026-03-17 18:19:01 +00:00
maxtkc changed title from Consider management side trip specification to Consider management-side trip identification 2026-03-19 01:07:38 +00:00
Author
Owner

This is likely the way that many small agencies would use it. And we are targeting small agencies. So it's important

This is likely the way that many small agencies would use it. And we are targeting small agencies. So it's important
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
gtfs.zone/deploy-gtfs-rt#51
No description provided.