GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T05:03:10Z,
for the dataset file:///shared/breckenridgefreeride_87f2e3b9.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Busmaps.com
Publisher URL:
https://busmaps.com
Feed Email:
alex@busmaps.com
Feed Language:
English
Feed Start Date:
2026-04-23
Feed End Date:
2027-12-31

Files included

  1. agency.txt
  2. calendar.txt
  3. feed_info.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 8
  • Routes: 6
  • Shapes: 9
  • Stops: 120
  • Trips: 316

Specification Compliance report

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

Notice Code Severity Total
feed_info_lang_and_agency_lang_mismatch WARNING 1

feed_info_lang_and_agency_lang_mismatch

Mismatching feed and agency language fields.

Files agency.txt and feed_info.txt should define matching agency.agency_lang and feed_info.feed_lang. The default language may be multilingual for datasets with the original text in multiple languages. In such cases, the feed_lang field should contain the language code mul defined by the norm ISO 639-2.

  • If feed_lang is not mul and does not match with agency_lang, that's an error.
  • If there is more than one agency_lang and feed_lang isn't mul, that's an error.
  • If feed_lang is mul and there isn't more than one agency_lang, that's an error.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. agencyId (?) The agency id of the faulty record. agencyName (?) The agency name of the faulty record. agencyLang (?) The agency language of the faulty record. feedLang (?) The feed language of the faulty record.
2 "105088-103" "Breck Free Ride" "en-US" "en"
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`.
"105088-2561" 2 "Trolley" "Trolley Route"
"105088-2563" 3 "Gold" "Gold Route"
"105088-3500" 6 "Gray" "Gray Route"
"105088-5900" 7 "Green" "Green Route"