---
id: ch10-overview
type: spine
title: "Four research questions behind the PoliRural+ platform"
readingTime: 3
standalone: true
core: true
teaser: "Grounded GeoAI, metadata, participation, territorial systems: what PoliRural+ tries to prove, how it tests it, and where its tools are reused."
voice: universal
parent: null
diagram: diagram-research-pillars
recallQ: "What are the four research pillars of PoliRural+, and how does the project show that its tools work beyond the pilots?"
recallA: "Grounded GeoAI, metadata and FAIR data, participation and foresight, and systems and territorial analysis. Reuse in FOCAL, BioClima, INTERESH, FAIR2Adapt and KijaniSpace shows the components working in climate, biodiversity, soil-health, FAIR-data and international settings."
highlights:
  - "Four pillars, each tied to a platform component and a public deliverable"
  - "Usability is tested with cognitive walkthroughs, the System Usability Scale and pilot-by-pilot validation"
  - "Five partner projects reuse PoliRural+ assets such as JackDaw, Hub4Everybody, SensLog and the MAA tool"
  - "Sustainability means a stable open core kept separate from project-specific configurations"
status: accepted
concept: research-pillars
conceptTitle: "Research pillars of PoliRural+"
parents: polirural-plus-project
lang: en
lens: generic
depth: standard
formalism: none
visuality: balanced
lengthBand: standard
genre: explainer
state: core
carriers: prose|table|diagram
---

PoliRural+ is a Horizon Europe Innovation Action (January 2024 to December 2026) coordinated by the Czech Technical University in Prague (project fact sheet). Its research follows from what the platform and the [pilots](#c/pilot-network) have to prove.

| Pillar | Research question | Where the evidence is |
|---|---|---|
| **Grounded GeoAI** | Can plain-language AI answer territorial questions from traceable data? | JackDaw, the Advisor, GeoRAG (D4.2 §3.7, §12) |
| **Metadata and FAIR data** | Can metadata, rather than code, decide which data and tools apply? | Raven, Magpie, the FAIR2Adapt cooperation (D4.2 §3.2, §9.4) |
| **Participation and foresight** | Can multi-actor engagement and foresight become traceable workflows? | The MAA tool, revised RAPs (D4.2 §3.9; D2.3 §5) |
| **Systems and territory** | Where and how do rural-urban linkages work? | System dynamics (objective O6, pilot TP1), a 1 km innovation-potential grid (D4.2 §3.10), a literature review (D2.3 §3) |

## How the project tests its tools

The tools are evaluated with established usability methods. The Advisor went through a **cognitive walkthrough**, the **System Usability Scale** (on which 68 is the average score) and a feedback form that includes a Net Promoter question (D2.3 Annex B). The Beta platform is tested pilot by pilot. The criteria are functional correctness, ease of onboarding, data readiness, interoperability, language, responsiveness on real networks, relevance to planning tasks, and whether users understand where results come from (D4.2 §6.1). So far this validation has been case-by-case and qualitative. For the final release (D4.3), it moves to systematic consultation with WP5 (D4.2 §11.1).

## Research that travels: five partner projects

| Project | Focus | What is reused or exchanged |
|---|---|---|
| FOCAL | Local climate services, Earth observation processing | JackDaw querying climate data through STAC and OGC API – Records catalogues |
| BioClima | Biodiversity and climate monitoring | Hub4Everybody, SensLog sensor data, JackDaw as an analytical orchestrator |
| INTERESH | Soil-health Living Labs | The MAA tool, Hub4Everybody, SensLog, JackDaw-based retrieval |
| FAIR2Adapt | FAIR data for climate adaptation | Provenance, RO-Crate and I-ADOPT patterns brought into PoliRural+ |
| KijaniSpace | Climate-smart farming, Lake Victoria Basin | Hybrid Hub4Everybody deployment, sensor integration, a multilingual JackDaw |

(D4.2 §9.1–9.5)

D4.2 draws one lesson from these cooperations. Reuse needs a **stable open core** of generic assets kept separate from project-specific configurations, such as local datasets, vocabularies and licences. It also needs documentation, training and maintenance (§9.6). The [tool ecosystem](#c/tool-ecosystem) is built around that split.

**Sources:**
- D4.2 PoliRuralPlus Platform Beta, §3.2, §3.7, §3.9, §3.10; §6.1 Testing methodology; §9.1–9.6 cross-project cooperation; §11.1; §12 Conclusions. [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)
- D2.3 Rural-urban data analysis, §3 Literature Review; §5 Key Learnings; Annex B Structured Evaluation. [PDF](https://www.poliruralplus.eu/docs/382/D2.3_Rural_Urban_data_analysis_v1.0.pdf)
- PoliRural+ public fact sheet (Grant Agreement facts), objective O6, technical pilots. [poliruralplus.eu](https://www.poliruralplus.eu/)