-
### Describe the bug
The is a wrong trip.
For more please see the screenshots.
### Steps/Code to Reproduce
Go to Ingolstadt on the Map.
Date: 11.06.2023 (Sunday)
Time: 09:35:00
Fore more Info…
-
### Describe the problem
The current validator seems unable to catch the following unreasonable data：
In `stop_times.txt`, multiple stops in a single trip have the same `departure_time` and `arriv…
-
**Issue by [barbeau](https://github.com/barbeau)**
_Oct 25, 2017_
_Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/299_
----
**Summary:**
In the upper-ri…
-
Hi, hello!
To keep this short: The current CLI implementation takes as an input parameter an URL (`-u`, `--url`) and set the location of its generated report with parameter `-s`, `--save-report`. T…
-
**Issue by [barbeau](https://github.com/barbeau)**
_Sep 11, 2018_
_Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/335_
----
**Summary:**
New rule - If a f…
-
**Summary:**
If a TripUpdate contains only stop_times_updates for arrival/departure times in the past, this is a warning.
I'd like for this to be an error, but currently the GTFS-rt spec (https…
-
**Summary:**
For trips defined in frequencies.txt with exact_times=0, TripUpdates feeds should not have stop_time_updates with a schedule_relationship of `SCHEDULED` or `SKIPPPED` - these are only…
-
_From [jav...@gmail.com](https://code.google.com/u/103896513105589097156/) on April 10, 2009 11:17:26_
What steps will reproduce the problem? 1. Run GTFS in feed validator
2. Validation successful, h…
-
**Issue by [barbeau](https://github.com/barbeau)**
_Tuesday Jan 12, 2016 at 21:45 GMT_
_Originally opened as https://github.com/CUTR-at-USF/gtfs-realtime-validator/issues/16_
----
In the "Stop Time…
-
It would be convenient to have possibility to bundle-fill the area.
Motivation: in Athens there are `airport` area and `urban` area. The `airport` area can be simply modeled by adding stops to the …