Tree

There is a problem

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

1102

reference: 765-tree-1
name: 1102
tree-preservation-order: undefined
765-tpo-1
uprn
address-text
point: POINT (-1.010794 50.886579)
geometry: MULTIPOLYGON (((-1.010723 50.886572,-1.010726 50.886586,-1.010736 50.886598,-1.010752 50.886609,-1.010771 50.886615,-1.010793 50.886617,-1.010815 50.886615,-1.010835 50.886609,-1.010851 50.886599,-1.010861 50.886587,-1.010865 50.886573,-1.010862 50.886559,-1.010852 50.886547,-1.010837 50.886537,-1.010817 50.886530,-1.010795 50.886528,-1.010773 50.886530,-1.010753 50.886536,-1.010737 50.886546,-1.010727 50.886558,-1.010723 50.886572)))
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