Trip and Calendar Patterns #20
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.
Dependencies
No dependencies set.
Reference
gtfs.zone/coloring-book#20
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?
It would be really cool if the ui could automatically identify trips that are just shifted versions of each other and show this in some compacted form. It could default to the compact mode and then you could expand it to edit one, for instance. Then that trip would jump out of the pattern view. This would just be a ui change, not changing the way we store the data.
For calendars, we should identify the set of US holidays and other common patterns for exclusions.
It would be nice to abstract this so it's easy to identify a pattern. It should allow for adding a trip to a trip set in an intuitive way.
This needs to be fleshed out.