Tree

There is a problem

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

0943

reference: 985-tree-1
name: 0943
tree-preservation-order: undefined
985-tpo-1
uprn
address-text
point: POINT (-0.973302 50.859069)
geometry: MULTIPOLYGON (((-0.973274 50.859066,-0.973275 50.859071,-0.973285 50.859081,-0.973302 50.859084,-0.973319 50.859081,-0.973325 50.859077,-0.973329 50.859072,-0.973331 50.859066,-0.973325 50.859056,-0.973319 50.859052,-0.973303 50.859048,-0.973286 50.859051,-0.973275 50.859060,-0.973274 50.859066)))
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