Skip to main content

This is a new service – your feedback will help us to improve it.

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

1037

reference
603-tree-1
name
1037
tree-preservation-order

undefined

603-tpo-1
uprn
address-text
point
POINT (-1.023429 50.879833)
geometry
MULTIPOLYGON (((-1.023387 50.879828,-1.023389 50.879837,-1.023394 50.879844,-1.023404 50.879850,-1.023416 50.879854,-1.023429 50.879856,-1.023454 50.879851,-1.023463 50.879845,-1.023470 50.879837,-1.023472 50.879829,-1.023470 50.879821,-1.023464 50.879813,-1.023455 50.879807,-1.023443 50.879803,-1.023430 50.879802,-1.023417 50.879803,-1.023405 50.879807,-1.023395 50.879813,-1.023389 50.879820,-1.023387 50.879828)))
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