Tree

There is a problem

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

1002

reference: 872-tree-1
name: 1002
tree-preservation-order: undefined
872-tpo-1
uprn
address-text
point: POINT (-1.040775 50.873587)
geometry: MULTIPOLYGON (((-1.040747 50.873584,-1.040748 50.873590,-1.040752 50.873595,-1.040766 50.873602,-1.040775 50.873603,-1.040784 50.873602,-1.040792 50.873599,-1.040798 50.873595,-1.040804 50.873585,-1.040803 50.873579,-1.040799 50.873574,-1.040792 50.873570,-1.040776 50.873567,-1.040767 50.873567,-1.040759 50.873570,-1.040753 50.873574,-1.040747 50.873584)))
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