gtfsrockregionmetro — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-12T01:14:38Z,
for the dataset file:///shared/gtfsrockregionmetro_7e3730ca.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_leg_rules.txt
  5. fare_products.txt
  6. networks.txt
  7. route_networks.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts


  • Agencies: 1
  • Blocks: 80
  • Routes: 16
  • Shapes: 81
  • Stops: 2249
  • Trips: 4180

Specification Compliance report

50 notices reported (1 errors, 42 warnings, 7 infos)

Notice Code Severity Total
invalid_currency_amount ERROR 1

invalid_currency_amount

A currency amount field has a value that does not match the format of its corresponding currency code field.

Typically, this means the amount did not have the expected number of decimal places. Check the formatting of your amount field so it matches the number of decimal places specified by the currency_code value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. currencyCode (?) Faulty record's currency code. fieldName (?) Faulty record's field name. fieldValue (?) Faulty currency field amount value.
"fare_products.txt" 2 "USD" "amount" "0"
equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 4

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

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 small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape. csvRowNumber (?) The row number from `shapes.txt`. shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value. shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`. prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point. prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value. prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`. actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"L13P30" 23552 7963.0 304 23551 7963.0 303 0.09999267810819687
"L13P26" 3717 5576.0 212 3716 5576.0 211 0.09999267810819687
"L13P26" 3734 5764.0 229 3733 5764.0 228 0.3477165261925225
"1stPullOutRoute8" 23995 1142.0 40 23994 1142.0 39 0.06490866389223535
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 16

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" "65th@I-30" 105
"stops.txt" "stop_name" "38th" 113
"stops.txt" "stop_name" "38th" 159
"stops.txt" "stop_name" "34th@MLK" 693
"stops.txt" "stop_name" "34th" 737
"stops.txt" "stop_name" "65th@I-30" 750
"stops.txt" "stop_name" "garage RRM" 806
"stops.txt" "stop_name" "scott bridge" 932
"stops.txt" "stop_name" "scott bridge" 935
"stops.txt" "stop_name" "34th" 1054
"stops.txt" "stop_name" "34th@MLK" 1180
"stops.txt" "stop_name" "garage RRM" 1189
"stops.txt" "stop_name" "scott bridge" 1207
"stops.txt" "stop_name" "34th" 1254
"stops.txt" "stop_name" "38th" 1550
"stops.txt" "stop_name" "65th@I-30" 1565
route_short_name_too_long WARNING 13

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"11" 2 "11-Dr. Martin Luther King Jr."
"22" 3 "22-University Ave/Mabelvale"
"23" 5 "23-Baseline/Southwest"
"13" 6 "13-UA Pulaski Technical College"
"16" 8 "16-UA Little Rock"
"1" 10 "01-Pulaski Heights"
"2" 11 "02-South Main"
"3" 12 "03-Baptist Medical Center"
"4" 13 "04-Levy/Amboy"
"5" 14 "05-West Markham"
"6" 15 "06-Granite Mountain"
"8" 16 "08-Rodney Parham"
"10" 17 "10-McCain Mall"
same_name_and_description_for_stop WARNING 3

same_name_and_description_for_stop

Same name and description for stop.

The GTFS spec defines stops.txt stop_description as:

Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty record. stopDesc (?) The faulty record's `stop_desc`.
1548 "1_keican" "Keightley & T"
1560 "1_forroo" "Fort Roots"
1579 "1_midtwn" "Midtown Target 2"
stop_without_stop_time WARNING 2

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.
806 "0_99999" "garage RRM"
1162 "0_99998" "GarageStreetCar"
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.
"1stPullOutRoute8" 23955
"STREETCAR-NORTH" 24429
"STREETCAR-SOUTH" 24487
trip_headsign_matches_intermediate_stop INFO 1

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`. tripId (?) The id of the trip with the problematic headsign. tripHeadsign (?) The headsign value that matches an intermediate stop name. stopId1 (?) The id of the intermediate stop whose name matches the headsign. stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign. stopId2 (?) The id of the actual last stop of the trip.
892 "0_3240157" "Simmons Bank" "0_12190" 4 "0_12197"
unknown_column INFO 6

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
"fare_leg_rules.txt" "from_stop_id" 5
"fare_leg_rules.txt" "to_stop_id" 6
"fare_leg_rules.txt" "route_id" 7
"fare_products.txt" "name" 2
"fare_products.txt" "transfers_duration" 5