midland-odessa-urban-transit-district — Source Data Validation Report
This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-27T20:25:47Z,
for the dataset file:///shared/midland-odessa-urban-transit-district_2458a93e.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
- Service Window:
- 2018-11-04 to 2050-12-30 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt
Files included
- agency.txt
- calendar.txt
- calendar_dates.txt
- fare_attributes.txt
- fare_rules.txt
- frequencies.txt
- routes.txt
- shapes.txt
- stop_times.txt
- stops.txt
- transfers.txt
- trips.txt
Counts
- Agencies: 0
- Blocks: 30
- Routes: 18
- Shapes: 14
- Stops: 652
- Trips: 214
Specification Compliance report
24 notices reported (1 errors, 23 warnings, 0 infos)
| Notice Code | Severity | Total | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| invalid_url | ERROR | 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
invalid_urlA field contains a malformed URL. Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator. You can see more about this notice here.
fast_travel_between_far_stops | WARNING | 1 | fast_travel_between_far_stopsA transit vehicle moves too fast between two far stops. Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops. The speed threshold depends on route type and are the same as
You can see more about this notice here.
missing_recommended_file | WARNING | 1 | missing_recommended_fileA recommended file is missing. You can see more about this notice here.
mixed_case_recommended_field | WARNING | 4 | mixed_case_recommended_fieldThis 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.
You can see more about this notice here.
stops_match_shape_out_of_order | WARNING | 1 | stops_match_shape_out_of_orderTwo stop entries are different than their arrival-departure order defined by 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.
unusable_trip | WARNING | 8 | unusable_tripTrips must have more than one stop to be usable. A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting. You can see more about this notice here.
unused_trip | WARNING | 8 | unused_tripTrip is not be used in Trips should be referred to at least once in You can see more about this notice here.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||