Tree

There is a problem

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

1224

reference: 746-tree-1
name: 1224
tree-preservation-order: undefined
746-tpo-1
uprn
address-text
point: POINT (-1.006906 50.884694)
geometry: MULTIPOLYGON (((-1.006835 50.884686,-1.006838 50.884700,-1.006848 50.884713,-1.006864 50.884723,-1.006883 50.884730,-1.006905 50.884732,-1.006927 50.884730,-1.006947 50.884724,-1.006963 50.884714,-1.006973 50.884702,-1.006977 50.884688,-1.006974 50.884674,-1.006964 50.884661,-1.006949 50.884651,-1.006929 50.884644,-1.006907 50.884642,-1.006885 50.884644,-1.006865 50.884650,-1.006849 50.884660,-1.006839 50.884673,-1.006835 50.884686)))
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