Tree

There is a problem

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

1102

reference: 756-tree-1
name: 1102
tree-preservation-order: undefined
756-tpo-1
uprn
address-text
point: POINT (-1.010185 50.888357)
geometry: MULTIPOLYGON (((-1.010128 50.888351,-1.010131 50.888362,-1.010138 50.888372,-1.010151 50.888380,-1.010167 50.888386,-1.010184 50.888387,-1.010202 50.888386,-1.010218 50.888381,-1.010230 50.888373,-1.010239 50.888363,-1.010242 50.888352,-1.010239 50.888341,-1.010231 50.888331,-1.010219 50.888323,-1.010203 50.888317,-1.010186 50.888316,-1.010168 50.888317,-1.010152 50.888322,-1.010139 50.888330,-1.010131 50.888340,-1.010128 50.888351)))
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