49860 nj2010_arra_3counties_m4868_metadata Data Set Published / External 49401 Lidar - partner (no harvest) Project Completed 2015-03-30 Lidar data was acquired over a 1613 square mile area of interest over Atlantic, Ocean, and Monmouth Counties, New Jersey. The lidar data had a nominal point spacing no greater than 1m with a side lap that did not exceed 60%. The lidar data was flown, under went boresight calibration, was processed and then converted to the final deliverable datum and projection provided as NAD83/2007 New Jersey State Plane Coordinate System in US Survey Feet. The vertical datum was North American Vertical Datum 1988 (NAVD88). Topographic elevation data utilizing airborne lidar in support of the floodplain mapping program and other potential uses. 10504 A report for this project is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4868/supplemental/nj2010_arra_3counties_m4868_surveyreport.pdf A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4868/supplemental/nj2010_arra_3counties_m4868.kmz Theme ISO 19115 Topic Category elevation Temporal 2011 Temporal February Office for Coastal Management Charleston SC Data Set None Planned LAS LAS 1.2 format (classes 1,2,7,9,11) none Any conclusions drawn from the analysis of this information are not the responsibility of Fugro Earth Data Inc, RAMPP, FEMA, NOAA, the Office for Coastal Management or its partners. Data Steward 2015-03-30 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Distributor 2015-03-30 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Metadata Contact 2015-03-30 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Point of Contact 2015-03-30 Organization NOAA Office for Coastal Management NOAA/OCM coastal.info@noaa.gov 2234 South Hobson Ave Charleston SC 29405-2413 (843) 740-1202 https://coast.noaa.gov NOAA Office for Coastal Management Home Page Online Resource Ground Condition -74.9863883835 -73.9899530565 40.2509146284 39.288191083 Discrete 2011-02-15 Yes Unclassified This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4868 The data set is dynamically generated based on user-specified parameters.; None Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data may no longer represent actual surface conditions. Users should not use this data for critical applications without a full awareness of its limitations. These data depict the heights at the time of the survey and are only accurate for that time. https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4868 Customized Download Create custom data files by choosing data area, product type, map projection, file format, datum, etc. https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4868/index.html Bulk Download Simple download of data files. https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4868/supplemental/nj2010_arra_3counties_m4868.kmz Browse Graphic Browse Graphic kmz This graphic shows the lidar coverage for the 2011 New Jersey ARRA Lidar Collection for Atlantic, Monmouth, and Ocean Counties. https://coast.noaa.gov Online Resource https://coast.noaa.gov/dataviewer Online Resource 2016-05-23 Date that the source FGDC record was last modified. 2017-11-14 Converted from FGDC Content Standards for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. 2018-02-08 Partial upload of Positional Accuracy fields only. 2018-03-13 Partial upload to move data access links to Distribution Info. The following methods are used to assure lidar accuracy. 1. Use of IMU and ground control network utilizing GPS techniques. 2. Use of airborne GPS in conjunction with the acquisition of lidar. 3. Measurement of quality control ground survey points within the finished product. The boresight of the lidar was processed against the ground control for the New Jersey AOI which consisted of 37 lidar ground survey points and 2 airborne GPS (ABGPS) base stations at the operation airport. The horizontal datum for the control was the North American Datum of 1983/2007 adjustment (NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). The Geoid09 model was used to transform the ellipsoidal heights to GPS derived orthometric heights. ABGPS data was collected during the acquisition mission for each flight line. During the data acquisition the Positional Dilution of Precision (PDOP) for the ABGPS was monitored. The control points were measured by technicians using Terrascan and Fugro EarthData proprietary software and applied to the boresight solution for the project lines. Horizontal accuracy will meet or exceed 0.6 m RMSEr; Quantitative Value: 0.60 meters, Test that produced the value: Horizontal accuracy will meet or exceed 0.6 m RMSEr Vertical elevations will meet or exceed 18.5 cm RMSEz; Quantitative Value: 0.054 meters, Test that produced the value: Vertical accuracy tested at FVA=0.35 ft (10.7 cm). RMSEz = 5.4 cm The bare earth surface will contain voids where insufficient energy was reflected from the surface to generate a valid return from the terrain. Voids in the bare earth surface tend to occur in heavily vegetated areas, water bodies, and beneath buildings, motor vehicles, bridges etc. Fresh or wet asphalt, wet sand and certain types of vegetation can also cause voids or anomalous elevations. Compliance with the accuracy standard was ensured by the collection of GPS ground control during the acquisition of aerial lidar and the establishment of a GPS base station operation airport. The following checks were performed. 1. The ground control and airborne GPS data stream were validated through a fully analytical boresight adjustment. 2. The lidar elevation data were checked against the project control. 3. Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). 1 TerraSurv under contract to Fugro EarthData, Inc. successfully established ground control for the New Jersey AOI. A total of 37 ground control points in the New Jersey AOI were acquired. GPS was used to establish the control network. The horizontal datum was the North American Datum of 1983, 2007 adjustment (NAD83/2007). The vertical datum was the North American Vertical Datum of 1988 (NAVD88). 2010-04-01T00:00:00 2 The Fugro EarthData, Inc. acquisition team collected ALS60 derived lidar over the Atlantic, Ocean, and Monmouth AOI in the State of New Jersey with a 1m, nominal post spacing using a Piper Navajo Chieftain aircraft tailnumber N76JN. The collection for the entire project area was accomplished on April 1st, 2nd, 3rd, 4th, 5th, 6th, 7th, and 10th. Coastal areas where only collected at low tide. The collection was performed using a Leica ALS60 MPiA lidar system, serial number ALS142, including an inertial measuring unit (IMU) and a dual frequency GPS receiver. This project required 14 lifts of flight lines to be collected. The lines were flown at an average of 8,700 feet above mean terrain using a maximum pulse rate frequency of 89,900 Hz. The sensor had a 40 degree FOV and a swath width of 1929 meters. 2010-04-10T00:00:00 3 1. Lidar, GPS, and IMU data was processed together using lidar processing software. 2. The lidar data set for each flight line was checked for project area coverage and lidar post spacing was checked to ensure it meets project specifications. 3. The lidar collected at the calibration area and project area were used to correct the rotational, atmospheric, and vertical elevation differences that are inherent to lidar data. 4. Intensity rasters were generated to verify that intensity was recorded for each lidar point. 5. Lidar data was transformed to the specified project coordinate system. 6. By utilizing the ground survey data collected at the calibration site and project area, the lidar data was vertically biased to the ground. 7. Comparisons between the biased lidar data and ground survey data within the project area were evaluated and a final RMSEz value was generated to ensure the data meets project specifications. 8. Lidar data in overlap areas of project flight lines were trimmed and data from all swaths were merged into a single data set. 9. The data set was trimmed to the digital project boundary including an additional buffer zone of 100 meters. 10. The resulting data set is referred to as the raw lidar data. 2010-06-15T00:00:00 4 1. The raw lidar data was processed through a minimum block mean algorithm, and points were classified as either bare earth or non-bare earth. 2. User developed "macros" that factor mean terrain angle and height from the ground were used to determine bare earth point classification. 3. The next phase of the surfacing process was a 2D edit procedure that ensures the accuracy of the automated feature classification. 4. Editors used a combination of imagery, intensity of the lidar reflection, profiles and tin-editing software to assess points. 5. The lidar data was filtered, as necessary, using a quadric error metric to remove redundant points. This method leaves points where there is a change in the slope of surfaces (road ditches) and eliminates points from evenly sloped terrain (flat field) where the points do not affect the surface. 6. The algorithms for filtering data were utilized within Fugro EarthData proprietary software and commercial software written by TerraSolid. 7. The flight line overlap points were merged back into filtered data set for delivery product. 8. The point cloud data were delivered tiled in LAS 1.2 format; class 1 - unclassified, class 2 - ground, class 7 - low point (noise), class 11 - overlap. 2010-08-20T00:00:00 5 The NOAA Office for Coastal Management (OCM) received the files in laz format from USGS via an FTP online repository. The files contained lidar elevation and intensity measurements. The data were in State Plane Zone 2900, NAVD88 (orthometric) heights in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. Erroneous elevations were removed. 3. The data were converted from NAVD88 (orthometric) heights in meters to GRS80 (ellipsoid) heights in meters using Geoid 09. 4. The LAS data were sorted by latitude and the headers were updated. 2015-03-10T00:00:00 gov.noaa.nmfs.inport:49860 Anne Ball 2017-11-15T15:22:48 SysAdmin InPortAdmin 2022-08-09T17:11:38 2022-03-16 OCM Partners OCMP 1002 Public No No 2022-03-16 1 Year 2023-03-16