transit-services-of-frederick-county — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-27T09:09:36Z,
for the dataset file:///shared/transit-services-of-frederick-county_71d81677.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included


Feed Info


Publisher Name:
Passio Technologies
Publisher URL:
https://passiotech.com
Feed Email:
support@passiotech.com
Feed Language:
English
Feed Start Date:
2026-06-25
Feed End Date:
2026-07-26

Files included


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

Counts


  • Agencies: 1
  • Blocks: 64
  • Routes: 17
  • Shapes: 59
  • Stops: 390
  • Trips: 877

Specification Compliance report

59 notices reported (0 errors, 48 warnings, 11 infos)

Notice Code Severity Total
fast_travel_between_consecutive_stops WARNING 4

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.
294 "714028" "6156" 199.3924030548901 3.3232067175815017 5169 1 "162799" "Waverley Transfer Facility" "16:55:00" 5176 8 "162872" "West South Street at Thomas Avenue" "16:55:00"
293 "714027" "6156" 199.3924030548901 3.3232067175815017 5156 1 "162799" "Waverley Transfer Facility" "15:55:00" 5163 8 "162872" "West South Street at Thomas Avenue" "15:55:00"
296 "714030" "6156" 199.3924030548901 3.3232067175815017 5195 1 "162799" "Waverley Transfer Facility" "18:55:00" 5202 8 "162872" "West South Street at Thomas Avenue" "18:55:00"
295 "714029" "6156" 199.3924030548901 3.3232067175815017 5182 1 "162799" "Waverley Transfer Facility" "17:55:00" 5189 8 "162872" "West South Street at Thomas Avenue" "17:55:00"
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

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 "20260627" "20260726" "20260727"
route_long_name_contains_short_name WARNING 10

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`.
"6154" 2 "10" "10 Connector"
"9349" 3 "15" "15 Connector"
"6155" 4 "20" "20 Connector"
"6156" 5 "40" "40 Connector"
"6157" 6 "50" "50 Connector"
"6158" 7 "51" "51 Connector"
"6159" 8 "60" "60 Connector"
"6160" 9 "61" "61 Connector"
"6161" 10 "65" "65 Connector"
"6162" 11 "80" "80 Connector"
stop_too_far_from_shape WARNING 3

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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.
873 "51784" "713851" 16041 "163069" "Monocacy MARC Train Station" [39.382202,-77.402185] 602.1084838259515
874 "51785" "713852" 16075 "163069" "Monocacy MARC Train Station" [39.382202,-77.402185] 602.1084838259515
752 "51829" "714491" 14262 "163156" "Jefferson Tech Park (Jefferson Station Boulevard at Mary Lou Lane)" [39.391202107585556,-77.44953970750211] 318.28558766777377
stop_too_far_from_shape_using_user_distance WARNING 3

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.
849 "51830" "714501" 15721 "162939" "Baughman's Lane at Walgreens" [39.42698405662899,-77.43597674186907] 807.8271330794164
849 "51830" "714501" 15722 "163125" "Mt. Zion Road Park and Ride" [39.37828398342257,-77.47383585010762] 166.65586990521786
849 "51830" "714501" 15723 "163126" "Point of Rocks MARC Train Station" [39.275340821423285,-77.54113272910014] 622.8956716276466
stop_without_stop_time WARNING 27

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.
43 "163181" "Avery's Restaurant"
66 "163115" "Brunswick Senior Center (12 East A Street)"
82 "162822" "Clarion Inn Frederick Event Center"
85 "162820" "Corporate Drive at New Design Road"
88 "162829" "Crestwood Boulevard at Bank Court"
114 "163027" "East Street at Peters Lane"
130 "191109" "FCC Exit Announcements"
144 "162800" "Frederick Towne Mall at Boscov's South Entrance"
145 "162864" "Frederick Towne Mall at Meet-the-MARC stop on Waverley"
147 "190265" "FSK Exit Announcements"
149 "162801" "Golden Mile Marketplace at Big Lots"
166 "163132" "Heather Ridge Drive at Taney Avenue"
179 "162808" "Himes Avenue at Coralberry Court"
192 "162900" "Key Parkway at Baker Place Apartments"
194 "163072" "Key Parkway at first entrance to Elmwood Terrace Apartments"
195 "163092" "Key Parkway at Hawthorne Square"
200 "163073" "Key Parkway at Waverley Drive"
243 "162823" "New Technology Way at Spectrum Drive eb"
261 "163071" "Old Camp Road at Key Parkway"
263 "163070" "Old Camp Road near 7-Eleven"
264 "172065" "Old Camp Road near 7-Eleven"
327 "203267" "Stauffer Sheetz Exit Announcements"
332 "162966" "Taney Avenue at Heather Ridge Drive"
337 "187567" "TC Exit Announcements"
353 "163050" "Waterside Drive at Caulfield Court- Worman's Mill"
357 "162865" "Waverley Drive at steps to strip mall"
358 "163074" "Waverley Drive at Waverley Center"
big_gap_in_service INFO 6

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.
"51783.134015" "2023-11-24" "2023-12-26" 31
"51783.134015" "2023-12-26" "2024-11-11" 320
"51783.134015" "2024-11-11" "2024-12-26" 44
"51783.134015" "2024-12-26" "2025-05-26" 150
"51783.134015" "2025-05-26" "2025-12-26" 213
"51783.134015" "2025-12-31" "2026-11-11" 314
service_window_outside_feed_period INFO 5

service_window_outside_feed_period

A service window is not covered by the feed's validity period.

You can see more about this notice here.

serviceId (?) The service_id whose active window extends outside the feed validity period. serviceWindowStartDate (?) The first active date of the service window. serviceWindowEndDate (?) The last active date of the service window. daysBeforeFeedStart (?) Number of days the service window extends before feed_start_date (0 if none). daysAfterFeedEnd (?) Number of days the service window extends after feed_end_date (0 if none).
"73888" "2025-01-01" "2027-12-31" 540 523
"51839.134159" "2025-01-01" "2027-12-31" 540 523
"51783.134013" "2025-01-02" "2027-12-31" 539 523
"51783.134015" "2023-11-10" "2026-11-11" 958 108
"51783.134016" "2025-01-04" "2027-12-25" 537 517