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

1206

reference
817-tree-1
name
1206
tree-preservation-order

undefined

817-tpo-1
uprn
address-text
point
POINT (-1.008038 50.888975)
geometry
MULTIPOLYGON (((-1.007953 50.888966,-1.007957 50.888982,-1.007969 50.888998,-1.007987 50.889010,-1.008011 50.889017,-1.008037 50.889020,-1.008064 50.889018,-1.008088 50.889010,-1.008107 50.888999,-1.008119 50.888984,-1.008124 50.888967,-1.008120 50.888950,-1.008108 50.888935,-1.008090 50.888923,-1.008066 50.888915,-1.008040 50.888912,-1.008013 50.888915,-1.007989 50.888922,-1.007970 50.888934,-1.007958 50.888949,-1.007953 50.888966)))
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