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

1029

reference
333-tree-1
name
1029
tree-preservation-order

undefined

333-tpo-1
uprn
address-text
point
POINT (-1.034884 50.862270)
geometry
MULTIPOLYGON (((-1.034842 50.862266,-1.034844 50.862274,-1.034849 50.862281,-1.034859 50.862288,-1.034884 50.862293,-1.034897 50.862292,-1.034909 50.862288,-1.034918 50.862282,-1.034925 50.862275,-1.034927 50.862266,-1.034925 50.862258,-1.034919 50.862250,-1.034910 50.862244,-1.034898 50.862240,-1.034885 50.862239,-1.034872 50.862240,-1.034860 50.862244,-1.034850 50.862250,-1.034844 50.862257,-1.034842 50.862266)))
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