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

undefined

391-tpo-1
uprn
address-text
point
POINT (-1.026115 50.884017)
geometry
MULTIPOLYGON (((-1.026044 50.884009,-1.026047 50.884023,-1.026057 50.884036,-1.026073 50.884046,-1.026093 50.884052,-1.026114 50.884055,-1.026136 50.884053,-1.026156 50.884047,-1.026172 50.884037,-1.026183 50.884024,-1.026186 50.884010,-1.026183 50.883996,-1.026173 50.883984,-1.026158 50.883974,-1.026138 50.883967,-1.026116 50.883965,-1.026094 50.883967,-1.026074 50.883973,-1.026058 50.883983,-1.026048 50.883995,-1.026044 50.884009)))
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