Tree

There is a problem

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

1518

reference: 851-tree-1
name: 1518
tree-preservation-order: undefined
851-tpo-1
uprn
address-text
point: POINT (-0.969128 50.864975)
geometry: MULTIPOLYGON (((-0.969071 50.864969,-0.969073 50.864980,-0.969081 50.864990,-0.969094 50.864998,-0.969109 50.865004,-0.969127 50.865005,-0.969145 50.865004,-0.969161 50.864999,-0.969173 50.864991,-0.969182 50.864981,-0.969185 50.864970,-0.969182 50.864959,-0.969174 50.864949,-0.969162 50.864941,-0.969146 50.864935,-0.969129 50.864934,-0.969111 50.864935,-0.969095 50.864940,-0.969082 50.864948,-0.969074 50.864958,-0.969071 50.864969)))
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