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

0955

reference
394-tree-1
name
0955
tree-preservation-order

undefined

394-tpo-1
uprn
address-text
point
POINT (-1.017640 50.866983)
geometry
MULTIPOLYGON (((-1.017612 50.866980,-1.017613 50.866985,-1.017617 50.866990,-1.017623 50.866994,-1.017631 50.866997,-1.017640 50.866998,-1.017657 50.866995,-1.017663 50.866991,-1.017667 50.866986,-1.017669 50.866980,-1.017668 50.866975,-1.017664 50.866970,-1.017650 50.866963,-1.017641 50.866962,-1.017624 50.866965,-1.017618 50.866969,-1.017614 50.866974,-1.017612 50.866980)))
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