GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T08:33:04Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • SN'go! (Vernon, Les Andelys, Seine Normandie Agglo)

Feed Info

Publisher Name:
N/A
Publisher URL:
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. transfers.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 26
  • Routes: 11
  • Shapes: 66
  • Stops: 189
  • Trips: 1043

Specification Compliance report

35 notices reported (0 errors, 35 warnings, 0 infos)

Notice Code Severity Total
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 22

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 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 (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.
"CALC_210431" 14483 1936.0 83 14482 1936.0 82 0.5120182867871919
"CALC_210433" 14911 1155.0 45 14910 1155.0 44 0.004764524445132944
"CALC_210433" 14984 2813.0 118 14983 2813.0 117 0.011119509878785294
"CALC_210442" 18351 9722.0 233 18350 9722.0 232 0.666198226723054
"CALC_210442" 18386 12024.0 268 18385 12024.0 267 0.11119510090982554
"CALC_210442" 18399 12083.0 281 18398 12083.0 280 0.1486564986260975
"CALC_210440" 17733 5536.0 266 17732 5536.0 265 0.11119510090982554
"CALC_210440" 17746 5595.0 279 17745 5595.0 278 0.1486564986260975
"CALC_210440" 17805 8344.0 338 17804 8344.0 337 0.666198226723054
"CALC_210445" 19610 4988.0 116 19609 4988.0 115 0.11119510090982554
"CALC_210444" 19210 5536.0 266 19209 5536.0 265 0.11119510090982554
"CALC_210444" 19223 5595.0 279 19222 5595.0 278 0.1486564986260975
"CALC_210444" 19282 8344.0 338 19281 8344.0 337 0.666198226723054
"CALC_210409" 9073 4718.0 246 9072 4718.0 245 0.6191160638940548
"CALC_210408" 8562 433.0 24 8561 433.0 23 0.6191160638940548
"CALC_210413" 9713 433.0 24 9712 433.0 23 0.6191160638940548
"CALC_210410" 9375 4763.0 278 9374 4763.0 277 0.7677585495432385
"CALC_210381" 1483 22191.0 713 1482 22191.0 712 0.4498132307772905
"CALC_210380" 715 22191.0 713 714 22191.0 712 0.4498132307772905
"CALC_210427" 13410 3585.0 154 13409 3585.0 153 0.4498132307772905
"CALC_210429" 13894 3849.0 225 13893 3849.0 224 0.011200576012934798
"CALC_210429" 13899 3868.0 230 13898 3868.0 229 0.011119509878785294
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"
mixed_case_recommended_field WARNING 12

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_long_name" "ECOS / VERNON REPUBLIQUE" 2
"routes.txt" "route_long_name" "VERNON ST ADJUTOR / VERNON REPUBLIQUE" 3
"routes.txt" "route_long_name" "VERNON LES DOUERS / VERNON REPUBLIQUE" 4
"routes.txt" "route_long_name" "VERNON L.DAMASSE / VERNON REPUBLIQUE" 5
"routes.txt" "route_long_name" "VERNON CORVETTE / VERNON REPUBLIQUE" 6
"routes.txt" "route_long_name" "ST MARCEL 11 NOVEMBRE / VERNON REPUBLIQUE" 7
"routes.txt" "route_long_name" "ST MARCEL CORNOUILLERES / VERNON REPUBLIQUE" 8
"routes.txt" "route_long_name" "PACY-SUR-EURE GARE ROUTIERE / VERNON REPUBLIQUE" 10
"routes.txt" "route_long_name" "LES ANDELYS RIVIERE / LES ANDELYS SAINT-JACQUES" 11
"routes.txt" "route_long_name" "LES ANDELYS GARE ROUTIERE / LES ANDELYS LONGUEMARE" 12
"stops.txt" "stop_name" "STE GENEVIEVE GASNY - RD5" 87
"stops.txt" "stop_name" "STE GENEVIEVE GASNY - D5" 97