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

1067

reference
735-tree-1
name
1067
tree-preservation-order

undefined

735-tpo-1
uprn
address-text
point
POINT (-1.030367 50.881060)
geometry
MULTIPOLYGON (((-1.030310 50.881054,-1.030313 50.881065,-1.030320 50.881075,-1.030333 50.881083,-1.030349 50.881088,-1.030366 50.881090,-1.030384 50.881089,-1.030400 50.881084,-1.030412 50.881076,-1.030421 50.881066,-1.030424 50.881055,-1.030421 50.881044,-1.030413 50.881033,-1.030401 50.881025,-1.030385 50.881020,-1.030368 50.881018,-1.030350 50.881020,-1.030334 50.881025,-1.030321 50.881033,-1.030313 50.881043,-1.030310 50.881054)))
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