Tree

There is a problem

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

0943

reference: 279-tree-1
name: 0943
tree-preservation-order: undefined
279-tpo-1
uprn
address-text
point: POINT (-0.973356 50.859076)
geometry: MULTIPOLYGON (((-0.973328 50.859073,-0.973329 50.859079,-0.973333 50.859084,-0.973339 50.859088,-0.973356 50.859091,-0.973365 50.859091,-0.973379 50.859084,-0.973385 50.859074,-0.973383 50.859068,-0.973379 50.859063,-0.973365 50.859056,-0.973357 50.859055,-0.973348 50.859056,-0.973333 50.859063,-0.973329 50.859068,-0.973328 50.859073)))
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