Search
  1. Home
  2. United States Feeds
  3. slc-airport
  4. Source Data Validation Report

slc-airport — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-07-24T17:26:33Z,
for the dataset file:///shared/slc-airport_60dba0d3.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. fare_attributes.txt
    5. fare_rules.txt
    6. frequencies.txt
    7. routes.txt
    8. shapes.txt
    9. stop_times.txt
    10. stops.txt
    11. transfers.txt
    12. trips.txt

    Counts

    • Agencies: 0
    • Blocks: 32
    • Routes: 7
    • Shapes: 4
    • Stops: 20
    • Trips: 32

    Specification Compliance report

    15 notices reported (1 errors, 8 warnings, 6 infos)

    Notice Code Severity Total
    invalid_url ERROR 1

    invalid_url

    A field contains a malformed URL.

    Definitions for valid URLs are quite vague. We perform strict validation using the Apache Commons UrlValidator.

    You can see more about this notice here.

    filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
    "agency.txt" 2 "agency_url" "SLCAirport.transloc.com"
    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"
    stop_without_stop_time WARNING 1

    stop_without_stop_time

    A stop in stops.txt is not referenced by any stop_times.stop_id.

    Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

    You can see more about this notice here.

    csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
    2 "TL-24" "Parking Off Route"
    stops_match_shape_out_of_order WARNING 2

    stops_match_shape_out_of_order

    Two stop entries are different than their arrival-departure order defined by shapes.txt.

    This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

    You can see more about this notice here.

    tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`. shapeId (?) The id of the shape that is referred to. tripId (?) The id of the trip that is referred to. stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`. stopId1 (?) The id of the first stop that is referred to. stopName1 (?) The name of the first stop that is referred to. match1 (?) Latitude and longitude pair of the first matching location. stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`. stopId2 (?) The id of the second stop that is referred to. stopName2 (?) The name of the second stop that is referred to. match2 (?) Latitude and longitude pair of the second matching location.
    2 "TL-12" "TL-71" 33 "TL-32" "EC Announcement 1" [40.78194340948912,-111.98072636369513] 32 "TL-28" "Economy Lot Stop" [40.78395015270718,-111.98518776042113]
    12 "TL-13" "TL-81" 121 "TL-32" "EC Announcement 1" [40.78194340948912,-111.98072636369513] 120 "TL-28" "Economy Lot Stop" [40.78395015270718,-111.98518776042113]
    unusable_trip WARNING 2

    unusable_trip

    Trips must have more than one stop to be usable.

    A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

    You can see more about this notice here.

    csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
    27 "TL-96"
    28 "TL-97"
    unused_trip WARNING 2

    unused_trip

    Trip is not be used in stop_times.txt

    Trips should be referred to at least once in stop_times.txt.

    You can see more about this notice here.

    tripId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
    "TL-96" 27
    "TL-97" 28
    big_gap_in_service INFO 1

    big_gap_in_service

    A service has a gap of more than 13 days between active service dates.

    You can see more about this notice here.

    serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
    "TL-11" "2025-06-29" "2025-08-05" 36
    service_extends_far_in_the_future INFO 5

    service_extends_far_in_the_future

    A service end date is more than 2 years in the future.

    You can see more about this notice here.

    serviceId (?) The service_id that ends far in the future. serviceWindowEndDate (?) The end date of the service (YYYY-MM-DD format).
    "TL-9" "2031-05-30"
    "TL-11" "2050-05-25"
    "TL-12" "2050-12-30"
    "TL-13" "2030-12-30"
    "TL-14" "2030-01-20"