Tree

There is a problem

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

1502

reference: 726-tree-1
name: 1502
tree-preservation-order: undefined
726-tpo-1
uprn
address-text
point: POINT (-0.988178 50.859877)
geometry: MULTIPOLYGON (((-0.988093 50.859868,-0.988097 50.859885,-0.988108 50.859900,-0.988127 50.859912,-0.988151 50.859920,-0.988177 50.859923,-0.988203 50.859920,-0.988227 50.859913,-0.988246 50.859901,-0.988259 50.859886,-0.988263 50.859869,-0.988259 50.859853,-0.988248 50.859838,-0.988229 50.859825,-0.988205 50.859818,-0.988179 50.859815,-0.988153 50.859817,-0.988129 50.859825,-0.988110 50.859836,-0.988097 50.859851,-0.988093 50.859868)))
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