Tree

There is a problem

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

1405

reference: 926-tree-1
name: 1405
tree-preservation-order: undefined
926-tpo-1
uprn
address-text
point: POINT (-1.032219 50.875839)
geometry: MULTIPOLYGON (((-1.032176 50.875834,-1.032178 50.875843,-1.032184 50.875850,-1.032194 50.875856,-1.032205 50.875860,-1.032219 50.875861,-1.032232 50.875860,-1.032244 50.875857,-1.032253 50.875851,-1.032259 50.875843,-1.032262 50.875835,-1.032260 50.875827,-1.032254 50.875819,-1.032245 50.875813,-1.032233 50.875809,-1.032220 50.875808,-1.032206 50.875809,-1.032194 50.875812,-1.032185 50.875818,-1.032179 50.875826,-1.032176 50.875834)))
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