Tree

There is a problem

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

1699

reference: 652-tree-1
name: 1699
tree-preservation-order: undefined
652-tpo-1
uprn
address-text
point: POINT (-1.006861 50.863746)
geometry: MULTIPOLYGON (((-1.006720 50.863731,-1.006726 50.863758,-1.006746 50.863784,-1.006777 50.863804,-1.006816 50.863817,-1.006860 50.863822,-1.006904 50.863818,-1.006944 50.863805,-1.006976 50.863786,-1.006996 50.863761,-1.007004 50.863733,-1.006997 50.863705,-1.006978 50.863680,-1.006947 50.863660,-1.006907 50.863647,-1.006864 50.863642,-1.006820 50.863646,-1.006780 50.863658,-1.006748 50.863678,-1.006727 50.863703,-1.006720 50.863731)))
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