Tree

There is a problem

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

1381

reference: 138-tree-1
name: 1381
tree-preservation-order: undefined
138-tpo-1
uprn
address-text
point: POINT (-1.031916 50.865204)
geometry: MULTIPOLYGON (((-1.031831 50.865195,-1.031835 50.865211,-1.031847 50.865227,-1.031865 50.865239,-1.031889 50.865247,-1.031915 50.865249,-1.031942 50.865247,-1.031966 50.865240,-1.031985 50.865228,-1.031997 50.865213,-1.032002 50.865196,-1.031998 50.865179,-1.031986 50.865164,-1.031967 50.865152,-1.031944 50.865144,-1.031917 50.865142,-1.031891 50.865144,-1.031867 50.865151,-1.031848 50.865163,-1.031836 50.865178,-1.031831 50.865195)))
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