Tree

There is a problem

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

1809

reference: 274-tree-1
name: 1809
tree-preservation-order: undefined
274-tpo-1
uprn
address-text
point: POINT (-0.979167 50.858770)
geometry: MULTIPOLYGON (((-0.979068 50.858759,-0.979072 50.858779,-0.979086 50.858796,-0.979107 50.858811,-0.979135 50.858820,-0.979166 50.858823,-0.979196 50.858820,-0.979224 50.858812,-0.979247 50.858798,-0.979261 50.858780,-0.979266 50.858761,-0.979262 50.858741,-0.979248 50.858724,-0.979227 50.858710,-0.979199 50.858701,-0.979168 50.858697,-0.979138 50.858700,-0.979110 50.858709,-0.979087 50.858722,-0.979073 50.858740,-0.979068 50.858759)))
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