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

1604

reference
213-tree-1
name
1604
tree-preservation-order

undefined

213-tpo-1
uprn
address-text
point
POINT (-1.040389 50.898474)
geometry
MULTIPOLYGON (((-1.040204 50.898454,-1.040213 50.898491,-1.040238 50.898523,-1.040279 50.898550,-1.040330 50.898567,-1.040387 50.898573,-1.040444 50.898568,-1.040496 50.898551,-1.040537 50.898526,-1.040564 50.898494,-1.040574 50.898458,-1.040566 50.898421,-1.040540 50.898389,-1.040500 50.898362,-1.040448 50.898345,-1.040391 50.898339,-1.040334 50.898344,-1.040282 50.898361,-1.040241 50.898386,-1.040214 50.898418,-1.040204 50.898454)))
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