Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

2023

reference: 144-tree-1
name: 2023
tree-preservation-order: undefined
144-tpo-1
uprn
address-text
point: POINT (-0.983157 50.785365)
geometry: MULTIPOLYGON (((-0.983100 50.785359,-0.983103 50.785371,-0.983111 50.785381,-0.983123 50.785389,-0.983139 50.785394,-0.983156 50.785396,-0.983174 50.785394,-0.983190 50.785389,-0.983203 50.785381,-0.983211 50.785371,-0.983214 50.785360,-0.983211 50.785349,-0.983203 50.785339,-0.983191 50.785331,-0.983175 50.785326,-0.983158 50.785324,-0.983140 50.785326,-0.983124 50.785331,-0.983112 50.785338,-0.983103 50.785348,-0.983100 50.785359)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

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

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL