Skip to main content

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

Liverpool City Council

Tree preservation zone

There is a problem

  • tree-preservation-order column must match the reference field in the tree preservation order dataset

No info.

reference
TPO104.A1
name
No info.
tree-preservation-order

undefined

TPO104
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-2.869174 53.376219,-2.869561 53.376606,-2.870153 53.377143,-2.870171 53.377151,-2.870705 53.377037,-2.871881 53.376678,-2.871711 53.376544,-2.871215 53.376100,-2.870598 53.376289,-2.870324 53.375979,-2.870281 53.375939,-2.870704 53.375812,-2.870374 53.375420,-2.871343 53.375231,-2.871254 53.375188,-2.871172 53.375054,-2.871172 53.375025,-2.871178 53.375024,-2.871171 53.374957,-2.871177 53.374939,-2.871296 53.374848,-2.871334 53.374787,-2.871346 53.374785,-2.871384 53.374745,-2.871070 53.374637,-2.871047 53.374628,-2.871062 53.374614,-2.870931 53.374569,-2.870505 53.374694,-2.870494 53.374698,-2.870499 53.374705,-2.870483 53.374702,-2.870406 53.374723,-2.870413 53.374731,-2.870399 53.374735,-2.870394 53.374729,-2.870337 53.374745,-2.870342 53.374751,-2.870332 53.374754,-2.870327 53.374749,-2.870270 53.374765,-2.870275 53.374772,-2.870260 53.374770,-2.870181 53.374792,-2.870185 53.374798,-2.870176 53.374801,-2.870171 53.374795,-2.870124 53.374803,-2.870050 53.374823,-2.869161 53.375091,-2.869336 53.375225,-2.869322 53.375251,-2.869217 53.375299,-2.868601 53.375472,-2.869030 53.376061,-2.869174 53.376219)))
point
POINT (-2.8702 53.375886)
notes
The several tree of whatever species situated within area A1 on map.
organisation
entry-date
1972-07-04
start-date
1972-09-06
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Liverpool 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