Address Counts
AGMT can count the number of addressable properties (buildings, houses, flats) within each shape. The method used depends on the region.
How It Works
Uses OS Open UPRN data loaded into a local DuckDB database. Every individual property has a precise coordinate — AGMT checks which ones fall within your shape boundary. No network request needed.
Queries the Overpass API for building data within your shape. Accuracy depends on how well-mapped the area is in OpenStreetMap.
| Region | Data Source | Accuracy |
|---|---|---|
| Leicester City | OS Open UPRN via DuckDB | Building-level precision |
| All other areas | OpenStreetMap / Overpass API | Varies by region |
The Counting Process (Leicester City)
For Leicester City, AGMT uses a smart two-path approach to count addresses as fast as possible:
- Your shape boundary is compared against every street's geographic bounds
- If a street fits entirely inside your shape → uses a pre-calculated total (instant)
- If a street partially overlaps → counts individual addresses one by one (thorough)
This is why you see and icons next to some building counts.
Learn what these icons mean →Other Areas — OpenStreetMap
For areas outside Leicester City, AGMT queries the Overpass API for building data within the shape boundary. Accuracy depends on how well-mapped the area is in OpenStreetMap.
Where Counts Appear
| Location | What you see |
|---|---|
| Sidebar → Streets tab | Per-shape street list with counts |
| Sidebar → Teams tab | Per-team aggregated totals |
| Planning Dashboard | Every street across all teams in one table |
Counts update automatically when you create, edit, or delete shapes.
All address counting happens locally in your browser. No address data is sent to any server.