isabelle-dr
isabelle-dr
After the [PR # 286](https://github.com/google/transit/pull/286) was merged in May 2022. ### Additional files: - [fare_products.txt](https://gtfs.org/schedule/reference/#fare_productstxt) - [fare_leg_rules.txt](https://gtfs.org/schedule/reference/#fare_leg_rulestxt) - [fare_transfer_rules.txt](https://gtfs.org/schedule/reference/#fare_transfer_rulestxt) - [areas.txt](https://gtfs.org/schedule/reference/#areastxt) - [stop_areas.txt](https://gtfs.org/schedule/reference/#stop_areastxt) ### Changes to existing files - [routes.txt](https://gtfs.org/schedule/reference/#routestxt):...
In RULES.md, the link [stop_times.txt best practices](https://github.com/MobilityData/GTFS_Schedule_Best-Practices/blob/master/en/stop_times.md) provided in the missing_timepoint_column notice is broken. Additionally, the Best Practice has no mention of timepoint, think link should refer to the specification...
closes #1225 This PR updates RULES.md for `decreasing_or_equal_stop_time_distance`. more specifically: - updates the reference file to stop_times.txt - fixes typo in `stop_pt_sequence` - (to do) modifies the definition to make...
As discussed [in this comment](https://github.com/MobilityData/gtfs-validator/pull/848#issuecomment-988812929): Modify the logic of the acceptance tests so a PR is flagged if there is at least one additional error in **one** dataset from the...
This is a follow-up issue after a temporary fix has been made in #1186 to allow the validator app to work on Mac. When we finish the process of getting...
### Context & Issue As we are getting more interest from contributors to this validator, improving some of our open source practices becomes a priority. Currently, interested contributors don't have...
Update [RELEASE.md](https://github.com/MobilityData/gtfs-validator/blob/master/docs/RELEASE.md) to add the wiki update. This wiki update is what is going to trigger the notification that appears in the application UI. Additional context in [#1176 ](https://github.com/MobilityData/gtfs-validator/pull/1176#discussion_r888364032)
The document [Notice migration from V2.0.0 to V3.0.0](https://github.com/MobilityData/gtfs-validator/blob/master/docs/MIGRATION_V2_V3.md) is used when users migrate from one version to another. This document should be updated with: - replace the CamelCase notice names...
To improve the visibility of this validator. Feedback, ideas, thoughts are welcome
**What problem in GTFS datasets does this new rule address? Please describe.** The spec in `stops.stop_lat` and `stops.stop_lon` mentions ([source](https://github.com/google/transit/blob/master/gtfs/spec/en/reference.md#stopstxt)): > Conditionally Required: > - Required for locations which are...