Tree

There is a problem

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

1633

reference: 379-tree-1
name: 1633
tree-preservation-order: undefined
379-tpo-1
uprn
address-text
point: POINT (-1.026085 50.883917)
geometry: MULTIPOLYGON (((-1.026043 50.883913,-1.026045 50.883921,-1.026051 50.883928,-1.026060 50.883935,-1.026085 50.883940,-1.026098 50.883939,-1.026110 50.883935,-1.026120 50.883929,-1.026126 50.883922,-1.026128 50.883913,-1.026126 50.883905,-1.026120 50.883897,-1.026111 50.883891,-1.026099 50.883887,-1.026086 50.883886,-1.026073 50.883887,-1.026061 50.883891,-1.026051 50.883897,-1.026045 50.883904,-1.026043 50.883913)))
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