GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T14:27:00Z,
for the dataset file:///shared/tutigerride-md.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
GMV Syncromatics
Feed Email:
support@gmvsync.com
Feed Language:
English
Feed Start Date:
2025-01-22
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: 9
  • Routes: 5
  • Shapes: 5
  • Stops: 48
  • Trips: 156

Specification Compliance report

46 notices reported (23 errors, 20 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`.
"2033" "7083555" 538 3268.256562993644 10 537 8120.819800150208 9
"2032" "7083555" 525 3268.256562993644 10 524 8120.819800150208 9
"2031" "7083555" 512 3268.256562993644 10 511 8120.819800150208 9
"2030" "7083555" 499 3268.256562993644 10 498 8120.819800150208 9
"2029" "7083555" 486 3268.256562993644 10 485 8120.819800150208 9
"2028" "7083555" 473 3268.256562993644 10 472 8120.819800150208 9
"2027" "7083555" 460 3268.256562993644 10 459 8120.819800150208 9
"2026" "7083555" 447 3268.256562993644 10 446 8120.819800150208 9
"2025" "7083555" 434 3268.256562993644 10 433 8120.819800150208 9
"2024" "7083555" 421 3268.256562993644 10 420 8120.819800150208 9
"2012" "7083555" 265 3268.256562993644 10 264 8120.819800150208 9
"2011" "7083555" 252 3268.256562993644 10 251 8120.819800150208 9
"2023" "7083555" 408 3268.256562993644 10 407 8120.819800150208 9
"2022" "7083555" 395 3268.256562993644 10 394 8120.819800150208 9
"2021" "7083555" 382 3268.256562993644 10 381 8120.819800150208 9
"2020" "7083555" 369 3268.256562993644 10 368 8120.819800150208 9
"2019" "7083555" 356 3268.256562993644 10 355 8120.819800150208 9
"2018" "7083555" 343 3268.256562993644 10 342 8120.819800150208 9
"2017" "7083555" 330 3268.256562993644 10 329 8120.819800150208 9
"2016" "7083555" 317 3268.256562993644 10 316 8120.819800150208 9
"2015" "7083555" 304 3268.256562993644 10 303 8120.819800150208 9
"2014" "7083555" 291 3268.256562993644 10 290 8120.819800150208 9
"2013" "7083555" 278 3268.256562993644 10 277 8120.819800150208 9
leading_or_trailing_whitespaces WARNING 5

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" 18 "stop_name" "#21 Kenilworth at Witherwood Ct. "
"stops.txt" 22 "stop_name" "#64 York Rd. Plaza "
"stops.txt" 30 "stop_name" "#29 Loch Raven Blvd at Glen Keith Blvd. "
"stops.txt" 47 "stop_name" "#326 Loch Raven and Taylor Ave "
"routes.txt" 6 "route_long_name" "Kenilworth Ave/401 "
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_color_contrast WARNING 1

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeColor (?) The faulty record's HTML route color. routeTextColor (?) The faulty record's HTML route text color.
"1823" 2 "#EDB323" "#F7F7F7"
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`.
"1823" 2 "Gold Route" "Gold Route"
"1844" 3 "Goucher - Loch Raven" "Goucher - Loch Raven"
"4313" 4 "Lake Ave" "Lake Ave"
"6120" 6 "Kenilworth Ave/401" "Kenilworth Ave/401"
route_short_name_too_long WARNING 3

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`.
"1844" 3 "Goucher - Loch Raven"
"5781" 5 "West Village to Core Campus"
"6120" 6 "Kenilworth Ave/401"
same_name_and_description_for_route WARNING 3

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`.
2 "1823" "Gold Route" "route_short_name"
4 "4313" "Lake Ave" "route_short_name"
5 "5781" "West Village to Core Campus" "route_short_name"
stop_too_far_from_shape_using_user_distance WARNING 2

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
26 "21906" "2011" 252 "7083555" "#32 W. Chesapeake MTA" [39.40791899999999,-76.611574] 1011.8955698421594
26 "21906" "2011" 253 "4923437" "#33 101 W. Pennsylvania" [39.40791899999999,-76.611574] 897.4224041144541
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"