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

1633

reference
378-tree-1
name
1633
tree-preservation-order

undefined

378-tpo-1
uprn
address-text
point
POINT (-1.026113 50.883875)
geometry
MULTIPOLYGON (((-1.026056 50.883869,-1.026059 50.883880,-1.026067 50.883890,-1.026079 50.883898,-1.026095 50.883904,-1.026113 50.883905,-1.026130 50.883904,-1.026146 50.883899,-1.026159 50.883891,-1.026167 50.883881,-1.026170 50.883870,-1.026168 50.883859,-1.026160 50.883849,-1.026147 50.883841,-1.026132 50.883835,-1.026114 50.883834,-1.026096 50.883835,-1.026081 50.883840,-1.026068 50.883848,-1.026059 50.883858,-1.026056 50.883869)))
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