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

1381

reference
131-tree-1
name
1381
tree-preservation-order

undefined

131-tpo-1
uprn
address-text
point
POINT (-1.032610 50.865236)
geometry
MULTIPOLYGON (((-1.032539 50.865228,-1.032542 50.865242,-1.032552 50.865255,-1.032567 50.865265,-1.032587 50.865272,-1.032609 50.865274,-1.032631 50.865272,-1.032651 50.865266,-1.032667 50.865256,-1.032677 50.865244,-1.032681 50.865230,-1.032678 50.865216,-1.032668 50.865203,-1.032652 50.865193,-1.032633 50.865187,-1.032611 50.865184,-1.032589 50.865186,-1.032569 50.865192,-1.032553 50.865202,-1.032543 50.865215,-1.032539 50.865228)))
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