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

1523

reference
360-tree-1
name
1523
tree-preservation-order

undefined

360-tpo-1
uprn
address-text
point
POINT (-1.035344 50.893461)
geometry
MULTIPOLYGON (((-1.035174 50.893443,-1.035181 50.893477,-1.035205 50.893507,-1.035242 50.893531,-1.035289 50.893547,-1.035342 50.893553,-1.035395 50.893548,-1.035443 50.893533,-1.035481 50.893509,-1.035506 50.893479,-1.035515 50.893446,-1.035507 50.893413,-1.035484 50.893382,-1.035446 50.893358,-1.035399 50.893342,-1.035346 50.893337,-1.035294 50.893342,-1.035246 50.893357,-1.035207 50.893380,-1.035183 50.893410,-1.035174 50.893443)))
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