Tree

There is a problem

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

1622

reference: 967-tree-1
name: 1622
tree-preservation-order: undefined
967-tpo-1
uprn
address-text
point: POINT (-0.994416 50.857524)
geometry: MULTIPOLYGON (((-0.994359 50.857518,-0.994362 50.857529,-0.994370 50.857539,-0.994382 50.857547,-0.994398 50.857552,-0.994416 50.857554,-0.994433 50.857553,-0.994449 50.857548,-0.994462 50.857540,-0.994470 50.857530,-0.994473 50.857519,-0.994471 50.857508,-0.994463 50.857498,-0.994450 50.857490,-0.994435 50.857484,-0.994417 50.857482,-0.994399 50.857484,-0.994384 50.857489,-0.994371 50.857497,-0.994362 50.857507,-0.994359 50.857518)))
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