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-07-17T16:45:49Z,
for the dataset file:///shared/rice_b66c662c.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: 11
    • Routes: 10
    • Shapes: 9
    • Stops: 53
    • Trips: 11

    Specification Compliance report

    8 notices reported (1 errors, 2 warnings, 5 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" "Rice.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"
    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.
    3 "TL-39"
    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-90" "2024-05-11" "2024-08-24" 104
    service_extends_far_in_the_future INFO 4

    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-17" "2029-12-30"
    "TL-90" "2050-12-24"
    "TL-97" "2034-08-18"
    "TL-104" "2050-05-25"