Problem

During an interview with Via, they shared that when a dataset contains the decreasing_or_equal_stop_time_distance notice, most of the time it comes from having the wrong stop selected in the software used to generate the GTFS dataset.
Associating the wrong stop can lead to multiple decreasing_or_equal_stop_time_distance notices being triggered.
The user then needs to manually find the stop_id in stop_times.txt to troubleshoot.
Having the stop_id available in the notice details would help the users understand that all the notices are generated by one particular stop.

Solution proposed

Add stop_id after trip_id in the notice details of decreasing_or_equal_stop_time_distance. The new notice details would contain:

• tripId
• stopId
• csvRowNumber
• shapeDistTraveled
• stopSequence
• prevCsvRowNumber
• prevShapeDistTraveled
• prevStopSequence