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

1357

reference
298-tree-1
name
1357
tree-preservation-order

undefined

298-tpo-1
uprn
address-text
point
POINT (-1.027226 50.893732)
geometry
MULTIPOLYGON (((-1.027099 50.893718,-1.027105 50.893743,-1.027122 50.893766,-1.027150 50.893784,-1.027186 50.893796,-1.027225 50.893800,-1.027265 50.893797,-1.027301 50.893786,-1.027329 50.893768,-1.027348 50.893746,-1.027355 50.893721,-1.027349 50.893695,-1.027331 50.893673,-1.027303 50.893655,-1.027268 50.893643,-1.027228 50.893639,-1.027189 50.893642,-1.027153 50.893653,-1.027124 50.893671,-1.027106 50.893693,-1.027099 50.893718)))
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