Illustration of an autonomous vehicle traveling on a connected rural road.

Literature review companion site

Rural Autonomous Vehicles

A Literature Review Linking RAV Challenges to Research Evidence and AV Pilots

Haohua Que · Tianle Zhu · Handong Yao
College of Engineering, University of Georgia

Read the key findings Narrative review PDF & Word: forthcoming

Choose your view

Basic follows the review argument. Advanced adds comparison, statistics, planning, and filtering tools.

118 references 5 RAV modules 2014–2026 coverage 4 named pilot programs

What the Literature Says

Start here · evidence synthesis

Rural autonomous-vehicle deployment is not simply an urban AV system moved onto a quieter road. Sparse markings and mapping, intermittent connectivity, long service distances, thin demand, and limited roadside support change both the technical design and the operating model. The literature follows the framework below: Tier 1 carries the service, Tier 2 extends it selectively, and field pilots validate each expansion step.

Tier 1 · Drive + Operate

Keep the core self-reliant

Autonomous Driving and Fleet Management form the existing-technology baseline: perception, localization, planning, fallback, dispatch, charging, and remote supervision must remain workable with sparse rural support.

See Tier 1 in the framework
Tier 2 · Road + Connect + Cooperate

Add support selectively

Infrastructure, multi-channel communication, and cooperative driving extend that baseline at high-value corridors and hazards. The evidence supports targeted augmentation, not universal dependence on continuous connectivity or roadside automation.

See Tier 2 in the framework
Validation · Field pilots

Validate in stages, then scale

Supervised, low-speed, geofenced pilots provide the strongest near-term path to rural learning. Comparable reporting on interventions, connectivity loss, accessibility, energy, and operator workload is needed before broader operation.

See the validation layer

Cross-cutting framework evidence

How the evidence supports—and limits—the framework

These five findings test the sequence across modules rather than duplicate the five framework blocks. They separate what the coded website corpus consistently supports from what remains an inference requiring rural field validation; they are not the forthcoming formal review manuscript.

The clearest point of convergence is a resilient onboard core.

High-strength reviews consistently identify perception, multi-sensor fusion, localization, and mapping as the reusable AV baseline. Rural-focused work reaches the same design direction, but only one of these representative reviews is coded as direct rural evidence; the rest establish transfer paths rather than shared proof from rural operations. [1–3, 19, 23, 25]

Implication: keep safety-critical sensing, positioning, planning, and fallback onboard, then validate their failure thresholds on local roads and in local weather.

Connectivity extends that baseline, but should not replace it.

Rural measurements and communication studies show that heterogeneous V2X links can add reach and shared context while remaining spatially variable. Cooperative-driving results from urban and suburban arterials demonstrate technical possibilities, not rural effectiveness; they therefore define an extrapolation boundary rather than evidence for continuous roadside support. [9, 40, 41, 50, 92, 94, 103]

Implication: combine links opportunistically, instrument only high-value locations, and preserve a safe degraded mode through every disconnection.

The operational evidence does not select one universal rural service model.

Modeling studies examine on-demand scheduling and station optimization, whereas named pilots document two different operating logics: demand-responsive service for dispersed riders and fixed routes for predictable park or public-site circulation. These sources are better read as complementary choices tied to demand and operating context than as competing demonstrations of a single best model. [14–16, 31, 78, 116, 117]

Boundary: the pilots remain supervised, bounded precedents; they do not establish unsupervised, high-speed, open-road rural scalability.

The corpus is broad, but direct rural validation is still thin.

Of 118 retained records, the review team coded 12 as direct rural evidence, 99 as transferable to rural, and 7 as context-limited. Direct evidence is concentrated in pilots and selected infrastructure, communication, fleet, and vehicle studies; no record whose primary module is Cooperative Driving is coded as direct rural evidence. [1, 9, 14–16, 31, 50, 78, 88, 116–118]

Interpretation: the literature supports plausible design directions more strongly than it supports claims of broad rural field readiness.

Together, the studies support a staged deployment inference.

Read across domains, the evidence suggests a sequence: screen road and connectivity conditions, establish an onboard fallback baseline, add targeted corridor support, operate a bounded pilot, and expand only after comparable safety and service measurements are reviewed. No single study tests this integrated sequence; it is the review team’s synthesis of technical, infrastructure, communication, and pilot evidence. [1, 7, 9, 14, 15, 50, 88, 116–118]

Next evidence need: report interventions, disconnections, energy use, accessibility, rider outcomes, and operator workload consistently enough to compare sites and deployment stages.

The Two-Tier Framework

Existing technology carries the rural service today; advanced, infrastructure-integrated technology extends it; four named field-pilot programs validate it. Hover over or tap a module.

Framework Flow Mode Trace how a selected submodule connects to downstream RAV capabilities.
TIER 1 · EXISTING RAV TECHNOLOGY Tier 2 · Advanced RAV Technology DRIVE Autonomous Driving Perception Localization Data Integration Route Planning OPERATE Fleet Management Dispatch & Matching Remote Supervision Fixed-Route Scheduling Fleet Support ROAD Infrastructure Physical RoadAssessment DigitalInfrastructure CONNECT Communication Rural V2X Multi-ChannelCommunication COOPERATE Cooperative Driving CooperativePerception Rural-ArterialControl Work & SchoolZones Rail GradeCrossings Cooperative Response to Extreme Weather VALIDATE Field Pilots goMARTI · Grand Rapids, MN ADASTEC · Sleeping Bear Dunes TEDDY · Yellowstone National Park CASSI · Wright Brothers + N.C. 4 programs · 5 source records existing technology carries the service · advanced technology extends it · pilots validate it

Tier 1 · Existing RAV Technology

Tier 2 · Advanced RAV Technology

Two tiers, one system

Existing technology carries the service today; advanced, infrastructure-integrated technology extends it; four named field-pilot programs ground it in practice. Hover over or tap a module.

Select a submodule to reveal its cross-tier path.

Evidence Map

25 sub-themes

Research sub-themes aligned with the current evidence coding and coloured by their role in the RAV evidence chain. Limitations motivate recommended directions; reusable baselines show what can transfer now. Select a theme, then follow its clickable progression links.

Reusable baseline Recommended direction — rural validation needed Limitation / unresolved RAV problem
0 of 4 themes selected

Add themes to compare their shared and unique supporting evidence.

Select a sub-theme to open its detailed evidence summary.

Ready to investigate further?

Open the analysis workspace

Advanced mode adds theme comparison, evidence-gap views, statistics, scenario planning, and the filterable Reference Explorer.

Evidence Journey & Decision Lab

Interactive synthesis

Trace how documented limitations motivate technical directions, compare themes side by side, and explore where the review is strong or still rural-evidence limited.

Open advanced synthesis tools Progression network, theme comparison, evidence-gap radar, and timeline
Progression network Wheel to zoom; drag to pan; select a node for its evidence profile.

Only literature-supported progressions are connected. Alternative service models and field pilots remain parallel where no causal sequence is established.

Recommendations for RAV and Stakeholders

From the literature review

The evidence points to a staged rural deployment strategy: keep safety-critical capability onboard, add infrastructure where it closes a demonstrated gap, and use pilots to calibrate the system with rural data.

Stakeholder view

Build a focused one-page briefing

Showing the complete staged deployment strategy across all stakeholder groups.

Choose one perspective to include its supporting reference numbers in the printable brief.

RAV vehicle platform

Build a resilient onboard core

  • Use camera plus radar as the lower-cost perception baseline; add LiDAR where its 3-D geometry materially improves safety.
  • Fuse GNSS/INS, vision, LiDAR, and an HD-map prior instead of relying on a single rural positioning source.
  • Retrain and validate perception, localization, and energy models on faded markings, unpaved roads, terrain, and local weather.

Evidence base: 27 references Explore evidence

Fleet and service operators

Match operations to thin demand

  • Use on-demand planning for healthcare service and fixed routes for regular transit and park service.
  • Reuse dispatch and ride-matching methods, while developing rural headways, timetables, and charging plans.
  • Define supervisor-to-vehicle ratios and safe takeover procedures that tolerate degraded telemetry and video links.

Evidence base: 20 references Explore evidence

Road and infrastructure agencies

Upgrade selectively, digitize systematically

  • Assess pavement, markings, signs, and gravel-road condition first using UAV, smartphone, imaging, and mobile LiDAR surveys.
  • Prioritize physical upgrades at the highest-risk segments and instrument only the conflict points where vehicles need help.
  • Maintain HD maps, roadside observations, and digital twins as layers of one shared road-information system.

Evidence base: 22 references Explore evidence

Connectivity partners

Design for disconnection

  • Combine direct and network-based V2X, cellular, and LEO satellite links; switch by measured coverage and latency.
  • Keep safety-critical functions onboard and use roadside edge computing as supplementary support.
  • Measure route-level coverage and define channel-switching and fallback thresholds before field deployment.

Evidence base: 18 references Explore evidence

Program, policy, and pilot partners

Use pilots to close the rural evidence gap

  • Progress from supervised, low-speed geofences toward longer-range open-road operation through explicit safety gates.
  • Field-test passive rail crossings, work and school zones, mixed traffic, and extreme-weather fallback behavior.
  • Publish comparable measures for interventions, connectivity loss, energy use, rider wait time, accessibility, and operator workload.

Evidence base: 31 references Explore evidence

Open the RAV scenario planner Generate and compare two evidence-informed deployment starting points

Interactive decision aid

RAV Scenario Planner

Choose a rural operating context to generate a research-backed deployment starting point.

Road environment
Weather exposure
Connectivity
Service demand
58Readiness

Deployment posture

Adapt before deployment

Retain a resilient onboard core and treat network support as opportunistic.

Recommended stack
Priority actions

    Planning aid based on review coding; not a safety certification or route approval.

    A/B scenario comparison

    Save two planner states to compare

    Use “Save as A” and “Save as B” to compare readiness, technology stacks, actions, and evidence.

    Field evidence at a glance

    Four rural and remote pilot programs

    Select a program to inspect its supporting sources in the Reference Explorer.

    Show

    Loading pilot locations…

    On-demand service Fixed-route service Illustrative RAV corridor Map data © OpenStreetMap contributors
    Compare two pilot programs Inspect service models, operating frames, and shared transfer lessons

    Pilot side-by-side

    Compare two deployment programs

    goMARTIOn-demand

    Grand Rapids, Minnesota

    Service
    App or 211 booking; roughly 97 stops
    Operating frame
    Low-speed, geofenced service with an onboard safety operator
    RAV lesson
    Accessible demand-responsive service can reach dispersed rural riders.
    2 source records →
    ADASTECFixed route

    Sleeping Bear Dunes, Michigan

    Service
    Scheduled automated bus in a remote public-land setting
    Operating frame
    Defined route with supervised operation
    RAV lesson
    Predictable routes simplify deployment but still require interruption planning.
    1 source record →
    TEDDYFixed route

    Yellowstone National Park

    Service
    Visitor shuttle tested in a remote national-park environment
    Operating frame
    Low-speed, geofenced operation with onboard supervision
    RAV lesson
    Weather, communications, and energy constraints must be planned together.
    1 shared pilot report →
    CASSIFixed route

    Wright Brothers Memorial + N.C. sites

    Service
    Automated shuttle demonstrations across public sites
    Operating frame
    Geofenced routes with onboard safety operators
    RAV lesson
    Comparable reporting across sites exposes repeatable operational barriers.
    2 source records →

    Statistics

    2014~2026
    Active view

    All 118 references

    Publication-year range

    Showing the complete publication range.

    References per RAV module

    Select a bar to filter the explorer and reference list.

    References per year

    Select a year to filter; select it again to clear.

    Evidence type

    Select a study design to combine it with other filters.

    Rural relevance

    Separate direct rural evidence from transferable and context-limited work.

    RAV module × publication year

    Each cell shows the number of references. Select a cell to filter by both module and year.

    Reference Explorer

    2014~2026
    Export
    Showing 118 of 118 references

    Research workspace

    Citation Cart 0

    Evidence network chart
    Keyboard: Tab to a marker, Enter or Space to pin it, and O to open its source.

    Hover or focus a point to preview its evidence neighbourhood; click, Enter, or Space to pin it; Esc releases it. Double-click or press O to open the paper. Markers: shape = source type, colour = RAV module.

    Review Methodology

    Last verified July 27, 2026

    A transparent evidence pipeline keeps the website traceable to real sources while distinguishing direct rural evidence from research that still needs rural validation. Select a step to inspect its rules, evidence inputs, and output.

    1

    Define scope

    Set the review boundary, publication window, technical modules, and field-pilot evidence needed for RAV.

    Inspect this step
    2

    Search and identify

    Combine scholarly indexes, authoritative public sources, and citation chaining to locate relevant records.

    Inspect this step
    3

    Screen and deduplicate

    Retain direct rural evidence and documented transfer paths while removing duplicates and unverifiable items.

    Inspect this step
    4

    Verify and code

    Resolve every retained source and code its module, design, rural relevance, strength, and access status.

    Inspect this step
    Step 1 of 4

    Define scope

    Establish what counts as usable evidence before searching so the review remains focused and reproducible.

    Decision rule

    Include road-vehicle research with direct rural relevance or a documented pathway to rural RAV service.

    Evidence handled

    2014–2026 research across five technical modules plus operational field-pilot validation.

    Output

    A review framework linking technology, fleet operations, infrastructure, connectivity, cooperation, and pilots.

    Representative query or audit rule ("autonomous vehicle" OR "automated shuttle") AND (rural OR remote)
    Verification checklist
      Example decision

      Traceable artifact

      118 retained records 92 DOI records 14 arXiv records 12 authoritative pages 85 open-access records
      Inclusion, exclusion, coding, and limitations

      Included

      Peer-reviewed articles, conference papers, preprints, public reports, and official deployment pages with a direct rural focus or a documented technology transfer path to rural service.

      Excluded

      Duplicate versions, sources outside automated road transport, corrections or withdrawn items, unverifiable records, and items with no usable connection to the RAV framework.

      How to read the tags

      Evidence strength is a transparent review-team coding based on publication and study design. It is a screening aid, not a formal risk-of-bias score or quantitative meta-analysis.

      Known limitations

      Rural terminology is inconsistent, pilot reporting is uneven, and many transferable studies were conducted in urban or instrumented settings. Those gaps are shown explicitly rather than treated as rural proof.

      Reference List

      2014~2026

      All references from the review bibliography, grouped by RAV module. In Advanced mode, this list also follows the Reference Explorer filters and search.

      All 118 references are shown below.

      Citation

      How to cite this website

      For use in publications and presentations, please cite this interactive website as follows:

      Que, H., Zhu, T., & Yao, H. (2026). Rural autonomous vehicles: A literature review linking RAV challenges to research evidence and AV pilots [Interactive website]. College of Engineering, University of Georgia. https://uga-mobility-lab.github.io/rav-literature-review/

      These exports cite the current interactive website. The formal narrative review and its PDF/Word downloads are forthcoming.

      Quick navigation

      Search the review

      ↑↓ move Enter open Esc close