Tree

There is a problem

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

1440

reference: 122-tree-1
name: 1440
tree-preservation-order: undefined
122-tpo-1
uprn
address-text
point: POINT (-1.031056 50.866844)
geometry: MULTIPOLYGON (((-1.031013 50.866839,-1.031015 50.866848,-1.031021 50.866855,-1.031030 50.866861,-1.031042 50.866865,-1.031055 50.866867,-1.031069 50.866866,-1.031081 50.866862,-1.031090 50.866856,-1.031096 50.866848,-1.031099 50.866840,-1.031097 50.866832,-1.031091 50.866824,-1.031081 50.866818,-1.031070 50.866814,-1.031057 50.866813,-1.031043 50.866814,-1.031031 50.866818,-1.031022 50.866824,-1.031016 50.866831,-1.031013 50.866839)))
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