Tree

There is a problem

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

0890

reference: 409-tree-1
name: 0890
tree-preservation-order: undefined
409-tpo-1
uprn
address-text
point: POINT (-1.025964 50.890093)
geometry: MULTIPOLYGON (((-1.025936 50.890090,-1.025937 50.890096,-1.025941 50.890101,-1.025947 50.890105,-1.025964 50.890108,-1.025981 50.890105,-1.025987 50.890101,-1.025993 50.890091,-1.025992 50.890085,-1.025988 50.890080,-1.025974 50.890073,-1.025965 50.890072,-1.025956 50.890073,-1.025948 50.890076,-1.025942 50.890080,-1.025936 50.890090)))
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