-
**Issue by [lionel-nj](https://github.com/lionel-nj)**
_Jan 19, 2022_
_Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/405_
----
**Summary:**
Test sets f…
-
**Is your feature request related to a problem? Please describe.**
A trip should not have many consecutive stops with the same times. This is a GTFS rule implemented in Google Python validator as Val…
-
**Is your feature request related to a problem? Please describe.**
A trip should be related to an existing shape. The related shape must have a non null length. This is a GTFS rule implemented in Goo…
-
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.…
-
**Is your feature request related to a problem? Please describe.**
Minimum transfer time should be present and valid. This is a GTFS rule implemented in Google Python validator and featured in Google…
-
## **Feature request**
GTFS feeds which contain `route_type` values referenced from [Extended GTFS Route Types](https://developers.google.com/transit/gtfs/reference/extended-route-types) , e.g. `700`…
-
## Problem
Referenced from #375 and #376:
MobilityData’s heard a number of pains from the community about the GTFS best practices and the spec’s SHOULD statements living in two different places…
-
**Summary:**
From the spec (https://developers.google.com/transit/gtfs-realtime/reference/TripDescriptor):
>If the frequency-based trip corresponds to exact_times=0, then its start_time may be …
-
### Describe the bug
When processing a large [GTFS file](https://download.gtfs.de/germany/nv_free/latest.zip), the desktop validator doesn't show any errors to the user.
When checking the `system_…
-
**Summary:**
We currently have the W004 threshold set at 26 meters per second (about 60 miles per hour):
https://github.com/CUTR-at-USF/gtfs-realtime-validator/blob/master/RULES.md#W004
We sho…