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
In AdjustFrequency, all PatternTimetables get put in a map from sourceTripId to PatternTimetable, which means that there can only be one entry per trip ID. This is problematic if you want to have multiple frequencies over the day.
Also, we will have to split TripSchedules because it's possible to have different pattern entries with the same source trip and different service (e.g. one is M–F and one is Saturday/Sunday). It's probably easiest to just create a TripSchedule per PatternTimetable.
The text was updated successfully, but these errors were encountered:
In AdjustFrequency, all PatternTimetables get put in a map from sourceTripId to PatternTimetable, which means that there can only be one entry per trip ID. This is problematic if you want to have multiple frequencies over the day.
Also, we will have to split TripSchedules because it's possible to have different pattern entries with the same source trip and different service (e.g. one is M–F and one is Saturday/Sunday). It's probably easiest to just create a TripSchedule per PatternTimetable.
The text was updated successfully, but these errors were encountered: