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

1583

reference
337-tree-1
name
1583
tree-preservation-order

undefined

337-tpo-1
uprn
address-text
point
POINT (-1.044547 50.894477)
geometry
MULTIPOLYGON (((-1.044490 50.894471,-1.044493 50.894482,-1.044500 50.894493,-1.044513 50.894501,-1.044529 50.894506,-1.044546 50.894508,-1.044564 50.894506,-1.044580 50.894501,-1.044592 50.894493,-1.044601 50.894483,-1.044604 50.894472,-1.044601 50.894461,-1.044593 50.894451,-1.044581 50.894443,-1.044565 50.894438,-1.044548 50.894436,-1.044530 50.894437,-1.044514 50.894442,-1.044501 50.894450,-1.044493 50.894460,-1.044490 50.894471)))
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