rezobus — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-28T14:58:34Z,
for the dataset file:///shared/rezobus_9e7744c3.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included


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

Counts


  • Agencies: 1
  • Blocks: 49
  • Routes: 23
  • Shapes: 69
  • Stops: 185
  • Trips: 771

Specification Compliance report

7793 notices reported (0 errors, 6956 warnings, 837 infos)

Notice Code Severity Total
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
missing_timepoint_value WARNING 6766

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "2-1662320641-LIL01-_____S_" 0
3 "2-1662320641-LIL01-_____S_" 1
4 "2-1662320641-LIL01-_____S_" 2
5 "2-1662320641-LIL01-_____S_" 3
6 "2-1662320641-LIL01-_____S_" 4
7 "2-1662320641-LIL01-_____S_" 5
8 "2-1662320641-LIL01-_____S_" 6
9 "2-1662320641-LIL01-_____S_" 7
10 "2-1662320641-LIL01-_____S_" 8
11 "2-1662320641-LIL01-_____S_" 9
12 "2-1662320641-LIL01-_____S_" 10
13 "2-1662320641-LIL01-_____S_" 11
14 "2-1662320641-LIL01-_____S_" 12
15 "2-1662320641-PJ01-LMCJ___" 0
16 "2-1662320641-PJ01-LMCJ___" 1
17 "2-1662320641-PJ01-LMCJ___" 2
18 "2-1662320641-PJ01-LMCJ___" 3
19 "2-1662320641-PJ01-LMCJ___" 4
20 "2-1662320641-PJ01-LMCJ___" 5
21 "2-1662320641-PJ01-LMCJ___" 6
22 "2-1662320641-PJ01-LMCJ___" 7
23 "2-1662320641-PJ01-LMCJ___" 8
24 "2-1662320641-PJ01-LMCJ___" 9
25 "2-1662320641-PJ01-LMCJ___" 10
26 "2-1662320641-PJ01-LMCJ___" 11
27 "2-1662320641-PJ01-LMCJ___" 12
28 "2-1662320642-LIL01-_____S_" 0
29 "2-1662320642-LIL01-_____S_" 1
30 "2-1662320642-LIL01-_____S_" 2
31 "2-1662320642-LIL01-_____S_" 3
32 "2-1662320642-LIL01-_____S_" 4
33 "2-1662320642-LIL01-_____S_" 5
34 "2-1662320642-LIL01-_____S_" 6
35 "2-1662320642-LIL01-_____S_" 7
36 "2-1662320642-LIL01-_____S_" 8
37 "2-1662320642-LIL01-_____S_" 9
38 "2-1662320642-LIL01-_____S_" 10
39 "2-1662320642-LIL01-_____S_" 11
40 "2-1662320642-LIL01-_____S_" 12
41 "2-1662320642-PJ01-LMCJ___" 0
42 "2-1662320642-PJ01-LMCJ___" 1
43 "2-1662320642-PJ01-LMCJ___" 2
44 "2-1662320642-PJ01-LMCJ___" 3
45 "2-1662320642-PJ01-LMCJ___" 4
46 "2-1662320642-PJ01-LMCJ___" 5
47 "2-1662320642-PJ01-LMCJ___" 6
48 "2-1662320642-PJ01-LMCJ___" 7
49 "2-1662320642-PJ01-LMCJ___" 8
50 "2-1662320642-PJ01-LMCJ___" 9
51 "2-1662320642-PJ01-LMCJ___" 10
mixed_case_recommended_field WARNING 188

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 188 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" "LILLEBONNE MJC" 36
"stops.txt" "stop_name" "ND GRAVENCHON EHPAD" 78
"stops.txt" "stop_name" "BOLBEC CCI" 176
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 2
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 3
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 4
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 5
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 6
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 7
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 8
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 9
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 28
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 29
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 30
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 31
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 32
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 33
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 34
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 35
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 36
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 37
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 38
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 39
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 40
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 41
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 42
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 43
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 44
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 45
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 64
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 65
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 66
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 67
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 68
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 69
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 70
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 71
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 72
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 73
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 74
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 75
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 76
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 77
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 78
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 79
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 80
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 81
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 82
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 83
"trips.txt" "trip_headsign" "PORT-JEROME-SUR-SEINE" 84
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260828" "20260901" "20270827"
big_gap_in_service INFO 64

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.

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

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.
"1" "2026-10-17" "2026-11-07" 20
"1" "2026-12-19" "2027-01-09" 20
"1" "2027-02-20" "2027-03-13" 20
"1" "2027-04-17" "2027-05-15" 27
"19" "2026-10-31" "2026-12-26" 55
"19" "2027-01-02" "2027-02-27" 55
"19" "2027-03-06" "2027-04-24" 48
"2" "2026-10-16" "2026-11-06" 20
"2" "2026-12-18" "2027-01-08" 20
"2" "2027-02-19" "2027-03-12" 20
"2" "2027-04-16" "2027-05-14" 27
"20" "2026-10-30" "2027-02-26" 118
"20" "2027-03-05" "2027-04-23" 48
"21" "2026-10-28" "2026-12-23" 55
"21" "2026-12-30" "2027-02-24" 55
"21" "2027-03-03" "2027-04-21" 48
"22" "2026-10-29" "2026-12-22" 53
"22" "2026-12-31" "2027-02-23" 53
"22" "2027-03-04" "2027-04-20" 46
"23" "2026-10-26" "2026-12-21" 55
"23" "2026-12-28" "2027-02-22" 55
"23" "2027-03-01" "2027-04-19" 48
"24" "2026-10-30" "2026-12-21" 51
"24" "2026-12-28" "2027-02-22" 55
"24" "2027-03-05" "2027-04-19" 44
"25" "2026-10-30" "2026-12-21" 51
"25" "2026-12-30" "2027-02-22" 53
"25" "2027-03-05" "2027-04-19" 44
"27" "2026-10-30" "2026-12-21" 51
"27" "2026-12-31" "2027-02-22" 52
"27" "2027-03-05" "2027-04-19" 44
"28" "2026-10-29" "2026-12-21" 52
"28" "2026-12-31" "2027-02-22" 52
"28" "2027-03-04" "2027-04-19" 45
"29" "2026-10-30" "2026-12-21" 51
"29" "2026-12-31" "2027-02-22" 52
"29" "2027-03-05" "2027-04-19" 44
"3" "2026-10-14" "2026-11-04" 20
"3" "2026-12-16" "2027-01-06" 20
"3" "2027-02-17" "2027-03-10" 20
"3" "2027-04-14" "2027-05-05" 20
"30" "2026-10-31" "2026-12-21" 50
"30" "2027-01-02" "2027-02-22" 50
"30" "2027-03-06" "2027-04-19" 43
"4" "2026-10-12" "2026-11-02" 20
"4" "2026-12-14" "2027-01-04" 20
"4" "2027-02-15" "2027-03-08" 20
"4" "2027-04-12" "2027-05-03" 20
"6" "2026-10-16" "2026-11-02" 16
"6" "2026-12-18" "2027-01-04" 16
future_calendar INFO 1

future_calendar

All services in the feed start in the future; no service covers today's date.

You can see more about this notice here.

minServiceStartDate (?) The earliest service start date across all services in the feed. currentDate (?) Today's date at validation time.
"2026-09-01" "2026-08-28"
trip_with_shape_dist_traveled_but_no_shape_distances INFO 771

trip_with_shape_dist_traveled_but_no_shape_distances

A trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt.

When stop times define distance values but the shape does not carry matching distances on every point, consumers cannot use those distances to align stops to the shape geometry reliably. This inconsistency may cause incorrect routing or display behaviour.

Note: Only the first stop time carrying a shape_dist_traveled value is referenced in the notice; this is a representative row rather than an exhaustive list.

You can see more about this notice here.

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

tripCsvRowNumber (?) The row number of the faulty record in trips.txt. tripId (?) The trip_id of the faulty trip. shapeId (?) The shape_id referenced by the trip. stopTimeCsvRowNumber (?) The row number of the first stop_times.txt record for this trip that contains a shape_dist_traveled value. Provided as a representative location; other stop times for the same trip may also carry distance values.
439 "3-51707922" "0321" 4059
438 "3-51707921" "0321" 4055
441 "3-51707924" "0321" 4067
440 "3-51707923" "0321" 4063
443 "3-51707926" "0321" 4075
442 "3-51707925" "0321" 4071
461 "3-54984730" "0371" 4173
445 "3-51707928" "0321" 4083
444 "3-51707927" "0321" 4079
120 "2-3674406913" "5203" 1206
446 "3-51707929" "0321" 4087
143 "2-4278321167" "7202" 1395
459 "3-54984728" "0371" 4161
458 "3-54984727" "0371" 4155
437 "3-51707920" "0321" 4051
460 "3-54984729" "0371" 4167
455 "3-54984724" "0371" 4137
454 "3-54984723" "0371" 4131
457 "3-54984726" "0371" 4149
456 "3-54984725" "0371" 4143
451 "3-54984720" "0371" 4113
434 "3-51707917" "0321" 4039
453 "3-54984722" "0371" 4125
452 "3-54984721" "0371" 4119
436 "3-51707919" "0321" 4047
435 "3-51707918" "0321" 4043
2 "2-1662320641-LIL01-_____S_" "2121" 2
40 "2-2031419395-LIL01-__C____" "2321" 438
144 "2-4278321170" "7402" 1402
448 "3-54984717" "0371" 4095
450 "3-54984719" "0371" 4107
621 "4-2333409290" "2821" 5629
449 "3-54984718" "0371" 4101
416 "3-4278583341" "7206" 3832
620 "4-2333409289" "2821" 5618
188 "2-54984706-BOL1-LMCJV__" "0371" 1781
619 "4-2333409288" "2821" 5607
650 "4-34996241" "0222" 5890
649 "4-34996240" "0222" 5882
654 "4-34996245" "0222" 5922
653 "4-34996244" "0222" 5914
652 "4-34996243" "0222" 5906
651 "4-34996242" "0222" 5898
43 "2-2031419396-PJ02-LM_JV__" "2321" 462
50 "2-21430278-BOL1-LMCJV__" "0171" 510
655 "4-34996246" "0222" 5930
18 "2-18153482-BOL1-LMCJV__" "0121" 186
142 "2-4278321154" "7202" 1388
121 "2-38207490-BOL1-LMCJV__" "0271" 1213
482 "3-68550661" "0422" 4328
unknown_column INFO 1

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"trips.txt" "ext_pis_code" 4