Repository navigation
Open
Labels
area: territoriesTerritory managementTerritory managementhelp wantedExtra attention is neededExtra attention is neededstatus: readyTriaged and ready to pick upTriaged and ready to pick uptype: featureNew capabilityNew capability
Description
Why
Today a territory is a list of addresses (entrances), and its outline is drawn around them. That fits towns surveyed building by building, but not two common cases:
- The classic territory drawn as an area: a few streets, a village, a rural sector. Publishers cover everything inside it. Listing every address is heavy, and in the country often impossible. It's also how congregations coming from other tools hold their territories.
- Places without stable addresses: markets, taxi ranks, book-sharing boxes, harbours, beaches. Today they can only be faked as addresses.
What we want
Any territory can have an area drawn on the map, whatever its type (door-to-door, businesses, phone…):
- a territory can be an area alone, addresses alone (as today), or both: an area plus the surveyed buildings inside it
- an area can be added to, or removed from, an existing territory
- everything else about a territory works the same for every kind: its card, its assignments, its status, the S-13, statistics, campaigns
Done when
- A manager can draw a territory's area on the map, adjust its points, and save it, when creating a territory or later.
- A territory with an area and no addresses is valid. A territory with addresses and no area works exactly as today.
- A territory's addresses must lie inside its area. The editor refuses an address outside it, or an area that would leave one of the territory's addresses out.
- Two areas can't overlap within the same territory type. The editor shows the neighbouring areas and refuses an overlapping one, saying which territory it collides with.
- The territory page and the territory card PDF show the area on the map. When the territory also has addresses, both appear.
- The territory list tells at a glance which territories have an area.
- Assignments, overdue status, the S-13 export, coverage statistics and publishing campaigns work for every kind. Statistics that count households say so plainly when a territory has none.
- Without a base map on the instance, the page explains that drawing an area needs one. Territories made of addresses stay fully usable.
- It's covered by tests, as described in the testing guide.
Out of scope
- Importing areas from KML or GeoJSON: feat(territories): import territory areas from KML or GeoJSON #573.
- Splitting or merging areas.
- New territory types.
To settle in this issue before coding
- When a manager adds an area to a territory that already has addresses, the outline drawn around them today can become the area's starting point. How exactly is to be defined: propose it here.
Where to look
- Territories: types, the editor, the outline around entrances, the card, campaigns, statistics.
- Maps: the base map the instance serves and its rules (a quiet base, our own controls, attribution always visible).
- Prior art for drawing an area: the congregation's perimeter on the « Carte de l'assemblée » settings page already lets an admin draw and edit a polygon.
- The architecture, coding conventions, row-level security and permissions guides.
New to the project? Start with CONTRIBUTING.md and the development setup.
Metadata
Metadata
Assignees
Labels
area: territoriesTerritory managementTerritory managementhelp wantedExtra attention is neededExtra attention is neededstatus: readyTriaged and ready to pick upTriaged and ready to pick uptype: featureNew capabilityNew capability
Type
Projects
- StatusShow more project fieldsLive
Activity
[-]Support zone-based territory type[/-][+]feat(territories): zone-based mode (polygon, no buildings)[/+][-]feat(territories): zone-based mode (polygon, no buildings)[/-][+]feat(territories): territories drawn as an area on the map[/+]mindsers commentedon Nov 19, 2026
Reopened and rewritten: the scope now covers the classic territory drawn as an area as well as places without addresses. A territory can have both an area and addresses, addresses must lie inside the area, and areas can't overlap within a type. Importing areas from KML/GeoJSON moved to #573.