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

1578

reference
345-tree-1
name
1578
tree-preservation-order

undefined

345-tpo-1
uprn
address-text
point
POINT (-1.045379 50.893942)
geometry
MULTIPOLYGON (((-1.045279 50.893932,-1.045284 50.893951,-1.045298 50.893969,-1.045319 50.893983,-1.045347 50.893992,-1.045378 50.893996,-1.045409 50.893993,-1.045436 50.893984,-1.045459 50.893970,-1.045473 50.893953,-1.045478 50.893934,-1.045474 50.893914,-1.045460 50.893896,-1.045439 50.893882,-1.045411 50.893873,-1.045380 50.893870,-1.045349 50.893873,-1.045322 50.893881,-1.045299 50.893895,-1.045285 50.893912,-1.045279 50.893932)))
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