Tree

There is a problem

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

1417

reference: 172-tree-1
name: 1417
tree-preservation-order: undefined
172-tpo-1
uprn
address-text
point: POINT (-0.945269 50.862469)
geometry: MULTIPOLYGON (((-0.945184 50.862460,-0.945188 50.862477,-0.945200 50.862492,-0.945218 50.862504,-0.945242 50.862512,-0.945268 50.862515,-0.945295 50.862513,-0.945319 50.862505,-0.945338 50.862493,-0.945350 50.862478,-0.945355 50.862462,-0.945351 50.862445,-0.945339 50.862430,-0.945321 50.862418,-0.945297 50.862410,-0.945271 50.862407,-0.945244 50.862409,-0.945220 50.862417,-0.945201 50.862429,-0.945189 50.862444,-0.945184 50.862460)))
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