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

1420

reference
585-tree-1
name
1420
tree-preservation-order

undefined

585-tpo-1
uprn
address-text
point
POINT (-1.044444 50.866140)
geometry
MULTIPOLYGON (((-1.044373 50.866133,-1.044376 50.866147,-1.044386 50.866159,-1.044401 50.866169,-1.044421 50.866176,-1.044443 50.866178,-1.044465 50.866176,-1.044485 50.866170,-1.044501 50.866160,-1.044511 50.866148,-1.044515 50.866134,-1.044512 50.866120,-1.044502 50.866107,-1.044486 50.866097,-1.044467 50.866091,-1.044445 50.866088,-1.044423 50.866090,-1.044403 50.866096,-1.044387 50.866106,-1.044377 50.866119,-1.044373 50.866133)))
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