Tree

There is a problem

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

1275

reference: 104-tree-1
name: 1275
tree-preservation-order: undefined
104-tpo-1
uprn
address-text
point: POINT (-1.005761 50.862091)
geometry: MULTIPOLYGON (((-1.005690 50.862083,-1.005693 50.862097,-1.005703 50.862110,-1.005718 50.862120,-1.005738 50.862126,-1.005760 50.862129,-1.005782 50.862127,-1.005802 50.862120,-1.005818 50.862110,-1.005828 50.862098,-1.005832 50.862084,-1.005829 50.862070,-1.005819 50.862058,-1.005803 50.862048,-1.005784 50.862041,-1.005762 50.862039,-1.005740 50.862041,-1.005720 50.862047,-1.005704 50.862057,-1.005693 50.862069,-1.005690 50.862083)))
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