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

1235

reference
771-tree-1
name
1235
tree-preservation-order

undefined

771-tpo-1
uprn
address-text
point
POINT (-1.044551 50.865079)
geometry
MULTIPOLYGON (((-1.044495 50.865073,-1.044497 50.865084,-1.044505 50.865095,-1.044518 50.865103,-1.044533 50.865108,-1.044551 50.865110,-1.044568 50.865108,-1.044584 50.865103,-1.044597 50.865095,-1.044605 50.865085,-1.044608 50.865074,-1.044606 50.865063,-1.044598 50.865053,-1.044586 50.865045,-1.044570 50.865040,-1.044552 50.865038,-1.044535 50.865039,-1.044519 50.865044,-1.044506 50.865052,-1.044498 50.865062,-1.044495 50.865073)))
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