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

1216

reference
63-tree-1
name
1216
tree-preservation-order

undefined

63-tpo-1
uprn
address-text
point
POINT (-1.011391 50.866398)
geometry
MULTIPOLYGON (((-1.011334 50.866392,-1.011337 50.866403,-1.011345 50.866413,-1.011357 50.866421,-1.011373 50.866426,-1.011390 50.866428,-1.011408 50.866426,-1.011424 50.866422,-1.011436 50.866414,-1.011445 50.866404,-1.011448 50.866393,-1.011445 50.866381,-1.011437 50.866371,-1.011425 50.866363,-1.011409 50.866358,-1.011392 50.866356,-1.011374 50.866358,-1.011358 50.866363,-1.011345 50.866371,-1.011337 50.866381,-1.011334 50.866392)))
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