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
822-tree-1
name
1628
tree-preservation-order

undefined

822-tpo-1
uprn
address-text
point
POINT (-1.036548 50.875003)
geometry
MULTIPOLYGON (((-1.036477 50.874996,-1.036480 50.875010,-1.036490 50.875022,-1.036505 50.875032,-1.036525 50.875039,-1.036547 50.875041,-1.036569 50.875039,-1.036589 50.875033,-1.036605 50.875023,-1.036615 50.875011,-1.036619 50.874997,-1.036616 50.874983,-1.036606 50.874970,-1.036590 50.874960,-1.036571 50.874954,-1.036549 50.874951,-1.036527 50.874953,-1.036507 50.874960,-1.036491 50.874969,-1.036481 50.874982,-1.036477 50.874996)))
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