Tree

There is a problem

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

1351

reference: 955-tree-1
name: 1351
tree-preservation-order: undefined
955-tpo-1
uprn
address-text
point: POINT (-0.999915 50.854461)
geometry: MULTIPOLYGON (((-0.999815 50.854451,-0.999820 50.854470,-0.999834 50.854488,-0.999855 50.854502,-0.999883 50.854511,-0.999914 50.854514,-0.999944 50.854512,-0.999972 50.854503,-0.999995 50.854489,-1.000009 50.854472,-1.000014 50.854452,-1.000010 50.854433,-0.999996 50.854415,-0.999974 50.854401,-0.999947 50.854392,-0.999916 50.854388,-0.999885 50.854391,-0.999858 50.854400,-0.999835 50.854414,-0.999821 50.854431,-0.999815 50.854451)))
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