Tree

There is a problem

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

1357

reference: 303-tree-1
name: 1357
tree-preservation-order: undefined
303-tpo-1
uprn
address-text
point: POINT (-1.026847 50.893582)
geometry: MULTIPOLYGON (((-1.026805 50.893577,-1.026806 50.893586,-1.026812 50.893593,-1.026822 50.893599,-1.026833 50.893603,-1.026847 50.893605,-1.026860 50.893604,-1.026872 50.893600,-1.026881 50.893594,-1.026888 50.893587,-1.026890 50.893578,-1.026888 50.893570,-1.026882 50.893562,-1.026873 50.893556,-1.026861 50.893552,-1.026848 50.893551,-1.026835 50.893552,-1.026823 50.893556,-1.026813 50.893562,-1.026807 50.893569,-1.026805 50.893577)))
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