Tree

There is a problem

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

1206

reference: 813-tree-1
name: 1206
tree-preservation-order: undefined
813-tpo-1
uprn
address-text
point: POINT (-1.008845 50.889599)
geometry: MULTIPOLYGON (((-1.008760 50.889590,-1.008764 50.889607,-1.008776 50.889622,-1.008795 50.889634,-1.008818 50.889642,-1.008844 50.889645,-1.008871 50.889642,-1.008895 50.889635,-1.008914 50.889623,-1.008926 50.889608,-1.008931 50.889591,-1.008927 50.889575,-1.008915 50.889559,-1.008897 50.889547,-1.008873 50.889540,-1.008847 50.889537,-1.008820 50.889539,-1.008796 50.889547,-1.008777 50.889558,-1.008765 50.889573,-1.008760 50.889590)))
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