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

1303

reference
636-tree-1
name
1303
tree-preservation-order

undefined

636-tpo-1
uprn
address-text
point
POINT (-1.047015 50.866958)
geometry
MULTIPOLYGON (((-1.046958 50.866952,-1.046961 50.866963,-1.046969 50.866973,-1.046981 50.866981,-1.046997 50.866986,-1.047014 50.866988,-1.047032 50.866987,-1.047048 50.866982,-1.047061 50.866974,-1.047069 50.866964,-1.047072 50.866953,-1.047069 50.866942,-1.047061 50.866932,-1.047049 50.866923,-1.047033 50.866918,-1.047016 50.866916,-1.046998 50.866918,-1.046982 50.866923,-1.046969 50.866931,-1.046961 50.866941,-1.046958 50.866952)))
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