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

1492

reference
596-tree-1
name
1492
tree-preservation-order

undefined

596-tpo-1
uprn
address-text
point
POINT (-1.021812 50.882007)
geometry
MULTIPOLYGON (((-1.021712 50.881996,-1.021717 50.882015,-1.021730 50.882033,-1.021752 50.882047,-1.021780 50.882056,-1.021810 50.882060,-1.021841 50.882057,-1.021869 50.882048,-1.021891 50.882034,-1.021906 50.882017,-1.021911 50.881998,-1.021907 50.881978,-1.021893 50.881960,-1.021871 50.881946,-1.021844 50.881937,-1.021813 50.881934,-1.021782 50.881937,-1.021754 50.881945,-1.021732 50.881959,-1.021718 50.881977,-1.021712 50.881996)))
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