---
id: ch10-ai-rural
type: spine
title: "AI in rural planning: grounded, cited and checked"
readingTime: 3
standalone: true
core: true
teaser: "The Beta showed that maps plus plain language help non-GIS users. It also showed what an AI answer needs before a planner can rely on it."
voice: thinker
parent: null
diagram: fig-grounded-ai-rules
recallQ: "Under what conditions does D4.2 consider AI answers usable for planning decisions?"
recallA: "When they are grounded in reliable data and structured metadata, with clear provenance, appropriate tool selection and openly stated limits. Outputs must show sources, data validity and limitations, and people validate what the AI extracts or proposes."
highlights:
  - "Main positive pilot finding: map interaction combined with plain-language dialogue"
  - "Four rules: a controlled corpus, visible sources and limits, human validation, sensitive data kept in-house"
  - "Open problems: uneven local data and metadata, local languages and place names, technical noise in answers"
status: accepted
concept: grounded-ai-planning
conceptTitle: "Grounded AI for rural planning"
parents: geoai
lang: en
lens: generic
depth: standard
formalism: none
visuality: balanced
lengthBand: standard
genre: explainer
state: core
carriers: prose|diagram
---

How JackDaw works is explained under [JackDaw](#c/jackdaw). This block covers what the Beta taught about using AI in planning at all.

## What worked

The main positive usability finding from the pilots is the **combination of map-based interaction with plain-language dialogue**. It helps users who need territorial evidence but do not work with advanced GIS, and it links spatial evidence to planning questions and stakeholder discussions (D4.2 §6.3). In the MAA tool, the Ramon assistant extracted stakeholders and objectives from pilot documents, and users then validated them, which reduced administrative effort (§6.3).

## Conditions for trust

D4.2 concludes that natural-language interfaces help people reach complex spatial resources **when they are connected to structured metadata, validated datasets and controlled analytical services**. AI interaction "must remain grounded in reliable data, clear provenance, appropriate tool selection and transparent communication of limitations" (§12). In practice this means four rules:

1. **Retrieve from a controlled corpus.** The Advisor runs as a private RAG over project-related collections, not the open web (§3.7).
2. **Show sources, data validity and limits** in every output meant for users, as a corrective action before wider deployment (§6.4).
3. **Keep people validating.** Ramon's proposals are created only after a user confirms them. Following FAIR2Adapt, claims extracted from documents need provenance and expert review before anyone treats them as reliable (§3.9, §9.4).
4. **Keep sensitive data at home.** MCP-based integration, local deployment and metadata-driven tool selection allow setups where data stays inside an institution, as public administrations and paying agencies require (§9.6).

## What still fails

The pilots name heterogeneous local data, uneven metadata completeness, different levels of technical skill, and the need for outputs that non-technical stakeholders can understand (§6.3). The roadmap adds linguistic robustness, the handling of local place names, the reliability of spatial queries, and removing unnecessary technical detail from answers (§11.1). Advisor testers also met a wrong programme reference that was corrected later in the dialogue (D2.3 Annex B).

## Where it is heading

The planned next steps are a Knowledge Graph behind the RAG, for entity linking and transparent evidence trails (§3.7), and continuous testing that includes the quality of AI responses (§11.1). The open problems are set out in the depth block that follows. The [public outputs](#c/research-outputs) include SHIELD, which filters unsafe or irrelevant queries before the AI responds.

**Sources:**
- D4.2 PoliRuralPlus Platform Beta, §3.7; §3.9; §6.3 Usability, performance and functional observations; §6.4 Issues, limitations and corrective actions; §9.4 FAIR2Adapt; §9.6 Lessons for sustainability; §11.1; §12 Conclusions. [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)
- D2.3 Rural-urban data analysis, Annex B Structured Evaluation of the PoliRuralPlus Services. [PDF](https://www.poliruralplus.eu/docs/382/D2.3_Rural_Urban_data_analysis_v1.0.pdf)