Tree

There is a problem

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

1576

reference: 356-tree-1
name: 1576
tree-preservation-order: undefined
356-tpo-1
uprn
address-text
point: POINT (-1.047136 50.892750)
geometry: MULTIPOLYGON (((-1.047036 50.892739,-1.047041 50.892758,-1.047055 50.892776,-1.047076 50.892790,-1.047104 50.892799,-1.047135 50.892803,-1.047165 50.892800,-1.047193 50.892791,-1.047216 50.892777,-1.047230 50.892760,-1.047235 50.892741,-1.047231 50.892721,-1.047217 50.892703,-1.047195 50.892689,-1.047168 50.892680,-1.047137 50.892677,-1.047106 50.892680,-1.047078 50.892688,-1.047056 50.892702,-1.047042 50.892720,-1.047036 50.892739)))
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