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

1628

reference
821-tree-1
name
1628
tree-preservation-order

undefined

821-tpo-1
uprn
address-text
point
POINT (-1.036529 50.875034)
geometry
MULTIPOLYGON (((-1.036458 50.875026,-1.036462 50.875040,-1.036472 50.875053,-1.036487 50.875063,-1.036507 50.875069,-1.036529 50.875072,-1.036551 50.875070,-1.036571 50.875063,-1.036586 50.875054,-1.036597 50.875041,-1.036601 50.875027,-1.036597 50.875013,-1.036588 50.875001,-1.036572 50.874991,-1.036552 50.874984,-1.036530 50.874982,-1.036508 50.874984,-1.036489 50.874990,-1.036473 50.875000,-1.036462 50.875012,-1.036458 50.875026)))
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