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
392-tree-1
name
1285
tree-preservation-order

undefined

392-tpo-1
uprn
address-text
point
POINT (-1.026236 50.884072)
geometry
MULTIPOLYGON (((-1.026137 50.884062,-1.026141 50.884081,-1.026155 50.884099,-1.026177 50.884113,-1.026205 50.884122,-1.026235 50.884125,-1.026266 50.884123,-1.026294 50.884114,-1.026316 50.884100,-1.026331 50.884083,-1.026336 50.884063,-1.026332 50.884044,-1.026318 50.884026,-1.026296 50.884012,-1.026269 50.884003,-1.026238 50.884000,-1.026207 50.884002,-1.026179 50.884011,-1.026157 50.884025,-1.026142 50.884042,-1.026137 50.884062)))
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