Tree

There is a problem

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

1357

reference: 302-tree-1
name: 1357
tree-preservation-order: undefined
302-tpo-1
uprn
address-text
point: POINT (-1.026923 50.893603)
geometry: MULTIPOLYGON (((-1.026852 50.893595,-1.026855 50.893609,-1.026865 50.893622,-1.026880 50.893632,-1.026900 50.893639,-1.026922 50.893641,-1.026944 50.893639,-1.026964 50.893633,-1.026980 50.893623,-1.026990 50.893610,-1.026994 50.893597,-1.026991 50.893583,-1.026981 50.893570,-1.026965 50.893560,-1.026946 50.893553,-1.026924 50.893551,-1.026902 50.893553,-1.026882 50.893559,-1.026866 50.893569,-1.026856 50.893582,-1.026852 50.893595)))
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