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

1830

reference
269-tree-1
name
1830
tree-preservation-order

undefined

269-tpo-1
uprn
address-text
point
POINT (-0.944913 50.859416)
geometry
MULTIPOLYGON (((-0.944715 50.859395,-0.944724 50.859434,-0.944751 50.859469,-0.944795 50.859497,-0.944850 50.859516,-0.944911 50.859522,-0.944973 50.859517,-0.945028 50.859500,-0.945073 50.859472,-0.945102 50.859437,-0.945113 50.859398,-0.945104 50.859359,-0.945076 50.859324,-0.945033 50.859296,-0.944978 50.859277,-0.944917 50.859271,-0.944855 50.859276,-0.944799 50.859294,-0.944755 50.859321,-0.944726 50.859356,-0.944715 50.859395)))
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