Tree

There is a problem

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

1185

reference: 888-tree-1
name: 1185
tree-preservation-order: undefined
888-tpo-1
uprn
address-text
point: POINT (-1.018577 50.879317)
geometry: MULTIPOLYGON (((-1.018520 50.879310,-1.018522 50.879322,-1.018530 50.879332,-1.018543 50.879340,-1.018558 50.879345,-1.018576 50.879347,-1.018593 50.879345,-1.018609 50.879340,-1.018622 50.879332,-1.018630 50.879323,-1.018633 50.879311,-1.018631 50.879300,-1.018623 50.879290,-1.018611 50.879282,-1.018595 50.879277,-1.018577 50.879275,-1.018560 50.879277,-1.018544 50.879282,-1.018531 50.879289,-1.018523 50.879299,-1.018520 50.879310)))
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