corpus-christi-regional-transportation-authority — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-01T22:27:34Z,
for the dataset file:///shared/corpus-christi-regional-transportation-authority_1af3862a.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


  • Corpus Christi Regional Transportation Authority

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. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. transfers.txt
  9. trips.txt

Counts


  • Agencies: 1
  • Blocks: 70
  • Routes: 33
  • Shapes: 88
  • Stops: 2657
  • Trips: 6760

Specification Compliance report

22 notices reported (0 errors, 21 warnings, 1 infos)

Notice Code Severity Total
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 10

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" "277-19th @ RR" 810
"stops.txt" "stop_name" "695-SPID" 907
"stops.txt" "stop_name" "697-SPID" 994
"stops.txt" "stop_name" "1473- leopard" 1321
"stops.txt" "stop_name" "1243-N 5th" 1339
"stops.txt" "stop_name" "695-SPID" 1455
"stops.txt" "stop_name" "1243-N 5th" 1629
"stops.txt" "stop_name" "697-SPID" 1796
"stops.txt" "stop_name" "277-19th @ RR" 1848
"stops.txt" "stop_name" "1473- leopard" 2150
stop_without_stop_time WARNING 6

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
3 "0:4003" "Special"
4 "0:4000" "B-Line"
5 "0:4002" "Special"
6 "0:4001" "B-Line"
345 "0:9999" "RTA Garage"
1109 "0:9990" "Port Aransas Garage"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260801" "20260731" "20260807"
unused_shape WARNING 3

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.
"L60P6" 7481
"L60P1" 12973
"L60P2" 13041
unknown_column INFO 1

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.
"stops.txt" "vehicle_type" 10