Frederick County TransIT

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change
• Realtime quality up 6.3

Fixed since the last check (2 findings):

• 4 of 13 trips scheduled during the sampling window had no live predictions. (scorecard_rt_trip_coverage)
• Some live predictions disagree with the schedule by more than 30 minutes. (scorecard_rt_predictions_implausible)

Top three things to fix

1. Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

2. Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

3. Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Effort: Usually a vendor support ticket.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve. Service data runs out in 30 days; renew before you certify.

Published Ready

Published at a public URL.

Valid Needs attention

2 validator errors to resolve.

Current Needs attention

Service data runs out in 30 days; renew before you certify.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

https://passio3.com/frederick/passioTransit/gtfs/google_transit.zip

Last checked

2026-07-09

Service window

30 days of service data remain. Last service date 2027-12-31.

Feed version

20250228

State

Maryland