Tree

There is a problem

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

1499

reference: 861-tree-1
name: 1499
tree-preservation-order: undefined
861-tpo-1
uprn
address-text
point: POINT (-0.971088 50.867020)
geometry: MULTIPOLYGON (((-0.971045 50.867015,-0.971047 50.867024,-0.971053 50.867031,-0.971062 50.867037,-0.971074 50.867041,-0.971087 50.867043,-0.971112 50.867038,-0.971122 50.867032,-0.971128 50.867024,-0.971130 50.867016,-0.971128 50.867008,-0.971123 50.867000,-0.971113 50.866994,-0.971102 50.866990,-0.971088 50.866989,-0.971075 50.866990,-0.971063 50.866994,-0.971054 50.866999,-0.971047 50.867007,-0.971045 50.867015)))
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