Consider management-side trip identification #51
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
gtfs.zone/deploy-gtfs-rt#51
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
How can we make it so drivers don't have to specify their trip?
We could have a rule based setup.
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.
Consider management side trip specificationto Consider management-side trip identificationThis is likely the way that many small agencies would use it. And we are targeting small agencies. So it's important