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

1056

reference
332-tree-1
name
1056
tree-preservation-order

undefined

332-tpo-1
uprn
address-text
point
POINT (-1.035094 50.862854)
geometry
MULTIPOLYGON (((-1.035051 50.862849,-1.035053 50.862857,-1.035059 50.862865,-1.035068 50.862871,-1.035080 50.862875,-1.035093 50.862876,-1.035106 50.862875,-1.035118 50.862872,-1.035128 50.862866,-1.035134 50.862858,-1.035136 50.862850,-1.035135 50.862841,-1.035129 50.862834,-1.035119 50.862828,-1.035108 50.862824,-1.035094 50.862823,-1.035081 50.862824,-1.035069 50.862827,-1.035060 50.862833,-1.035053 50.862841,-1.035051 50.862849)))
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