Tree

There is a problem

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

1499

reference: 575-tree-1
name: 1499
tree-preservation-order: undefined
575-tpo-1
uprn
address-text
point: POINT (-0.971456 50.866928)
geometry: MULTIPOLYGON (((-0.971400 50.866922,-0.971402 50.866933,-0.971410 50.866943,-0.971422 50.866951,-0.971438 50.866956,-0.971456 50.866958,-0.971473 50.866956,-0.971489 50.866952,-0.971502 50.866944,-0.971510 50.866934,-0.971513 50.866923,-0.971511 50.866911,-0.971503 50.866901,-0.971491 50.866893,-0.971475 50.866888,-0.971457 50.866886,-0.971440 50.866888,-0.971424 50.866893,-0.971411 50.866901,-0.971403 50.866911,-0.971400 50.866922)))
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