Newcastle City Council
Tree preservation zone
About this data
We accept data in different formats and standardise it, so that we can combine it with data from other sources. This means the data we show might be in a different format to the data you provided. For example, we standardise all dates as YYYY-MM-DD.
| Reference | Name | Tree preservation order | Tree preservation zone type | Geometry | Point | Notes | Entry date | Start date | End date |
|---|---|---|---|---|---|---|---|---|---|
| 2017/005.T34 | Land West of Diana Street | 2017/005.T34 | individual | MULTIPOLYGON (((-1.629454 54.97505, -1.62961 54.97505, -1.629611 54.974961, -1.629455 54.97496, -1.629454 54.97505))) | POINT (-1.629532 54.975005) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2017-10-13 | 2017-10-13 | |
| 2017/005.T35 | Land West of Diana Street | 2017/005.T35 | individual | MULTIPOLYGON (((-1.62945 54.974992, -1.629606 54.974993, -1.629607 54.974903, -1.62945 54.974902, -1.62945 54.974992))) | POINT (-1.629528 54.974947) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2017-10-13 | 2017-10-13 | |
| 2017/005.T36 | Land West of Diana Street | 2017/005.T36 | individual | MULTIPOLYGON (((-1.629455 54.974913, -1.629611 54.974913, -1.629612 54.974824, -1.629455 54.974823, -1.629455 54.974913))) | POINT (-1.629533 54.974868) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2017-10-13 | 2017-10-13 | |
| 2017/005.T37 | Land West of Diana Street | 2017/005.T37 | individual | MULTIPOLYGON (((-1.629468 54.974841, -1.629625 54.974841, -1.629625 54.974751, -1.629469 54.974751, -1.629468 54.974841))) | POINT (-1.629547 54.974796) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2017-10-13 | 2017-10-13 | |
| 2017/005.T38 | Land West of Diana Street | 2017/005.T38 | individual | MULTIPOLYGON (((-1.629463 54.974762, -1.629619 54.974762, -1.62962 54.974672, -1.629464 54.974672, -1.629463 54.974762))) | POINT (-1.629542 54.974717) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2017-10-13 | 2017-10-13 | |
| 2024/08.T2 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T2 | individual | MULTIPOLYGON (((-1.633369 55.008673, -1.633525 55.008674, -1.633526 55.008584, -1.63337 55.008583, -1.633369 55.008673))) | POINT (-1.633447 55.008629) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T3 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T3 | individual | MULTIPOLYGON (((-1.633499 55.008656, -1.633655 55.008657, -1.633656 55.008567, -1.6335 55.008566, -1.633499 55.008656))) | POINT (-1.633577 55.008612) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T4 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T4 | individual | MULTIPOLYGON (((-1.633647 55.008632, -1.633803 55.008632, -1.633804 55.008542, -1.633648 55.008542, -1.633647 55.008632))) | POINT (-1.633725 55.008587) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T5 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T5 | individual | MULTIPOLYGON (((-1.63377 55.0086, -1.633927 55.008601, -1.633928 55.008511, -1.633771 55.008511, -1.63377 55.0086))) | POINT (-1.633849 55.008556) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T6 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T6 | individual | MULTIPOLYGON (((-1.633862 55.008586, -1.634018 55.008587, -1.634019 55.008497, -1.633863 55.008497, -1.633862 55.008586))) | POINT (-1.633941 55.008542) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T7 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T7 | individual | MULTIPOLYGON (((-1.634007 55.008564, -1.634164 55.008565, -1.634165 55.008475, -1.634008 55.008474, -1.634007 55.008564))) | POINT (-1.634086 55.008519) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T8 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T8 | individual | MULTIPOLYGON (((-1.634105 55.008549, -1.634261 55.008549, -1.634262 55.008459, -1.634106 55.008459, -1.634105 55.008549))) | POINT (-1.634184 55.008504) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T9 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T9 | individual | MULTIPOLYGON (((-1.6342 55.008535, -1.634356 55.008536, -1.634357 55.008446, -1.6342 55.008445, -1.6342 55.008535))) | POINT (-1.634278 55.00849) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T10 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T10 | individual | MULTIPOLYGON (((-1.634318 55.008519, -1.634474 55.00852, -1.634475 55.00843, -1.634319 55.008429, -1.634318 55.008519))) | POINT (-1.634396 55.008474) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T11 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T11 | individual | MULTIPOLYGON (((-1.634427 55.008503, -1.634583 55.008503, -1.634584 55.008413, -1.634428 55.008413, -1.634427 55.008503))) | POINT (-1.634506 55.008458) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T12 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T12 | individual | MULTIPOLYGON (((-1.634556 55.008484, -1.634712 55.008484, -1.634713 55.008394, -1.634557 55.008394, -1.634556 55.008484))) | POINT (-1.634635 55.008439) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T13 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T13 | individual | MULTIPOLYGON (((-1.634642 55.008471, -1.634798 55.008471, -1.634799 55.008381, -1.634643 55.008381, -1.634642 55.008471))) | POINT (-1.63472 55.008426) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T14 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T14 | individual | MULTIPOLYGON (((-1.634773 55.008453, -1.634929 55.008454, -1.63493 55.008364, -1.634774 55.008363, -1.634773 55.008453))) | POINT (-1.634851 55.008409) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T15 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T15 | individual | MULTIPOLYGON (((-1.634899 55.008432, -1.635055 55.008433, -1.635056 55.008343, -1.6349 55.008342, -1.634899 55.008432))) | POINT (-1.634977 55.008387) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T16 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T16 | individual | MULTIPOLYGON (((-1.634943 55.008424, -1.635099 55.008424, -1.6351 55.008335, -1.634944 55.008334, -1.634943 55.008424))) | POINT (-1.635021 55.008379) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T17 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T17 | individual | MULTIPOLYGON (((-1.635031 55.008413, -1.635187 55.008414, -1.635188 55.008324, -1.635032 55.008323, -1.635031 55.008413))) | POINT (-1.63511 55.008369) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 2024/08.T18 | St Nicholas Hospital, Gosforth eastern section | 2024/08.T18 | individual | MULTIPOLYGON (((-1.635113 55.0084, -1.635269 55.008401, -1.63527 55.008311, -1.635114 55.00831, -1.635113 55.0084))) | POINT (-1.635192 55.008356) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2024-03-21 | 2024-04-29 | |
| 1991/024.T1 | Woolsington Metro Bund Area | 1991/024.T1 | individual | MULTIPOLYGON (((-1.69563 55.021569, -1.695787 55.021569, -1.695787 55.021479, -1.695631 55.021479, -1.69563 55.021569))) | POINT (-1.695709 55.021524) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1991-01-01 | 1991-01-01 | |
| 1968/014.T42 | Moorside South | 1968/014.T42 | individual | MULTIPOLYGON (((-1.646402 54.983408, -1.646558 54.983409, -1.646559 54.983319, -1.646403 54.983318, -1.646402 54.983408))) | POINT (-1.646481 54.983364) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1968-01-01 | 1968-01-01 | |
| 1975/001.T36 | Low Gosforth House | 1975/001.T36 | individual | MULTIPOLYGON (((-1.618874 55.027633, -1.619031 55.027633, -1.619031 55.027543, -1.618875 55.027543, -1.618874 55.027633))) | POINT (-1.618953 55.027588) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1975-01-01 | 1975-01-01 | |
| 1996/006.T2 | Woolsington | 1996/006.T2 | individual | MULTIPOLYGON (((-1.694807 55.027183, -1.694964 55.027184, -1.694964 55.027094, -1.694808 55.027093, -1.694807 55.027183))) | POINT (-1.694886 55.027139) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 1996/006.T3 | Woolsington | 1996/006.T3 | individual | MULTIPOLYGON (((-1.694858 55.026905, -1.695015 55.026906, -1.695015 55.026816, -1.694859 55.026815, -1.694858 55.026905))) | POINT (-1.694937 55.026861) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 1996/006.T4 | Woolsington | 1996/006.T4 | individual | MULTIPOLYGON (((-1.694936 55.02693, -1.695092 55.02693, -1.695093 55.02684, -1.694937 55.02684, -1.694936 55.02693))) | POINT (-1.695014 55.026885) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 1996/006.T5 | Woolsington | 1996/006.T5 | individual | MULTIPOLYGON (((-1.695065 55.026929, -1.695222 55.026929, -1.695222 55.026839, -1.695066 55.026839, -1.695065 55.026929))) | POINT (-1.695144 55.026884) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 1996/006.T6 | Woolsington | 1996/006.T6 | individual | MULTIPOLYGON (((-1.695259 55.027006, -1.695416 55.027007, -1.695416 55.026917, -1.69526 55.026917, -1.695259 55.027006))) | POINT (-1.695338 55.026962) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 1996/006.T8 | Woolsington | 1996/006.T8 | individual | MULTIPOLYGON (((-1.69529 55.027142, -1.695446 55.027142, -1.695447 55.027053, -1.695291 55.027052, -1.69529 55.027142))) | POINT (-1.695368 55.027097) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 1996/006.T7 | Woolsington | 1996/006.T7 | individual | MULTIPOLYGON (((-1.694789 55.026978, -1.694946 55.026979, -1.694946 55.026889, -1.69479 55.026889, -1.694789 55.026978))) | POINT (-1.694868 55.026934) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 1996-01-01 | 1996-01-01 | |
| 2026/03.T1 | Land to the West of 11 Coquet Avenue | 2026/03.T1 | individual | MULTIPOLYGON (((-1.630434 55.014223, -1.630591 55.014224, -1.630591 55.014134, -1.630435 55.014133, -1.630434 55.014223))) | POINT (-1.630513 55.014179) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-14 | 2026-05-14 | |
| 2026/05.T1 | Hodgkin Park Upper | 2026/05.T1 | individual | MULTIPOLYGON (((-1.671255 54.973315, -1.671411 54.973315, -1.671412 54.973226, -1.671256 54.973225, -1.671255 54.973315))) | POINT (-1.671333 54.97327) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T2 | Hodgkin Park Upper | 2026/05.T2 | individual | MULTIPOLYGON (((-1.671264 54.973255, -1.67142 54.973256, -1.671421 54.973166, -1.671265 54.973165, -1.671264 54.973255))) | POINT (-1.671342 54.97321) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T3 | Hodgkin Park Upper | 2026/05.T3 | individual | MULTIPOLYGON (((-1.671269 54.973194, -1.671425 54.973195, -1.671425 54.973105, -1.671269 54.973105, -1.671269 54.973194))) | POINT (-1.671347 54.97315) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T4 | Hodgkin Park Upper | 2026/05.T4 | individual | MULTIPOLYGON (((-1.67127 54.97315, -1.671426 54.97315, -1.671427 54.973061, -1.671271 54.97306, -1.67127 54.97315))) | POINT (-1.671348 54.973105) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T5 | Hodgkin Park Upper | 2026/05.T5 | individual | MULTIPOLYGON (((-1.671245 54.97307, -1.671402 54.973071, -1.671402 54.972981, -1.671246 54.972981, -1.671245 54.97307))) | POINT (-1.671324 54.973026) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T6 | Hodgkin Park Upper | 2026/05.T6 | individual | MULTIPOLYGON (((-1.671256 54.97305, -1.671412 54.97305, -1.671413 54.972961, -1.671256 54.97296, -1.671256 54.97305))) | POINT (-1.671334 54.973005) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T10 | Hodgkin Park Upper | 2026/05.T10 | individual | MULTIPOLYGON (((-1.671229 54.972817, -1.671385 54.972817, -1.671386 54.972727, -1.671229 54.972727, -1.671229 54.972817))) | POINT (-1.671307 54.972772) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T11 | Hodgkin Park Upper | 2026/05.T11 | individual | MULTIPOLYGON (((-1.671227 54.972788, -1.671383 54.972789, -1.671384 54.972699, -1.671228 54.972699, -1.671227 54.972788))) | POINT (-1.671306 54.972744) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T12 | Hodgkin Park Upper | 2026/05.T12 | individual | MULTIPOLYGON (((-1.671222 54.97276, -1.671379 54.97276, -1.671379 54.97267, -1.671223 54.97267, -1.671222 54.97276))) | POINT (-1.671301 54.972715) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T13 | Hodgkin Park Upper | 2026/05.T13 | individual | MULTIPOLYGON (((-1.671132 54.972739, -1.671288 54.972739, -1.671289 54.972649, -1.671133 54.972649, -1.671132 54.972739))) | POINT (-1.671211 54.972694) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T14 | Hodgkin Park Upper | 2026/05.T14 | individual | MULTIPOLYGON (((-1.671158 54.972437, -1.671314 54.972437, -1.671315 54.972347, -1.671159 54.972347, -1.671158 54.972437))) | POINT (-1.671237 54.972392) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T15 | Hodgkin Park Upper | 2026/05.T15 | individual | MULTIPOLYGON (((-1.671184 54.97235, -1.67134 54.97235, -1.671341 54.972261, -1.671185 54.97226, -1.671184 54.97235))) | POINT (-1.671262 54.972305) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T16 | Hodgkin Park Upper | 2026/05.T16 | individual | MULTIPOLYGON (((-1.671184 54.972325, -1.671341 54.972325, -1.671341 54.972235, -1.671185 54.972235, -1.671184 54.972325))) | POINT (-1.671263 54.97228) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T17 | Hodgkin Park Upper | 2026/05.T17 | individual | MULTIPOLYGON (((-1.671173 54.972229, -1.67133 54.97223, -1.67133 54.97214, -1.671174 54.972139, -1.671173 54.972229))) | POINT (-1.671252 54.972185) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T18 | Hodgkin Park Upper | 2026/05.T18 | individual | MULTIPOLYGON (((-1.671029 54.972162, -1.671185 54.972162, -1.671186 54.972073, -1.67103 54.972072, -1.671029 54.972162))) | POINT (-1.671107 54.972117) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T19 | Hodgkin Park Upper | 2026/05.T19 | individual | MULTIPOLYGON (((-1.671143 54.972129, -1.671299 54.97213, -1.6713 54.97204, -1.671143 54.97204, -1.671143 54.972129))) | POINT (-1.671221 54.972085) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 | |
| 2026/05.T20 | Hodgkin Park Upper | 2026/05.T20 | individual | MULTIPOLYGON (((-1.671136 54.972055, -1.671292 54.972055, -1.671292 54.971965, -1.671136 54.971965, -1.671136 54.972055))) | POINT (-1.671214 54.97201) | These data are update live via a feed to NCC's Tree Managament System, EzyTreev | 2026-05-19 | 2026-05-19 |
Showing rows 7601 to 7650 of 8271