Skip to main content
Planning application data standard

POC This is a proof of concept viewer for the planning permission specifications - your feedback will help us to improve it.

Dataset

site

Records of development sites linked to planning applications

Fields

Reference

The reference for the site

Reference
reference
Cardinality
1
Datatype
string
Requirement level
MUST

No needs satisfied by this field.

Name

Plain-language name for the site so it can be referenced in discussions and reports

Reference
name
Cardinality
1
Datatype
string
Requirement level
SHOULD
Guidance

How to use it

Use a short name that people can recognise and use when discussing the site.

Use an established site, building or development name. Omit name where there is no meaningful established name. Use address-text to provide a readable description of an unaddressed site.

Examples

Good

  • Former Riverside Mill
  • Units 4 to 8, Beacon Industrial Estate

Avoid

  • Site 1
  • a site or planning application reference
  • the full description of the proposed development
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field address-text, field postcode, field uprns and field usrns satisfy need dd-need-094.
  • This field and field address-text, field postcode, field uprns and field usrns satisfy need dd-need-095.
  • This field and field address-text, field postcode, field uprns and field usrns satisfy need data-need-005.
Address Text

Plain-language address or description that helps identify the site location

Reference
address-text
Cardinality
1
Datatype
string
Requirement level
MUST
Guidance

How to use it

Provide a readable address or description that helps people identify the site location.

For an addressed site, use its postal address. For unaddressed land, describe its location using nearby roads, places or landmarks, for example Land north of Station Road. The site boundary remains the authoritative record of the site's extent.

Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field geometry and field site (dataset planning-application) satisfy need dd-need-051.
  • This field and field postcode, field uprns, field usrns and field name satisfy need dd-need-094.
  • This field and field postcode, field uprns, field usrns and field name satisfy need dd-need-095.
  • This field and field postcode, field uprns, field usrns and field name satisfy need data-need-005.
Postcode

Postcode for the site, where one is available

Reference
postcode
Cardinality
1
Datatype
string
Requirement level
SHOULD
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field address-text, field uprns, field usrns and field name satisfy need dd-need-094.
  • This field and field address-text, field uprns, field usrns and field name satisfy need dd-need-095.
  • This field and field address-text, field uprns, field usrns and field name satisfy need data-need-005.
UPRNs

UPRNs for existing properties and premises within the site boundary, where known

Reference
uprns
Cardinality
n
Datatype
string
Requirement level
SHOULD
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field address-text, field postcode, field usrns and field name satisfy need dd-need-094.
  • This field and field address-text, field postcode, field usrns and field name satisfy need dd-need-095.
  • This field and field address-text, field postcode, field usrns and field name satisfy need data-need-005.
USRNs

USRNs for streets associated with the site, where known

Reference
usrns
Cardinality
n
Datatype
string
Requirement level
SHOULD
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

  • This field and field address-text, field postcode, field uprns and field name satisfy need dd-need-094.
  • This field and field address-text, field postcode, field uprns and field name satisfy need dd-need-095.
  • This field and field address-text, field postcode, field uprns and field name satisfy need data-need-005.
Geometry

The boundary for the site

Reference
geometry
Cardinality
1
Datatype
multipolygon
Requirement level
MUST
Needs this field satisfies

Fields should only be added if they satisfy a user need. This field helps satisfy the following needs.

Examples

Site with an established name

This example shows that the site has its own stable reference. Its human-readable name, address and boundary help people identify it but do not replace that reference.

Example formats

Table

Field Value
reference site-2026-0123
name Former Crown Works
address-text Former Crown Works, 10 Example Street, London
postcode W1A 1AA
geometry POLYGON ((-0.1447 51.5166, -0.1442 51.5166, -0.1442 51.5162, -0.1447 51.5162, -0.1447 51.5166))

JSON

{
  "reference": "site-2026-0123",
  "name": "Former Crown Works",
  "address-text": "Former Crown Works, 10 Example Street, London",
  "postcode": "W1A 1AA",
  "geometry": "POLYGON ((-0.1447 51.5166, -0.1442 51.5166, -0.1442 51.5162, -0.1447 51.5162, -0.1447 51.5166))"
}

Needs satisfied by this dataset

Datasets should only be included in the specification if they satisfy user needs.

dd-need-051 fully satisfied, confidence high

Linked need: dd-need-051

Justification record: just-0027

This dataset is required to satisfy this need.

Recording a site dataset provides a way to show which land or buildings a proposal relates to, helping users understand the location and its context.

The geometry field provides the precise spatial extent. The address-text field gives a familiar plain-language address or description, including for sites that are better identified by describing the land or buildings.