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

1949

reference
28-tree-1
name
1949
tree-preservation-order

undefined

28-tpo-1
uprn
address-text
point
POINT (-0.974535 50.849292)
geometry
MULTIPOLYGON (((-0.974478 50.849286,-0.974480 50.849297,-0.974488 50.849307,-0.974501 50.849315,-0.974516 50.849321,-0.974534 50.849323,-0.974551 50.849321,-0.974567 50.849316,-0.974580 50.849308,-0.974588 50.849298,-0.974591 50.849287,-0.974589 50.849276,-0.974581 50.849266,-0.974569 50.849258,-0.974553 50.849253,-0.974535 50.849251,-0.974518 50.849252,-0.974502 50.849257,-0.974489 50.849265,-0.974481 50.849275,-0.974478 50.849286)))
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