{ "agency": { "id": "potomac-and-rappahannock-transportation-commission-prtc-481", "name": "Potomac and Rappahannock Transportation Commission (PRTC)" }, "autofix": { "available": true, "download_path": "data/artifacts/potomac-and-rappahannock-transportation-commission-prtc-481/corrected.zip", "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/potomac-and-rappahannock-transportation-commission-prtc-481/corrected.zip", "fixes": [ { "code": "autofix_stop_name_case", "count": 18, "examples": [ "MANASSAS PARK VRE -> Manassas Park Vre", "VAN BUREN ST @ HERNDON PKWY -> Van Buren St @ Herndon Pkwy", "575 HERNDON PKWY -> 575 Herndon Pkwy" ], "label": "Recased shouting stop names" }, { "code": "autofix_route_name_case", "count": 1, "examples": [ "PWME - WEEKEND -> Pwme - Weekend" ], "label": "Recased shouting route names" } ], "total": 19 }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 0.0, "stops_marked_accessible_pct": 0.0, "stops_marked_not_accessible_pct": 0.0, "stops_stated_pct": 0.0, "trips_stated_pct": 0.0 }, "accessibility_measures": "presence_not_usability", "components": { "contact": 7.5, "fares": 0.0, "headsigns": 15.0, "stop_names": 14.5, "wheelchair_stops": 0.0, "wheelchair_trips": 0.0 }, "fare_free": false, "fares": { "applied": false, "has_leg_rules": false, "has_products": false, "has_transfer_rules": false, "model": "none", "product_count": 0 }, "flex": { "booking_reachable": false, "booking_rule_count": 0, "has_booking_rules": false, "has_flex": false }, "has_fares": false, "headsign_pct": 99.9, "mixed_case_stop_name_pct": 96.7, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": false, "has_step_free": false, "pathway_count": 0 }, "stops": 545, "trips": 1598, "wheelchair_accessible_pct": 0.0, "wheelchair_boarding_pct": 0.0, "wheelchair_marked_accessible_pct": 0.0, "wheelchair_marked_not_accessible_pct": 0.0 }, "findings": [ { "code": "scorecard_wheelchair_boarding_unknown", "count": 545, "effort": "A column in stops.txt; your scheduling software likely has it.", "fix": "Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.", "owner": "Likely your team", "points": 25.0, "severity": "WARNING", "what": "545 of 545 stops don't say whether a wheelchair user can board there.", "why": "Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all." }, { "code": "scorecard_wheelchair_accessible_unknown", "count": 1598, "effort": "Often one default setting in your export.", "fix": "Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).", "owner": "Likely your export tool", "points": 15.0, "severity": "WARNING", "what": "1598 of 1598 trips don't say whether the vehicle is wheelchair accessible.", "why": "Even with accessible stops, riders need to know the bus itself can take them." }, { "code": "scorecard_no_fare_data", "count": 1, "effort": "A small file for most flat-fare systems.", "fix": "Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.", "owner": "", "points": 15.0, "severity": "WARNING", "what": "The feed contains no fare information.", "why": "Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected." }, { "code": "scorecard_missing_headsigns", "count": 1, "effort": "Usually a bulk edit in your scheduling software.", "fix": "Populate trip_headsign to match what the bus displays.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "1 of 1598 trips have no headsign.", "why": "Riders at the stop can't tell which direction a bus is going." }, { "code": "scorecard_no_feed_contact", "count": 1, "effort": "One field.", "fix": "Add feed_contact_email to feed_info.txt.", "owner": "", "points": 7.5, "severity": "INFO", "what": "feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).", "why": "App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger." } ], "name": "completeness", "score": 37.0, "status": "measured", "summary": "0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 16, "instances_by_severity": { "ERROR": 2, "INFO": 3, "WARNING": 8322 }, "validator_version": "8.0.1" }, "findings": [ { "code": "equal_shape_distance_diff_coordinates", "count": 1, "effort": "Varies.", "fix": "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.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Equal shape distance diff coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "foreign_key_violation", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Foreign key violation (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "equal_shape_distance_diff_coordinates_distance_below_threshold", "count": 7181, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 8.0, "severity": "WARNING", "what": "Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "mixed_case_recommended_field", "count": 1109, "effort": "Often a bulk fix in your scheduling software.", "fix": "Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').", "owner": "Likely your export tool", "points": 8.0, "severity": "WARNING", "what": "Some rider-facing names are in ALL CAPS or all lowercase.", "why": "ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers." }, { "code": "route_color_contrast", "count": 7, "effort": "One field per route.", "fix": "Pick a darker/lighter route_text_color for the flagged routes.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Some route colors don't contrast with their text color.", "why": "Route badges become unreadable, especially for riders with low vision." }, { "code": "expired_calendar", "count": 5, "effort": "One setting in most export tools.", "fix": "Remove past service periods the next time you export the feed.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some service calendars in the feed have already expired.", "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors." }, { "code": "same_name_and_description_for_stop", "count": 5, "effort": "Varies.", "fix": "Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Same name and description for stop (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "stop_too_far_from_shape", "count": 5, "effort": "A few minutes per flagged stop.", "fix": "Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some stops sit far from the route line they belong to.", "why": "Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner." }, { "code": "service_has_no_active_day_of_the_week", "count": 3, "effort": "A few minutes in your scheduling software.", "fix": "Delete the empty calendars or set their service days.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some service calendars have no days of the week switched on.", "why": "Trips tied to these calendars never run; they are dead data that can mask real schedule problems." }, { "code": "stop_too_far_from_shape_using_user_distance", "count": 3, "effort": "Varies.", "fix": "Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Stop too far from shape using user distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "feed_expiration_date7_days", "count": 1, "effort": "Usually a re-export from your scheduling software.", "fix": "Export and publish an updated GTFS feed that covers at least the next 30 days of service.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "This feed's service calendar runs out within the next 7 days.", "why": "When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all." }, { "code": "missing_feed_contact_email_and_url", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Missing feed contact email and url (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "trip_coverage_not_active_for_next7_days", "count": 1, "effort": "One setting in most export tools.", "fix": "Trim past service periods the next time you export.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Many of the feed's trips don't run at all in the next 7 days.", "why": "It usually means old service periods are still in the export, making the feed bigger and harder to check." }, { "code": "unusable_trip", "count": 1, "effort": "Worth a vendor question if it appears often.", "fix": "Check the flagged trips in your scheduling software; remove them or restore their missing stops.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some trips serve fewer than two stops.", "why": "A trip with one stop can't be ridden; planners ignore it and it may signal an export problem." }, { "code": "big_gap_in_service", "count": 2, "effort": "Varies.", "fix": "Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Big gap in service (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unknown_file", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Unknown file (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "name": "correctness", "score": 17.0, "status": "measured", "summary": "The MobilityData validator flagged 16 kinds of issue across 8327 instances (2 error, 8322 warning, 3 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": -579, "feed_end_date": "2024-12-08", "feed_start_date": "2024-07-29", "feed_version": "2024 July_20241030", "has_feed_info": true, "last_service_date": "2024-12-08", "seasonal_boundary": false, "service_type": "fixed" }, "findings": [ { "code": "scorecard_feed_expired", "count": 1, "effort": "Usually one export setting; export on a schedule so it never lapses again.", "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.", "owner": "Likely your export tool", "points": 100.0, "severity": "ERROR", "what": "Service data ended 579 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist." } ], "name": "freshness", "score": 0.0, "status": "measured", "summary": "Service data ended 579 day(s) ago. Trip planners have likely already dropped this feed.", "weight": 0.2 }, "realtime": { "name": "realtime", "status": "not_yet_measured", "summary": "Not scored yet. Nothing here counts against the grade.", "weight": 0.2 } }, "conformance": { "awarded": false, "criteria": [ { "detail": "2 validator errors to resolve.", "key": "valid", "met": false }, { "detail": "Service data expired 569 days ago.", "key": "current", "met": false }, { "detail": "States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "This feed is close to the conformance mark. 2 validator errors to resolve. Service data expired 569 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each." }, "feed": { "license_note": "No stated data license in the Mobility Database; verify before publishing.", "reachable": true, "sha256": "479b9b16c106de93713f327f20e5b5ffe9c0e7809294ee2e73ae19561b66908b", "size_bytes": 1356868, "static_url": "http://www.prtctransit.org/feeds/google_transit.zip" }, "generated_at": "2026-06-30T00:00:00+00:00", "geo": { "bbox": [ -77.63731, 38.21598, -76.99249, 38.95909 ], "lat": 38.66771, "lon": -77.32827, "stop_count": 545 }, "ntd_id_alignment": { "detail": "If you report to the National Transit Database, your GTFS agency_id should be your five-digit NTD ID by report year 2026 (2025 for full reporters). We don't have your NTD ID on file, so this one is not checked yet.", "feed_agency_ids": [ "OMNI" ], "status": "unknown" }, "ntd_readiness": { "pillars": [ { "detail": "Published at a public URL.", "key": "published", "status": "ready" }, { "detail": "2 validator errors to resolve.", "key": "valid", "status": "at_risk" }, { "detail": "Service data expired 569 days ago, so FTA would find the link out of date.", "key": "current", "status": "not_ready" } ], "status": "not_ready", "summary": "Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 569 days ago, so FTA would find the link out of date." }, "overall": { "grade": "F", "margin_to_lower_band": 19.0, "margin_to_next_band": 41.0, "score": 19.0 }, "recommendations": [ { "code": "scorecard_route_color_low_contrast", "count": 21, "effort": "A per-route color setting in your scheduling software.", "fix": "Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "21 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (17STRAT, 51, 52, 53, 541, and more).", "why": "Low-contrast route badges are hard to read for riders with low vision and wash out on a phone screen in sunlight at the stop." }, { "code": "scorecard_stop_name_needs_tts", "count": 503, "effort": "A short text field per affected stop; start with the busiest.", "fix": "Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.", "owner": "", "points": 0.0, "severity": "INFO", "what": "503 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Chinn Park Dr @ Chinn Center Departures\", \"Old Bridge Rd @ Smoketown Rd\", \"Prince William Pkwy @ Hillendale Dr\", and more).", "why": "Riders who use a screen reader hear the raw name, so 'Main St & 2nd Ave' can come out as 'Main saint' or drop the ampersand." } ], "recompute": { "as_of": "2026-07-10", "feed_fetched_date": "2026-06-30", "kind": "freshness" }, "routability": { "boardable_stops": 545, "findings": [ { "code": "scorecard_single_stop_trips", "count": 1, "effort": "Usually an export setting or a stop_times mapping in your software.", "fix": "Check your scheduling export: every trip should list each stop it calls at, in order, with times.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "1 of 1598 trips list fewer than two stops.", "why": "A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist." } ], "orphan_stops": 0, "single_stop_trips": 1, "trips_total": 1598 }, "rubric_version": "1.1", "schema_version": "1.4", "snapshot_date": "2026-07-10", "top_fixes": [ { "code": "scorecard_feed_expired", "count": 1, "effort": "Usually one export setting; export on a schedule so it never lapses again.", "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.", "owner": "Likely your export tool", "points": 100.0, "rank": 1, "severity": "ERROR", "what": "Service data ended 579 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist." }, { "code": "equal_shape_distance_diff_coordinates", "count": 1, "effort": "Varies.", "fix": "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.", "owner": "", "points": 12.0, "rank": 2, "severity": "ERROR", "what": "Equal shape distance diff coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "foreign_key_violation", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "rank": 3, "severity": "ERROR", "what": "Foreign key violation (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "validator_version": "8.0.1" }