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
310-tree-1
name
1357
tree-preservation-order

undefined

310-tpo-1
uprn
address-text
point
POINT (-1.026493 50.893390)
geometry
MULTIPOLYGON (((-1.026450 50.893385,-1.026452 50.893394,-1.026458 50.893401,-1.026467 50.893407,-1.026479 50.893411,-1.026492 50.893413,-1.026518 50.893408,-1.026527 50.893402,-1.026533 50.893394,-1.026536 50.893386,-1.026534 50.893378,-1.026528 50.893370,-1.026518 50.893364,-1.026507 50.893360,-1.026493 50.893359,-1.026480 50.893360,-1.026468 50.893364,-1.026459 50.893369,-1.026453 50.893377,-1.026450 50.893385)))
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