Tree

There is a problem

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

0664

reference: 724-tree-1
name: 0664
tree-preservation-order: undefined
724-tpo-1
uprn
address-text
point: POINT (-0.982440 50.866992)
geometry: MULTIPOLYGON (((-0.982369 50.866984,-0.982372 50.866998,-0.982382 50.867011,-0.982397 50.867021,-0.982417 50.867027,-0.982439 50.867030,-0.982461 50.867028,-0.982481 50.867021,-0.982497 50.867012,-0.982507 50.866999,-0.982511 50.866985,-0.982508 50.866971,-0.982498 50.866959,-0.982482 50.866949,-0.982463 50.866942,-0.982441 50.866940,-0.982419 50.866942,-0.982399 50.866948,-0.982383 50.866958,-0.982373 50.866970,-0.982369 50.866984)))
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