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

rice — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-02T14:57:40Z,
for the dataset file:///shared/rice_b15fdb93.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: 16
    • Routes: 14
    • Shapes: 13
    • Stops: 65
    • Trips: 20

    Specification Compliance report

    36 notices reported (5 errors, 4 warnings, 27 infos)

    Notice Code Severity Total
    block_trips_with_overlapping_stop_times ERROR 4

    block_trips_with_overlapping_stop_times

    Trips with the same block id have overlapping stop times.

    You can see more about this notice here.

    csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip. tripIdA (?) The id of first faulty trip. serviceIdA (?) The service id of the first faulty trip. csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip. tripIdB (?) The id of the other faulty trip. serviceIdB (?) The service id of the other faulty trip. blockId (?) The `trips.block_id` of the overlapping trip. intersection (?) The overlapping period.
    2 "TL-160" "TL-101" 3 "TL-161" "TL-102" "Night Escort_01" "20241005"
    2 "TL-160" "TL-101" 14 "TL-139" "TL-94" "Night Escort_01" "20241004"
    3 "TL-161" "TL-102" 13 "TL-137" "TL-93" "Night Escort_01" "20241006"
    13 "TL-137" "TL-93" 14 "TL-139" "TL-94" "Night Escort_01" "20240930"
    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" "Rice.transloc.com"
    fast_travel_between_consecutive_stops WARNING 1

    fast_travel_between_consecutive_stops

    A transit vehicle moves too fast between two consecutive stops.

    The speed threshold depends on route type:

    Route type Description Threshold, km/h
    0 Light rail 100
    1 Subway 150
    2 Rail 500
    3 Bus 150
    4 Ferry 80
    5 Cable tram 30
    6 Aerial lift 50
    7 Funicular 50
    11 Trolleybus 150
    12 Monorail 150
    - Unknown 200

    You can see more about this notice here.

    tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
    9 "TL-64" "TL-9" 184.1210266037529 3.068683776729215 241 14 "TL-29" "Bus Stop 17" "00:15:35" 242 15 "TL-41" "Target and Fiesta Shopping Center" "00:16:35"
    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"
    stops_match_shape_out_of_order WARNING 1

    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-29" "TL-160" 142 "TL-7" "College Way 7/ Allen Center" [29.717734511796564,-95.39838257816757] 141 "TL-52" "College Way 6" [29.71770392755465,-95.39836614896853]
    unusable_trip WARNING 1

    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.
    8 "TL-39"
    big_gap_in_service INFO 13

    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-6" "2017-05-13" "2017-08-19" 97
    "TL-6" "2018-05-12" "2026-08-22" 3023
    "TL-44" "2019-05-11" "2019-08-24" 104
    "TL-44" "2020-08-15" "2026-08-22" 2197
    "TL-65" "2020-08-14" "2026-08-28" 2204
    "TL-90" "2024-05-11" "2024-08-24" 104
    "TL-93" "2026-05-20" "2026-08-23" 94
    "TL-94" "2026-05-20" "2026-08-21" 92
    "TL-101" "2026-05-16" "2026-08-21" 96
    "TL-102" "2026-05-17" "2026-08-22" 96
    "TL-106" "2017-05-14" "2017-08-20" 97
    "TL-106" "2018-05-13" "2026-08-23" 3023
    "TL-107" "2020-08-15" "2026-08-29" 2204
    service_extends_far_in_the_future INFO 14

    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-6" "2050-12-24"
    "TL-17" "2029-12-30"
    "TL-44" "2050-12-24"
    "TL-65" "2050-12-30"
    "TL-90" "2050-12-24"
    "TL-93" "2050-12-29"
    "TL-94" "2050-12-30"
    "TL-97" "2050-08-18"
    "TL-101" "2050-12-30"
    "TL-102" "2050-12-25"
    "TL-104" "2050-05-25"
    "TL-105" "2050-12-28"
    "TL-106" "2050-12-25"
    "TL-107" "2050-12-24"