Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

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

0977

reference
879-tree-1
name
0977
tree-preservation-order

undefined

879-tpo-1
uprn
address-text
point
POINT (-1.025921 50.877327)
geometry
MULTIPOLYGON (((-1.025793 50.877314,-1.025799 50.877339,-1.025816 50.877362,-1.025844 50.877380,-1.025880 50.877392,-1.025919 50.877396,-1.025959 50.877392,-1.025995 50.877381,-1.026023 50.877363,-1.026042 50.877341,-1.026049 50.877316,-1.026043 50.877291,-1.026025 50.877268,-1.025997 50.877250,-1.025962 50.877238,-1.025923 50.877234,-1.025883 50.877238,-1.025847 50.877249,-1.025818 50.877267,-1.025800 50.877289,-1.025793 50.877314)))
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

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL