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

1185

reference
891-tree-1
name
1185
tree-preservation-order

undefined

891-tpo-1
uprn
address-text
point
POINT (-1.016408 50.879434)
geometry
MULTIPOLYGON (((-1.016351 50.879428,-1.016354 50.879439,-1.016361 50.879449,-1.016374 50.879457,-1.016390 50.879463,-1.016407 50.879464,-1.016425 50.879463,-1.016441 50.879458,-1.016453 50.879450,-1.016462 50.879440,-1.016465 50.879429,-1.016462 50.879418,-1.016454 50.879408,-1.016442 50.879400,-1.016426 50.879394,-1.016409 50.879393,-1.016391 50.879394,-1.016375 50.879399,-1.016362 50.879407,-1.016354 50.879417,-1.016351 50.879428)))
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