Tree

There is a problem

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

1809

reference: 275-tree-1
name: 1809
tree-preservation-order: undefined
275-tpo-1
uprn
address-text
point: POINT (-0.979126 50.858892)
geometry: MULTIPOLYGON (((-0.979027 50.858881,-0.979031 50.858901,-0.979045 50.858918,-0.979066 50.858932,-0.979094 50.858942,-0.979125 50.858945,-0.979155 50.858942,-0.979183 50.858933,-0.979206 50.858920,-0.979220 50.858902,-0.979225 50.858883,-0.979221 50.858863,-0.979207 50.858846,-0.979186 50.858832,-0.979158 50.858822,-0.979127 50.858819,-0.979097 50.858822,-0.979069 50.858831,-0.979046 50.858844,-0.979032 50.858862,-0.979027 50.858881)))
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