---
id: ch10-polirural-legacy
type: spine
title: "The PoliRural legacy: what PoliRural+ inherited"
readingTime: 2
standalone: true
core: false
teaser: "Eight of nine pilots, a Digital Innovation Hub, an attractiveness index and a shared map: what the H2020 predecessor handed over, and what is new."
voice: thinker
parent: null
diagram: fig-polirural-legacy
recallQ: "What did PoliRural+ inherit from PoliRural (H2020), and what did it add?"
recallA: "It inherited eight of its nine pilots, the PoliRural Digital Innovation Hub (now part of Hub4Everybody), the Rural Attractiveness Explorer, the Atlas of Best Practices and Map Whiteboard. New are the GeoAI layer JackDaw, natural-language interfaces and broader data integration. The MAA tool came from Cities2030, not from PoliRural."
highlights:
  - "8 of the 9 PoliRural+ pilots continue from PoliRural"
  - "The PoliRural Hub moved from Liferay to Wagtail CMS and became part of Hub4Everybody"
  - "The MAA tool is the Multi-Actor Approach tool from Cities2030, not a PoliRural output"
status: accepted
concept: research-pillars
lang: en
lens: generic
depth: standard
formalism: none
visuality: balanced
lengthBand: standard
genre: explainer
state: edited
carriers: prose|diagram
---

PoliRural+ continues the H2020 project PoliRural: **8 of its 9 pilots carry on from it** (project fact sheet). The technical inheritance is listed in D4.1 §2.1.1.

## What was inherited

- **The PoliRural Digital Innovation Hub.** A place to share knowledge, tools and best practices, with social-space features (forums, blogs, wikis, science shops) on OpenStack cloud infrastructure. D4.1 notes that some components "require modernization" to keep up with AI and GeoAI.
- **The Rural Attractiveness Explorer**, which produces a composite Rural Attractiveness Index ([today's version](#c/rural-attractiveness)).
- **The Atlas of Best Practices**, refined under PoliRural, with region-specific practices from projects such as Enabling, Dalia and Data4Food2030.
- **Map Whiteboard**, which lets several parties edit spatial data on one map and store the results.
- **Pilot-specific action plans and methods** from each region.

D1.1 adds the Hub's history. The user portal moved from Liferay to **Wagtail CMS** to make content easier to edit, and it offered a geoportal, social communication, storyboards, data management and legislative support. The PoliRural Hub then became part of the more generic **Hub4Everybody** framework (D1.1 §2).

## What is new in PoliRural+

D4.1 names three gaps that advances in large language models and GeoAI made it possible to close: **JackDaw** as a GeoAI layer combining LLMs with geospatial analytics, simpler interfaces through natural-language interaction, and broader data integration, including IoT and European Data Spaces (§2.1.2). Components from Data4Food2030, THEROS and ALIANCE joined the stack.

One common confusion: the **MAA tool** is the Multi-Actor Approach tool. Social InnoLabs first developed it in the Cities2030 project, and PoliRural+ is redesigning it ([the tool](#c/maa-tool)).

**Sources:**
- D4.1 PoliRuralPlus platform design, §2.1.1 Key Components and Their Current State; §2.1.2 Gaps and Opportunities. [PDF](https://www.poliruralplus.eu/docs/162/D4.1_PoliRuralPlus_platform_design_v1.pdf)
- D1.1 Project Web Pages Update, §2 From PoliRural Hub to Hub4Everybody. [PDF](https://www.poliruralplus.eu/docs/139/Attachment_0_53.pdf)
- PoliRural+ public fact sheet (Grant Agreement facts), predecessor. [poliruralplus.eu](https://www.poliruralplus.eu/)