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

0923

reference
370-tree-1
name
0923
tree-preservation-order

undefined

370-tpo-1
uprn
address-text
point
POINT (-1.016010 50.894749)
geometry
MULTIPOLYGON (((-1.015911 50.894738,-1.015915 50.894757,-1.015929 50.894775,-1.015951 50.894789,-1.015978 50.894798,-1.016009 50.894802,-1.016040 50.894799,-1.016068 50.894790,-1.016090 50.894776,-1.016104 50.894759,-1.016110 50.894740,-1.016105 50.894720,-1.016091 50.894702,-1.016070 50.894688,-1.016042 50.894679,-1.016011 50.894676,-1.015981 50.894679,-1.015953 50.894687,-1.015930 50.894701,-1.015916 50.894719,-1.015911 50.894738)))
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