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

1276

reference
408-tree-1
name
1276
tree-preservation-order

undefined

408-tpo-1
uprn
address-text
point
POINT (-1.025353 50.889994)
geometry
MULTIPOLYGON (((-1.025310 50.889989,-1.025312 50.889997,-1.025318 50.890005,-1.025328 50.890011,-1.025339 50.890015,-1.025352 50.890016,-1.025366 50.890015,-1.025378 50.890011,-1.025387 50.890006,-1.025393 50.889998,-1.025396 50.889990,-1.025394 50.889981,-1.025388 50.889974,-1.025379 50.889968,-1.025367 50.889964,-1.025354 50.889962,-1.025328 50.889967,-1.025319 50.889973,-1.025313 50.889981,-1.025310 50.889989)))
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