Tree

There is a problem

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

2097

reference: 957-tree-1
name: 2097
tree-preservation-order: undefined
957-tpo-1
uprn
address-text
point: POINT (-0.975446 50.848987)
geometry: MULTIPOLYGON (((-0.975390 50.848980,-0.975392 50.848992,-0.975400 50.849002,-0.975412 50.849010,-0.975428 50.849015,-0.975446 50.849017,-0.975463 50.849015,-0.975479 50.849010,-0.975492 50.849002,-0.975500 50.848993,-0.975503 50.848981,-0.975501 50.848970,-0.975493 50.848960,-0.975480 50.848952,-0.975465 50.848947,-0.975447 50.848945,-0.975430 50.848947,-0.975414 50.848952,-0.975401 50.848959,-0.975393 50.848969,-0.975390 50.848980)))
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