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

1054

reference
426-tree-1
name
1054
tree-preservation-order

undefined

426-tpo-1
uprn
address-text
point
POINT (-1.037611 50.895014)
geometry
MULTIPOLYGON (((-1.037554 50.895008,-1.037557 50.895019,-1.037565 50.895029,-1.037577 50.895037,-1.037593 50.895042,-1.037610 50.895044,-1.037628 50.895043,-1.037644 50.895038,-1.037657 50.895030,-1.037665 50.895020,-1.037668 50.895009,-1.037665 50.894998,-1.037658 50.894988,-1.037645 50.894979,-1.037629 50.894974,-1.037612 50.894972,-1.037594 50.894974,-1.037578 50.894979,-1.037566 50.894987,-1.037557 50.894997,-1.037554 50.895008)))
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