Tree

There is a problem

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

1135

reference: 837-tree-1
name: 1135
tree-preservation-order: undefined
837-tpo-1
uprn
address-text
point: POINT (-1.042033 50.859516)
geometry: MULTIPOLYGON (((-1.041991 50.859512,-1.041992 50.859520,-1.041998 50.859528,-1.042008 50.859534,-1.042019 50.859538,-1.042033 50.859539,-1.042046 50.859538,-1.042058 50.859534,-1.042067 50.859528,-1.042073 50.859521,-1.042076 50.859513,-1.042074 50.859504,-1.042068 50.859497,-1.042059 50.859491,-1.042047 50.859487,-1.042034 50.859485,-1.042009 50.859490,-1.041999 50.859496,-1.041993 50.859504,-1.041991 50.859512)))
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