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

1357

reference
301-tree-1
name
1357
tree-preservation-order

undefined

301-tpo-1
uprn
address-text
point
POINT (-1.026993 50.893566)
geometry
MULTIPOLYGON (((-1.026936 50.893560,-1.026939 50.893571,-1.026947 50.893581,-1.026959 50.893589,-1.026975 50.893594,-1.026993 50.893596,-1.027010 50.893595,-1.027026 50.893590,-1.027039 50.893582,-1.027047 50.893572,-1.027050 50.893561,-1.027048 50.893550,-1.027040 50.893539,-1.027027 50.893531,-1.027012 50.893526,-1.026994 50.893524,-1.026976 50.893526,-1.026960 50.893531,-1.026948 50.893539,-1.026939 50.893549,-1.026936 50.893560)))
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