-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Flex features to list #1776
Comments
I'd like to modify Deviated Fixed Route a bit: |
@emmambd Could you elaborate on the definition of Zone-based Demand Responsive Transit? In the first screenshot, each trip_id corresponds to a location_id. Is this a valid example? (I believe yes) |
@qcdyx You're correct - Zone-based Demand Responsive Transit should be triggered when there is a location_id associated with a trip_id. It should not be triggered when stop_id is associated with trip_id. So the logic is: if the trip has a location_id and NO stop_id, trigger Zone-based Demand DRT make sense? |
Describe the problem
Now that Flex is adopted, we want to be able to track usage of Flex features within the validator and within the Mobility Database API, which includes features generated by the GTFS Schedule Validator.
Proposed solution
The following four features should be added:
Booking Rules: At least one record in booking_rules.txt
Fixed-Stops Demand Responsive Transit: At least one record in location_groups.txt
Zone-based Demand Responsive Transit: At least a trip in stop_times references only location_id
Deviated Fixed Route: At least a trip in stop_times references location_id AND stop_id AND arrival_time AND departure_time
Alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: