Tree

There is a problem

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

1499

reference: 865-tree-1
name: 1499
tree-preservation-order: undefined
865-tpo-1
uprn
address-text
point: POINT (-0.971015 50.866995)
geometry: MULTIPOLYGON (((-0.970973 50.866990,-0.970974 50.866999,-0.970980 50.867006,-0.970990 50.867012,-0.971001 50.867016,-0.971015 50.867018,-0.971040 50.867013,-0.971049 50.867007,-0.971055 50.866999,-0.971058 50.866991,-0.971056 50.866983,-0.971050 50.866975,-0.971041 50.866969,-0.971029 50.866965,-0.971016 50.866964,-0.971003 50.866965,-0.970981 50.866974,-0.970975 50.866982,-0.970973 50.866990)))
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