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

1224

reference
740-tree-1
name
1224
tree-preservation-order

undefined

740-tpo-1
uprn
address-text
point
POINT (-1.008397 50.886358)
geometry
MULTIPOLYGON (((-1.008340 50.886352,-1.008343 50.886363,-1.008350 50.886373,-1.008363 50.886381,-1.008379 50.886386,-1.008396 50.886388,-1.008414 50.886386,-1.008430 50.886381,-1.008442 50.886374,-1.008451 50.886364,-1.008454 50.886353,-1.008451 50.886341,-1.008443 50.886331,-1.008431 50.886323,-1.008415 50.886318,-1.008398 50.886316,-1.008380 50.886318,-1.008364 50.886323,-1.008351 50.886331,-1.008343 50.886341,-1.008340 50.886352)))
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