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

1124

reference
676-tree-1
name
1124
tree-preservation-order

undefined

676-tpo-1
uprn
address-text
point
POINT (-1.018020 50.879855)
geometry
MULTIPOLYGON (((-1.017978 50.879850,-1.017979 50.879858,-1.017985 50.879866,-1.017995 50.879872,-1.018006 50.879876,-1.018020 50.879877,-1.018033 50.879876,-1.018045 50.879872,-1.018054 50.879866,-1.018061 50.879859,-1.018063 50.879851,-1.018061 50.879842,-1.018055 50.879835,-1.018046 50.879829,-1.018034 50.879825,-1.018021 50.879823,-1.017996 50.879828,-1.017986 50.879834,-1.017980 50.879842,-1.017978 50.879850)))
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