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: 19137704

reference
27
name
tree-preservation-order

tree-preservation-order missing

tree-preservation-zone-type
geometry
MULTIPOLYGON (((-0.161250 51.490820,-0.160600 51.491180,-0.161280 51.491840,-0.161620 51.491630,-0.162080 51.491380,-0.162160 51.491310,-0.162170 51.491310,-0.162490 51.491070,-0.162690 51.490950,-0.162690 51.490940,-0.162790 51.490880,-0.163250 51.490830,-0.163340 51.490870,-0.163380 51.490900,-0.163400 51.490900,-0.163500 51.490960,-0.163980 51.491200,-0.164070 51.491230,-0.164200 51.491300,-0.164220 51.491300,-0.164320 51.491360,-0.164490 51.491440,-0.164610 51.491510,-0.164630 51.491510,-0.164750 51.491570,-0.164810 51.491610,-0.164840 51.491620,-0.164910 51.491670,-0.166310 51.490830,-0.166520 51.490960,-0.166860 51.490780,-0.167190 51.490770,-0.167280 51.490760,-0.167320 51.490730,-0.167340 51.490580,-0.167330 51.490540,-0.167110 51.490550,-0.167090 51.490260,-0.167230 51.490260,-0.167270 51.490240,-0.167630 51.490180,-0.167670 51.490520,-0.168470 51.490490,-0.169670 51.490360,-0.169860 51.490530,-0.169920 51.490560,-0.169990 51.490620,-0.170000 51.490640,-0.170030 51.490660,-0.170180 51.490810,-0.170630 51.491220,-0.171100 51.491600,-0.171140 51.491570,-0.171330 51.491490,-0.171360 51.491470,-0.171760 51.491830,-0.172670 51.491290,-0.172530 51.491160,-0.172520 51.491160,-0.172370 51.491040,-0.172300 51.491080,-0.172070 51.490880,-0.171910 51.490760,-0.171780 51.490820,-0.171770 51.490800,-0.171370 51.490430,-0.171400 51.490410,-0.171640 51.490330,-0.171730 51.490290,-0.171730 51.490300,-0.171910 51.490230,-0.171650 51.489980,-0.171540 51.490030,-0.171420 51.489900,-0.170540 51.490140,-0.169310 51.488280,-0.169190 51.488320,-0.169020 51.488360,-0.168950 51.488390,-0.169070 51.488550,-0.169090 51.488590,-0.169170 51.488680,-0.169300 51.488870,-0.169300 51.488880,-0.168310 51.489100,-0.168270 51.489050,-0.168240 51.488990,-0.168030 51.488650,-0.168210 51.488600,-0.168120 51.488470,-0.167900 51.488540,-0.167810 51.488560,-0.167850 51.488620,-0.167950 51.488590,-0.167980 51.488590,-0.167990 51.488610,-0.167640 51.488720,-0.167440 51.488770,-0.167430 51.488780,-0.167310 51.488630,-0.166880 51.488820,-0.166770 51.488730,-0.166640 51.488590,-0.166380 51.488660,-0.166320 51.488690,-0.166190 51.488530,-0.165670 51.488730,-0.165960 51.489090,-0.166250 51.489010,-0.166280 51.489060,-0.166380 51.489180,-0.166070 51.489260,-0.166090 51.489300,-0.165800 51.489360,-0.165580 51.489420,-0.165480 51.489270,-0.165460 51.489250,-0.165400 51.489260,-0.165380 51.489220,-0.165220 51.489250,-0.165130 51.489280,-0.165100 51.489220,-0.164930 51.489010,-0.164010 51.489350,-0.163320 51.489670,-0.163300 51.489690,-0.163250 51.489710,-0.163410 51.489850,-0.163650 51.490170,-0.163680 51.490230,-0.163700 51.490250,-0.163780 51.490410,-0.163800 51.490480,-0.163810 51.490490,-0.163810 51.490510,-0.163840 51.490570,-0.163880 51.490570,-0.164290 51.490510,-0.164500 51.490460,-0.164560 51.490540,-0.164580 51.490540,-0.164580 51.490550,-0.164500 51.490560,-0.164400 51.490560,-0.164370 51.490570,-0.164400 51.490720,-0.163370 51.490820,-0.163300 51.490780,-0.163280 51.490730,-0.163220 51.490630,-0.163200 51.490610,-0.163200 51.490590,-0.163150 51.490510,-0.162970 51.490280,-0.162880 51.490320,-0.162870 51.490310,-0.162770 51.490360,-0.162730 51.490370,-0.162640 51.490280,-0.162480 51.490150,-0.162430 51.490170,-0.161250 51.490820)))
point
POINT (-0.166848 51.490173)
notes
entry-date
2025-01-03
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