norfolk — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-04T13:38:24Z,
for the dataset file:///shared/norfolk_2e8c721e.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


    Feed Info


    Publisher Name:
    N/A
    Publisher URL:
    N/A
    Feed Email:
    N/A
    Feed Language:
    N/A

    Files included


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

    Counts


    • Agencies: 0
    • Blocks: 0
    • Routes: 1
    • Shapes: 2
    • Stops: 8
    • Trips: 4

    Specification Compliance report

    3 notices reported (1 errors, 2 warnings, 0 infos)

    Notice Code Severity Total
    empty_column_name ERROR 1

    empty_column_name

    A column name is empty.

    Such columns are skipped by the validator.

    You can see more about this notice here.

    filename (?) The name of the faulty file. index (?) The index of the empty column.
    "agency.txt" 9
    missing_recommended_file WARNING 1

    missing_recommended_file

    A recommended file is missing.

    You can see more about this notice here.

    filename (?) The name of the faulty file.
    "feed_info.txt"
    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`.
    "1" 2 "Brantford" "Brantford"