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
369-tree-1
name
0923
tree-preservation-order

undefined

369-tpo-1
uprn
address-text
point
POINT (-1.015998 50.894762)
geometry
MULTIPOLYGON (((-1.015871 50.894749,-1.015876 50.894774,-1.015894 50.894797,-1.015922 50.894815,-1.015957 50.894827,-1.015997 50.894831,-1.016036 50.894827,-1.016072 50.894816,-1.016101 50.894798,-1.016120 50.894776,-1.016126 50.894751,-1.016121 50.894726,-1.016103 50.894703,-1.016075 50.894685,-1.016040 50.894673,-1.016000 50.894669,-1.015961 50.894673,-1.015925 50.894684,-1.015896 50.894702,-1.015877 50.894724,-1.015871 50.894749)))
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