Tree

There is a problem

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

1499

reference: 893-tree-1
name: 1499
tree-preservation-order: undefined
893-tpo-1
uprn
address-text
point: POINT (-0.971111 50.866096)
geometry: MULTIPOLYGON (((-0.971068 50.866092,-0.971070 50.866100,-0.971076 50.866108,-0.971085 50.866114,-0.971097 50.866118,-0.971110 50.866119,-0.971124 50.866118,-0.971136 50.866114,-0.971145 50.866108,-0.971151 50.866101,-0.971154 50.866093,-0.971152 50.866084,-0.971146 50.866077,-0.971136 50.866071,-0.971125 50.866067,-0.971112 50.866065,-0.971098 50.866066,-0.971086 50.866070,-0.971077 50.866076,-0.971071 50.866084,-0.971068 50.866092)))
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