spokane — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T14:19:08Z,
for the dataset file:///shared/spokane_4d5dfc93.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Spokane Transit Authority
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-05-17
Feed End Date:
2026-09-19

Files included


  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. fare_attributes.txt
  5. fare_leg_rules.txt
  6. fare_media.txt
  7. fare_products.txt
  8. fare_rules.txt
  9. fare_transfer_rules.txt
  10. feed_info.txt
  11. routes.txt
  12. shapes.txt
  13. stop_times.txt
  14. stops.txt
  15. transfers.txt
  16. trips.txt

Counts


  • Agencies: 1
  • Blocks: 206
  • Routes: 83
  • Shapes: 256
  • Stops: 1665
  • Trips: 8396

Specification Compliance report

87 notices reported (0 errors, 77 warnings, 10 infos)

Notice Code Severity Total
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.
20 "671.8.1"
missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2
missing_recommended_field WARNING 1

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.
"fare_attributes.txt" 2 "agency_id"
mixed_case_recommended_field WARNING 43

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
Field Text Dataset
"Schwerin, Hauptbahnhof" Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin" NYC Ferry
"Campo Grande Norte" Carris
Bad examples:
Field Text
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file. fieldName (?) Name of the faulty field. fieldValue (?) Faulty value. csvRowNumber (?) The row number of the faulty record.
"stops.txt" "stop_name" "1st @ W 800" 680
"stops.txt" "stop_name" "16th @ 14210 E" 938
"stops.txt" "stop_name" "16th @ E. 14204" 951
"stops.txt" "stop_name" "32nd @ SR 27" 957
"stops.txt" "stop_name" "8th @ 6th" 1114
"stops.txt" "stop_name" "8th @ 6th" 1151
"trips.txt" "trip_headsign" "EWU PUB" 2341
"trips.txt" "trip_headsign" "EWU PUB" 2342
"trips.txt" "trip_headsign" "EWU PUB" 2343
"trips.txt" "trip_headsign" "EWU PUB" 2344
"trips.txt" "trip_headsign" "EWU PUB" 2345
"trips.txt" "trip_headsign" "EWU PUB" 2346
"trips.txt" "trip_headsign" "EWU PUB" 2347
"trips.txt" "trip_headsign" "EWU PUB" 2348
"trips.txt" "trip_headsign" "EWU PUB" 2349
"trips.txt" "trip_headsign" "EWU PUB" 2350
"trips.txt" "trip_headsign" "EWU PUB" 2351
"trips.txt" "trip_headsign" "EWU PUB" 2352
"trips.txt" "trip_headsign" "EWU PUB" 2353
"trips.txt" "trip_headsign" "EWU PUB" 2354
"trips.txt" "trip_headsign" "EWU PUB" 2355
"trips.txt" "trip_headsign" "EWU PUB" 2356
"trips.txt" "trip_headsign" "EWU PUB" 2357
"trips.txt" "trip_headsign" "EWU PUB" 2358
"trips.txt" "trip_headsign" "EWU PUB" 2359
"trips.txt" "trip_headsign" "EWU PUB" 2360
"trips.txt" "trip_headsign" "EWU PUB" 2361
"trips.txt" "trip_headsign" "EWU PUB" 2362
"trips.txt" "trip_headsign" "EWU PUB" 2363
"trips.txt" "trip_headsign" "EWU PUB" 2364
"trips.txt" "trip_headsign" "EWU PUB" 2365
"trips.txt" "trip_headsign" "EWU PUB" 2366
"trips.txt" "trip_headsign" "EWU PUB" 2367
"trips.txt" "trip_headsign" "EWU PUB" 2368
"trips.txt" "trip_headsign" "EWU PUB" 2369
"trips.txt" "trip_headsign" "EWU PUB" 2370
"trips.txt" "trip_headsign" "EWU PUB" 2371
"trips.txt" "trip_headsign" "EWU PUB" 2372
"trips.txt" "trip_headsign" "EWU PUB" 2373
"trips.txt" "trip_headsign" "EWU PUB" 2374
"trips.txt" "trip_headsign" "EWU PUB" 2375
"trips.txt" "trip_headsign" "EWU PUB" 2376
"trips.txt" "trip_headsign" "EWU PUB" 2377
service_has_no_active_day_of_the_week WARNING 21

service_has_no_active_day_of_the_week

A service is not valid for any day of the week.

You can see more about this notice here.

csvRowNumber (?) The row number in calendar.txt where the error occurs. serviceId (?) The service_id field value.
3 "671.0.14"
6 "671.101.1"
7 "671.125.14"
8 "671.125.2"
9 "671.126.1"
10 "671.126.14"
11 "671.126.2"
12 "671.126.3"
13 "671.31.1"
14 "671.6.1"
15 "671.65.1"
16 "671.65.2"
17 "671.65.3"
18 "671.74.1"
19 "671.74.2"
20 "671.8.1"
21 "671.82.1"
22 "671.91.1"
23 "671.93.1"
24 "671.97.1"
25 "671.98.1"
stop_too_far_from_shape_using_user_distance WARNING 9

stop_too_far_from_shape_using_user_distance

Stop time too far from shape.

A stop time entry that is a large distance away from the location of the shape in shapes.txt as defined by shape_dist_traveled values.

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. stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`. stopId (?) The id of the stop that is referred to. stopName (?) The name of the stop that is referred to. match (?) Latitude and longitude pair of the location. geoDistanceToShape (?) Distance from stop to shape.
2 "62499" "1363097" 5 "1STADAEN" "1st @ Adams" [47.656529000000006,-117.43441400000002] 230.25198725206477
2 "62499" "1363097" 6 "1STMONEN" "1st @ Monroe" [47.656528,-117.431119] 275.01252421613833
2 "62499" "1363097" 15 "MISCOLCL" "Mission @ Columbus" [47.671669,-117.397831] 221.82292723716907
107 "62502" "1363202" 1989 "MISCOLCL" "Mission @ Columbus" [47.671791,-117.390607] 319.2624674203965
107 "62502" "1363202" 1998 "SPRMONWM" "Sprague @ Monroe" [47.657198,-117.42322100000001] 308.98549341562216
107 "62502" "1363202" 1999 "SPRADACL" "Sprague @ Adams St" [47.656677,-117.434214] 200.89003708516432
211 "62503" "1363306" 4069 "MISCOLCL" "Mission @ Columbus" [47.671791,-117.390607] 319.2624674203965
211 "62503" "1363306" 4078 "SPRMONWM" "Sprague @ Monroe" [47.657198,-117.42322100000001] 308.98549341562216
211 "62503" "1363306" 4079 "SPRADACL" "Sprague @ Adams St" [47.656677,-117.434214] 200.89003708516432
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.
5193 "1363535"
big_gap_in_service INFO 10

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.
"671.0.14" "2026-05-25" "2026-06-19" 24
"671.0.14" "2026-06-19" "2026-07-04" 14
"671.0.14" "2026-07-04" "2026-09-07" 64
"671.125.14" "2026-05-25" "2026-09-07" 104
"671.125.2" "2026-05-30" "2026-08-01" 62
"671.126.14" "2026-06-19" "2026-07-04" 14
"671.31.1" "2026-06-16" "2026-08-26" 70
"671.82.1" "2026-06-15" "2026-08-31" 76
"671.97.1" "2026-06-16" "2026-08-26" 70
"671.98.1" "2026-05-22" "2026-06-17" 25