Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • 1 entry with tree-preservation-order field must match the reference field in the tree preservation order
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Felled date Entry date Start date End date
0418/T001 418 Leamington Road No.2 2015

0418

Missing associated entity

POINT (-1.515963 52.388219) MULTIPOLYGON (((-1.515870 52.388219,-1.515871 52.388226,-1.515876 52.388239,-1.515887 52.388251,-1.515912 52.388265,-1.515950 52.388273,-1.515978 52.388273,-1.515990 52.388271,-1.516011 52.388266,-1.516025 52.388260,-1.516037 52.388253,-1.516046 52.388244,-1.516051 52.388238,-1.516056 52.388225,-1.516056 52.388215,-1.516053 52.388205,-1.516047 52.388195,-1.516034 52.388184,-1.516017 52.388175,-1.516002 52.388170,-1.515968 52.388165,-1.515945 52.388166,-1.515929 52.388169,-1.515918 52.388172,-1.515895 52.388182,-1.515879 52.388196,-1.515873 52.388206,-1.515870 52.388219))) 2026-09-26 2015-03-16

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 Coventry City 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