Tree

There is a problem

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

1499

reference: 863-tree-1
name: 1499
tree-preservation-order: undefined
863-tpo-1
uprn
address-text
point: POINT (-0.971023 50.866868)
geometry: MULTIPOLYGON (((-0.970966 50.866862,-0.970969 50.866873,-0.970976 50.866883,-0.970989 50.866891,-0.971005 50.866896,-0.971022 50.866898,-0.971040 50.866896,-0.971056 50.866891,-0.971068 50.866884,-0.971077 50.866874,-0.971080 50.866863,-0.971077 50.866851,-0.971069 50.866841,-0.971057 50.866833,-0.971041 50.866828,-0.971024 50.866826,-0.971006 50.866828,-0.970990 50.866833,-0.970977 50.866841,-0.970969 50.866851,-0.970966 50.866862)))
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