---
id: ch5-guide-mapwhiteboard
type: spine
title: "How to run a MapWhiteboard session with stakeholders"
readingTime: 2
standalone: true
core: false
teaser: "Everyone on one map, every cursor visible, every drawn line shared: how to run a workshop on boundaries or corridors, and what the Beta does not keep."
parent: null
diagram: fig-mapwhiteboard-session
recallQ: "What does the Beta MapWhiteboard share between participants, and what should a facilitator do because of its limits?"
recallA: "The Beta instance exchanges cursors between connected maps and features drawn on shared vector layers, so a group can navigate and draw together. It is not a full planning suite with moderation or saved annotations, so the facilitator should export or record the results of the session."
highlights:
  - "Beta: shared cursors and shared drawn features on OpenLayers maps"
  - "D4.1's fuller tool adds WMS layers, GeoJSON upload and download and new editable layers"
  - "Apulia used collaborative map work and vector drawing for municipal dialogue"
  - "No moderation or saved annotations yet: record the outcome yourself"
status: accepted
concept: vulture-mapwhiteboard
lang: en
lens: italy|slovakia
depth: intro..standard
formalism: none
visuality: balanced
lengthBand: standard
genre: worked-example
state: edited
carriers: prose|diagram
---

**When to use it:** a meeting has to agree on something that lives on a map, such as a boundary, a corridor, a land-use conflict or local assets (D4.2 §6.3).

## What you need

- **A session set up for you.** The pack gives no public address; MapWhiteboard runs in the web-mapping environment of the platform, and restricted sessions use its shared authentication (D4.2 §3.8). Ask your pilot's technical partner.
- A base map and the layers you want to discuss; GeoJSON data if you bring your own.
- One facilitator who keeps notes.

## Steps

1. **Open the shared map.** Pre-defined maps combine base layers with editable layers (D4.1 §6.9).
2. **Bring everyone in.** Each connected session shows the others' cursors live (D4.2 §3.8).
3. **Navigate together** to the place in question and let people point rather than describe.
4. **Draw on the shared layer.** Features drawn on a vector layer are exchanged between sessions, so each person sees the others' lines and areas (D4.2 §3.8).
5. **Add context, where your instance supports it.** D4.1 lists WMS layers, GeoJSON upload, user-created editable layers and simultaneous editing of attributes (§6.9).
6. **Secure the result.** Download the drawn features as GeoJSON or publish them through web services if available (D4.1 §6.9); otherwise capture them before the session ends.

## What you get

A shared visual workspace: synchronised cursors, exchanged features and a common map the group has inspected together (D4.2 §3.8).

## Pilot use

- **Apulia (Italy):** collaborative map work and vector drawing supported municipal dialogue on local territorial development and community engagement (D4.2 Table 7).
- **Slovakia:** MapWhiteboard was part of the set-up for participatory foresight and defining the rural-urban boundary (D4.2 Table 7).

## Watch out

- The Beta is a **new simplified instance**. It covers shared navigation and shared objects, not a participatory planning suite with workflow, moderation or **persistent annotations** (D4.2 §3.8).
- The feature list in D4.1 (TRL 7) describes the earlier, fuller tool. Check what your instance offers before the workshop.
- D4.2 wants MapWhiteboard linked to the MAA tool, the Hub and the advisory services; until then, record who said what in the [MAA tool](#c/maa-tool) or your minutes.

**Sources:**
- D4.2 PoliRuralPlus Platform Beta, §3.8 MapWhiteboard collaborative mapping; §6.2 Table 7; §6.3 Usability observations. [PDF](https://www.poliruralplus.eu/docs/421/D4.2_PoliRuralPlus_Platform_Beta.pdf)
- D4.1 PoliRuralPlus platform design, §6.9 MapWhiteboard Evolution. [PDF](https://www.poliruralplus.eu/docs/162/D4.1_PoliRuralPlus_platform_design_v1.pdf)