{ "agency": { "id": "virginia-railway-express-vre", "name": "Virginia Railway Express (VRE)" }, "autofix": { "available": false }, "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", "cemv": { "declared": false, "supported": false }, "components": { "contact": 7.5, "fares": 0.0, "headsigns": 15.0, "stop_names": 15.0, "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": 100.0, "mixed_case_stop_name_pct": 100.0, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": true, "has_step_free": false, "pathway_count": 0 }, "stops": 67, "trips": 64, "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": 67, "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": "67 of 67 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": 64, "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": "64 of 64 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_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." }, { "code": "scorecard_station_no_pathways", "count": 1, "effort": "Worth it for multi-level or large stations; flat stops don't need it.", "fix": "Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each.", "owner": "", "points": 0.0, "severity": "WARNING", "what": "This feed models stations or entrances but has no pathways.txt.", "why": "Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users." } ], "name": "completeness", "score": 37.5, "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": 8, "instances_by_severity": { "ERROR": 1, "INFO": 0, "WARNING": 60 }, "validator_version": "8.0.1" }, "findings": [ { "code": "location_with_unexpected_stop_time", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'location_with_unexpected_stop_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Location with unexpected stop time (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "stop_without_stop_time", "count": 28, "effort": "A review pass in your scheduling software.", "fix": "Remove retired stops from the export, or add them back to the trips that should serve them.", "owner": "Likely your export tool", "points": 6.0, "severity": "WARNING", "what": "Some stops exist in the feed but no trip ever stops at them.", "why": "Riders may walk to a stop where no bus is scheduled to arrive." }, { "code": "stop_too_far_from_shape_using_user_distance", "count": 21, "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": 6.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": "stops_match_shape_out_of_order", "count": 6, "effort": "Varies.", "fix": "Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Stops match shape out of order (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_recommended_field", "count": 2, "effort": "A field at a time; not urgent.", "fix": "Review the flagged fields and fill in the ones your riders would use.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Some files leave out fields that GTFS asks for but does not require.", "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners." }, { "code": "expired_calendar", "count": 1, "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 ended.", "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors." }, { "code": "missing_recommended_file", "count": 1, "effort": "One small file, set once in export settings.", "fix": "Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "A file GTFS asks for (usually feed_info.txt) is missing.", "why": "feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale." }, { "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." } ], "name": "correctness", "score": 54.0, "status": "measured", "summary": "The MobilityData validator flagged 8 kinds of issue across 61 instances (1 error, 60 warning, 0 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": -587, "feed_end_date": null, "feed_start_date": null, "feed_version": null, "has_feed_info": false, "last_service_date": "2024-11-29", "seasonal_boundary": true, "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 587 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": "scorecard_missing_feed_info_dates", "count": 1, "effort": "Two fields, set once in export settings.", "fix": "Add feed_info.txt with feed_start_date and feed_end_date to your export.", "owner": "Likely your export tool", "points": 15.0, "severity": "WARNING", "what": "feed_info.txt is missing its start/end dates (the file itself is absent)", "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates." } ], "name": "freshness", "score": 0.0, "status": "measured", "summary": "Service data ended 587 day(s) ago. Trip planners have likely already dropped this feed.", "weight": 0.2 }, "realtime": { "details": { "coverage_pct": null, "kinds_reachable": 0, "rt_freshness": null, "samples": 6, "scheduled_trips_in_window": 0, "worst_lag_seconds": null }, "findings": [ { "code": "scorecard_rt_trip_updates_unreachable", "count": 1, "effort": "Usually a vendor support ticket.", "fix": "Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.", "owner": "", "points": 8.3, "severity": "ERROR", "what": "The trip updates realtime feed failed during sampling.", "why": "When this feed is down, riders see scheduled times presented as if they were live." }, { "code": "scorecard_rt_vehicle_positions_unreachable", "count": 1, "effort": "Usually a vendor support ticket.", "fix": "Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.", "owner": "", "points": 8.3, "severity": "ERROR", "what": "The vehicle positions realtime feed failed during sampling.", "why": "When this feed is down, riders see scheduled times presented as if they were live." }, { "code": "scorecard_rt_service_alerts_unreachable", "count": 1, "effort": "Usually a vendor support ticket.", "fix": "Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.", "owner": "", "points": 8.3, "severity": "ERROR", "what": "The service alerts realtime feed failed during sampling.", "why": "When this feed is down, riders see scheduled times presented as if they were live." } ], "name": "realtime", "score": 0.0, "status": "measured", "summary": "Sampled 6 times outside service hours: 0 of 3 feeds healthy.", "weight": 0.2 } }, "confidence": { "feed_age_days": 0, "fetch_source": "mirror", "level": "medium", "measured_categories": 4, "notes": [ "All four score categories were measured this run.", "Realtime was sampled in one bounded window of 6 snapshots.", "The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead." ], "rt_windows": 1, "total_categories": 4 }, "conformance": { "awarded": false, "criteria": [ { "detail": "1 validator error to resolve.", "key": "valid", "met": false }, { "detail": "Service data expired 586 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. 1 validator error to resolve. Service data expired 586 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": "a33dc8e80191b9332623b2e652d6df53b0039cdf892eb14606e2b300e8c81051", "size_bytes": 27972, "static_url": "https://www.vre.org/gtfs/google_transit.zip" }, "fetch": { "final_url": "https://storage.googleapis.com/storage/v1/b/mdb-latest/o/us-virginia-virginia-railway-express-vre-gtfs-478.zip?alt=media", "max_attempts": 1, "origin_error": "HTTPError", "source": "mirror", "user_agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" }, "generated_at": "2026-07-08T00:00:00+00:00", "geo": { "bbox": [ -77.52548, 38.22099, -77.00472, 38.89955 ], "lat": 38.76596, "lon": -77.25349, "stop_count": 67 }, "ntd_id_alignment": { "detail": "Your feed's agency_id is 1; your National Transit Database ID is 30073. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error.", "feed_agency_ids": [ "1" ], "fix": "Optionally set the agency_id for your service to 30073 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.", "ntd_id": "30073", "status": "mismatch" }, "ntd_readiness": { "pillars": [ { "detail": "Published at a public URL.", "key": "published", "status": "ready" }, { "detail": "1 validator error to resolve.", "key": "valid", "status": "at_risk" }, { "detail": "Service data expired 586 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. 1 validator error to resolve. Service data expired 586 days ago, so FTA would find the link out of date." }, "overall": { "grade": "F", "margin_to_lower_band": 28.3, "margin_to_next_band": 31.7, "score": 28.3 }, "recommendations": [ { "code": "scorecard_stop_name_needs_tts", "count": 1, "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": "1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Franconia / Springfield\").", "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." }, { "code": "scorecard_station_missing_step_free_data", "count": 2, "effort": "Worth it for multi-level or large stations; flat stops don't need it.", "fix": "Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.", "owner": "", "points": 0.0, "severity": "WARNING", "what": "This feed models stations or entrances but has no pathways.txt and levels.txt.", "why": "Without pathways and levels, a wheelchair user can't tell whether a step-free route exists inside the station, and trip planners can't route anyone through it." } ], "recompute": { "as_of": "2026-07-09", "feed_fetched_date": "2026-07-08", "kind": "freshness" }, "routability": { "boardable_stops": 48, "findings": [ { "code": "scorecard_orphan_stops", "count": 28, "effort": "A cleanup pass in your scheduling software.", "fix": "Remove stops no route serves, or add the trips that should call at them.", "owner": "Likely your export tool", "points": 0.0, "severity": "INFO", "what": "28 of 48 boardable stops are never served by any trip.", "why": "Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data." } ], "orphan_stops": 28, "single_stop_trips": 0, "trips_total": 64 }, "route_map": { "drawn_route_count": 2, "has_shapes": true, "path": "data/artifacts/virginia-railway-express-vre/geometry.geojson", "route_count": 2, "routes": [ { "color": "FF0000", "color_name": "red", "has_shape": true, "id": "2", "label": "Fredericksburg Line", "long": "Fredericksburg Line", "short": "", "text_color": "FFFFFF", "type_label": "Rail" }, { "color": "6496FF", "color_name": "blue", "has_shape": true, "id": "4", "label": "Manassas Line", "long": "Manassas Line", "short": "", "text_color": "FFFFFF", "type_label": "Rail" } ], "stop_count": 67, "stop_points_capped": false }, "rubric_version": "1.1", "schema_version": "1.7", "shapes_readiness": { "detail": "All 64 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 64, "trips_with_shape": 64 }, "snapshot_date": "2026-07-09", "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 587 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": "location_with_unexpected_stop_time", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'location_with_unexpected_stop_time' 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": "Location with unexpected stop time (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "scorecard_rt_trip_updates_unreachable", "count": 1, "effort": "Usually a vendor support ticket.", "fix": "Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.", "owner": "", "points": 8.3, "rank": 3, "severity": "ERROR", "what": "The trip updates realtime feed failed during sampling.", "why": "When this feed is down, riders see scheduled times presented as if they were live." } ], "validator_version": "8.0.1" }