syncromatics-tahoetransportation — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T23:54:02Z,
for the dataset file:///shared/syncromatics-tahoetransportation_41e6514e.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2026-07-22
Feed End Date:
N/A

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_attributes.txt
  4. directions.txt
  5. feed_info.txt
  6. realtime_routes.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts


  • Agencies: 1
  • Blocks: 30
  • Routes: 6
  • Shapes: 14
  • Stops: 112
  • Trips: 360

Specification Compliance report

54 notices reported (2 errors, 47 warnings, 5 infos)

Notice Code Severity Total
decreasing_or_equal_stop_time_distance ERROR 2

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

tripId (?) The id of the faulty trip. stopId (?) The id of the faulty stop. csvRowNumber (?) The row number from `stop_times.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. stopSequence (?) The faulty record's `stop_times.stop_sequence`. prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time. prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"npdgqo1" "6731188" 3815 0.0 1 3814 35544.023033980724 0
"y7gpr6q" "6731188" 5334 0.0 1 5333 35544.023033980724 0
equal_shape_distance_same_coordinates WARNING 1

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

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 the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"29872" 4387 30995.285340366332 494 4386 30995.285340366332 493
leading_or_trailing_whitespaces WARNING 1

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 9 "stop_name" "US 50/Tahoe Keys Blvd "
missing_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
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_end_date"
mixed_case_recommended_field WARNING 42

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.
"trips.txt" "trip_headsign" "55 LTCC" 4
"trips.txt" "trip_headsign" "51 KINGSBURY TO Y" 58
"trips.txt" "trip_headsign" "51 KINGSBURY TO Y" 69
"trips.txt" "trip_headsign" "51 KINGSBURY TO Y" 70
"trips.txt" "trip_headsign" "51 Y TO KINGSBURY" 79
"trips.txt" "trip_headsign" "51 Y TO KINGSBURY" 80
"trips.txt" "trip_headsign" "51 Y TO KINGSBURY" 81
"trips.txt" "trip_headsign" "51 KINGSBURY TO Y" 82
"trips.txt" "trip_headsign" "51 KINGSBURY TO Y" 85
"trips.txt" "trip_headsign" "51 KINGSBURY TO Y" 88
"trips.txt" "trip_headsign" "51 Y TO KINGSBURY" 89
"trips.txt" "trip_headsign" "51 Y TO KINGSBURY" 90
"trips.txt" "trip_headsign" "51 Y TO KINGSBURY" 92
"trips.txt" "trip_headsign" "55 LTCC" 96
"trips.txt" "trip_headsign" "55 LTCC" 107
"trips.txt" "trip_headsign" "55 LTCC" 120
"trips.txt" "trip_headsign" "55 LTCC" 148
"trips.txt" "trip_headsign" "55 LTCC" 152
"trips.txt" "trip_headsign" "55 LTCC" 156
"trips.txt" "trip_headsign" "55 LTCC" 168
"trips.txt" "trip_headsign" "55 LTCC" 169
"trips.txt" "trip_headsign" "55 LTCC" 175
"trips.txt" "trip_headsign" "55 LTCC" 196
"trips.txt" "trip_headsign" "55 LTCC" 219
"trips.txt" "trip_headsign" "55 LTCC" 221
"trips.txt" "trip_headsign" "55 LTCC" 231
"trips.txt" "trip_headsign" "55 LTCC" 247
"trips.txt" "trip_headsign" "55 LTCC" 256
"trips.txt" "trip_headsign" "55 LTCC" 260
"trips.txt" "trip_headsign" "55 LTCC" 261
"trips.txt" "trip_headsign" "55 LTCC" 263
"trips.txt" "trip_headsign" "55 LTCC" 264
"trips.txt" "trip_headsign" "55 LTCC" 283
"trips.txt" "trip_headsign" "55 LTCC" 292
"trips.txt" "trip_headsign" "55 LTCC" 301
"trips.txt" "trip_headsign" "55 LTCC" 303
"trips.txt" "trip_headsign" "55 LTCC" 306
"trips.txt" "trip_headsign" "55 LTCC" 316
"trips.txt" "trip_headsign" "55 LTCC" 319
"trips.txt" "trip_headsign" "55 LTCC" 328
"trips.txt" "trip_headsign" "55 LTCC" 346
"trips.txt" "trip_headsign" "55 LTCC" 349
stops_match_shape_out_of_order WARNING 1

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
252 "24969" "npdgqo1" 3815 "6731188" "Kingsbury Transit Center" [38.969348999999994,-119.93479800000001] 3814 "7911748" "Hwy 28 at Tunnel Creek" [39.236453,-119.928928]
service_extends_far_in_the_future INFO 2

service_extends_far_in_the_future

A service end date is more than 2 years in the future.

You can see more about this notice here.

serviceId (?) The service_id that ends far in the future. serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
"1" "2099-12-31"
"2" "2099-12-30"
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"calendar_attributes.txt"
"realtime_routes.txt"
"directions.txt"