Tree

There is a problem

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

1499

reference: 867-tree-1
name: 1499
tree-preservation-order: undefined
867-tpo-1
uprn
address-text
point: POINT (-0.971099 50.866717)
geometry: MULTIPOLYGON (((-0.971014 50.866708,-0.971018 50.866725,-0.971030 50.866740,-0.971048 50.866752,-0.971072 50.866760,-0.971098 50.866762,-0.971125 50.866760,-0.971149 50.866753,-0.971168 50.866741,-0.971180 50.866726,-0.971185 50.866709,-0.971181 50.866693,-0.971169 50.866677,-0.971151 50.866665,-0.971127 50.866657,-0.971101 50.866655,-0.971074 50.866657,-0.971050 50.866664,-0.971031 50.866676,-0.971019 50.866691,-0.971014 50.866708)))
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