wcta-rideralerts-com-westmoreland-county-transit-a — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-05-10T01:45:46Z,
for the dataset file:///shared/wcta-rideralerts-com-westmoreland-county-transit-a_75f2c9a1.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included


Feed Info


Publisher Name:
Westmoreland Transit
Feed Email:
N/A
Feed Language:
English
Feed Start Date:
2026-04-20
Feed End Date:
2026-04-20

Files included


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

Counts


  • Agencies: 1
  • Blocks: 46
  • Routes: 15
  • Shapes: 55
  • Stops: 1010
  • Trips: 171

Specification Compliance report

24 notices reported (0 errors, 24 warnings, 0 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.
2 "2"
fast_travel_between_consecutive_stops WARNING 5

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.
144 "t38A-b77-sl2" "8" 174.21956101214175 0.7259148375505907 2016 405 "897" "Center Ave + RHJ (Bus Shelter)" "09:12:45" 2017 420 "866" "Center Ave + Sunny Ln" "09:13:00"
146 "t452-b77-sl2" "8" 174.21956101214175 0.7259148375505907 3099 405 "897" "Center Ave + RHJ (Bus Shelter)" "11:12:45" 3100 420 "866" "Center Ave + Sunny Ln" "11:13:00"
150 "t5E2-bCF-sl2" "8" 174.21956101214175 0.7259148375505907 5208 405 "897" "Center Ave + RHJ (Bus Shelter)" "15:12:45" 5209 420 "866" "Center Ave + Sunny Ln" "15:13:00"
148 "t51A-b77-sl2" "8" 174.21956101214175 0.7259148375505907 4122 405 "897" "Center Ave + RHJ (Bus Shelter)" "13:12:45" 4123 420 "866" "Center Ave + Sunny Ln" "13:13:00"
152 "t6AA-bCF-sl2" "8" 174.21956101214175 0.7259148375505907 6698 405 "897" "Center Ave + RHJ (Bus Shelter)" "17:12:45" 6699 420 "866" "Center Ave + Sunny Ln" "17:13:00"
feed_expiration_date7_days WARNING 1

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20260510" "20260420" "20260517"
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
mixed_case_recommended_field WARNING 4

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" "I HOP (FS)" 42
"stops.txt" "stop_name" "RT 66S + RT 366" 125
"stops.txt" "stop_name" "RT 981N + RT 819N" 244
"stops.txt" "stop_name" "ATWOOD STATION" 556
stop_too_far_from_shape_using_user_distance WARNING 2

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.
144 "1476_shp" "t38A-b77-sl2" 2015 "869" "RIDC Park East Entrance" [40.186087,-79.574165] 169.46072589223172
143 "1475_shp" "t32F-b73-sl2" 1567 "869" "RIDC Park East Entrance" [40.186087,-79.574165] 169.46072589223172
stop_without_stop_time WARNING 9

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.
331 "1661" "N. 4th St + Depot St"
332 "1662" "S. 3rd St + Depot St"
333 "1663" "S. 4th St + Newill St"
334 "1664" "N. 3rd St + Newill St"
335 "1665" "S. 4th St + Hillis St"
336 "1666" "S. 3rd St + E. Hillis St"
566 "401" "Main St. + Pennsylvania Ave."
895 "872" "Tech Center Dr + Central Rd"
905 "896" "Tech Center Dr + Central Rd"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20260510" "20260420" "20260420"