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

2046

reference
6-tree-1
name
2046
tree-preservation-order

undefined

6-tpo-1
uprn
10013683749
address-text
Street Record, Copperview Mews, Cowplain, Waterlooville
point
POINT (-1.013740 50.901209)
geometry
MULTIPOLYGON (((-1.013683 50.901203,-1.013686 50.901214,-1.013694 50.901224,-1.013706 50.901232,-1.013722 50.901237,-1.013739 50.901239,-1.013757 50.901237,-1.013773 50.901232,-1.013786 50.901225,-1.013794 50.901215,-1.013797 50.901204,-1.013794 50.901192,-1.013786 50.901182,-1.013774 50.901174,-1.013758 50.901169,-1.013741 50.901167,-1.013723 50.901169,-1.013707 50.901174,-1.013694 50.901182,-1.013686 50.901192,-1.013683 50.901203)))
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