Skip to main content

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

Royal Borough of Kingston upon Thames

Tree preservation zone

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

entity: 19207113

reference
1412
name
tree-preservation-order

undefined

Multiple Addresses In The New Malden Area
tree-preservation-zone-type
area
geometry
MULTIPOLYGON (((-0.265024 51.416124,-0.265019 51.416110,-0.265002 51.416088,-0.264976 51.416050,-0.264906 51.415969,-0.264843 51.415909,-0.264765 51.415842,-0.264742 51.415828,-0.264713 51.415815,-0.264662 51.415803,-0.264539 51.415785,-0.264275 51.415755,-0.264185 51.415750,-0.264117 51.415748,-0.263983 51.415752,-0.263895 51.415758,-0.263835 51.415764,-0.263715 51.415781,-0.263431 51.415834,-0.263346 51.415847,-0.263218 51.415864,-0.263172 51.415868,-0.263119 51.415870,-0.263070 51.415869,-0.262841 51.415853,-0.262761 51.415854,-0.262730 51.415857,-0.262700 51.415862,-0.262642 51.415875,-0.262522 51.415921,-0.262350 51.416006,-0.262284 51.416033,-0.262226 51.416049,-0.262181 51.416061,-0.261994 51.416101,-0.261388 51.416215,-0.261335 51.416228,-0.261305 51.416241,-0.261291 51.416258,-0.261284 51.416275,-0.261283 51.416290,-0.261292 51.416311,-0.261440 51.416585,-0.261474 51.416634,-0.261514 51.416669,-0.261562 51.416700,-0.261628 51.416730,-0.261747 51.416752,-0.261882 51.416762,-0.262050 51.416762,-0.262406 51.416739,-0.262672 51.416711,-0.263212 51.416633,-0.263300 51.416614,-0.263828 51.416491,-0.264059 51.416431,-0.264257 51.416374,-0.264628 51.416259,-0.264855 51.416184,-0.265024 51.416124)))
point
POINT (-0.26309 51.416247)
notes
entry-date
2024-04-02
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

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 Royal Borough of Kingston upon Thames’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