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

1224

reference
739-tree-1
name
1224
tree-preservation-order

undefined

739-tpo-1
uprn
address-text
point
POINT (-1.008022 50.886385)
geometry
MULTIPOLYGON (((-1.007966 50.886379,-1.007968 50.886390,-1.007976 50.886400,-1.007988 50.886408,-1.008004 50.886414,-1.008022 50.886415,-1.008039 50.886414,-1.008055 50.886409,-1.008068 50.886401,-1.008076 50.886391,-1.008079 50.886380,-1.008077 50.886369,-1.008069 50.886359,-1.008056 50.886351,-1.008041 50.886345,-1.008023 50.886344,-1.008006 50.886345,-1.007990 50.886350,-1.007977 50.886358,-1.007969 50.886368,-1.007966 50.886379)))
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