Tree

There is a problem

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

1354

reference: 980-tree-1
name: 1354
tree-preservation-order: undefined
980-tpo-1
uprn
address-text
point: POINT (-1.009424 50.852809)
geometry: MULTIPOLYGON (((-1.009367 50.852803,-1.009369 50.852814,-1.009377 50.852824,-1.009390 50.852832,-1.009405 50.852837,-1.009423 50.852839,-1.009440 50.852838,-1.009456 50.852833,-1.009469 50.852825,-1.009477 50.852815,-1.009480 50.852804,-1.009478 50.852793,-1.009470 50.852782,-1.009458 50.852774,-1.009442 50.852769,-1.009424 50.852767,-1.009407 50.852769,-1.009391 50.852774,-1.009378 50.852782,-1.009370 50.852792,-1.009367 50.852803)))
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