zenbus-laurentides — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-08T10:46:27Z,
for the dataset file:///shared/zenbus-laurentides_457af6db.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
TACL
Feed Email:
N/A
Feed Language:
French
Feed Start Date:
2026-08-03
Feed End Date:
2027-08-07

Files included


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

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 1
  • Shapes: 4
  • Stops: 114
  • Trips: 48

Specification Compliance report

2769 notices reported (0 errors, 2761 warnings, 8 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 18

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"zenbus:Route:4855355715616768:LOC" 5190 1147.0 34 5189 1147.0 33 0.3295333278092403
"zenbus:Route:4855355715616768:LOC" 5606 19017.0 450 5605 19017.0 449 0.0774019618782906
"zenbus:Route:4855355715616768:LOC" 5810 26469.0 654 5809 26469.0 653 0.5016708988534245
"zenbus:Route:4855355715616768:LOC" 6327 44351.0 1171 6326 44351.0 1170 0.22239020252697528
"zenbus:Route:4855355715616768:LOC" 6409 48077.0 1253 6408 48077.0 1252 0.1902466699623425
"zenbus:Route:4855355715616768:LOC" 6478 50559.0 1322 6477 50559.0 1321 0.23539929274767007
"zenbus:Route:4855355715616768:LOC" 6646 63493.0 1490 6645 63493.0 1489 0.07709700394640254
"zenbus:Route:4855355715616768:LOC" 6676 66300.0 1520 6675 66300.0 1519 0.23536848206439545
"zenbus:Route:4855355715616768:LOC" 6742 71518.0 1586 6741 71518.0 1585 0.2706021097249566
"zenbus:Route:5444211468926976:LOC" 3437 1147.0 34 3436 1147.0 33 0.3295333278092403
"zenbus:Route:5444211468926976:LOC" 3833 18775.0 430 3832 18775.0 429 0.0774019618782906
"zenbus:Route:5444211468926976:LOC" 4037 26227.0 634 4036 26227.0 633 0.5016708988534245
"zenbus:Route:5444211468926976:LOC" 4554 44109.0 1151 4553 44109.0 1150 0.22239020252697528
"zenbus:Route:5444211468926976:LOC" 4636 47835.0 1233 4635 47835.0 1232 0.1902466699623425
"zenbus:Route:5444211468926976:LOC" 4705 50317.0 1302 4704 50317.0 1301 0.23539929274767007
"zenbus:Route:5444211468926976:LOC" 4873 63251.0 1470 4872 63251.0 1469 0.07709700394640254
"zenbus:Route:5444211468926976:LOC" 4903 66058.0 1500 4902 66058.0 1499 0.23536848206439545
"zenbus:Route:5444211468926976:LOC" 4969 71276.0 1566 4968 71276.0 1565 0.2706021097249566
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_timepoint_value WARNING 2740

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 2740 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 "6048212216446976:0" 0
3 "6048212216446976:0" 1
4 "6048212216446976:0" 2
5 "6048212216446976:0" 3
6 "6048212216446976:0" 4
7 "6048212216446976:0" 5
8 "6048212216446976:0" 6
9 "6048212216446976:0" 7
10 "6048212216446976:0" 8
11 "6048212216446976:0" 9
12 "6048212216446976:0" 10
13 "6048212216446976:0" 11
14 "6048212216446976:0" 12
15 "6048212216446976:0" 13
16 "6048212216446976:0" 14
17 "6048212216446976:0" 15
18 "6048212216446976:0" 16
19 "6048212216446976:0" 17
20 "6048212216446976:0" 18
21 "6048212216446976:0" 19
22 "6048212216446976:0" 20
23 "6048212216446976:0" 21
24 "6048212216446976:0" 22
25 "6048212216446976:0" 23
26 "6048212216446976:0" 24
27 "6048212216446976:0" 25
28 "6048212216446976:0" 26
29 "6048212216446976:0" 27
30 "6048212216446976:0" 28
31 "6048212216446976:0" 29
32 "6048212216446976:0" 30
33 "6048212216446976:0" 31
34 "6048212216446976:0" 32
35 "6048212216446976:0" 33
36 "6048212216446976:0" 34
37 "6048212216446976:0" 35
38 "6048212216446976:0" 36
39 "6048212216446976:0" 37
40 "6048212216446976:0" 38
41 "6048212216446976:0" 39
42 "6048212216446976:0" 40
43 "6048212216446976:0" 41
44 "6048212216446976:0" 42
45 "6048212216446976:0" 43
46 "6048212216446976:0" 44
47 "6048212216446976:0" 45
48 "6048212216446976:0" 46
49 "6048212216446976:0" 47
50 "6048212216446976:0" 48
51 "6048212216446976:0" 49
route_long_name_contains_short_name WARNING 1

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`. routeLongName (?) The faulty record's `route_long_name`.
"zenbus:Line:6398051127132160:LOC" 2 "Inter" "Inter"
service_has_no_active_day_of_the_week WARNING 1

service_has_no_active_day_of_the_week

A service is not valid for any day of the week.

You can see more about this notice here.

csvRowNumber (?) The row number in calendar.txt where the error occurs. serviceId (?) The service_id field value.
4 "cal3-9"
big_gap_in_service INFO 6

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.
"cal3-9" "2026-09-07" "2026-10-12" 34
"cal3-9" "2026-10-12" "2026-12-25" 73
"cal3-9" "2026-12-25" "2027-02-01" 37
"cal3-9" "2027-02-01" "2027-03-26" 52
"cal3-9" "2027-03-29" "2027-05-24" 55
"cal3-9" "2027-05-24" "2027-06-24" 30
unknown_column INFO 2

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" "zenbus_mission_id" 11
"trips.txt" "trip_headsign_code" 12