Tree

There is a problem

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

1389

reference: 587-tree-1
name: 1389
tree-preservation-order: undefined
587-tpo-1
uprn
address-text
point: POINT (-1.036161 50.866443)
geometry: MULTIPOLYGON (((-1.036104 50.866437,-1.036107 50.866449,-1.036114 50.866459,-1.036127 50.866467,-1.036143 50.866472,-1.036160 50.866474,-1.036178 50.866472,-1.036194 50.866467,-1.036206 50.866459,-1.036215 50.866449,-1.036218 50.866438,-1.036215 50.866427,-1.036207 50.866417,-1.036195 50.866409,-1.036179 50.866404,-1.036162 50.866402,-1.036144 50.866403,-1.036128 50.866408,-1.036115 50.866416,-1.036107 50.866426,-1.036104 50.866437)))
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