Tree

There is a problem

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

1502

reference: 732-tree-1
name: 1502
tree-preservation-order: undefined
732-tpo-1
uprn
address-text
point: POINT (-0.988418 50.859590)
geometry: MULTIPOLYGON (((-0.988348 50.859582,-0.988351 50.859596,-0.988361 50.859609,-0.988376 50.859619,-0.988396 50.859626,-0.988418 50.859628,-0.988440 50.859626,-0.988460 50.859620,-0.988475 50.859610,-0.988486 50.859597,-0.988490 50.859584,-0.988486 50.859570,-0.988477 50.859557,-0.988461 50.859547,-0.988441 50.859540,-0.988420 50.859538,-0.988398 50.859540,-0.988378 50.859546,-0.988362 50.859556,-0.988351 50.859569,-0.988348 50.859582)))
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