Tree

There is a problem

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

1499

reference: 717-tree-1
name: 1499
tree-preservation-order: undefined
717-tpo-1
uprn
address-text
point: POINT (-0.971282 50.865005)
geometry: MULTIPOLYGON (((-0.971239 50.865001,-0.971241 50.865009,-0.971247 50.865017,-0.971256 50.865023,-0.971268 50.865027,-0.971281 50.865028,-0.971295 50.865027,-0.971307 50.865023,-0.971316 50.865017,-0.971322 50.865010,-0.971325 50.865001,-0.971323 50.864993,-0.971317 50.864986,-0.971308 50.864979,-0.971283 50.864974,-0.971269 50.864975,-0.971257 50.864979,-0.971248 50.864985,-0.971242 50.864992,-0.971239 50.865001)))
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