v7.0.0 #2011
emmambd
announced in
Announcements
v7.0.0
#2011
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Highlights
🧒 👵 👨 Rules for rider categories in GTFS-Fares
Rider Categories are groups of passengers, like adults, children, seniors, or students, who may get different fare pricing based on their age, status, or needs. As of February this year, it's now possible to describe rider categories in GTFS. We've added validation rules to check the quality of new rider categories data, as well as a new Rider Category Feature that will display in the summary report when this data is provided.
📞🚌 Full list of Flex rules
GTFS Flex is a proposal that ensures riders can discover demand responsive services and how to book them. Flex was officially adopted into GTFS last year. With this validator release, we offer a full list of validation rules for Flex. You can see more under "Flex notices".
Breaking JSON report change:
N/Avalues now display as""To help standardize empty strings, empty values are now populated with
""instead ofN/Ain the generatedreport.json.Notice changes
🔴
duplicate_key: Triggers whenrider_category_idis not unique inrider_categories.txt.🔴
foreign_key_violation: Verifies thatnetwork_idfound infare_leg_join_rules.txtmatches an entry innetworks.txtorroutes.txt.rider_category_idfound infare_products.txtmatches an entry inrider_categories.txt.🔴
invalid_url: Triggers wheneligibility_urlinrider_categories.txtis invalid.🔴
missing_required_field: Triggers whenfrom_stop_idorto_stop_idis present infare_leg_join_rules.txtbut the other is omittedrider_category_idand/orrider_category_nameand/oris_default_fare_categoryare omitted fromrider_categories.txt🔴
unexpected_enum_value: Triggers whenis_default_fare_categoryis a value other than 0, empty or 1.⬜
unused_parent_stationrenamed tounused_stationNew notices
🔴
fare_product_with_multiple_default_rider_categories: This notice is generated when a fare product is associated with multiple rider categories that are marked as default.🟡
transfer_distance_too_large: The transfer distance from stop to stop in transfers.txt is larger than 10 km.⬜
transfer_distance_above_2_kmThe transfer distance from stop to stop in transfers.txt is larger than 2 km.Flex notices
Flex new notices
🔴
duplicate_geography_id: ID must be unique across allstops.stop_id,locations.geojson id, andlocation_groups.location_group_idvalues.🔴
forbidden_geography_id: In stop_times.txt, you can have only one ofstop_id,location_group_idorlocation_iddefined for given entry.🔴
missing_stop_times_record: Travel within the same location group or GeoJSON location requires two records in stop_times.txt with the samelocation_group_idorlocation_id.🔴
forbidden_arrival_or_departure_time: The arrival or departure times are provided alongside pickup or drop-off windows in stop_times.txt. This violates GTFS specification, as both cannot coexist for a single stop time record.🔴
forbidden_continuous_pickup_drop_off: Continuous pickup or drop-off are forbidden whenroutes.continuous_pickuporroutes.continuous_drop_offare 0, 2 or 3 andstop_times.start_pickup_drop_off_windoworstop_times.end_pickup_drop_off_windoware defined for any trip of this route.🔴
forbidden_pickup_type:pickup_drop_off_windowfields are forbidden when the pickup_type is regularly scheduled (0) or must be coordinated with the driver (3).🔴
forbidden_drop_off_type:pickup_drop_off_windowfields are forbidden when the drop_off_type is regularly scheduled (0).🔴
invalid_pickup_drop_off_window: The end_pickup_drop_off_window must be strictly later than the start_pickup_drop_off_window.🔴
missing_pickup_or_drop_off_window: Either the start or end pickup/drop-off window is missing in stop_times.txt.🟡
missing_pickup_drop_off_booking_rule_id:pickup_booking_rule_idis recommended whenpickup_type=2anddrop_off_booking_rule_idis recommended whendrop_off_type=2. Currently, this notice is only triggered on feeds when eitherstart_pickup_drop_off_windoworend_pickup_drop_off_windowis defined, since this recommendation was added to the specification for feeds with GTFS-Flex.locations.geojson notices
🔴
duplicate_geo_json_key: The key must be unique for each feature in the GeoJSON file.🔴
geo_json_duplicated_element: Duplicated elements in locations.geojson file.🔴
overlapping_zone_and_pickup_drop_off_window: Two entities instop_times.txtwith the sametrip_idhave the samepickup_typeordrop_off_typeand overlapping pickup/drop-off windows and overlapping zones in locations.geojson.⬜ geo_json_unknown_element: Unknown elements in locations.geojson file.
Flex notice changes
🔴
foreign_key_violation: Checks that thelocation_idfield in stop_times.txt reference valid entries in the locations.geojson file.🔴
missing_prior_day_booking_field_valueseparated into missing_prior_notice_last_day and missing_prior_notice_last_time noticesImpacts on existing data
You can find the impact of this release on all existing datasets we have in the Mobility Database in this spreadsheet.
Other notable improvements
invalid_input_files_in_subfolderwas not being triggered in certain valid cases.New Contributors
Full PR List
Continuous Stopsfrom flex alert by @cka-y in fix: filter outContinuous Stopsfrom flex alert #1920overlapping_zone_and_pickup_drop_off_windowby @cka-y in feat: flex -overlapping_zone_and_pickup_drop_off_window#1934duplicate_geography_id,duplicate_geo_json_keyandforbidden_geography_idnotices by @cka-y in feat:duplicate_geography_id,duplicate_geo_json_keyandforbidden_geography_idnotices #1953fare_leg_join_rules.txtschema and validation by @cka-y in feat: addedfare_leg_join_rules.txtschema and validation #1956missing_recommended_columnand related annotation + changedmissing_timepoint_valuenotice description by @cka-y in feat: removedmissing_recommended_columnand related annotation + changedmissing_timepoint_valuenotice description #1963missing_pickup_booking_rule_idnotice by @cka-y in feat: addedmissing_pickup_booking_rule_idnotice #1966missing_prior_day_booking_field_valueby @cka-y in feat: separate outmissing_prior_day_booking_field_value#1996Full Changelog: v6.0.0...v7.0.0
This discussion was created from the release v7.0.0.
Beta Was this translation helpful? Give feedback.
All reactions