Skip to main content

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

Royal Borough of Kensington and Chelsea

Tree preservation zone

There is a problem

  • tree-preservation-order column is missing values

entity: 19137718

reference
41
name
tree-preservation-order

tree-preservation-order missing

tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.166520 51.490960,-0.167240 51.491400,-0.167810 51.491780,-0.168400 51.492150,-0.168990 51.492550,-0.169160 51.492660,-0.169250 51.492620,-0.169400 51.492540,-0.169590 51.492430,-0.169610 51.492420,-0.169610 51.492410,-0.169590 51.492400,-0.169780 51.492290,-0.169770 51.492280,-0.169840 51.492240,-0.169570 51.492050,-0.169650 51.491960,-0.169790 51.491790,-0.169830 51.491750,-0.169930 51.491620,-0.169940 51.491610,-0.170030 51.491560,-0.170260 51.491450,-0.170290 51.491430,-0.170400 51.491530,-0.170510 51.491620,-0.170620 51.491560,-0.170730 51.491520,-0.170830 51.491470,-0.170860 51.491450,-0.170900 51.491430,-0.170890 51.491430,-0.170880 51.491420,-0.170720 51.491290,-0.170630 51.491220,-0.170560 51.491150,-0.170420 51.491030,-0.170350 51.490960,-0.170180 51.490810,-0.170030 51.490660,-0.170000 51.490640,-0.169920 51.490560,-0.169910 51.490560,-0.169900 51.490550,-0.169890 51.490550,-0.169860 51.490530,-0.169800 51.490470,-0.169670 51.490360,-0.169480 51.490380,-0.169220 51.490410,-0.168470 51.490490,-0.168400 51.490490,-0.168120 51.490500,-0.167670 51.490520,-0.167370 51.490530,-0.167330 51.490540,-0.167340 51.490580,-0.167320 51.490730,-0.167280 51.490760,-0.167190 51.490770,-0.167050 51.490770,-0.166860 51.490780,-0.166520 51.490960)))
point
POINT (-0.168789 51.491305)
notes
entry-date
2025-01-08
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 Kensington and Chelsea’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