Tree

There is a problem

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

0888

reference: 984-tree-1
name: 0888
tree-preservation-order: undefined
984-tpo-1
uprn
address-text
point: POINT (-0.968825 50.862928)
geometry: MULTIPOLYGON (((-0.968796 50.862925,-0.968801 50.862936,-0.968808 50.862940,-0.968824 50.862943,-0.968833 50.862943,-0.968841 50.862940,-0.968852 50.862931,-0.968853 50.862926,-0.968852 50.862920,-0.968848 50.862915,-0.968834 50.862908,-0.968825 50.862907,-0.968816 50.862908,-0.968808 50.862911,-0.968802 50.862915,-0.968796 50.862925)))
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