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

1216

reference
109-tree-1
name
1216
tree-preservation-order

undefined

109-tpo-1
uprn
address-text
point
POINT (-1.011715 50.865354)
geometry
MULTIPOLYGON (((-1.011672 50.865350,-1.011674 50.865358,-1.011680 50.865365,-1.011689 50.865372,-1.011714 50.865377,-1.011728 50.865376,-1.011740 50.865372,-1.011749 50.865366,-1.011755 50.865359,-1.011758 50.865350,-1.011756 50.865342,-1.011750 50.865334,-1.011740 50.865328,-1.011729 50.865324,-1.011716 50.865323,-1.011702 50.865324,-1.011690 50.865328,-1.011681 50.865334,-1.011675 50.865341,-1.011672 50.865350)))
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