Tree

There is a problem

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

1565

reference: 335-tree-1
name: 1565
tree-preservation-order: undefined
335-tpo-1
uprn
address-text
point: POINT (-1.028081 50.863785)
geometry: MULTIPOLYGON (((-1.028053 50.863782,-1.028054 50.863788,-1.028058 50.863793,-1.028064 50.863797,-1.028081 50.863800,-1.028098 50.863797,-1.028104 50.863793,-1.028110 50.863783,-1.028105 50.863772,-1.028090 50.863765,-1.028082 50.863764,-1.028073 50.863765,-1.028065 50.863768,-1.028054 50.863777,-1.028053 50.863782)))
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