Tree preservation order
There are 2 datasets you must provide for Tree preservation orders:
Format
You can provide data in one of these formats:
- CSV
- GeoJSON
- GML
- Geopackage
For more information, see how to provide your data.
Tree preservation order dataset
This dataset is about conservation areas. These are areas where extra planning controls apply due to their special architectural and historic interest.
The dataset must contain at least one entry (row) for each tree preservation order
It must containing the following fields (columns):
confirmed-date
description
document-url
The URL of an authoritative order or notice designating the tree preservation order.
Example: http://www.LPAwebsite.org.uk/tpo1.pdf
documentation-url
The URL of the webpage citing the document.
Each document should be linked to on a documentation webpage that includes a short description of the data. The website URL should be unique for each tree preservation order, either by creating a separate page or a separate anchor (fragment identifier) for each one.
Example: http://www.LPAwebsite.org.uk/data#tpo1
end-date
If applicable, the date that the TPO was no longer in effect, written in YYYY-MM-DD format. If it's still in effect, leave the cell blank.
Example: 1999-01-20
entity
entry-date
The date this dataset was created or last updated, written in YYYY-MM-DD format.
Example: 2022-12-20
legislation
made-date
name
This will be the title of the page hosting data about this TPO on our website. This can be:
name reference address blank
notes
Optional text on how this data was made or produced, or how it can be interpreted.
organisation
prefix
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
start-date
The date that the TPO came into force, written in YYYY-MM-DD format.
Example: 1984-03-28
Tree dataset
This dataset is about conservation areas. These are areas where extra planning controls apply due to their special architectural and historic interest.
The dataset must contain at least one entry (row) for each tree
It must containing the following fields (columns):
address
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
description
end-date
If applicable, the date from which the tree preservation order no longer affects the tree, written in YYYY-MM-DD format. If it's still in effect, leave the cell blank.
Example: 1999-01-20
entry-date
The date this dataset was created or last updated, written in YYYY-MM-DD format.
Example: 2022-12-20
entity
entry-date
felled-date
geometry
The boundary of the tree as a single polygon or multipolygon value. Points must be in the WGS84 coordinate reference system.
This should be in GeoJSON format.
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...
name
This will be the title of the page hosting data about this TPO on our website. This can be:
name reference address blank
notes
Optional text on how this data was made or produced, or how it can be interpreted.
organisation
point
The approximate location of the centre of the tree.
You must provide a point or geometry for each tree. You may provide both.
prefix
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
start-date
The date from which the tree preservation order affects the tree, written in YYYY-MM-DD format.
Example: 1984-03-28
tree
tree-preservation-order
The reference for the tree preservation order that affects this tree.
Example: TPO1