Tree

There is a problem

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

1499

reference: 569-tree-1
name: 1499
tree-preservation-order: undefined
569-tpo-1
uprn
address-text
point: POINT (-0.972853 50.866521)
geometry: MULTIPOLYGON (((-0.972782 50.866514,-0.972785 50.866528,-0.972795 50.866540,-0.972811 50.866550,-0.972830 50.866557,-0.972852 50.866559,-0.972874 50.866557,-0.972894 50.866551,-0.972910 50.866541,-0.972920 50.866529,-0.972924 50.866515,-0.972921 50.866501,-0.972911 50.866489,-0.972896 50.866478,-0.972876 50.866472,-0.972854 50.866470,-0.972832 50.866472,-0.972812 50.866478,-0.972796 50.866488,-0.972786 50.866500,-0.972782 50.866514)))
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