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
779-tree-1
name
1056
tree-preservation-order

undefined

779-tpo-1
uprn
address-text
point
POINT (-1.035327 50.862775)
geometry
MULTIPOLYGON (((-1.035270 50.862769,-1.035273 50.862780,-1.035281 50.862790,-1.035293 50.862798,-1.035309 50.862803,-1.035326 50.862805,-1.035344 50.862803,-1.035360 50.862798,-1.035373 50.862791,-1.035381 50.862781,-1.035384 50.862770,-1.035381 50.862758,-1.035374 50.862748,-1.035361 50.862740,-1.035345 50.862735,-1.035328 50.862733,-1.035310 50.862735,-1.035294 50.862740,-1.035282 50.862748,-1.035273 50.862758,-1.035270 50.862769)))
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