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

1645

reference
358-tree-1
name
1645
tree-preservation-order

undefined

358-tpo-1
uprn
address-text
point
POINT (-1.029486 50.884242)
geometry
MULTIPOLYGON (((-1.029387 50.884231,-1.029391 50.884251,-1.029405 50.884268,-1.029427 50.884283,-1.029454 50.884292,-1.029485 50.884295,-1.029516 50.884292,-1.029544 50.884284,-1.029566 50.884270,-1.029581 50.884252,-1.029586 50.884233,-1.029581 50.884213,-1.029568 50.884196,-1.029546 50.884182,-1.029518 50.884173,-1.029488 50.884169,-1.029457 50.884172,-1.029429 50.884181,-1.029407 50.884194,-1.029392 50.884212,-1.029387 50.884231)))
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