GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-27T01:50:49Z,
for the dataset file:///shared/cacl-semop_afcbb870.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
CACL-SEMOP
Feed Email:
N/A
Feed Language:
French
Feed Start Date:
2025-12-29
Feed End Date:
2026-12-31

Files included


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

Counts


  • Agencies: 1
  • Blocks: 167
  • Routes: 8
  • Shapes: 16
  • Stops: 536
  • Trips: 2799

Specification Compliance report

5635 notices reported (0 errors, 2802 warnings, 2833 infos)

Notice Code Severity Total
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 1

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" "CACL-SEMOP" 2
non_ascii_or_non_printable_char WARNING 2799

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

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

filename (?) Name of the faulty file. csvRowNumber (?) Row number of the faulty record. columnName (?) Name of the column where the error occurred. fieldValue (?) Faulty value.
"trips.txt" 2 "block_id" "N°3-1PV1"
"trips.txt" 3 "block_id" "N°3-1PV1"
"trips.txt" 4 "block_id" "N°3-1PV1"
"trips.txt" 5 "block_id" "N°3-1PV1"
"trips.txt" 6 "block_id" "N°3-1PV1"
"trips.txt" 7 "block_id" "N°3-1PV1"
"trips.txt" 8 "block_id" "N°3-1PV1"
"trips.txt" 9 "block_id" "N°3-1PV1"
"trips.txt" 10 "block_id" "N°3-1PV1"
"trips.txt" 11 "block_id" "N°3-1PV1"
"trips.txt" 12 "block_id" "N°3-1PV1"
"trips.txt" 13 "block_id" "N°3-1PV1"
"trips.txt" 14 "block_id" "N°3-1PV1"
"trips.txt" 15 "block_id" "N°3-1PV1"
"trips.txt" 16 "block_id" "N°3-1PV1"
"trips.txt" 17 "block_id" "N°3-1PV1"
"trips.txt" 18 "block_id" "N°3-1PV1"
"trips.txt" 19 "block_id" "N°3-1PV1"
"trips.txt" 20 "block_id" "N°3-1PV1"
"trips.txt" 21 "block_id" "N°3-2PV1"
"trips.txt" 22 "block_id" "N°3-2PV1"
"trips.txt" 23 "block_id" "N°3-2PV1"
"trips.txt" 24 "block_id" "N°3-2PV1"
"trips.txt" 25 "block_id" "N°3-2PV1"
"trips.txt" 26 "block_id" "N°3-2PV1"
"trips.txt" 27 "block_id" "N°3-2PV1"
"trips.txt" 28 "block_id" "N°3-2PV1"
"trips.txt" 29 "block_id" "N°3-2PV1"
"trips.txt" 30 "block_id" "N°3-2PV1"
"trips.txt" 31 "block_id" "N°3-2PV1"
"trips.txt" 32 "block_id" "N°3-2PV1"
"trips.txt" 33 "block_id" "N°3-2PV1"
"trips.txt" 34 "block_id" "N°3-2PV1"
"trips.txt" 35 "block_id" "N°3-2PV1"
"trips.txt" 36 "block_id" "N°3-2PV1"
"trips.txt" 37 "block_id" "N°3-2PV1"
"trips.txt" 38 "block_id" "N°3-2PV1"
"trips.txt" 39 "block_id" "N°3-3PV1"
"trips.txt" 40 "block_id" "N°3-3PV1"
"trips.txt" 41 "block_id" "N°3-3PV1"
"trips.txt" 42 "block_id" "N°3-3PV1"
"trips.txt" 43 "block_id" "N°3-3PV1"
"trips.txt" 44 "block_id" "N°3-3PV1"
"trips.txt" 45 "block_id" "N°3-3PV1"
"trips.txt" 46 "block_id" "N°3-3PV1"
"trips.txt" 47 "block_id" "N°3-3PV1"
"trips.txt" 48 "block_id" "N°3-3PV1"
"trips.txt" 49 "block_id" "N°3-3PV1"
"trips.txt" 50 "block_id" "N°3-3PV1"
"trips.txt" 51 "block_id" "N°3-3PV1"
big_gap_in_service INFO 33

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.
"1" "2026-01-02" "2026-02-09" 37
"1" "2026-02-20" "2026-04-02" 40
"1" "2026-04-14" "2026-10-19" 187
"1" "2026-10-30" "2026-12-21" 51
"2" "2026-01-02" "2026-02-09" 37
"2" "2026-02-20" "2026-04-02" 40
"2" "2026-04-15" "2026-10-19" 186
"2" "2026-10-30" "2026-12-21" 51
"3" "2025-12-31" "2026-02-11" 41
"3" "2026-02-18" "2026-04-08" 48
"3" "2026-04-15" "2026-10-21" 188
"3" "2026-10-28" "2026-12-23" 55
"7" "2026-02-05" "2026-02-23" 17
"7" "2026-03-31" "2026-04-16" 15
"7" "2026-07-02" "2026-08-31" 59
"7" "2026-10-15" "2026-11-02" 17
"8" "2026-02-04" "2026-02-25" 20
"8" "2026-04-01" "2026-04-22" 20
"8" "2026-07-01" "2026-09-02" 62
"8" "2026-10-14" "2026-11-04" 20
"9" "2026-02-07" "2026-02-28" 20
"9" "2026-03-28" "2026-04-18" 20
"9" "2026-07-04" "2026-09-05" 62
"9" "2026-10-17" "2026-11-07" 20
"10" "2026-01-03" "2026-02-14" 41
"10" "2026-02-21" "2026-04-04" 41
"10" "2026-04-11" "2026-10-24" 195
"10" "2026-10-31" "2026-12-26" 55
"12" "2026-02-06" "2026-02-27" 20
"12" "2026-03-27" "2026-04-17" 20
"12" "2026-04-24" "2026-05-15" 20
"12" "2026-07-03" "2026-09-04" 62
"12" "2026-10-16" "2026-11-06" 20
trip_with_shape_dist_traveled_but_no_shape_distances INFO 2799

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 2799 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.
559 "70710" "376" 17612
561 "70712" "376" 17678
560 "70711" "377" 17644
1929 "70707" "377" 59828
1928 "70706" "376" 59796
558 "70709" "377" 17578
557 "70708" "376" 17546
1925 "70703" "377" 59696
1924 "70702" "376" 59664
1927 "70705" "377" 59762
1926 "70704" "376" 59730
570 "70721" "377" 17974
569 "70720" "376" 17942
572 "70723" "377" 18040
571 "70722" "376" 18008
567 "70718" "376" 17876
566 "70717" "377" 17842
568 "70719" "377" 17908
563 "70714" "376" 17744
562 "70713" "377" 17710
565 "70716" "376" 17810
564 "70715" "377" 17776
540 "70732" "377" 16984
539 "70731" "376" 16952
542 "70734" "377" 17050
541 "70733" "376" 17018
538 "70730" "377" 16918
537 "70729" "377" 16884
536 "70728" "376" 16852
574 "70725" "377" 18106
573 "70724" "376" 18074
576 "70727" "377" 18172
575 "70726" "376" 18140
551 "70743" "376" 17348
550 "70742" "377" 17314
553 "70745" "376" 17414
552 "70744" "377" 17380
549 "70741" "376" 17282
548 "70740" "377" 17248
547 "70739" "376" 17216
544 "70736" "377" 17116
543 "70735" "376" 17084
546 "70738" "377" 17182
545 "70737" "376" 17150
2060 "71602" "388" 63794
2220 "70754" "377" 68827
2061 "71603" "389" 63816
2219 "70753" "376" 68795
2058 "71600" "389" 63750
2222 "70756" "377" 68893
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.
"log_GTFS.txt"