eveole — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-09T13:16:55Z,
for the dataset file:///shared/eveole_308fab79.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included


Feed Info


Publisher Name:
EVEOLE
Publisher URL:
http://www.eveole.com
Feed Email:
N/A
Feed Language:
French
Feed Start Date:
2026-05-04
Feed End Date:
2026-08-30

Files included


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

Counts


  • Agencies: 2
  • Blocks: 1369
  • Routes: 41
  • Shapes: 295
  • Stops: 1464
  • Trips: 6646

Specification Compliance report

39 notices reported (30 errors, 8 warnings, 1 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 24

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
5255 "749184" "9" 5163 "749240" "9" "A-20" "20260504"
5255 "749184" "9" 5161 "749170" "9" "A-20" "20260504"
5161 "749170" "9" 5252 "749091" "9" "A-20" "20260504"
5252 "749091" "9" 5162 "749173" "9" "A-20" "20260504"
5162 "749173" "9" 5257 "749199" "9" "A-20" "20260504"
5257 "749199" "9" 5164 "749242" "9" "A-20" "20260504"
489 "755314" "2" 344 "755318" "2" "3-05" "20260504"
344 "755318" "2" 493 "755351" "2" "3-05" "20260504"
493 "755351" "2" 343 "755307" "2" "3-05" "20260504"
343 "755307" "2" 490 "755317" "2" "3-05" "20260504"
490 "755317" "2" 4850 "755322" "13" "3-05" "20260504"
490 "755317" "2" 436 "755282" "3" "3-05" "20260506"
4850 "755322" "13" 488 "755279" "2" "3-05" "20260504"
436 "755282" "3" 488 "755279" "2" "3-05" "20260506"
488 "755279" "2" 4849 "750464" "13" "3-05" "20260504"
488 "755279" "2" 152 "755303" "3" "3-05" "20260506"
4849 "750464" "13" 492 "755343" "2" "3-05" "20260504"
152 "755303" "3" 492 "755343" "2" "3-05" "20260506"
492 "755343" "2" 150 "755306" "2" "3-05" "20260504"
150 "755306" "2" 491 "755337" "2" "3-05" "20260504"
491 "755337" "2" 151 "755347" "2" "3-05" "20260504"
442 "755286" "1" 435 "755281" "1" "3-02" "20260509"
339 "755340" "2" 4853 "755320" "9" "3-01" "20260504"
4853 "755320" "9" 335 "755294" "2" "3-01" "20260504"
missing_required_field ERROR 1

missing_required_field

A required field is missing.

The given field has no value in some input row, even though values are required.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"fare_attributes.txt" 2 "agency_id"
stop_time_with_arrival_before_previous_departure_time ERROR 5

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. prevCsvRowNumber (?) The row of the previous stop time. tripId (?) The trip_id associated to the faulty record. arrivalTime (?) Arrival time at the faulty record. departureTime (?) Departure time at the previous stop time.
36644 36643 "755191" "05:54:51" "06:04:00"
26485 26484 "755357" "15:42:59" "15:48:00"
26413 26412 "755355" "13:54:59" "14:00:00"
26629 26628 "755361" "19:17:59" "19:23:00"
26557 26556 "755359" "17:30:59" "17:36:00"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 1

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) The name of the missing field.
"feed_info.txt" 2 "feed_version"
mixed_case_recommended_field WARNING 4

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"agency.txt" "agency_name" "TAD EVEOLE" 3
"stops.txt" "stop_name" "08-mai" 858
"stops.txt" "stop_name" "08-mai" 859
"stops.txt" "stop_name" "08-mai" 899
route_color_contrast WARNING 1

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"80" 19 "#9FBDFF" "#FFFFFF"
stop_too_far_from_shape WARNING 1

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.
5665 "37786" "765923" 100462 "21970" "Hôtel de ville" [50.332106,3.233497] 175.78850591849752
unknown_file INFO 1

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"trips.txt.bak"