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

0923

reference
367-tree-1
name
0923
tree-preservation-order

undefined

367-tpo-1
uprn
address-text
point
POINT (-1.015960 50.894807)
geometry
MULTIPOLYGON (((-1.015861 50.894796,-1.015866 50.894816,-1.015879 50.894834,-1.015901 50.894848,-1.015929 50.894857,-1.015959 50.894860,-1.015990 50.894857,-1.016018 50.894849,-1.016040 50.894835,-1.016055 50.894818,-1.016060 50.894798,-1.016056 50.894779,-1.016042 50.894761,-1.016020 50.894747,-1.015993 50.894738,-1.015962 50.894734,-1.015931 50.894737,-1.015903 50.894746,-1.015881 50.894760,-1.015866 50.894777,-1.015861 50.894796)))
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