GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-01-23T15:24:34Z,
for the dataset file:///shared/hampton-roads.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

  • Hampton Roads Transit (HRT)

Feed Info

Publisher Name:
Hampton Roads Transit (HRT)
Publisher URL:
https://gohrt.com/
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2025-10-12
Feed End Date:
2026-05-23

Files included

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

Counts

  • Agencies: 1
  • Blocks: 1915
  • Routes: 89
  • Shapes: 252
  • Stops: 2657
  • Trips: 14054

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 20

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.
6 "F-2510-FFAL2510-Holiday3-02"
7 "F-2510-FFAL2510-Holiday3-02-1111111"
14 "N-2510-NFAL2510-Holiday2-04"
15 "N-2510-NFAL2510-Holiday2-04-1111111"
16 "N-2510-NFAL2510-Holiday1-02"
17 "N-2510-NFAL2510-Holiday1-02-1111111"
18 "N-2510-NFAL2510-Weekday-04"
23 "R-2510-RFAL2510-Holiday2-01"
24 "R-2510-RFAL2510-Holiday2-01-1111111"
25 "R-2510-RFAL2510-Holiday1-01"
26 "R-2510-RFAL2510-Holiday1-01-1111111"
31 "S-2510-SFAL2510-Holiday2-03"
32 "S-2510-SFAL2510-Holiday2-03-1111111"
33 "S-2510-SFAL2510-Holiday1-03"
34 "S-2510-SFAL2510-Holiday1-03-1111111"
35 "S-2510-SFAL2510-Weekday-05"
36 "S-2510-SFAL2510-Holiday2-04"
37 "S-2510-SFAL2510-Holiday2-04-1111111"
42 "V-2510-VFAL2510-Holiday1-02"
43 "V-2510-VFAL2510-Holiday1-02-1111111"
missing_bike_allowance WARNING 248

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

Only the first 50 of 248 affected records are displayed below.

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
2 "090" "10758609"
3 "090" "10758610"
4 "090" "10758611"
5 "090" "10758612"
6 "090" "10758613"
7 "090" "10758614"
8 "090" "10758615"
9 "090" "10758616"
10 "090" "10758617"
11 "090" "10758618"
12 "090" "10758619"
13 "090" "10758620"
14 "090" "10758621"
15 "090" "10758622"
16 "090" "10758623"
17 "090" "10758624"
18 "090" "10758625"
19 "090" "10758626"
20 "090" "10758627"
21 "090" "10758628"
22 "090" "10758629"
23 "090" "10758630"
24 "090" "10758631"
25 "090" "10758632"
26 "090" "10758633"
27 "090" "10758634"
28 "090" "10758635"
29 "090" "10758636"
30 "090" "10758637"
31 "090" "10758638"
32 "090" "10758639"
33 "090" "10758640"
34 "090" "10758641"
35 "090" "10758642"
36 "090" "10758643"
37 "090" "10758644"
38 "090" "10758645"
39 "090" "10758646"
40 "090" "10758647"
41 "090" "10758648"
42 "090" "10758649"
43 "090" "10758650"
44 "090" "10758651"
45 "090" "10758652"
46 "090" "10758653"
47 "090" "10758654"
48 "090" "10758655"
49 "090" "10758656"
50 "090" "10758657"
51 "090" "10758658"
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
mixed_case_recommended_field WARNING 2749

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.

Only the first 50 of 2749 affected records are displayed below.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"routes.txt" "route_long_name" "GRANBY ST" 2
"routes.txt" "route_long_name" "HAMPTON BLVD" 3
"routes.txt" "route_long_name" "CHESAPEAKE BLVD" 4
"routes.txt" "route_long_name" "CHURCH ST" 5
"routes.txt" "route_long_name" "SOUTH NORFOLK" 7
"routes.txt" "route_long_name" "TIDEWATER DRIVE" 8
"routes.txt" "route_long_name" "SEWELLS POINT RD" 9
"routes.txt" "route_long_name" "COLONIAL AVE" 10
"routes.txt" "route_long_name" "INDIAN RIVER RD" 11
"routes.txt" "route_long_name" "CAMPOSTELLA RD" 12
"routes.txt" "route_long_name" "BATTLEFIELD BLVD" 13
"routes.txt" "route_long_name" "MILITARY HWY" 14
"routes.txt" "route_long_name" "BALLENTINE BLVD" 15
"routes.txt" "route_long_name" "757X - VIRGINIA BEACH BLVD" 16
"routes.txt" "route_long_name" "LITTLE CREEK RD" 17
"routes.txt" "route_long_name" "WESLEYAN & HAYGOOD RD" 18
"routes.txt" "route_long_name" "PRINCESS ANNE RD" 19
"routes.txt" "route_long_name" "KEMPSVILLE RD" 20
"routes.txt" "route_long_name" "NEWTOWN RD" 21
"routes.txt" "route_long_name" "LYNNHAVEN MALL/TCC VB" 22
"routes.txt" "route_long_name" "NORTHAMPTON BLVD" 23
"routes.txt" "route_long_name" "GREAT NECK/LYNNHAVEN PKWY" 24
"routes.txt" "route_long_name" "ATLANTIC AVENUE TROLLEY" 25
"routes.txt" "route_long_name" "AQUARIUM & CAMPGROUND SHUTTLE" 26
"routes.txt" "route_long_name" "GENERAL BOOTH BLVD" 27
"routes.txt" "route_long_name" "BAY FRONT & OCEANFRONT SHUTTLE" 28
"routes.txt" "route_long_name" "HOLLAND RD" 29
"routes.txt" "route_long_name" "PORTSMOUTH BLVD" 33
"routes.txt" "route_long_name" "HIGH ST" 34
"routes.txt" "route_long_name" "ACADEMY PARK" 35
"routes.txt" "route_long_name" "DEEP CREEK" 36
"routes.txt" "route_long_name" "BAINBRIDGE BLVD" 37
"routes.txt" "route_long_name" "ELIZABETH RIVER FERRY" 38
"routes.txt" "route_long_name" "QUEEN STREET" 40
"routes.txt" "route_long_name" "SHELL RD" 41
"routes.txt" "route_long_name" "MARSHALL AVENUE" 42
"routes.txt" "route_long_name" "BRIARFIELD RD" 43
"routes.txt" "route_long_name" "WARWICK BOULEVARD" 44
"routes.txt" "route_long_name" "DENBIGH BOULEVARD" 45
"routes.txt" "route_long_name" "WARWICK/LEE HALL" 46
"routes.txt" "route_long_name" "VIRGINIA PENINSULA COMMUNITY COLLEGE" 48
"routes.txt" "route_long_name" "PATRICK HENRY MALL" 49
"routes.txt" "route_long_name" "757X - JEFFERSON AVE" 50
"routes.txt" "route_long_name" "757X - MERCURY BOULEVARD" 51
"routes.txt" "route_long_name" "FOX HILL" 52
"routes.txt" "route_long_name" "NEIL ARMSTRONG PARKWAY" 53
"routes.txt" "route_long_name" "BUCKROE SHOPPING CENTER" 54
"routes.txt" "route_long_name" "W. OAKS/COL.MALL" 55
"routes.txt" "route_long_name" "NEWPORT NEWS TRANSIT CENTER - OAKLAND INDUSTRIAL" 56
"routes.txt" "route_long_name" "SYE-DENBIGH FPL TO WEST AVE" 57
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`.
54 "403" "Buckroe Shopping Center" "route_long_name"