Tree

There is a problem

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

1499

reference: 567-tree-1
name: 1499
tree-preservation-order: undefined
567-tpo-1
uprn
address-text
point: POINT (-0.972285 50.866461)
geometry: MULTIPOLYGON (((-0.972243 50.866456,-0.972245 50.866464,-0.972250 50.866472,-0.972260 50.866478,-0.972271 50.866482,-0.972285 50.866483,-0.972298 50.866482,-0.972310 50.866478,-0.972319 50.866473,-0.972326 50.866465,-0.972328 50.866457,-0.972326 50.866448,-0.972320 50.866441,-0.972311 50.866435,-0.972299 50.866431,-0.972286 50.866429,-0.972261 50.866434,-0.972251 50.866440,-0.972245 50.866448,-0.972243 50.866456)))
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