Tree

There is a problem

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

1274

reference: 646-tree-1
name: 1274
tree-preservation-order: undefined
646-tpo-1
uprn
address-text
point: POINT (-1.046823 50.863772)
geometry: MULTIPOLYGON (((-1.046767 50.863766,-1.046769 50.863778,-1.046777 50.863788,-1.046789 50.863796,-1.046805 50.863801,-1.046823 50.863803,-1.046840 50.863801,-1.046856 50.863796,-1.046869 50.863788,-1.046877 50.863778,-1.046880 50.863767,-1.046878 50.863756,-1.046870 50.863746,-1.046857 50.863738,-1.046842 50.863733,-1.046824 50.863731,-1.046807 50.863733,-1.046791 50.863738,-1.046778 50.863745,-1.046770 50.863755,-1.046767 50.863766)))
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