Tree

There is a problem

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

1400

reference: 507-tree-1
name: 1400
tree-preservation-order: undefined
507-tpo-1
uprn
address-text
point: POINT (-1.021237 50.899129)
geometry: MULTIPOLYGON (((-1.021167 50.899121,-1.021170 50.899135,-1.021180 50.899148,-1.021195 50.899158,-1.021215 50.899164,-1.021237 50.899167,-1.021259 50.899165,-1.021279 50.899158,-1.021295 50.899149,-1.021305 50.899136,-1.021309 50.899122,-1.021306 50.899108,-1.021296 50.899096,-1.021280 50.899086,-1.021261 50.899079,-1.021239 50.899077,-1.021217 50.899079,-1.021197 50.899085,-1.021181 50.899095,-1.021170 50.899107,-1.021167 50.899121)))
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