GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-12T21:42:42Z,
for the dataset file:///shared/brite.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
BRITE Bus
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2024-11-01
Feed End Date:
2028-01-01

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. frequencies.txt
  6. routes.txt
  7. shapes.txt
  8. stop_times.txt
  9. stops.txt
  10. transfers.txt
  11. trips.txt

Counts

  • Agencies: 1
  • Blocks: 0
  • Routes: 12
  • Shapes: 19
  • Stops: 178
  • Trips: 93

Specification Compliance report

30 notices reported (0 errors, 30 warnings, 0 infos)

Notice Code Severity Total
duplicate_route_name WARNING 1

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
4 "36976" 5 "250CE" "" "250 Connector" 3 ""
expired_calendar WARNING 4

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
3 "114789"
4 "114790"
5 "107618"
6 "107619"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 12

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.
"routes.txt" 2 "agency_id"
"routes.txt" 3 "agency_id"
"routes.txt" 4 "agency_id"
"routes.txt" 5 "agency_id"
"routes.txt" 6 "agency_id"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
"routes.txt" 13 "agency_id"
route_long_name_contains_short_name WARNING 1

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`.
"134070" 10 "West / North Loop" "West / North Loop"
route_short_name_too_long WARNING 1

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`.
"134070" 10 "West / North Loop"
stop_too_far_from_shape WARNING 6

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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.
27 "118342 162959" "9560736" 163 "103" "Walmart (Rt 42, Dayton)" [38.43069602356477,-78.90926741188811] 102.92285818836103
84 "afton-express-1440" "9241930" 2646 "2927596" "Waynesboro Park & Ride" [38.022220000000004,-78.55438] 34347.661781194154
84 "afton-express-1440" "9241930" 2647 "3349053" "Fishersville Park & Ride" [38.022220000000004,-78.55438] 38983.205397156395
84 "afton-express-1440" "9241930" 2648 "2927598" "Staunton Mall (Frontier Drive/JCPenney)" [38.022220000000004,-78.55438] 45926.584864347155
89 "west-north-loop_D1_S1" "10086975" 2716 "3609349" "Social Security Offices (Call Stop)" [38.16658000000001,-79.05503] 343.1744801314878
89 "west-north-loop_D1_S1" "10086975" 2720 "3" "Churchville Ave / Albemarle Ave" [38.15622,-79.0745] 195.53013136790392
stops_match_shape_out_of_order WARNING 4

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

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.

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. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
10 "116362 162953" "9560735" 910 "3460633" "Route 11 SB / Overlook Ave" [38.25970230825641,-78.9580273083027] 909 "100" "BRCC" [38.27955,-78.93939]
81 "afton-express-0530" "9239791" 2613 "3349049" "Downtown Transit Center" [38.02888537714924,-78.47734703614313] 2612 "2927595" "Wegmans" [38.008783642044136,-78.50136]
7 "116365 162951" "3471673" 844 "68" "Brittany Knoll" [38.049176653465224,-79.01908003964418] 843 "67" "Augusta Farms Apartments" [38.05191865195576,-79.01455242954783]
88 "afton-express-1800" "9242022" 2686 "3349048" "Ridge McIntire Rd. at Omni Hotel" [38.03160018854336,-78.4849579497351] 2685 "2927595" "Wegmans" [38.008783642044136,-78.50136]