Parent Layer: Labeling

Name: Waterbodies

Display Field: Name

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: 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 reservoirs only: NYCDEP BWS GIS Staff (T. Spies) edited all polygons representing NYC reservoirs to show the true inundation area of water impoundment when the reservoir is full, including all areas separated from the main pool by a road or bridge. Therefore, any streams or rivers wider than 5m and represented in this NHDArea feature class were also edited as needed to match any edges where they transitioned from a NYC reservoir polygon. All edges and vertices were snapped to eliminate any gaps or slivers between reservoirs/lakes/ponds (NHDWaterbody) and stream/rivers (NHDArea).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. 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

Service Item Id: fef703ad281040ef8c9acf35b5eae79d

Copyright Text: For NYCDEP watershed - Original data developed under NYCDEP contract CAT-393 by IAGT/RACNE. QA edits and reservoir inundation polygons developed in-house by NYCDEP BWS GIS. This data packaging is owned by the New York City Department of Environmental Protection, Bureau of Water Supply, 2013. For portions of Ulster County outside the NYC watershed - Original data developed under Ulster County contract C13-00216. This data packaging is owned by the Ulster County, 2013.

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: true

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:

XMin: -8325219.414845428
YMin: 5059613.961223344
XMax: -8211855.667678433
YMax: 5231139.809642713
Spatial Reference: 102100  (3857)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [240, 240, 240, 0]
Outline:
N/A
Label: N/A
Description: N/A
Transparency: 0
Labeling Info:
Label Placement: esriServerPolygonPlacementAlwaysHorizontal
Label Expression: [Name]
Use Coded Values: true
Symbol:
Color: [255, 255, 255, 255]
Background Color: N/A
Outline Color: N/A
Vertical Alignment: baseline
Horizontal Alignment: left
Right to Left: false
Angle: 0
XOffset: 0
YOffset: 0
Size: 10
Font Family: Arial
Font Style: normal
Font Weight: normal
Font Decoration: none

Min. Scale: 0.0
Max. Scale: 0.0

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false
Supports Binning LOD: false
Supports Query With LOD Spatial Reference: false

HasZ: true

HasM: true

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID, alias: OBJECTID )
• Name ( type: esriFieldTypeString, alias: Name, length: 100 )
• Shape ( type: esriFieldTypeGeometry, alias: Shape )

Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata