Tree

There is a problem

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

1499

reference: 561-tree-1
name: 1499
tree-preservation-order: undefined
561-tpo-1
uprn
address-text
point: POINT (-0.972553 50.866513)
geometry: MULTIPOLYGON (((-0.972524 50.866510,-0.972525 50.866515,-0.972529 50.866520,-0.972543 50.866527,-0.972552 50.866528,-0.972569 50.866525,-0.972580 50.866516,-0.972581 50.866510,-0.972580 50.866505,-0.972576 50.866500,-0.972570 50.866496,-0.972562 50.866493,-0.972553 50.866492,-0.972536 50.866495,-0.972530 50.866499,-0.972526 50.866504,-0.972524 50.866510)))
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