Tree

There is a problem

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

1087

reference: 350-tree-1
name: 1087
tree-preservation-order: undefined
350-tpo-1
uprn
address-text
point: POINT (-1.019929 50.894849)
geometry: MULTIPOLYGON (((-1.019872 50.894843,-1.019875 50.894854,-1.019882 50.894864,-1.019895 50.894873,-1.019911 50.894878,-1.019928 50.894880,-1.019946 50.894878,-1.019962 50.894873,-1.019974 50.894865,-1.019983 50.894855,-1.019986 50.894844,-1.019983 50.894833,-1.019975 50.894823,-1.019963 50.894815,-1.019947 50.894810,-1.019930 50.894808,-1.019912 50.894809,-1.019896 50.894814,-1.019883 50.894822,-1.019875 50.894832,-1.019872 50.894843)))
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