News
Territorial resilience: first detailed mapping of the pilot site
5/8/2026 · by Coordination team
Water, food-bearing land, buildings, supply chains, local skills, weak points: the resilience mapping of an 8 km radius territory, delivered to the village.
Why mapping matters
Thinking resilience without mapping the concrete territory is fiction. Before deciding what to install, store, or pool, you need to know what already exists within a useful radius: accessible water sources, available cultivable land, recyclable building stock, present economic chains, mobilizable local skills, weak points (flood zones, fragile power line, single access road).
Method
Three months of combined work: exploitation of public data (geoportal, statistics agency, water agency), 38 interviews with residents and local actors (breeder, market gardener, country doctor, teacher, mayors), systematic physical walk-through of paths. Everything is recorded in an internal interactive map and a paper logbook (re-deployable without electricity).
What emerges
Three strong findings: (1) twice as much accessible water as the official map suggests, thanks to 12 unrecorded springs identified by elders, (2) dependence on a single road remains the major weak point, (3) three short food chains already ready to be densified. Local skills (carpentry, mechanics, care) exceed initial estimates.
Practical use
The mapping has become the steering tool for strategic decisions: prioritizing workstreams, land negotiations, stock sizing, and supply-chain partnerships. The method is documented for replication by local groups. More analysis on the territorial resilience ecology page.
Sources and methodology
This article relies on measured field data, interviews, and public references. The method is made traceable so every figure and statement can be verified or replicated.
Methodology: direct observations on the pilot site, cross-checked against the monthly reviews of the authoring team and discussions with relevant local coordinators. Any factual correction can be reported via the contact page.