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

1718

reference
232-tree-1
name
1718
tree-preservation-order

undefined

232-tpo-1
uprn
address-text
point
POINT (-1.005818 50.852721)
geometry
MULTIPOLYGON (((-1.005747 50.852713,-1.005750 50.852727,-1.005760 50.852740,-1.005775 50.852750,-1.005795 50.852757,-1.005817 50.852759,-1.005839 50.852757,-1.005859 50.852751,-1.005875 50.852741,-1.005885 50.852729,-1.005889 50.852715,-1.005886 50.852701,-1.005876 50.852688,-1.005860 50.852678,-1.005841 50.852672,-1.005819 50.852669,-1.005797 50.852671,-1.005777 50.852677,-1.005761 50.852687,-1.005751 50.852700,-1.005747 50.852713)))
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