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

1084

reference
423-tree-1
name
1084
tree-preservation-order

undefined

423-tpo-1
uprn
address-text
point
POINT (-1.037484 50.895292)
geometry
MULTIPOLYGON (((-1.037427 50.895286,-1.037430 50.895297,-1.037437 50.895307,-1.037450 50.895315,-1.037466 50.895321,-1.037483 50.895322,-1.037501 50.895321,-1.037517 50.895316,-1.037529 50.895308,-1.037538 50.895298,-1.037541 50.895287,-1.037538 50.895276,-1.037530 50.895266,-1.037518 50.895258,-1.037502 50.895252,-1.037485 50.895251,-1.037467 50.895252,-1.037451 50.895257,-1.037438 50.895265,-1.037430 50.895275,-1.037427 50.895286)))
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