Search
  1. Home
  2. United States Feeds
  3. midland-odessa-urban-transit-district
  4. Source Data Validation Report

midland-odessa-urban-transit-district — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-15T09:17:20Z,
for the dataset file:///shared/midland-odessa-urban-transit-district_7590bd53.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

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

Counts

  • Agencies: 1
  • Blocks: 26
  • Routes: 18
  • Shapes: 14
  • Stops: 652
  • Trips: 276

Specification Compliance report

76 notices reported (23 errors, 25 warnings, 28 infos)

Notice Code Severity Total
invalid_row_length ERROR 23

invalid_row_length

Invalid csv row length.

A row in the input file has a different number of values than specified by the CSV header.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. rowLength (?) The length of the faulty record. headerCount (?) The number of column in the faulty file.
"stop_times.txt" 10163 9 8
"stop_times.txt" 10209 9 8
"stop_times.txt" 10255 9 8
"stop_times.txt" 10301 9 8
"stop_times.txt" 10347 9 8
"stop_times.txt" 10393 9 8
"stop_times.txt" 10439 9 8
"stop_times.txt" 10485 9 8
"stop_times.txt" 10531 9 8
"stop_times.txt" 10577 9 8
"stop_times.txt" 10623 9 8
"stop_times.txt" 10669 9 8
"stop_times.txt" 10715 9 8
"stop_times.txt" 12948 9 8
"stop_times.txt" 12994 9 8
"stop_times.txt" 13040 9 8
"stop_times.txt" 13086 9 8
"stop_times.txt" 13132 9 8
"stop_times.txt" 13178 9 8
"stop_times.txt" 13224 9 8
"stop_times.txt" 13270 9 8
"stop_times.txt" 13316 9 8
"stop_times.txt" 13362 9 8
missing_recommended_field WARNING 18

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.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
"routes.txt" 13 "agency_id"
"routes.txt" 14 "agency_id"
"routes.txt" 15 "agency_id"
"routes.txt" 16 "agency_id"
"routes.txt" 17 "agency_id"
"routes.txt" 18 "agency_id"
"routes.txt" 19 "agency_id"
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 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" "2nd (WTO)" 299
"stops.txt" "stop_name" "36- 250 svc rd. S & 191 svc rd. W" 358
"stops.txt" "stop_name" "28- 250 svc rd. (MVSC)" 518
"stops.txt" "stop_name" "27- 250 svc rd. & H.E.B." 622
unused_shape WARNING 2

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"39" 5960
"40" 7015
service_extends_far_in_the_future INFO 28

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).
"23" "2029-11-29"
"24" "2029-11-29"
"30" "2029-11-23"
"31" "2029-11-24"
"32" "2029-11-23"
"33" "2029-11-24"
"34" "2030-03-29"
"35" "2030-03-29"
"36" "2030-03-29"
"37" "2030-03-29"
"38" "2030-03-29"
"39" "2030-03-29"
"41" "2030-03-29"
"43" "2030-03-29"
"45" "2030-03-29"
"46" "2030-03-30"
"47" "2030-03-30"
"48" "2030-03-30"
"49" "2030-03-30"
"50" "2030-03-30"
"51" "2030-03-30"
"53" "2030-03-30"
"55" "2030-03-30"
"57" "2030-03-30"
"58" "2030-05-30"
"59" "2030-05-25"
"69" "2050-12-30"
"72" "2050-12-30"