Skip to main content
Submit and update your planning data

Tree preservation order data

Version: 1.2.2
Published: 8 September 2023

This is guidance on how to meet the tree preservation order technical specification

There are 3 datasets you must provide for tree preservation orders:

Format

The tree preservation order dataset should be provided as a CSV file. You can provide the zone and individual tree data in one of these formats:

  • CSV
  • GeoJSON
  • GML
  • Geopackage

These may be uploaded to a single URL, or served via an OGC WFS or ArcGIS API.

Field names

You can provide fields names using hyphens, underscores or spaces.

For example:

  • start-date
  • start_date
  • start date

These are all valid, and any uppercase characters will be converted to lowercase.

Tree preservation order dataset

This dataset is about tree preservation orders (TPOs). These are orders made by local planning authorities to protect specific trees, groups of trees or woodlands.

The dataset must contain at least one entry (row) for each tree preservation order.

It must containing the following fields (columns):

reference

A reference or ID for each tree preservation order that is:

  • unique within your dataset
  • permanent - it doesn’t change when the dataset is updated

If you don’t use a reference already, you will need to create one. This can be a short set of letters or numbers.

Example: TPO1

name

This will be the title of the page hosting data about this tree preservation order on your website. This can be:

  • name
  • reference
  • address
  • blank

document-url

The URL of an authoritative order or notice designating the tree preservation order. If the TPO has been revoked, you can blank out this field.

Example: http://www.LPAwebsite.org.uk/tpo1.pdf

documentation-url

The URL of the webpage on your website that introduces the document.

Each document should be linked to from a documentation webpage that includes a short description of the data and the document you’re linking to. Each tree preservation order should have a unique URL. This means you can create a separate page for each one, or you could list several on one page. If you do that, there must be a separate anchor link (fragment identifier) for each one.

This means each section of your page should have its own URL. Most publishing systems will allow you to use a hashtag to create the identifiers for each tree preservation order you list - as in the examples shown.

Examples:

One tree preservation order per page:

http://www.LPAwebsite.org.uk/data/treepreservationorders/smithroad

More than one tree preservation order per page with an anchor link for each one:

http://www.LPAwebsite.org.uk/data/treepreservationorders#smithroad

http://www.LPAwebsite.org.uk/data/treepreservationorders#broadhousepark

notes

Optional text on how this data was or produced, or how it can be interpreted.

made-date

The date a tree preservation order was made available to the public. The tree or trees are temporarily protected from this date, until the order is confirmed.

Write in YYYY-MM-DD format.

Example: 2022-12-20

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

confirmed-date

The date a tree preservation order is confirmed as being in effect, and the tree or trees are fully protected. This comes after all objections have been considered.

Write in YYYY-MM-DD format.

Example: 2022-12-20

end-date

Where the tree preservation order is revoked, this should be the date that it was no longer in effect, written in YYYY-MM-DD format. If the TPO is still active, leave this field blank. If the tree has been felled, use the felled-date field.

Example: 1999-01-20

felled-date

If applicable, the date that the tree was felled, written in YYYY-MM-DD format. If the tree hasn’t been felled, leave this field blank.

entry-date

The date the entity was last updated.

If the entity has never been updated, enter the same date as start-date.

Write in YYYY-MM-DD format.

Example: 2022-12-20

Tree preservation zone dataset

This dataset is about tree preservation zones. These are areas of trees that are under a tree preservation order. You may also know them as tree preservation zones or groups.

The dataset must contain at least one entry (row) for each tree preservation zone.

It must containing the following fields (columns):

reference

A reference or ID for each tree preservation zone that is:

  • unique within your dataset
  • permanent - it doesn’t change when the dataset is updated

If you don’t use a reference already, you will need to create one. This can be a short set of letters or numbers.

Example: TPO1

name

This will be the display name of the page hosting data about this tree preservation zone on your website. This can be:

  • name
  • reference
  • address
  • blank

tree-preservation-order

The reference for the tree preservation order that covers this zone.

tree-preservation-zone-type

What sort of tree preservation zone this is.

This can be:

  • area
  • group
  • woodland

geometry

The boundary for the tree preservation zone as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

notes

Optional text on how this data was made or produced, or how it can be interpreted.

start-date

The date that the tree preservation order came into force, written in YYYY-MM-DD format.

Example: 1984-03-28

end-date

If applicable, the date that the tree preservation order was revoked, written in YYYY-MM-DD format. If it’s still in effect, leave the cell blank.

Example: 1999-01-20

entry-date

The date the entity was last updated.

If the entity has never been updated, enter the same date as start-date.

Write in YYYY-MM-DD format.

Example: 2022-12-20

Tree dataset

This dataset is about trees. These are individual trees that are under a tree preservation order.

The dataset must contain at least one entry (row) for each tree.

It must containing the following fields (columns):

reference

A reference or ID for each tree that is:

  • unique within your dataset
  • permanent - it doesn’t change when the dataset is updated

If you don’t use a reference already, you will need to create one. This can be a short set of letters or numbers.

Example: T1

name

This will be the title of the page hosting data about this tree preservation order on your website. This can be:

  • name
  • reference
  • address
  • blank

point

The approximate location of the centre of the tree.

You must provide a point or geometry for each tree. You may provide both.

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

uprn

If the tree has one, you can provide the Unique Property Reference Number (UPRN). Find the UPRN on GeoPlace.

If you provide the UPRN, you must also provide the address text.

address-text

If the tree has one, you can provide the address, written as text.

If you provide the address text, you must also provide the UPRN.

Example: 100 High Street, Bath

notes

Optional text on how this data was made or produced, or how it can be interpreted.

start-date

The date from which the tree preservation order affects the tree, written in YYYY-MM-DD format.

Example: 1984-03-28

end-date

Where the tree preservation order is revoked, this should be the date that it was no longer in effect, written in YYYY-MM-DD format. If the TPO is still active, leave this field blank. If the tree has been felled, use the felled-date field.

Example: 1999-01-20

felled-date

If applicable, the date that the tree was felled, written in YYYY-MM-DD format. If the tree hasn’t been felled, leave this field blank.

entry-date

The date the entity was last updated.

If the entity has never been updated, enter the same date as start-date.

Write in YYYY-MM-DD format.

Example: 2022-12-20

BETA This is a new service – your feedback will help us to improve it.