GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T18:06:20Z,
for the dataset file:///shared/sel-et-vermois.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
CC Sel et Vermois
Feed Email:
N/A
Feed Language:
French
Feed Start Date:
2025-09-01
Feed End Date:
2026-08-30

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: 0
  • Blocks: 0
  • Routes: 1
  • Shapes: 2
  • Stops: 92
  • Trips: 27

Specification Compliance report

1044 notices reported (0 errors, 1042 warnings, 2 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 24

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:4898591756779520:LOC" 103 1843.0 101 102 1843.0 100 0.07350518961415733
"zenbus:Route:4898591756779520:LOC" 133 2757.0 131 132 2757.0 130 0.7372561382600967
"zenbus:Route:4898591756779520:LOC" 146 3047.0 144 145 3047.0 143 0.07349853887406717
"zenbus:Route:4898591756779520:LOC" 157 3385.0 155 156 3385.0 154 0.860750095434845
"zenbus:Route:4898591756779520:LOC" 238 5384.0 236 237 5384.0 235 0.2469184627663499
"zenbus:Route:4898591756779520:LOC" 313 7281.0 311 312 7281.0 310 0.22044274760642338
"zenbus:Route:4898591756779520:LOC" 351 8197.0 349 350 8197.0 348 0.31427336962769636
"zenbus:Route:4898591756779520:LOC" 377 9436.0 375 376 9436.0 374 0.5263282042069191
"zenbus:Route:4898591756779520:LOC" 579 14599.0 577 578 14599.0 576 0.31438269290589993
"zenbus:Route:4898591756779520:LOC" 592 15168.0 590 591 15168.0 589 0.553047642236858
"zenbus:Route:4898591756779520:LOC" 747 18663.0 745 746 18663.0 744 0.2666128438261047
"zenbus:Route:5999002525892608:LOC" 1025 3363.0 156 1024 3363.0 155 0.13330642260955694
"zenbus:Route:5999002525892608:LOC" 1066 4252.0 197 1065 4252.0 196 0.07351804852285196
"zenbus:Route:5999002525892608:LOC" 1173 6831.0 304 1172 6831.0 303 0.184349808527857
"zenbus:Route:5999002525892608:LOC" 1220 8696.0 351 1219 8696.0 350 0.07350979985968911
"zenbus:Route:5999002525892608:LOC" 1237 9128.0 368 1236 9128.0 367 0.23422318727788036
"zenbus:Route:5999002525892608:LOC" 1321 10629.0 452 1320 10629.0 451 0.11119510090982554
"zenbus:Route:5999002525892608:LOC" 1397 12897.0 528 1396 12897.0 527 0.18431596168690345
"zenbus:Route:5999002525892608:LOC" 1517 16998.0 648 1516 16998.0 647 0.454707158303814
"zenbus:Route:5999002525892608:LOC" 1547 17658.0 678 1546 17658.0 677 0.07348641721991431
"zenbus:Route:5999002525892608:LOC" 1562 17982.0 693 1561 17982.0 692 0.5331392494212717
"zenbus:Route:5999002525892608:LOC" 1584 18691.0 715 1583 18691.0 714 0.49641800517687473
"zenbus:Route:5999002525892608:LOC" 1653 20208.0 784 1652 20208.0 783 0.07349753989770627
"zenbus:Route:5999002525892608:LOC" 1698 21431.0 829 1697 21431.0 828 0.31318371375202453
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 2

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.
"agency.txt" 2 "agency_id"
"routes.txt" 2 "agency_id"
missing_timepoint_value WARNING 1013

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 1013 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 "4884444067397632:0" 0
3 "4884444067397632:0" 1
4 "4884444067397632:0" 2
5 "4884444067397632:0" 3
6 "4884444067397632:0" 4
7 "4884444067397632:0" 5
8 "4884444067397632:0" 6
9 "4884444067397632:0" 7
10 "4884444067397632:0" 8
11 "4884444067397632:0" 9
12 "4884444067397632:0" 10
13 "4884444067397632:0" 11
14 "4884444067397632:0" 12
15 "4884444067397632:0" 13
16 "4884444067397632:0" 14
17 "4884444067397632:0" 15
18 "4884444067397632:0" 16
19 "4884444067397632:0" 17
20 "4884444067397632:0" 18
21 "4884444067397632:0" 19
22 "4884444067397632:0" 20
23 "4884444067397632:0" 21
24 "4884444067397632:0" 22
25 "4884444067397632:0" 23
26 "4884444067397632:0" 24
27 "4884444067397632:0" 25
28 "4884444067397632:0" 26
29 "4884444067397632:0" 27
30 "4884444067397632:0" 28
31 "4884444067397632:0" 29
32 "4884444067397632:0" 30
33 "4884444067397632:0" 31
34 "4884444067397632:0" 32
35 "4884444067397632:0" 33
36 "4884444067397632:0" 34
37 "4884444067397632:0" 35
38 "4884444067397632:0" 36
39 "4884444067397632:1" 0
40 "4884444067397632:1" 1
41 "4884444067397632:1" 2
42 "4884444067397632:1" 3
43 "4884444067397632:1" 4
44 "4884444067397632:1" 5
45 "4884444067397632:1" 6
46 "4884444067397632:1" 7
47 "4884444067397632:1" 8
48 "4884444067397632:1" 9
49 "4884444067397632:1" 10
50 "4884444067397632:1" 11
51 "4884444067397632:1" 12
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.
"routes.txt" "route_desc" "PUBLISH_AS_LINE_ID=287440019" 2
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:287440019:LOC" 2 "La Navette" "La Navette – Sel & Vermois"
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