Tree

There is a problem

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

1499

reference: 897-tree-1
name: 1499
tree-preservation-order: undefined
897-tpo-1
uprn
address-text
point: POINT (-0.970518 50.865775)
geometry: MULTIPOLYGON (((-0.970404 50.865763,-0.970409 50.865785,-0.970425 50.865806,-0.970450 50.865822,-0.970481 50.865832,-0.970516 50.865836,-0.970551 50.865833,-0.970583 50.865823,-0.970609 50.865807,-0.970625 50.865787,-0.970631 50.865765,-0.970626 50.865743,-0.970611 50.865723,-0.970586 50.865707,-0.970554 50.865696,-0.970519 50.865692,-0.970484 50.865695,-0.970452 50.865705,-0.970427 50.865721,-0.970410 50.865741,-0.970404 50.865763)))
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