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

1381

reference
135-tree-1
name
1381
tree-preservation-order

undefined

135-tpo-1
uprn
address-text
point
POINT (-1.032225 50.865228)
geometry
MULTIPOLYGON (((-1.032140 50.865219,-1.032144 50.865236,-1.032155 50.865251,-1.032174 50.865263,-1.032198 50.865271,-1.032224 50.865274,-1.032250 50.865271,-1.032274 50.865264,-1.032293 50.865252,-1.032306 50.865237,-1.032310 50.865220,-1.032306 50.865204,-1.032295 50.865188,-1.032276 50.865176,-1.032252 50.865169,-1.032226 50.865166,-1.032200 50.865168,-1.032176 50.865176,-1.032157 50.865187,-1.032144 50.865202,-1.032140 50.865219)))
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