courchevel — Enhanced Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-08T01:05:51Z,
for the dataset file:///shared/courchevel_b71cafcb.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 Language:
French
Feed Start Date:
2026-07-01
Feed End Date:
2026-08-21

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. trips.txt

Counts


  • Agencies: 1
  • Blocks: 8
  • Routes: 6
  • Shapes: 20
  • Stops: 63
  • Trips: 138

Specification Compliance report

86 notices reported (2 errors, 82 warnings, 2 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 2

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.
19 18 "104958-26" "00:00:00" "23:59:00"
514 513 "104958-1314" "00:00:00" "23:59:00"
fast_travel_between_far_stops WARNING 2

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
32 "104958-1314" "104958-A" 615.6152871778208 10.260254786297013 499 2 "104958-3" "Plan DU Vah" "23:24:00" 514 17 "104958-15" "Saint BON LE Bas" "00:00:00"
2 "104958-26" "104958-A" 615.6152871778208 10.260254786297013 4 2 "104958-3" "Plan DU Vah" "23:24:00" 19 17 "104958-15" "Saint BON LE Bas" "00:00:00"
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260808" "20260821" "20260907"
mixed_case_recommended_field WARNING 79

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.

Only the first 50 of 79 affected records are displayed below.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "lac de la rosiere" 22
"trips.txt" "trip_headsign" "vignotan" 2
"trips.txt" "trip_headsign" "courchevel gare routiere" 3
"trips.txt" "trip_headsign" "saint bon le bas" 4
"trips.txt" "trip_headsign" "courchevel gare routiere" 5
"trips.txt" "trip_headsign" "saint bon le bas" 6
"trips.txt" "trip_headsign" "vignotan" 7
"trips.txt" "trip_headsign" "courchevel gare routiere" 8
"trips.txt" "trip_headsign" "saint bon le bas" 9
"trips.txt" "trip_headsign" "courchevel gare routiere" 10
"trips.txt" "trip_headsign" "saint bon le bas" 11
"trips.txt" "trip_headsign" "courchevel gare routiere" 12
"trips.txt" "trip_headsign" "saint bon le bas" 13
"trips.txt" "trip_headsign" "courchevel gare routiere" 14
"trips.txt" "trip_headsign" "saint bon le bas" 15
"trips.txt" "trip_headsign" "courchevel gare routiere" 16
"trips.txt" "trip_headsign" "courchevel gare routiere" 17
"trips.txt" "trip_headsign" "saint bon le bas" 18
"trips.txt" "trip_headsign" "courchevel gare routiere" 19
"trips.txt" "trip_headsign" "saint bon le bas" 20
"trips.txt" "trip_headsign" "courchevel gare routiere" 21
"trips.txt" "trip_headsign" "saint bon le bas" 22
"trips.txt" "trip_headsign" "courchevel gare routiere" 23
"trips.txt" "trip_headsign" "saint bon le bas" 24
"trips.txt" "trip_headsign" "courchevel gare routiere" 25
"trips.txt" "trip_headsign" "saint bon le bas" 26
"trips.txt" "trip_headsign" "vignotan" 32
"trips.txt" "trip_headsign" "courchevel gare routiere" 33
"trips.txt" "trip_headsign" "saint bon le bas" 34
"trips.txt" "trip_headsign" "courchevel gare routiere" 35
"trips.txt" "trip_headsign" "saint bon le bas" 36
"trips.txt" "trip_headsign" "courchevel gare routiere" 37
"trips.txt" "trip_headsign" "saint bon le bas" 38
"trips.txt" "trip_headsign" "courchevel gare routiere" 39
"trips.txt" "trip_headsign" "saint bon le bas" 40
"trips.txt" "trip_headsign" "courchevel gare routiere" 41
"trips.txt" "trip_headsign" "saint bon le bas" 42
"trips.txt" "trip_headsign" "courchevel gare routiere" 43
"trips.txt" "trip_headsign" "saint bon le bas" 44
"trips.txt" "trip_headsign" "courchevel gare routiere" 45
"trips.txt" "trip_headsign" "courchevel gare routiere" 46
"trips.txt" "trip_headsign" "courchevel gare routiere" 48
"trips.txt" "trip_headsign" "courchevel gare routiere" 50
"trips.txt" "trip_headsign" "courchevel gare routiere" 67
"trips.txt" "trip_headsign" "courchevel gare routiere" 70
"trips.txt" "trip_headsign" "auditorium" 71
"trips.txt" "trip_headsign" "auditorium" 72
"trips.txt" "trip_headsign" "auditorium" 73
"trips.txt" "trip_headsign" "auditorium" 74
"trips.txt" "trip_headsign" "auditorium" 75
big_gap_in_service INFO 1

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"104958-1_5_6_7_8_16_17" "2026-07-24" "2026-08-17" 23
trip_headsign_matches_intermediate_stop INFO 1

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
58 "104958-12506" "La Perriere (Giglary)" "104958-73" 20 "104958-89"