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

1293

reference
826-tree-1
name
1293
tree-preservation-order

undefined

826-tpo-1
uprn
address-text
point
POINT (-1.044909 50.870385)
geometry
MULTIPOLYGON (((-1.044838 50.870377,-1.044841 50.870391,-1.044851 50.870404,-1.044867 50.870414,-1.044886 50.870421,-1.044908 50.870423,-1.044930 50.870421,-1.044950 50.870415,-1.044966 50.870405,-1.044977 50.870392,-1.044980 50.870379,-1.044977 50.870365,-1.044967 50.870352,-1.044952 50.870342,-1.044932 50.870335,-1.044910 50.870333,-1.044888 50.870335,-1.044868 50.870341,-1.044852 50.870351,-1.044842 50.870364,-1.044838 50.870377)))
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