Grounds boundaries and building footprints: choosing the right geometry


A polygon can describe land, a building or proposed works. Knowing which one you have is essential before using it to measure property exposure.

It is easy to put two shapes on a map and assume they describe the same thing. Both surround an address. Both have an area. Both may arrive in a property-data response. Yet one could include a house, its garden and a garage, while the other traces only the building.

Using the wrong shape can change the answer even when the spatial calculation is technically correct.

Start with the object being represented

A building footprint describes a building's horizontal extent according to the source and method used to create it. Details such as roof overhangs, attached structures and how adjoining buildings are separated depend on that method.

A land polygon answers a different question. HM Land Registry describes its INSPIRE Index Polygons as showing the position and indicative extent of registered property in England and Wales. The official guidance is the appropriate starting point for understanding their scope and conditions of use.

Chimnie's grounds_polygon field is defined using the INSPIRE polygon in which the property lies. It should not be relabelled as an AI-derived building footprint or treated as a surveyed boundary. Building-footprint development is a separate task with its own evidence and quality checks.

Planning geometry adds another distinction: the area associated with an application can include access, landscaping or a wider site, rather than only the structure proposed for construction.

Match the geometry to the decision

Imagine a fictional house beside a river. Part of its garden overlaps a flood-hazard surface, but the building footprint does not. A test using the grounds polygon identifies overlap. A test using the footprint produces a different result.

Neither result should be converted automatically into 'the house floods' or 'the house is safe'. Each answers a narrower spatial question. The decision may also require floor levels, hazard resolution, defences and the vulnerability of the building.

For a lender reviewing a site, the grounds may be relevant to understanding the wider holding. For an insurer considering structures, the footprint may be the more useful starting point. A separate garage or outbuilding may need its own treatment.

Write down the object and the relationship being tested before choosing a spatial operation. Intersection, containment, nearest distance and percentage overlap are not interchangeable.

Check the join as carefully as the shape

An accurate polygon linked to the wrong property still produces a wrong answer. Review cases involving flats, terraces, large campuses and properties with several structures. Some relationships are one-to-many, and a single address point may not identify every relevant feature.

Check coordinate systems before measuring distance or area. Chimnie's grounds geometry is documented in British National Grid; other sources may use longitude and latitude. A transformation must be explicit and tested.

Also retain the source, version and derivation. Where the available geometry is incomplete or ambiguous, route the case for review rather than filling the gap with an apparently precise shape.

The value of spatial data comes from answering a defined property question consistently. A clear description of what a polygon represents is therefore part of the product, alongside the coordinates themselves.


Talk to Chimnie about your spatial use case, including the object you need to assess and the evidence required to validate the match.

Put this data to work

Everything discussed here is available through the Chimnie API, with up to £16 of free balance to try it.

© 2026 Chimnie is a trading name of Little Chimney Limited. All rights reserved.

London, United Kingdom · hello@chimnie.com