Tree

There is a problem

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

1064

reference: 598-tree-1
name: 1064
tree-preservation-order: undefined
598-tpo-1
uprn
address-text
point: POINT (-1.020201 50.879849)
geometry: MULTIPOLYGON (((-1.020144 50.879843,-1.020147 50.879854,-1.020154 50.879864,-1.020167 50.879872,-1.020183 50.879877,-1.020200 50.879879,-1.020218 50.879877,-1.020234 50.879872,-1.020246 50.879865,-1.020255 50.879855,-1.020258 50.879844,-1.020255 50.879832,-1.020247 50.879822,-1.020235 50.879814,-1.020219 50.879809,-1.020202 50.879807,-1.020184 50.879809,-1.020168 50.879814,-1.020155 50.879822,-1.020147 50.879831,-1.020144 50.879843)))
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