Search
  1. Home
  2. United States Feeds
  3. kiryas-joel-area-transit
  4. Source Data Validation Report

kiryas-joel-area-transit — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-27T17:08:31Z,
for the dataset file:///shared/kiryas-joel-area-transit_574f4e75.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
Trillium Solutions, Inc.
Feed Email:
support+test+kiryasjoel-ny-us@trilliumtransit.com
Feed Language:
English
Feed Start Date:
N/A
Feed End Date:
N/A

Files included

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

Counts

  • Agencies: 1
  • Blocks: 14
  • Routes: 8
  • Shapes: 16
  • Stops: 62
  • Trips: 637

Specification Compliance report

20 notices reported (6 errors, 11 warnings, 3 infos)

Notice Code Severity Total
foreign_key_violation ERROR 5

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "Walmart Summer Friday" 618
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "Walmart Summer Sunday" 619
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "Walmart Summer Mon-Thurs" 620
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "Walmart Non Summer Sunday" 621
"trips.txt" "service_id" "calendar.txt or calendar_dates.txt" "service_id" "Walmart Non Summer Friday" 622
start_and_end_range_out_of_order ERROR 1

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. entityId (?) The faulty service id. startFieldName (?) The start value's field name. startValue (?) The start value. endFieldName (?) The end value's field name. endValue (?) The end value.
"calendar.txt" 15 "Walmart 600 Exception" "start_date" "20251102" "end_date" "20251031"
expired_calendar WARNING 1

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
15 "Walmart 600 Exception"
missing_recommended_field WARNING 2

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_start_date"
"feed_info.txt" 2 "feed_end_date"
route_long_name_contains_short_name WARNING 8

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`.
"E" 2 "E" "E"
"D" 3 "D" "D"
"C" 4 "C" "C"
"B" 5 "B" "B"
"A" 6 "A" "A"
"Local" 7 "Local" "Local Route"
"Walmart" 8 "Walmart" "Walmart Route"
"Woodbury" 9 "Woodbury" "Woodbury Route"
unknown_column INFO 3

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file. fieldName (?) The name of the unknown column. index (?) The index of the faulty column.
"agency.txt" "agency_branding_url" 7
"feed_info.txt" "feed_id" 2
"routes.txt" "route_branding_url" 8