GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T02:38:36Z,
for the dataset file:///shared/offre-de-transport-du-reseau.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
French
Feed Start Date:
2025-05-23
Feed End Date:
2026-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. transfers.txt
  10. trips.txt

Counts

  • Agencies: 1
  • Blocks: 18
  • Routes: 4
  • Shapes: 7
  • Stops: 102
  • Trips: 104

Specification Compliance report

3 notices reported (0 errors, 3 warnings, 0 infos)

Notice Code Severity Total
stop_too_far_from_shape WARNING 2

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
96 "105678-8879$513$2" "105678-6789" 842 "105678-HCC.SU" "ZI DU Malambas - Sud" [49.20830200000001,6.1856] 171.64754723866625
82 "105678-8879$258$7" "105678-6719" 690 "105678-TRM.ST" "Stellantis" [49.240601,6.209999999999999] 126.80279954445187
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
32 "105678-8879$1027$4" "105678-6941" 292 "105678-NOV.EB1" "Ecoparc - Bellevue" [49.178501007268096,6.147380000001627] 291 "105678-NOV.PG1" "Pres Godarts" [49.18439519209025,6.147363377745817]