Pioneer Valley Transit Authority (PVTA)

What changed since the last check

• Correctness no change
• Freshness down 1.7
• Rider experience no change
• Realtime quality no change

Top three things to fix

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

   Equal shape distance diff coordinates (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

   Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

   Effort: Varies.

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

   The trip updates 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 11 observed fixes).

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 2 validator errors to resolve.

Published Ready

Published at a public URL.

Valid Needs attention

2 validator errors to resolve.

Current Ready

Service data covers the next 60 days.

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://www.pvta.com/g_trans/google_transit.zip

Last checked

2026-07-09

Service window

51 days of service data remain. Last service date 2026-08-29.

Feed version

2026-06-30-1438

State

Massachusetts