Skip to main content

Listed Buildings

What it is

Listed Buildings are buildings and structures of special architectural or historic interest, protected under the Planning (Listed Buildings and Conservation Areas) Act 1990, and held on the National Heritage List for England (NHLE) by Historic England. They are graded:

  • Grade I — exceptional interest.
  • Grade II* — particularly important, more than special interest.
  • Grade II — special interest (the large majority).

How it's produced

Compiled and maintained by Historic England as part of the NHLE and published as open data. In the NHLE export, listed buildings are represented as point features (a location per entry), not building-footprint polygons.

Update frequency & currency

Continuously maintained as buildings are listed, amended, or delisted.

Spatial resolution / precision

A critical handling note: listed buildings are point geometry — a marker at each building's location, not its outline. This has a hard engineering consequence:

Engineering gotcha

Because listed buildings are points (in this dataset, a MULTIPOINT layer), area must never be calculated from themST_Area() on a point is meaningless. Spatial work uses intersection/proximity only. In the WildStack pipeline this is an explicit rule for constraint_listed_buildings.

Known limitations

  • Point location, not footprint. The marker doesn't delineate the building's extent or curtilage.
  • Curtilage complexity. Protection can extend to structures within a listed building's curtilage that aren't separately marked.
  • Heritage, not ecology. A planning constraint, not habitat evidence.

How it compares to Scheduled Monuments

Same publisher and source list, different regime and geometry — see the comparison table on the Scheduled Monuments profile. One line: Scheduled Monuments are polygons under the 1979 Act; Listed Buildings are points under the 1990 Act.

Role in BNG assessment

Briefing-pack context only in WildStack's stack — listed buildings inform the planning narrative but do not fire a BNG trigger and never contribute habitat parcels. They are handled by intersection/proximity only, never by area.

WildStack's take

Listed buildings are the textbook example of why geometry type is a data-literacy issue, not a technicality. They look like just another "heritage points" layer, but the point-versus-polygon distinction versus Scheduled Monuments is exactly what trips up naive spatial analysis — try to compute an area or a proper overlap from points and you get nonsense, silently. We treat the geometry type as a first-class fact about the dataset. On the planning side, the honest framing is the same as for any heritage layer: flag it, hand it to a heritage specialist, and don't let it distort the ecological assessment it has nothing to do with.

Official source

Last reviewed

5 July 2026. Revisit if the NHLE data distribution, the geometry representation, or the listing framework changes.