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

2132

reference
65-tree-1
name
2132
tree-preservation-order

undefined

65-tpo-1
uprn
address-text
point
POINT (-0.940316 50.845702)
geometry
MULTIPOLYGON (((-0.940259 50.845696,-0.940261 50.845707,-0.940269 50.845717,-0.940282 50.845725,-0.940297 50.845730,-0.940315 50.845732,-0.940332 50.845731,-0.940348 50.845726,-0.940361 50.845718,-0.940369 50.845708,-0.940373 50.845697,-0.940370 50.845686,-0.940362 50.845676,-0.940350 50.845668,-0.940334 50.845662,-0.940317 50.845660,-0.940299 50.845662,-0.940283 50.845667,-0.940270 50.845675,-0.940262 50.845685,-0.940259 50.845696)))
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