Tree

There is a problem

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

0893

reference: 261-tree-1
name: 0893
tree-preservation-order: undefined
261-tpo-1
uprn
address-text
point: POINT (-0.944294 50.859052)
geometry: MULTIPOLYGON (((-0.944252 50.859047,-0.944254 50.859055,-0.944260 50.859063,-0.944269 50.859069,-0.944281 50.859073,-0.944294 50.859074,-0.944307 50.859073,-0.944319 50.859070,-0.944329 50.859064,-0.944335 50.859056,-0.944337 50.859048,-0.944335 50.859040,-0.944329 50.859032,-0.944320 50.859026,-0.944308 50.859022,-0.944295 50.859021,-0.944282 50.859022,-0.944270 50.859025,-0.944260 50.859031,-0.944254 50.859039,-0.944252 50.859047)))
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