{"id":"6a13701b9e96654a068ed0e6","title":"Parish Allocations","path":"how-to/committee/editing-content/area-maps/parish-allocations","contentMarkdown":"# Parish footpath observer allocations\n\nIf your area looks after footpaths, the area map can show a footpath observer's coverage parish by parish. Each parish is shaded **green where an observer is allocated** and **red where the slot is vacant**, so the gaps you need to recruit for stand out at a glance. Hovering over a parish shows who covers it.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/a863d14c-c7dd-4335-b003-a5e71bc06204.webp)\n\n*An area map, with Kent shown here as an example. Green parishes have a footpath observer, red ones are vacant; hovering shows the parish and its observer.*\n\n## Two ways to manage allocations\n\nYou can manage allocations one parish at a time on the map, or in bulk from a spreadsheet. Both update the same data, so use whichever suits the job.\n\n### 1. On the map, one parish at a time\n\nWith the site in edit mode, click a parish to open its popup. As an administrator you can then assign a member or mark the parish vacant.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/457e467d-8b27-4ba1-a557-e83ef65a806e.png)\n\n*Click a parish to open its popup: it shows the status and parish code, with an Assign member box and a Mark Vacant button.*\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/d3abd937-96de-4bb6-8229-b11b4197f20b.png)\n\n*Start typing in the Assign member box and pick the volunteer from the member list.*\n\nThe map updates straight away - the parish turns **green** once a volunteer is assigned, and **red** again if you mark it vacant.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/dd5bff87-e083-4b8e-8c31-84082f9ee7a3.png)\n\n*Allocated - the parish is green and the tooltip names the observer.*\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/d75ec9b5-8a94-4428-90da-080afca2be3e.webp)\n\n*Vacant - the parish is red until someone is assigned.*\n\n### 2. In bulk, from a CSV file\n\nTo set up or refresh a whole area at once, go to **Admin → System Settings → Maps → Parish Allocations**. Click **Choose CSV File** (or drag a file onto the drop zone), then **Import**. A summary reports how many rows were created, updated or had errors.\n\nThe file needs a header row. These are the columns it understands:\n\n| Column | Required? | What it does |\n|---|---|---|\n| `parishName` | **Required** | The parish name, for example Smarden. |\n| `parishCode` | **Required for the map to colour the parish** | The official ONS parish code, for example E04004856. The map shades each parish by matching this code, so a row without it still imports but the parish stays uncoloured. The codes are shown in the **Parish Code** column of the allocations table. |\n| `status` | Optional | `vacant` marks the parish red; anything else, including blank, counts as `allocated` (green). |\n| `assignee` | Optional | The observer's name. If it matches a member's name it is also linked to their record. |\n| `notes` | Optional | Free text, for your own reference. |\n\nOne further optional column, `assigneeMemberId`, links a row straight to a member by id and takes precedence over `assignee`, but naming the person in `assignee` is the usual way.\n\nThe **Current Allocations** list below shows every parish with its code, status and assignee. You can filter by name or code, sort any column, and drag the bottom edge to resize it. **Clear All Allocations** removes them all if you need to start again.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/243f3057-5729-4068-bad8-389ddfac5540.png)\n\n*The Parish Allocations tab: CSV import, the expected columns, and the live allocations table.*\n\n### Download a starter template\n\nRather than build the CSV from scratch, download the template below and edit it. It is seeded with real parish names and their official codes, a mix of allocated and vacant rows, and two worked examples showing the optional `assignee` and `notes` columns. Replace the rows with your own and import it on the Parish Allocations tab.\n\n## See also\n\n* [Configuring your area map](https://ngx-ramblers.org.uk/how-to/committee/editing-content/area-maps/configuring-the-map)\n* [Area Maps overview](https://ngx-ramblers.org.uk/how-to/committee/editing-content/area-maps)","contentHtml":"

Parish footpath observer allocations

\n

If your area looks after footpaths, the area map can show a footpath observer's coverage parish by parish. Each parish is shaded green where an observer is allocated and red where the slot is vacant, so the gaps you need to recruit for stand out at a glance. Hovering over a parish shows who covers it.

\n

\"\"

\n

An area map, with Kent shown here as an example. Green parishes have a footpath observer, red ones are vacant; hovering shows the parish and its observer.

\n

Two ways to manage allocations

\n

You can manage allocations one parish at a time on the map, or in bulk from a spreadsheet. Both update the same data, so use whichever suits the job.

\n

1. On the map, one parish at a time

\n

With the site in edit mode, click a parish to open its popup. As an administrator you can then assign a member or mark the parish vacant.

\n

\"\"

\n

Click a parish to open its popup: it shows the status and parish code, with an Assign member box and a Mark Vacant button.

\n

\"\"

\n

Start typing in the Assign member box and pick the volunteer from the member list.

\n

The map updates straight away - the parish turns green once a volunteer is assigned, and red again if you mark it vacant.

\n

\"\"

\n

Allocated - the parish is green and the tooltip names the observer.

\n

\"\"

\n

Vacant - the parish is red until someone is assigned.

\n

2. In bulk, from a CSV file

\n

To set up or refresh a whole area at once, go to Admin → System Settings → Maps → Parish Allocations. Click Choose CSV File (or drag a file onto the drop zone), then Import. A summary reports how many rows were created, updated or had errors.

\n

The file needs a header row. These are the columns it understands:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ColumnRequired?What it does
parishNameRequiredThe parish name, for example Smarden.
parishCodeRequired for the map to colour the parishThe official ONS parish code, for example E04004856. The map shades each parish by matching this code, so a row without it still imports but the parish stays uncoloured. The codes are shown in the Parish Code column of the allocations table.
statusOptionalvacant marks the parish red; anything else, including blank, counts as allocated (green).
assigneeOptionalThe observer's name. If it matches a member's name it is also linked to their record.
notesOptionalFree text, for your own reference.
\n

One further optional column, assigneeMemberId, links a row straight to a member by id and takes precedence over assignee, but naming the person in assignee is the usual way.

\n

The Current Allocations list below shows every parish with its code, status and assignee. You can filter by name or code, sort any column, and drag the bottom edge to resize it. Clear All Allocations removes them all if you need to start again.

\n

\"\"

\n

The Parish Allocations tab: CSV import, the expected columns, and the live allocations table.

\n

Download a starter template

\n

Rather than build the CSV from scratch, download the template below and edit it. It is seeded with real parish names and their official codes, a mix of allocated and vacant rows, and two worked examples showing the optional assignee and notes columns. Replace the rows with your own and import it on the Parish Allocations tab.

\n

See also

\n\n"}