Tree

There is a problem

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

1577

reference: 353-tree-1
name: 1577
tree-preservation-order: undefined
353-tpo-1
uprn
address-text
point: POINT (-1.046009 50.893507)
geometry: MULTIPOLYGON (((-1.045910 50.893497,-1.045914 50.893516,-1.045928 50.893534,-1.045950 50.893548,-1.045977 50.893557,-1.046008 50.893561,-1.046039 50.893558,-1.046067 50.893549,-1.046089 50.893535,-1.046103 50.893518,-1.046109 50.893498,-1.046104 50.893479,-1.046090 50.893461,-1.046069 50.893447,-1.046041 50.893438,-1.046011 50.893435,-1.045980 50.893438,-1.045952 50.893446,-1.045929 50.893460,-1.045915 50.893477,-1.045910 50.893497)))
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