GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-22T23:59:18Z,
for the dataset file:///shared/core-transit_c162c3cb.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:
Core Transit
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-04-12
Feed End Date:
2026-11-21

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. frequencies.txt
  8. routes.txt
  9. shapes.txt
  10. stop_times.txt
  11. stops.txt
  12. transfers.txt
  13. trips.txt

Counts

  • Agencies: 1
  • Blocks: 35
  • Routes: 4
  • Shapes: 35
  • Stops: 96
  • Trips: 442

Specification Compliance report

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

Notice Code Severity Total
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 3

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.
"fare_attributes.txt" 2 "agency_id"
"fare_attributes.txt" 3 "agency_id"
"fare_attributes.txt" 4 "agency_id"
mixed_case_recommended_field WARNING 96

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 96 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_desc" "VAIL/BC EXPRESS" 2
"stops.txt" "stop_name" "LEADVILLE PARK N RIDE" 2
"stops.txt" "stop_name" "HARRISON ST and 3RD ST" 3
"stops.txt" "stop_name" "HARRISON ST and 8TH ST" 4
"stops.txt" "stop_name" "POPLAR ST and 11TH ST" 5
"stops.txt" "stop_name" "MOUNTAIN VIEW DR and EAGLES NEST" 6
"stops.txt" "stop_name" "HIGHWAY 24 and MOUNTAIN VIEW VILLAGE" 7
"stops.txt" "stop_name" "HIGHWAY 24 and WATER STREET" 8
"stops.txt" "stop_name" "HIGHWAY 24 + 996 MAIN" 9
"stops.txt" "stop_name" "HIGHWAY 24 + 472 MAIN" 10
"stops.txt" "stop_name" "HWY24 @ TOLEDO ST w" 11
"stops.txt" "stop_name" "FOREST SERVICE PARK AND RIDE" 12
"stops.txt" "stop_name" "SOUTH FRONTAGE RD and CHAMONIX RD" 13
"stops.txt" "stop_name" "SOUTH FRONTAGE RD and LIONSHEAD" 14
"stops.txt" "stop_name" "SOUTH FRONTAGE RD and VAIL RD" 15
"stops.txt" "stop_name" "VAIL TRANSPORTATION CENTER" 16
"stops.txt" "stop_name" "FAWCETT RD + YODER AVE" 17
"stops.txt" "stop_name" "BEAVER CREEK ELK LOT" 18
"stops.txt" "stop_name" "HIGHWAY 24 + HARRISON AVE" 19
"stops.txt" "stop_name" "HIGHWAY 24 + 996 MAIN" 20
"stops.txt" "stop_name" "HARRISON ST and 8TH ST" 21
"stops.txt" "stop_name" "HARRISON ST and 3RD ST" 22
"stops.txt" "stop_name" "LAKE CREEK VILLAGE" 23
"stops.txt" "stop_name" "HIGHWAY 6 and EAGLE RIVER VILLAGE" 24
"stops.txt" "stop_name" "HIGHWAY 6 and EDWARDS SPUR RD" 25
"stops.txt" "stop_name" "HIGHWAY 6 and RIVERWALK" 26
"stops.txt" "stop_name" "HIGHWAY 6 and BULL RUN RD" 27
"stops.txt" "stop_name" "HIGHWAY 6 and RESERVE RD" 28
"stops.txt" "stop_name" "HWY6 and MILLER RANCH RD e" 29
"stops.txt" "stop_name" "HWY6 and ARROWHEAD e" 30
"stops.txt" "stop_name" "HIGHWAY 6 and SAWATCH DR" 31
"stops.txt" "stop_name" "BEAVER CREEK BEAR LOT e" 32
"stops.txt" "stop_name" "HWY6 @ RIVERS EDGE e" 33
"stops.txt" "stop_name" "HIGHWAY 6 + EAGLE BEND" 34
"stops.txt" "stop_name" "HIGHWAY 6 + STONE BRIDGE DR" 35
"stops.txt" "stop_name" "HIGHWAY 6 + EAGLE VAIL RD" 36
"stops.txt" "stop_name" "HIGHWAY 6 + STONE CREEK DR" 37
"stops.txt" "stop_name" "HWY6 @ EAGLE RD e" 38
"stops.txt" "stop_name" "HIGHWAY 6 + EAGLE VAIL BUSINESS CNTR" 39
"stops.txt" "stop_name" "HWY6 @ DOWD PARK BUISNESS CEN e" 40
"stops.txt" "stop_name" "FREEDOM PARK" 41
"stops.txt" "stop_name" "HIGHWAY 6 + DOWD PARK BUSINESS CNTR" 42
"stops.txt" "stop_name" "HIGHWAY 6 + EAGLE VAIL BUSINESS CENTER" 43
"stops.txt" "stop_name" "HIGHWAY 6 + STONE CREEK DR" 44
"stops.txt" "stop_name" "HIGHWAY 6 + EAGLE VAIL RD" 45
"stops.txt" "stop_name" "HIGHWAY 6 + STONEBRIDGE DR" 46
"stops.txt" "stop_name" "HIGHWAY 6 + EAGLEBEND" 47
"stops.txt" "stop_name" "HIGHWAY 6 + RIVERSEDGE" 48
"stops.txt" "stop_name" "HIGHWAY 6 + W BEAVER CREEK BLVD" 49
"stops.txt" "stop_name" "HWY6 @ ARROWHEAD w" 50