Tree

There is a problem

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

1357

reference: 304-tree-1
name: 1357
tree-preservation-order: undefined
304-tpo-1
uprn
address-text
point: POINT (-1.026822 50.893634)
geometry: MULTIPOLYGON (((-1.026779 50.893630,-1.026781 50.893638,-1.026787 50.893646,-1.026796 50.893652,-1.026808 50.893656,-1.026821 50.893657,-1.026835 50.893656,-1.026847 50.893652,-1.026856 50.893646,-1.026862 50.893639,-1.026865 50.893631,-1.026863 50.893622,-1.026857 50.893615,-1.026847 50.893609,-1.026836 50.893605,-1.026823 50.893603,-1.026809 50.893604,-1.026797 50.893608,-1.026788 50.893614,-1.026782 50.893622,-1.026779 50.893630)))
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