Tree

There is a problem

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

1499

reference: 715-tree-1
name: 1499
tree-preservation-order: undefined
715-tpo-1
uprn
address-text
point: POINT (-0.971466 50.866047)
geometry: MULTIPOLYGON (((-0.971381 50.866038,-0.971385 50.866055,-0.971396 50.866070,-0.971415 50.866082,-0.971438 50.866090,-0.971465 50.866093,-0.971491 50.866090,-0.971515 50.866083,-0.971534 50.866071,-0.971547 50.866056,-0.971551 50.866039,-0.971547 50.866023,-0.971536 50.866008,-0.971517 50.865995,-0.971493 50.865988,-0.971467 50.865985,-0.971441 50.865987,-0.971417 50.865995,-0.971398 50.866006,-0.971385 50.866021,-0.971381 50.866038)))
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