Tree

There is a problem

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

1499

reference: 576-tree-1
name: 1499
tree-preservation-order: undefined
576-tpo-1
uprn
address-text
point: POINT (-0.971396 50.866915)
geometry: MULTIPOLYGON (((-0.971325 50.866907,-0.971328 50.866921,-0.971338 50.866934,-0.971353 50.866944,-0.971373 50.866950,-0.971395 50.866953,-0.971417 50.866951,-0.971437 50.866944,-0.971453 50.866935,-0.971463 50.866922,-0.971467 50.866908,-0.971464 50.866894,-0.971454 50.866882,-0.971438 50.866872,-0.971419 50.866865,-0.971397 50.866863,-0.971375 50.866865,-0.971355 50.866871,-0.971339 50.866881,-0.971328 50.866893,-0.971325 50.866907)))
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