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

1582

reference
339-tree-1
name
1582
tree-preservation-order

undefined

339-tpo-1
uprn
address-text
point
POINT (-1.044804 50.894321)
geometry
MULTIPOLYGON (((-1.044719 50.894312,-1.044723 50.894329,-1.044735 50.894344,-1.044754 50.894356,-1.044777 50.894364,-1.044803 50.894367,-1.044830 50.894364,-1.044854 50.894357,-1.044873 50.894345,-1.044885 50.894330,-1.044890 50.894314,-1.044886 50.894297,-1.044874 50.894282,-1.044856 50.894270,-1.044832 50.894262,-1.044806 50.894259,-1.044779 50.894261,-1.044755 50.894269,-1.044736 50.894281,-1.044724 50.894296,-1.044719 50.894312)))
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