Tree

There is a problem

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

1418

reference: 692-tree-1
name: 1418
tree-preservation-order: undefined
692-tpo-1
uprn
address-text
point: POINT (-1.011439 50.882222)
geometry: MULTIPOLYGON (((-1.011368 50.882214,-1.011371 50.882228,-1.011381 50.882241,-1.011397 50.882251,-1.011416 50.882257,-1.011438 50.882260,-1.011460 50.882258,-1.011480 50.882251,-1.011496 50.882242,-1.011507 50.882229,-1.011510 50.882215,-1.011507 50.882201,-1.011497 50.882189,-1.011482 50.882179,-1.011462 50.882172,-1.011440 50.882170,-1.011418 50.882172,-1.011398 50.882178,-1.011382 50.882188,-1.011372 50.882200,-1.011368 50.882214)))
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