Tree

There is a problem

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

1550

reference: 990-tree-1
name: 1550
tree-preservation-order: undefined
990-tpo-1
uprn
address-text
point: POINT (-1.018199 50.875847)
geometry: MULTIPOLYGON (((-1.018142 50.875841,-1.018145 50.875852,-1.018153 50.875862,-1.018165 50.875870,-1.018181 50.875876,-1.018198 50.875878,-1.018216 50.875876,-1.018232 50.875871,-1.018244 50.875863,-1.018253 50.875853,-1.018256 50.875842,-1.018253 50.875831,-1.018245 50.875821,-1.018233 50.875813,-1.018217 50.875808,-1.018200 50.875806,-1.018182 50.875807,-1.018166 50.875812,-1.018153 50.875820,-1.018145 50.875830,-1.018142 50.875841)))
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