Tree

There is a problem

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

0993

reference: 259-tree-1
name: 0993
tree-preservation-order: undefined
259-tpo-1
uprn
address-text
point: POINT (-0.935656 50.858810)
geometry: MULTIPOLYGON (((-0.935599 50.858804,-0.935601 50.858815,-0.935609 50.858825,-0.935622 50.858833,-0.935637 50.858838,-0.935655 50.858840,-0.935672 50.858838,-0.935688 50.858833,-0.935701 50.858826,-0.935709 50.858816,-0.935712 50.858805,-0.935710 50.858793,-0.935702 50.858783,-0.935690 50.858775,-0.935674 50.858770,-0.935656 50.858768,-0.935639 50.858770,-0.935623 50.858775,-0.935610 50.858782,-0.935602 50.858792,-0.935599 50.858804)))
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