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

1418

reference
696-tree-1
name
1418
tree-preservation-order

undefined

696-tpo-1
uprn
address-text
point
POINT (-1.011889 50.881367)
geometry
MULTIPOLYGON (((-1.011847 50.881362,-1.011849 50.881370,-1.011855 50.881378,-1.011864 50.881384,-1.011876 50.881388,-1.011889 50.881389,-1.011902 50.881388,-1.011924 50.881379,-1.011930 50.881371,-1.011932 50.881363,-1.011930 50.881354,-1.011924 50.881347,-1.011915 50.881341,-1.011903 50.881337,-1.011890 50.881335,-1.011865 50.881340,-1.011855 50.881346,-1.011849 50.881354,-1.011847 50.881362)))
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