This dataset is a combination of 2 data projects: 1- Data were updated within NYC watershed portions using 1m resolution LiDAR and 1ft orthoimagery collected in 2009 as part of the NYS Digital Ortho Program under contract with NYCDEP under CAT-371.For NYC reservoir areas only: NYCDEP BWS GIS Staff (T. Spies) edited all artificial path and stream transitions to snap exactly to polygon edges representing NYC reservoirs, where those areas were updated by NYCDEP for correct inundation area based on spillway elevation.QA edits to NHD hydrography, including this feature class, were also made where needed based on field verification and correction of the NYCbasin1m boundary.As an additional departure from standard NHD to meet DEP’s needs, DEP GIS staff attributed all flowlines by their respective NYC reservoir basin and NYC water supply “region” as defined in the feature class “NYCbasin1m”. This was done using the “select by location” tool rather than “identity” tool, so as not to split any flowlines across boundaries. Any flowlines crossing basin boundaries in error were corrected by splitting the lines and snapping their endpoints to the appropriate spillway or basin edge instead. After these edits were made, a new geometric network was built to test and ensure all flowlines in the entire dataset were correctly connected so that they can be used for routing.2- Data was updated within portions of Ulster County outside the NYC watershed using NYS 1ft orthoimagery collected in 2013 and multiple Elevation datasets (2013 NYS DEC 1m Lidar Hudson River, 2005 NYS DEC 3m Lidar Ulster Stream Corridors, 1992 USGS 10m Digital Elevation Model (DEM)).Primary quality control was performed visually using enhanced symbology and supporting reference data. A detailed QC checklist is provided in the QC report. Specific emphasis was placed on the areas bordering the NYC Watershed and the areas encompassed by the Town of Woodstock’s local hydrography data. To the extent connections occurred, the data captured on this project was “snapped” to the corresponding locations in the NYC Watershed so that the data could be seamlessly integrated. The hydrography data from the Town of Woodstock, however, was inconsistent when applied to the data capture protocol. Many locally derived features did not appear to be supported by the source data (i.e., they did not exist) and were not included. All visual inspections were made at 1:1000 scale or better. During data capture, the Data Capture Analyst used a separate point feature class named “Flags” to identify locations where there may have been some interpretation or confusion. Later, the QC Analyst also used additional bookmarks in ArcGIS to track locations where additional investigation or interpretation was required. Finally, after an initial pass through the data, the QC Analyst evaluated and resolved all such flags and bookmarks, collaborating with the Data Capture Analyst as necessary to discuss findings and resolve questions.As data was completed, naming convention and separate storage locations were used for data management to ensure that source and modified datasets were clearly separated. In addition, a detailed QC tracking spreadsheet was used to track and manage effort on completing QC and resolving any issues.Finally, after the initial data delivery, several rounds of QC review were performed by Ulster County to include: additional visual inspection of flow line connectivity, geometric network tracking, and utility network analysisMost of the issues that were not readily apparent in the manual QC process were attributed to minor errors in data capture and discovered here. Examples include digitizing lines in the wrong direction (not downstream), existence of multi-part features, and topology errors. In all cases, issues were evaluated and resolved

This dataset is a combination of 2 data projects: 1- Data were updated within NYC watershed portions using 1m resolution LiDAR and 1ft orthoimagery collected in 2009 as part of the NYS Digital Ortho Program under contract with NYCDEP under CAT-371.For NYC reservoir areas only: NYCDEP BWS GIS Staff (T. Spies) edited all artificial path and stream transitions to snap exactly to polygon edges representing NYC reservoirs, where those areas were updated by NYCDEP for correct inundation area based on spillway elevation.QA edits to NHD hydrography, including this feature class, were also made where needed based on field verification and correction of the NYCbasin1m boundary.As an additional departure from standard NHD to meet DEP’s needs, DEP GIS staff attributed all flowlines by their respective NYC reservoir basin and NYC water supply “region” as defined in the feature class “NYCbasin1m”. This was done using the “select by location” tool rather than “identity” tool, so as not to split any flowlines across boundaries. Any flowlines crossing basin boundaries in error were corrected by splitting the lines and snapping their endpoints to the appropriate spillway or basin edge instead. After these edits were made, a new geometric network was built to test and ensure all flowlines in the entire dataset were correctly connected so that they can be used for routing.2- Data was updated within portions of Ulster County outside the NYC watershed using NYS 1ft orthoimagery collected in 2013 and multiple Elevation datasets (2013 NYS DEC 1m Lidar Hudson River, 2005 NYS DEC 3m Lidar Ulster Stream Corridors, 1992 USGS 10m Digital Elevation Model (DEM)).Primary quality control was performed visually using enhanced symbology and supporting reference data. A detailed QC checklist is provided in the QC report. Specific emphasis was placed on the areas bordering the NYC Watershed and the areas encompassed by the Town of Woodstock’s local hydrography data. To the extent connections occurred, the data captured on this project was “snapped” to the corresponding locations in the NYC Watershed so that the data could be seamlessly integrated. The hydrography data from the Town of Woodstock, however, was inconsistent when applied to the data capture protocol. Many locally derived features did not appear to be supported by the source data (i.e., they did not exist) and were not included. All visual inspections were made at 1:1000 scale or better. During data capture, the Data Capture Analyst used a separate point feature class named “Flags” to identify locations where there may have been some interpretation or confusion. Later, the QC Analyst also used additional bookmarks in ArcGIS to track locations where additional investigation or interpretation was required. Finally, after an initial pass through the data, the QC Analyst evaluated and resolved all such flags and bookmarks, collaborating with the Data Capture Analyst as necessary to discuss findings and resolve questions.As data was completed, naming convention and separate storage locations were used for data management to ensure that source and modified datasets were clearly separated. In addition, a detailed QC tracking spreadsheet was used to track and manage effort on completing QC and resolving any issues.Finally, after the initial data delivery, several rounds of QC review were performed by Ulster County to include: additional visual inspection of flow line connectivity, geometric network tracking, and utility network analysisMost of the issues that were not readily apparent in the manual QC process were attributed to minor errors in data capture and discovered here. Examples include digitizing lines in the wrong direction (not downstream), existence of multi-part features, and topology errors. In all cases, issues were evaluated and resolved

Fire Service boundary polygons show the geographic extent for an agency, such as a Fire District responder agency. Service boundaries are used by the Emergency Call Routing Function (ECRF) during routing requests, and they are used by the Location Validation Function (LVF) to validate whether a given location is routable. Took tax Fire districts and Incorporated fire departments and added National Emergency Number Association (NENA) recommended fields for Next Generation Core Services (NGCS). Must maintain the polygons as fire agency annexations and move the edges between two different boundaries to snap to street centerlines, originally created only to parcels edges.

LEP 2014 - " LZN" - zoning layer. This dataset has been developed using a cadastre that has large sections of misaligned boundaries.10/10/13 - Created to repair holes in 'Final_LZN_s68_081013_10cm_Dissolved_2.shp'.A shire wide polygon shapefile was ERASED with 'Final_LZN_s68_081013_10cm_Dissolved_2.shp' to create a shapefile of "donut" holes. This "donut hole" layer was then used to UPDATE 'Final_LZN_s68_081013_10cm_Dissolved_2.shp' which created "Final_LZN_s68_081013_10cm_Dissolved_2_Updated_shire_poly".shp A further DISSOLVE was run on "Final_LZN_s68_081013_10cm_Dissolved_2_Updated_shire_poly".shp to produce "Final_LZN_s68_081013_10cm_Dissolved_3.shp", after which all E2/E3/E4 zones were selected (using SQL query) and reclassified as "Deferred Matter" in accordance with Council resolution on 19 Sept 2013 (Final_LZN_s68_081013_INCL_DEF_MATTERS.shp). 10/3/15 - Edits to zone boundary running along rear of properties in Melaleuca Drive Mullumbimby following edits to the cadastre for Tallowood Ridge Estate stage 3A. Zone boundary on eastern side of PN 11430 also edited and DM polygon within PN 113730 edited. Sue Green4/8/15 - LEP Amendment No 5 Gazetted 31/7/15 - Lot 5 DP 880917 PN 221940 - Zoning of part of parcel zoned RE1. (Sue Green)27/1/16- LEP Amendment No 7 Gazetted 22/1/16 - part Lot 10 DP 748099 PN 143070 - Rezoning to part R2 and part SP3 (Melissa Moore)28/1/16- LEP Amendment No 6 Gazetted 22/1/16 - part of Lot 7 DP 626084 PN 45750 - Rezoning to IN1 (Melissa Moore)8/3/16 - LEP Amendment No 9 Gazetted 19/2/16 - Lots 231-233 DP 1194657 PN 267277 267278 & 267279 - Rezoning to R2 (Sue Green)17/1/17 - Misalignment of zone boundary snapped to cadastral boundary PN 201750 66990 120170. Misalignment was less than 1 metre and correction approved by Alex Caras. (Sue Green)28/2/17 - Boundary of E1 zone snapped to cadastral boundary PN 65220 268510 following realignment of railway corridor and to reflect boundary as per gazetted maps. Refer #E2017/14107. (Sue Green)22/3/17 - LEP Amendment No 12 Gazetted 17/3/17. Minor amendments to a number of parcels of land as per gazetted maps. (Sue Green)5/4/17 - B4 & R2 Zone Boundary snapping anomaly corrected to snap to property boundaries PN 21890 & 53400. Refer #E2017/23514. (Sue Green)25/9/17 - LEP Amendment No 14 Gazetted 22/9/17. PN 268750 268751 268048 268049 Tallowood Ridge Estate. #E2017/92171 (Sue Green)26/9/17 - LEP Amendment No 13 Gazetted 22/9/17. PN 240482, 240483, 119790, 238081. #E2017/92166 (Sue Green)27/11/17 - Area of Bangalow in Blackwood Cres & to the south and east of Ballina Road area realigned to cadastre following cadastral adjustments. (Sue Green)13/12/17 - Snapped SP2 & RU1, RU2 edge to cadastre PN67720. (Sue Green)30/1/19 - LOT: 4 DP: 576360 PN 141960 - After discussions with Alex Caras E1 & DM zone boundary adjustment due to realignment of cadastre on eastern boundary along creek. (Sue Green)12/3/19 - Following discussion with Alex Caras adjustments to zone boundary to snap to realigned cadastre following processing of DP1235920. Section of R5 adjacent to PN 241915 & 269340 realigned to road reserve. Other parcels affected include PN 269344, 269341, 369340, 269339. (Sue Green)5/6/19 - Following discussions with Alex Caras adjustments to zone boundary on PN 13860 & adjoining road reserve to the south to remove small sliver of 1(a) land and to snap the zoning to the lot boundary. Refer #E2019/40938 (Sue Green)22/7/19 - Following discussions with Alex Caras adjustments to zone boundaries in Omega Circuit Brunswick Head to align with adjusted cadastre. Refer #E2019/53697 (Sue Green)19/11/19 - Following discussions with Alex Caras zone boundaries in relation to PN 267109 Lot 12 DP 1189646 Bayshore Drive were adjusted to align with lot boundaries in latest gazetted LZN map 1350_COM_LZN_003CC_020_20161121. Refer #E2019/84773. (Sue Green)23/3/20 - Updated following gazettal of LEP Amendment No. 17 28/2/20. (Sue Green)6/4/20 - Error from Amendment 17 update corrected on PN 238081. Refer #E2020/24925. (Sue Green)6/5/20 - This layer was amended following discussion with Alex Caras and realignment of the shire boundary in the vicinity of the Pacific Motorway south of Bangalow to align with the state local government boundary along with some adjustments to DP1229946 & DP1229072 this layer was amended. Refer to #E2020/32295. (Sue Green)3/6/20 - Zone boundary snapped to cadastre at PN 15940, 15930 & 15910 following adjustment to cadastre in preparation for mapping for LEP Amendment 22. (Sue Green)3/6/20 - Zoning amended following removal of slivers of (1a) land from hybrid layer. PN 108600, 5350, 98640, 240605, 99620, 240604, 103010, 102980, 200480. Refer #E2020/41220. (Sue Green) 6/7/20 - Updated following gazettal of LEP Amendment No. 18 3/7/20. (Sue Green)4/8/20 - Corrected misalignments at Broken Head Reserve Road PN 269414 & 240566. Refer to email from Alex Caras #E2020/54543. (Sue Green) 14/9/20 - Merged adjoining polygons of same zoning from LEP Amendment 17. (Sue Green)13/10/20 - Boundary between B2 and R2 zones adjusted following plan of consolidation DP1263368. Refer email from Alex Caras #E2020/79392 (Melissa Moore)27/11/20 - Boundary between RU2 and R5 zones adjusted following plan of subdivision DP1267961. Refer email from Alex Caras #E2020/95689 (Melissa Moore)27/11/20 - Zone boundary snapped to cadastre at PN270477 following plan of subdivision for road widening DP1268676. Refer email from Alex Caras #E2020/95711 (Melissa Moore)1/12/20 - Zone boundary snapped to cadastre at PN 240318, 11720 & 205370 to reflect gazetted map sheet LZN_003CD. Refer to email from Alex Caras #E2020/89980 (Sue Green)7/12/20 - Zone boundary realigned to remove 1(b1) sliver PN 269088 & 13370. (Sue Green)6/1/20 - Zone boundary realigned to remove overlap with RU1 & SP2 in PN 67680, 166280 & 67720. (Sue Green)16/2/21 - Updated following gazettal of LEP Amendment No. 225/2/21. (Sue Green)17/2/21 - Updated following gazettal of LEP Amendment No. 24 12/2/21 (Melissa Moore)2/3/21 - Updated following gazettal of LEP Amendment No 25 26/2/21 (Sue Green)11/5/21 Updated following gazettal of LEP Amendment No 23 12/2/21 (Sue Green)19/5/21 Updated following gazettal of LEP Amendment No 26 14/5/21 (Sue Green)23/7/21 Zone boundary snapped to cadastre at 270794, 270795, 270796 following plan of subdivision DP1269332. Refer email from Alex Caras #E2021/94777(Melissa Moore)4/8/21 - R2 zone boundary snapped to cadastre at PN 121740, 6710, 6720, 6730, 11880, 11870. Refer email from Alex Caras #E2021/98736 (Sue Green)8/9/21 -3E2 polygons removed in creek area adjacent to PN 240038 and restored to 1(b1) after discrepancy discovered by Dept Planning between our LZN layer (and hence hybrid layer) and the gazetted maps. Refer to Item 2 pg 7 of #E2021/106486. (Sue Green)30/9/21 - Zoning fixed to match lot boundary PN 197850 & gazetted zoning map LZN_002A Amendment No 23 (Sue Green)3/11/21 - Updated following gazettal of LEP Amendment No 29 29/10/21 (Sue Green)22/11/21 - Realigned to match cadastre and shire boundary at PN 241731 & 241733 (Sue Green)1/12/21 - Updated attribute table to change E1, E2, and E3 zone to C1, C2 and C3 zone following changed to legislation 5/11/21 effective 1/12/21. (Sue Green)11/1/22 - Updated following gazettal of LEP Map Amendment No 1 22/12/21. (Sue Green)9/3/22 - Error corrected and zones realigned at PN 118770, 13270, 203830. Refer to #E2022/21429. (Sue Green)12/4/22 - Polygon on polygon - 1(a) Polygon clipped out of RU2 area on PN 270665 & 270666 an RU2 areas merged. (Sue Green)17/5/22 - Updated following gazettal of LEP Amendment No 33 6/5/22. (Sue Green)24/5/22 - Realigned and snapped to cadastre at PN 20060, 20070, 20050, 228170 & 238283 Dudgeons Lane Bangalow. Refer to #E2022/47312. (Sue Green)24/5/22 - Realigned zoning to snap to cadastre at PN 271096 following consolidation of lots DP1281936. (Sue Green)15/6/22 - Updated following gazettal of LEP Map Amendment No 2 10/6/22 (Sue Green)22/8/22 - Layer clipped to shire boundary at PN 270839, 208790 & 41570 following realignment of cadastre. (Sue Green)16/9/22 - Realigned to cadastre at PN271191 following processing of DP1283927. (Melissa Moore)30/11/22 - Recreated following gazettal of LEP Map Amendment No 3. Edited version of the Department of Planning LZN layer LZN_CZones_Deleted_20220907_DOP was used. DM areas exported and saved as a shp file. DM removed from the Department's layer. The DM was used to clip the 1988 zone layer to produce the 1988 zones for these areas. This was then pasted into the Dept's LZN with the DM removed. (Sue Green)16/12/22 - Realigned to cadastre at PN271259 following processing of SP105499 (Melissa Moore)3/1/23 - Updated following gazettal of LEP Map Amendment No 4 16/12/22. PN 46360 (Sue Green)30/1/23 - PN 271299 aligned to cadastre following consolidation of lot and road realignment. Refer to email from Alex Caras #E2023/9615. (Sue Green)30/1/23 - PN 47490 - area of DM land in realigned to snap to cadastre. Property was part of LEP Amendment No 23. Refer to email #E2023/9807. (Sue Green)1/3/23 - Realigned to cadastre at PN 271330 following plan of subdivision DP1289363. Refer #E2023/25370 (Melissa Moore)26/4/23 - Updated to implement Employment Zones gazetted in December 2022 and effective 26/5/23. (Sue Green)31/5/23 - Sliver of DM ie 1988 zones removed from PN 21270 and aligned to cadastre. (Sue Green)29/06/23 - Updated following gazettal Map Amendment No. 5 16/06/23 (Anthony Murphy)7/7/23 - Realigned to cadastre at PN 271486 following plan of subdivision DP1295639. Refer #E2023/70138 (Melissa Moore)