v8.0.0 #2167
emmambd
announced in
Announcements
v8.0.0
#2167
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.
-
Breaking Change for JAR Users
Version 8.0 introduced an unintended breaking change for third-party applications that use the gtfs-validator as a JAR library. This can lead to a compiling error against v8.0.0.
Who is affected: Projects integrating the gtfs-validator JAR directly.
The minor release of v8.0.1 restores backward compatibility.
Highlights
Rules for New GTFS Features: Three new features have been added to GTFS in the past year. We’ve added validation rules for each, as well as a feature in the summary report so they are easy to track:
💳 Contactless EMV Support allows data producers to indicate whether riders can access a transit service using contactless cards or devices (for example, in tap-to-pay systems).
🚘 Cars Allowed indicates if vehicles serving specific trips (such as car ferries or trains capable of transporting cars) are able to accommodate cars or not on the vehicle.
🚏Stop Access indicates if the stop or platform can be directly accessed from the street network or not. This feature allows trip planners to generate more accurate directions to reach the stop or platform.
📅 Better Validation for Service Windows: Seven notices have been created to more thoroughly test service windows. Check to see if a service is out of date or in the future, if there are big gaps in service, or if there are large discrepancies between the feed info and calendar files.
Notice changes
🔴
fare_transfer_rule_missing_transfer_countchanged to ->fare_transfer_rule_without_transfer_countto align with naming conventions🔴
unexpected_enum_value: Triggers whencars_allowedis a value other than 0, empty, 1 or 2.cemv_supportis a value other than 0, empty, 1 or 2.stop_accessis a value other than 0, empty or 1.New notices
🔴
missing_required_agency_id:agency_idis required when there are multiple agencies.🔴
stop_access_specified_for_incorrect_location: A location that is not a stop hasstop_accessspecified.stops.stop_accessis forbidden for locations that are stations, entrances, generic nodes or boarding areas. It can only be specific when a stop is associated with a parent station.🔴
stop_access_specified_for_stop_with_no_parent_station: A stop without a value for parent station hasstop_accessspecified. stops.stop_access is forbidden for stops that are not associated with a parent station.🔴
pathway_to_stop_with_access_outside_of_station_pathways: A pathway has an endpoint that is a stop with stop_access=1, which should be accessible outside of the station’s pathways.🟡
inconsistent_route_type_for_block_id: A block should have the same route mode.🟡
inconsistent_route_type_for_in_seat_transfer: An in-seat transfer should occur in the same route mode.🟡
service_has_no_active_day_of_the_week: A service is not valid for any day of the week.⬜
big_gap_in_service: A service has a gap of more than 13 days between active service dates.⬜
feed_valid_beyond_total_service_window: The feed is valid 14 days beyond its total service window.⬜
future_calendar: All services in the feed start in the future; no service covers today's date.⬜
future_feed: The minimumstart_dateinfeed_info.txtis greater than today's date, indicating the feed covers the future only.⬜
service_extends_far_in_the_future: A service end date is more than 2 years in the future.⬜
service_window_extends_past_feed_period: A service window is not covered by the feed's validity period.⬜
trip_headsign_matches_intermediate_stop: Trip headsign matches the name of an intermediate stop, not the last stop.⬜
trip_with_shape_dist_traveled_but_no_shape_distances: A trip hasshape_dist_traveledvalues instop_times.txtbut the shape referenced by the trip'sshape_iddoes not haveshape_dist_traveledvalues on all of its points inshapes.txt.⬜
unsorted_stop_times: Stop times are not sorted bytrip_idandstop_sequence. stop_times.txtentries for a given trip are not sorted bystop_sequence, or are not contiguous in the file.Impacts on existing data
You can see how the new release affects real world data in the Mobility Database here.
Other notable improvements
What's Changed
big_gap_in_serviceINFO notice by @cka-y in feat:big_gap_in_serviceINFO notice #2116ServiceIntervalCacheto compute the service window by @cka-y in fix: usingServiceIntervalCacheto compute the service window #2130future_calendarnotice by @cka-y in feat:future_calendarnotice #2133New Contributors
Full Changelog: v7.1.0...v8.0.0
Beta Was this translation helpful? Give feedback.
All reactions