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

1216

reference
112-tree-1
name
1216
tree-preservation-order

undefined

112-tpo-1
uprn
address-text
point
POINT (-1.011700 50.866164)
geometry
MULTIPOLYGON (((-1.011601 50.866153,-1.011605 50.866173,-1.011619 50.866191,-1.011641 50.866205,-1.011668 50.866214,-1.011699 50.866217,-1.011730 50.866214,-1.011757 50.866206,-1.011780 50.866192,-1.011794 50.866174,-1.011800 50.866155,-1.011795 50.866136,-1.011781 50.866118,-1.011760 50.866104,-1.011732 50.866095,-1.011701 50.866091,-1.011671 50.866094,-1.011643 50.866103,-1.011620 50.866117,-1.011606 50.866134,-1.011601 50.866153)))
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