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

1859

reference
48-tree-1
name
1859
tree-preservation-order

undefined

48-tpo-1
uprn
address-text
point
POINT (-0.941435 50.856993)
geometry
MULTIPOLYGON (((-0.941378 50.856986,-0.941380 50.856998,-0.941388 50.857008,-0.941401 50.857016,-0.941416 50.857021,-0.941434 50.857023,-0.941452 50.857021,-0.941468 50.857016,-0.941480 50.857009,-0.941489 50.856999,-0.941492 50.856988,-0.941489 50.856976,-0.941481 50.856966,-0.941469 50.856958,-0.941453 50.856953,-0.941436 50.856951,-0.941418 50.856953,-0.941402 50.856958,-0.941389 50.856965,-0.941381 50.856975,-0.941378 50.856986)))
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