Tree

There is a problem

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

1499

reference: 574-tree-1
name: 1499
tree-preservation-order: undefined
574-tpo-1
uprn
address-text
point: POINT (-0.971429 50.866897)
geometry: MULTIPOLYGON (((-0.971358 50.866890,-0.971362 50.866904,-0.971371 50.866916,-0.971387 50.866926,-0.971407 50.866933,-0.971428 50.866935,-0.971450 50.866933,-0.971470 50.866927,-0.971486 50.866917,-0.971497 50.866905,-0.971500 50.866891,-0.971497 50.866877,-0.971488 50.866864,-0.971472 50.866854,-0.971452 50.866848,-0.971430 50.866845,-0.971408 50.866847,-0.971388 50.866854,-0.971373 50.866863,-0.971362 50.866876,-0.971358 50.866890)))
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