GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:09:24Z,
for the dataset file:///shared/graysharbor.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Transnnovation
Publisher URL:
https://mjcaction.com/
Feed Email:
marcy@mjcaction.com
Feed Language:
English
Feed Start Date:
2025-09-02
Feed End Date:
2026-10-30

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_rules.txt
  6. feed_info.txt
  7. route_directions.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 14
  • Shapes: 104
  • Stops: 344
  • Trips: 507

Specification Compliance report

37 notices reported (0 errors, 21 warnings, 16 infos)

Notice Code Severity Total
equal_shape_distance_same_coordinates WARNING 17

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`.
"50:3" 11894 1319.075321 18 11893 1319.075321 17
"30:3" 17796 9419.487554 109 17795 9419.487554 108
"30:2" 17482 9412.807569 104 17481 9412.807569 103
"30:1" 17639 9434.659014 109 17638 9434.659014 108
"10S:1" 25737 6059.880904 91 25736 6059.880904 90
"10S:3" 25984 6198.898817 96 25983 6198.898817 95
"171:8" 24280 5413.210404 42 24279 5413.210404 41
"171:9" 24232 5433.601261 44 24231 5433.601261 43
"171:4" 24049 5433.601261 44 24048 5433.601261 43
"171:6" 23739 5413.210404 42 23738 5413.210404 41
"171:6" 23856 19350.409956 159 23855 19350.409956 158
"40:4" 15355 826.418558 17 15354 826.418558 16
"40:5" 15954 826.418558 17 15953 826.418558 16
"70:2" 1358 38292.86953 223 1357 38292.86953 222
"70:1" 1026 36282.194318 178 1025 36282.194318 177
"70:3" 639 36282.194318 178 638 36282.194318 177
"70:5" 1923 43367.70969 264 1922 43367.70969 263
mixed_case_recommended_field WARNING 4

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.
"stops.txt" "stop_name" "4th at D" 6
"stops.txt" "stop_name" "4th at G" 7
"stops.txt" "stop_name" "C at 1st" 48
"stops.txt" "stop_name" "C at 3rd" 49
unknown_column INFO 15

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.
"agency.txt" "agency_primary" 9
"routes.txt" "tts_route_short_name" 4
"routes.txt" "tts_route_long_name" 6
"routes.txt" "direction0_name" 13
"routes.txt" "direction1_name" 14
"trips.txt" "ext_trip_short_name" 6
"trips.txt" "ext_block_id" 8
"trips.txt" "ext_grid_id" 12
"trips.txt" "exceptional" 13
"trips.txt" "ext_atp_index" 14
"stops.txt" "city_name" 14
"stops.txt" "area_name" 15
"stops.txt" "direction_id" 16
"stops.txt" "ext_id" 17
"calendar.txt" "service_name" 11
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.
"route_directions.txt"