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
64-tree-1
name
1216
tree-preservation-order

undefined

64-tpo-1
uprn
address-text
point
POINT (-1.011546 50.866508)
geometry
MULTIPOLYGON (((-1.011475 50.866500,-1.011479 50.866514,-1.011488 50.866527,-1.011504 50.866537,-1.011524 50.866543,-1.011545 50.866546,-1.011567 50.866544,-1.011587 50.866538,-1.011603 50.866528,-1.011614 50.866515,-1.011617 50.866502,-1.011614 50.866488,-1.011604 50.866475,-1.011589 50.866465,-1.011569 50.866458,-1.011547 50.866456,-1.011525 50.866458,-1.011505 50.866464,-1.011489 50.866474,-1.011479 50.866486,-1.011475 50.866500)))
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