Tree

There is a problem

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

1793

reference: 986-tree-1
name: 1793
tree-preservation-order: undefined
986-tpo-1
uprn
address-text
point: POINT (-0.974167 50.858492)
geometry: MULTIPOLYGON (((-0.974082 50.858483,-0.974085 50.858499,-0.974097 50.858514,-0.974116 50.858527,-0.974139 50.858534,-0.974166 50.858537,-0.974192 50.858535,-0.974216 50.858527,-0.974235 50.858516,-0.974248 50.858501,-0.974252 50.858484,-0.974248 50.858467,-0.974236 50.858452,-0.974218 50.858440,-0.974194 50.858432,-0.974168 50.858429,-0.974142 50.858432,-0.974118 50.858439,-0.974099 50.858451,-0.974086 50.858466,-0.974082 50.858483)))
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