Search
  1. Home
  2. United States Feeds
  3. colum-busa-usa
  4. Source Data Validation Report

colum-busa-usa — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-10T00:24:52Z,
for the dataset file:///shared/colum-busa-usa_3a03a6e4.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2026-05-05
Feed End Date:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_attributes.txt
  4. directions.txt
  5. feed_info.txt
  6. realtime_routes.txt
  7. routes.txt
  8. shapes.txt
  9. stop_times.txt
  10. stops.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 10
  • Routes: 5
  • Shapes: 7
  • Stops: 188
  • Trips: 115

Specification Compliance report

66 notices reported (23 errors, 40 warnings, 3 infos)

Notice Code Severity Total
decreasing_or_equal_stop_time_distance ERROR 23

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

tripId (?) The id of the faulty trip. stopId (?) The id of the faulty stop. csvRowNumber (?) The row number from `stop_times.txt`. shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record. stopSequence (?) The faulty record's `stop_times.stop_sequence`. prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time. prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time. prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"OL-5" "9519198" 1431 15952.408790349811 33 1430 15952.408790349811 32
"OL-4" "9519198" 1391 15952.408790349811 33 1390 15952.408790349811 32
"OL-7" "9519198" 1511 15952.408790349811 33 1510 15952.408790349811 32
"OL-6" "9519198" 1471 15952.408790349811 33 1470 15952.408790349811 32
"OL-1" "9519198" 1071 15952.408790349811 33 1070 15952.408790349811 32
"OL-3" "9519198" 1351 15952.408790349811 33 1350 15952.408790349811 32
"OL-2" "9519198" 1311 15952.408790349811 33 1310 15952.408790349811 32
"OL-11" "9519198" 1151 15952.408790349811 33 1150 15952.408790349811 32
"OL-9" "9519198" 1591 15952.408790349811 33 1590 15952.408790349811 32
"OL-12" "9519198" 1191 15952.408790349811 33 1190 15952.408790349811 32
"OL-8" "9519198" 1551 15952.408790349811 33 1550 15952.408790349811 32
"OL-13" "9519198" 1231 15952.408790349811 33 1230 15952.408790349811 32
"OL-14" "9519198" 1271 15952.408790349811 33 1270 15952.408790349811 32
"OL-10" "9519198" 1111 15952.408790349811 33 1110 15952.408790349811 32
"SOL-3" "9519198" 3180 15952.408790349811 33 3179 15952.408790349811 32
"SOL-4" "9519198" 3220 15952.408790349811 33 3219 15952.408790349811 32
"SOL-1" "9519198" 3100 15952.408790349811 33 3099 15952.408790349811 32
"SOL-2" "9519198" 3140 15952.408790349811 33 3139 15952.408790349811 32
"SOL-9" "9519198" 3420 15952.408790349811 33 3419 15952.408790349811 32
"SOL-7" "9519198" 3340 15952.408790349811 33 3339 15952.408790349811 32
"SOL-8" "9519198" 3380 15952.408790349811 33 3379 15952.408790349811 32
"SOL-5" "9519198" 3260 15952.408790349811 33 3259 15952.408790349811 32
"SOL-6" "9519198" 3300 15952.408790349811 33 3299 15952.408790349811 32
leading_or_trailing_whitespaces WARNING 32

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 7 "stop_name" "Gladstone Ave & 16th "
"stops.txt" 35 "stop_name" "Gladstone Apts on Gladstone "
"stops.txt" 36 "stop_name" "Gladstone & Indiana "
"stops.txt" 47 "stop_name" "State & Pence Calla "
"stops.txt" 52 "stop_name" "16th & Pearl "
"stops.txt" 53 "stop_name" "16th & California "
"stops.txt" 57 "stop_name" "Cummins/St Peter's on California "
"stops.txt" 58 "stop_name" "Goodwill on Carr Hill "
"stops.txt" 59 "stop_name" "Franklin & 4th "
"stops.txt" 62 "stop_name" "Washington & 8th "
"stops.txt" 112 "stop_name" "8th & Washington "
"stops.txt" 131 "stop_name" "3rd & Sycamore "
"stops.txt" 143 "stop_name" "Nexus Park on Herman Darlage "
"stops.txt" 146 "stop_name" "22nd & Cottage "
"stops.txt" 150 "stop_name" "Eastgate & Lockerbie "
"stops.txt" 152 "stop_name" "22nd & Maple "
"stops.txt" 155 "stop_name" "Washington & 19th "
"stops.txt" 167 "stop_name" "West Hill Shopping Center "
"stops.txt" 168 "stop_name" "27th & Lafayette "
"stops.txt" 174 "stop_name" "8th & Jackson "
"stops.txt" 176 "stop_name" "Lafayette & 17th "
"stops.txt" 177 "stop_name" "Washington & 14th "
"stops.txt" 179 "stop_name" "Central Ave & 18th "
"stops.txt" 180 "stop_name" "Central Ave & 13th "
"stops.txt" 189 "stop_name" "3rd & Jackson "
"routes.txt" 2 "route_long_name" "Blue "
"routes.txt" 3 "route_short_name" "Green "
"routes.txt" 3 "route_long_name" "Green "
"routes.txt" 4 "route_short_name" "Orange "
"routes.txt" 4 "route_long_name" "Orange "
"routes.txt" 5 "route_short_name" "Purple "
"routes.txt" 5 "route_long_name" "Purple "
missing_feed_info_date WARNING 1

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. fieldName (?) Either `feed_end_date` or `feed_start_date`.
2 "feed_end_date"
missing_recommended_field WARNING 1

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.
"feed_info.txt" 2 "feed_end_date"
route_long_name_contains_short_name WARNING 4

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name Dataset
"N"/"Judah" Muni San Fransisco
"6"/"ML King Jr Blvd" Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent" STM Montreal
"1"/"Rangiora/Cashmere" Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

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`. routeLongName (?) The faulty record's `route_long_name`.
"6991" 3 "Green" "Green"
"6992" 4 "Orange" "Orange"
"6993" 5 "Purple" "Purple"
"7003" 6 "Red" "Red"
same_name_and_description_for_route WARNING 1

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

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

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. routeId (?) The id of the faulty record. routeDesc (?) The `routes.routes_desc` of the faulty record. specifiedField (?) Either `route_short_name` or `route_long_name`.
6 "7003" "Red" "route_short_name"
stop_without_stop_time WARNING 1

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.
109 "12007179" "Mapleton & State"
unknown_file INFO 3

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"calendar_attributes.txt"
"realtime_routes.txt"
"directions.txt"