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

1334

reference
835-tree-1
name
1334
tree-preservation-order

undefined

835-tpo-1
uprn
address-text
point
POINT (-1.037301 50.858071)
geometry
MULTIPOLYGON (((-1.037230 50.858063,-1.037233 50.858077,-1.037243 50.858090,-1.037259 50.858100,-1.037278 50.858106,-1.037300 50.858109,-1.037322 50.858107,-1.037342 50.858101,-1.037358 50.858091,-1.037368 50.858078,-1.037372 50.858064,-1.037369 50.858050,-1.037359 50.858038,-1.037344 50.858028,-1.037324 50.858021,-1.037302 50.858019,-1.037280 50.858021,-1.037260 50.858027,-1.037244 50.858037,-1.037234 50.858049,-1.037230 50.858063)))
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