Tree

There is a problem

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

1386

reference: 833-tree-1
name: 1386
tree-preservation-order: undefined
833-tpo-1
uprn
address-text
point: POINT (-1.043819 50.857417)
geometry: MULTIPOLYGON (((-1.043776 50.857412,-1.043778 50.857421,-1.043784 50.857428,-1.043793 50.857434,-1.043805 50.857438,-1.043818 50.857440,-1.043831 50.857439,-1.043843 50.857435,-1.043853 50.857429,-1.043859 50.857421,-1.043861 50.857413,-1.043859 50.857405,-1.043854 50.857397,-1.043844 50.857391,-1.043832 50.857387,-1.043819 50.857386,-1.043806 50.857387,-1.043794 50.857391,-1.043785 50.857397,-1.043778 50.857404,-1.043776 50.857412)))
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