Name: GATE_SHU: 2m Smoothed Contours (2014 LiDAR)

Display Field: Id

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: TASK NAME: USGS New Jersey CMGP Sandy Lidar 0.7 Meter NPS LIDAR lidar Data Acquisition and Processing Production Task USGS Contract No. G10PC00057 Task Order No. G14PD00854 Woolpert Order No. 073714 CONTRACTOR: Woolpert, Inc. This data set is comprised of lidar point cloud data, raster DEM, hydrologic 3-d breaklines, raster intensity, survey control, project tile index, and project data extent. This task order requires lidar data to be acquired over several areas in the state of New Jersey to include the entire counties of Bergen, Essex, Hudson, Middlesex, Monmouth, and Union and including Morristown National Historical Park. The total area of the New Jersey Sandy Lidar AOI is approximately 1,312 square miles. The lidar data will be acquired and processed under the requirements identified in this task order. lidar data is a remotely sensed high resolution elevation data collected by an airborne platform. The lidar sensor uses a combination of laser range finding, GPS positioning, and inertial measurement technologies. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The task required the LiDAR data to be collected at a nominal pulse spacing (NPS) of 0.7 meters. The final products include classified LAS, one (1) meter pixel raster DEMs of the bare-earth surface in ERDAS IMG Format, and 8-bit intensity images. Each LAS file contains lidar point information, which has been calibrated, controlled, and classified. Additional deliverables include hydrologic breakline data, control data, tile index, lidar processing and survey reports in PDF format, FGDC metadata files for each data deliverable in .xml format, and LAS swath data. Collected swath files that were that were larger than 2GB were provided in multiple sub-swath files, each less than 2GB. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. The tide window requirements for the lidar data acquisition; Tidally impacted waters within the AOI are expected to be acquired at Predicted MLW +- 2 hours exclusive of neap tide.; The bare earth DEMs along the coast may have a variance in the water heights due to temporal differences during the lidar data acquisition and will be represented in DEM as a seam-like anomaly.; One coastal elevation was applied to entire project area. Due to differing acquisition dates and thus differing tide levels there will be areas in the DEM exhibiting what appears to be "digging" water features. Sometimes as much as approximately 1 meter. This was done to ensure that no coastal hydro feature was "floating" above ground surface. This coastal elevation will also affect connected river features wherein a sudden increase in flow will be observed in the DEM to accommodate the coastal elevation value; During Hydrologic breakline collection, Woolpert excluded obvious above-water piers or pier-like structures from the breakline placement. Some features extend beyond the apparent coastline and are constructed in a manner that can be considered an extension of the ground. These features were treated as ground during classification and subsequent hydrologic delineation. In all cases, professional practice was applied to delineate what appeared to be the coast based on data from multiple sources; Due to the many substructures and the complexity of the urban environment, interpolation and apparent "divots" (caused by tinning) may be evident in the surface of the bare earth DEM. In all cases, professional practice was applied to best represent the topography.

Copyright Text:

Min. Scale: 169501

Max. Scale: 0

Default Visibility: true

Max Record Count: 1000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

XMin: -8239807.2093
YMin: 4923507.6512
XMax: -8234939.496
YMax: 4936075.9328
Spatial Reference: 102100 (3857)

Drawing Info:

{"renderer":{"type":"simple","symbol":{"type":"esriSLS","style":"esriSLSSolid","color":[221,168,64,255],"width":0.4},"label":"","description":""},"transparency":0,"labelingInfo":null}

HasZ: false

HasM: false

Has Attachments: false

Has Geometry Properties: false

HTML Popup Type: esriServerHTMLPopupTypeNone

Object ID Field: OBJECTID

Unique ID Field:

Name : OBJECTID

IsSystemMaintained : True

Global ID Field: GlobalID

Type ID Field:

Fields:

• OBJECTID (type: esriFieldTypeInteger, alias: OBJECTID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
• Id (type: esriFieldTypeInteger, alias: Id, SQL Type: sqlTypeOther, nullable: true, editable: true)
• Contour (type: esriFieldTypeDouble, alias: Contour, SQL Type: sqlTypeOther, nullable: true, editable: true)
• GlobalID (type: esriFieldTypeGlobalID, alias: GlobalID, SQL Type: sqlTypeOther, length: 38, nullable: false, editable: false)
• SHAPE_Length (type: esriFieldTypeDouble, alias: SHAPE_Length, SQL Type: sqlTypeOther, nullable: true, editable: false)

Templates:

Name: SHU_TOPO_Contour_2mSmooth_USGS_2014LiDAR_ln
Description:
Drawing Tool: esriFeatureEditToolLine
Prototype:

Attributes:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 6/15/2016 3:48:41 PM

Schema Last Edit Date: 6/15/2016 3:48:41 PM

Data Last Edit Date: 6/15/2016 3:48:41 PM

Supported Operations:   Query   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat