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

1471

reference
382-tree-1
name
1471
tree-preservation-order

undefined

382-tpo-1
uprn
address-text
point
POINT (-1.027249 50.884579)
geometry
MULTIPOLYGON (((-1.027178 50.884572,-1.027181 50.884586,-1.027191 50.884598,-1.027206 50.884608,-1.027226 50.884615,-1.027248 50.884617,-1.027270 50.884615,-1.027290 50.884609,-1.027306 50.884599,-1.027316 50.884587,-1.027320 50.884573,-1.027317 50.884559,-1.027307 50.884546,-1.027291 50.884536,-1.027272 50.884530,-1.027250 50.884527,-1.027228 50.884529,-1.027208 50.884536,-1.027192 50.884545,-1.027181 50.884558,-1.027178 50.884572)))
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