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

1350

reference
589-tree-1
name
1350
tree-preservation-order

undefined

589-tpo-1
uprn
address-text
point
POINT (-1.041860 50.865610)
geometry
MULTIPOLYGON (((-1.041789 50.865602,-1.041792 50.865616,-1.041802 50.865629,-1.041818 50.865639,-1.041837 50.865645,-1.041859 50.865648,-1.041881 50.865646,-1.041901 50.865639,-1.041917 50.865629,-1.041927 50.865617,-1.041931 50.865603,-1.041928 50.865589,-1.041918 50.865577,-1.041903 50.865567,-1.041883 50.865560,-1.041861 50.865558,-1.041839 50.865560,-1.041819 50.865566,-1.041803 50.865576,-1.041793 50.865588,-1.041789 50.865602)))
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