Tree

There is a problem

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

0993

reference: 257-tree-1
name: 0993
tree-preservation-order: undefined
257-tpo-1
uprn
address-text
point: POINT (-0.935743 50.858960)
geometry: MULTIPOLYGON (((-0.935686 50.858954,-0.935689 50.858965,-0.935697 50.858975,-0.935709 50.858983,-0.935725 50.858989,-0.935742 50.858991,-0.935760 50.858989,-0.935776 50.858984,-0.935789 50.858976,-0.935797 50.858966,-0.935800 50.858955,-0.935797 50.858944,-0.935790 50.858934,-0.935777 50.858926,-0.935762 50.858921,-0.935744 50.858919,-0.935726 50.858920,-0.935710 50.858925,-0.935698 50.858933,-0.935689 50.858943,-0.935686 50.858954)))
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