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

1285

reference
389-tree-1
name
1285
tree-preservation-order

undefined

389-tpo-1
uprn
address-text
point
POINT (-1.025794 50.883932)
geometry
MULTIPOLYGON (((-1.025723 50.883924,-1.025726 50.883938,-1.025736 50.883951,-1.025751 50.883961,-1.025771 50.883967,-1.025793 50.883970,-1.025815 50.883968,-1.025835 50.883962,-1.025851 50.883952,-1.025861 50.883939,-1.025865 50.883925,-1.025862 50.883912,-1.025852 50.883899,-1.025836 50.883889,-1.025817 50.883882,-1.025795 50.883880,-1.025773 50.883882,-1.025753 50.883888,-1.025737 50.883898,-1.025726 50.883910,-1.025723 50.883924)))
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