Tree

There is a problem

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

1002

reference: 874-tree-1
name: 1002
tree-preservation-order: undefined
874-tpo-1
uprn
address-text
point: POINT (-1.040074 50.873938)
geometry: MULTIPOLYGON (((-1.040003 50.873930,-1.040006 50.873944,-1.040016 50.873957,-1.040032 50.873967,-1.040051 50.873973,-1.040073 50.873976,-1.040095 50.873974,-1.040115 50.873968,-1.040131 50.873958,-1.040141 50.873945,-1.040145 50.873931,-1.040142 50.873918,-1.040132 50.873905,-1.040117 50.873895,-1.040097 50.873888,-1.040075 50.873886,-1.040053 50.873888,-1.040033 50.873894,-1.040017 50.873904,-1.040007 50.873916,-1.040003 50.873930)))
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