Tree

There is a problem

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

1341

reference: 387-tree-1
name: 1341
tree-preservation-order: undefined
387-tpo-1
uprn
address-text
point: POINT (-1.028756 50.882551)
geometry: MULTIPOLYGON (((-1.028714 50.882546,-1.028716 50.882555,-1.028722 50.882562,-1.028731 50.882568,-1.028743 50.882572,-1.028756 50.882574,-1.028781 50.882569,-1.028791 50.882563,-1.028797 50.882555,-1.028799 50.882547,-1.028797 50.882539,-1.028791 50.882531,-1.028782 50.882525,-1.028770 50.882521,-1.028757 50.882520,-1.028744 50.882521,-1.028732 50.882525,-1.028722 50.882531,-1.028716 50.882538,-1.028714 50.882546)))
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