-
Spec violations should be errors, but the below best practice is an error and not in the spec. Options:
1. Add this requirement to the GTFS RT Spec definition and remove from GTFS Best Practices.…
-
The feed could be decoded as [Protocol Buffers TextFormat](https://developers.google.com/protocol-buffers/docs/reference/java/com/google/protobuf/TextFormat) or JSON to allow debugging specific values…
-
### Relevant [Best Practice](https://gtfs.org/realtime/best-practices/) text:
> Feeds should use HTTPS instead of HTTP (without encryption) to ensure feed integrity.
-
For the uninitiated: how does Navitia convert GTFS to the format your project can ingest? Navitia seems error-prone and fickle (arbitrarily drops region support).
Would it be reasonable to do the G…
-
-
### Describe the problem
During the release process, this [document ](https://github.com/MobilityData/gtfs-validator/blob/master/docs/RELEASE.md#4-remove-all-sha-docker-images-added-since-last-rele…
-
### Describe the bug
At busmaps.com we are experiencing an issue with the Mobility Data Validator v6 when validating GTFS feeds that were previously validated successfully in version 5.0.1. Specifica…
-
### Describe the bug
Bug or feature request?
The web validator html report gives the filename of the dataset. e.g.:
 but it also shutdowns with any realtime data feed I te…