Tree

There is a problem

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

1618

reference: 115-tree-1
name: 1618
tree-preservation-order: undefined
115-tpo-1
uprn
address-text
point: POINT (-0.935931 50.859142)
geometry: MULTIPOLYGON (((-0.935874 50.859136,-0.935877 50.859147,-0.935884 50.859157,-0.935897 50.859165,-0.935913 50.859171,-0.935930 50.859173,-0.935948 50.859171,-0.935964 50.859166,-0.935976 50.859158,-0.935985 50.859148,-0.935988 50.859137,-0.935985 50.859126,-0.935977 50.859116,-0.935965 50.859108,-0.935949 50.859103,-0.935932 50.859101,-0.935914 50.859102,-0.935898 50.859107,-0.935885 50.859115,-0.935877 50.859125,-0.935874 50.859136)))
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