Tree

There is a problem

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

1803

reference: 250-tree-1
name: 1803
tree-preservation-order: undefined
250-tpo-1
uprn
address-text
point: POINT (-0.995563 50.853288)
geometry: MULTIPOLYGON (((-0.995449 50.853275,-0.995454 50.853298,-0.995470 50.853318,-0.995495 50.853334,-0.995526 50.853345,-0.995561 50.853348,-0.995597 50.853345,-0.995629 50.853335,-0.995654 50.853320,-0.995671 50.853300,-0.995677 50.853277,-0.995672 50.853255,-0.995656 50.853235,-0.995631 50.853219,-0.995600 50.853208,-0.995565 50.853205,-0.995529 50.853208,-0.995497 50.853218,-0.995472 50.853233,-0.995455 50.853253,-0.995449 50.853275)))
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