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

1942

reference
39-tree-1
name
1942
tree-preservation-order

undefined

39-tpo-1
uprn
address-text
point
POINT (-1.018511 50.897002)
geometry
MULTIPOLYGON (((-1.018455 50.896996,-1.018457 50.897007,-1.018465 50.897018,-1.018477 50.897026,-1.018493 50.897031,-1.018511 50.897033,-1.018528 50.897031,-1.018544 50.897026,-1.018557 50.897018,-1.018565 50.897008,-1.018568 50.896997,-1.018566 50.896986,-1.018558 50.896976,-1.018545 50.896968,-1.018530 50.896963,-1.018512 50.896961,-1.018495 50.896962,-1.018479 50.896967,-1.018466 50.896975,-1.018458 50.896985,-1.018455 50.896996)))
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