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

undefined

823-tpo-1
uprn
address-text
point
POINT (-1.036677 50.874733)
geometry
MULTIPOLYGON (((-1.036620 50.874727,-1.036623 50.874738,-1.036631 50.874748,-1.036643 50.874756,-1.036659 50.874762,-1.036676 50.874763,-1.036694 50.874762,-1.036710 50.874757,-1.036723 50.874749,-1.036731 50.874739,-1.036734 50.874728,-1.036731 50.874717,-1.036724 50.874707,-1.036711 50.874699,-1.036695 50.874693,-1.036678 50.874692,-1.036660 50.874693,-1.036644 50.874698,-1.036632 50.874706,-1.036623 50.874716,-1.036620 50.874727)))
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