Search
  1. Home
  2. United States Feeds
  3. breckenridgefreeride
  4. Source Data Validation Report

breckenridgefreeride — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-05T05:03:11Z,
for the dataset file:///shared/breckenridgefreeride_7e02d726.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:
    2024-11-26
    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: 0
    • Blocks: 8
    • Routes: 6
    • Shapes: 9
    • Stops: 120
    • Trips: 316

    Specification Compliance report

    10 notices reported (1 errors, 6 warnings, 3 infos)

    Notice Code Severity Total
    missing_required_field ERROR 1

    missing_required_field

    A required field is missing.

    The given field has no value in some input row, even though values are required.

    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.
    "agency.txt" 3 "agency_url"
    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_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`.
    "2561" 2 "Trolley" "Trolley Route"
    "2563" 3 "Gold" "Gold Route"
    "3500" 6 "Gray" "Gray Route"
    "5900" 7 "Green" "Green Route"
    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"