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

1056

reference
777-tree-1
name
1056
tree-preservation-order

undefined

777-tpo-1
uprn
address-text
point
POINT (-1.035439 50.862827)
geometry
MULTIPOLYGON (((-1.035396 50.862822,-1.035398 50.862831,-1.035404 50.862838,-1.035413 50.862844,-1.035425 50.862848,-1.035438 50.862850,-1.035464 50.862845,-1.035473 50.862839,-1.035479 50.862831,-1.035482 50.862823,-1.035480 50.862815,-1.035474 50.862807,-1.035464 50.862801,-1.035453 50.862797,-1.035440 50.862796,-1.035426 50.862797,-1.035414 50.862801,-1.035405 50.862807,-1.035399 50.862814,-1.035396 50.862822)))
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