| 2012 USACE Post Sandy Topographic LiDAR: Rhode Island and Massachusetts Coast | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49609 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset contact: (CI_ResponsibleParty) organisationName: OCM Partners contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (missing) address: (CI_Address) role: (CI_RoleCode) resourceProvider contact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2022-08-09T17:11:37 metadataStandardName: ISO 19115-2 Geographic Information - Metadata Part 2 Extensions for imagery and gridded data metadataStandardVersion: ISO 19115-2:2009(E) return to top spatialRepresentationInfo: return to top referenceSystemInfo: return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: NAD83(2011) date: (CI_Date) date: 2008-11-12 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/CoordRefSystem/6318/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:6318 version: 6.18.3 return to top referenceSystemInfo: (MD_ReferenceSystem) referenceSystemIdentifier: (RS_Identifier) authority: (CI_Citation) title: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters alternateTitle: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters citedResponsibleParty: (CI_ResponsibleParty) organisationName: (withheld) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://apps.epsg.org/api/v1/VerticalCoordRefSystem/5703/?api_key=gml name: North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters description: Link to Geographic Markup Language (GML) description of reference system. function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) resourceProvider citedResponsibleParty: (CI_ResponsibleParty) organisationName: European Petroleum Survey Group contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.epsg.org/ name: European Petroleum Survey Group Geodetic Parameter Registry description: Registry that accesses the EPSG Geodetic Parameter Dataset, which is a structured dataset of Coordinate Reference Systems and Coordinate Transformations. function: (CI_OnLineFunctionCode) search role: (CI_RoleCode) publisher VerticalCS: metaDataProperty: CommonMetaData: type: vertical informationSource: OGP revisionDate: 2006-11-28 isDeprecated: false identifier: urn:ogc:def:cs:EPSG::6499 name: Vertical CS. Axis: height (H). Orientation: up. UoM: meter. remarks: Used in vertical coordinate reference systems. axis: CoordinateSystemAxis: descriptionReference: urn:ogc:def:axis-name:EPSG::9904 identifier: urn:ogc:def:axis:EPSG::114 axisAbbrev: H axisDirection: up code: urn:ogc:def:crs:EPSG::5703 return to top identificationInfo: (MD_DataIdentification) citation: (CI_Citation) title: 2012 USACE Post Sandy Topographic LiDAR: Rhode Island and Massachusetts Coast alternateTitle: 2012_USACE_PostSandy_MA_RI_lidar_m1435_metadata date: (CI_Date) date: 2013-01 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49609 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49609 protocol: WWW:LINK-1.0-http--link name: Full Metadata Record description: View the complete metadata record on InPort for more information about this dataset. function: (CI_OnLineFunctionCode) information role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: Citation URL description: Online Resource function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: This topographic elevation point data derived from multiple return light detection and ranging (LiDAR) represents 354.272 square miles of coastline for Rhode Island and Massachusetts. The LiDAR point cloud is delivered in LAS 1.2 format with the following classifications: Class 1: Unclassified Class 2: Ground Class 9: Water Class 10: Ignored Points Class 12: Overlap Original contact information: Contact Name: Steve Newman Contact Org: ERDC-CRREL, RS/GIS and Water Branch Phone: (603) 646-4372 Email: Stephen.D.Newman@usace.army.mil This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: HQ, USACE required digital elevation data to generate digital elevation models and contours for use in: damage assessment to USACE projects, engineering design and design reviews, conservation planning, research, delivery, floodplain mapping and hydrologic modeling using LiDAR technology. status: (MD_ProgressCode) completed pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact pointOfContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) custodian resourceMaintenance: (MD_MaintenanceInformation) maintenanceAndUpdateFrequency: (MD_MaintenanceFrequencyCode) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1435/supplemental/2012_USACE_PostSandy_MA_RI_footprint.KMZ fileDescription: This graphic shows the post Sandy LiDAR coverage for coastal Connecticut fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Bathymetry/Topography keyword: Elevation keyword: LAS keyword: LiDAR type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) resourceConstraints: (MD_LegalConstraints) useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Cite As: OCM Partners, [Date of Access]: 2012 USACE Post Sandy Topographic LiDAR: Rhode Island and Massachusetts Coast [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49609. resourceConstraints: (MD_Constraints) useLimitation: NOAA provides no warranty, nor accepts any liability occurring from any incomplete, incorrect, or misleading data, or from any incorrect, incomplete, or misleading use of the data. It is the responsibility of the user to determine whether or not the data is suitable for the intended purpose. resourceConstraints: (MD_LegalConstraints) accessConstraints: (MD_RestrictionCode) otherRestrictions useConstraints: (MD_RestrictionCode) otherRestrictions otherConstraints: Access Constraints: None. | Use Constraints: 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. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of Magnolia River, USACE, USGS, NOAA, the Office for Coastal Management or its partners. resourceConstraints: (MD_SecurityConstraints) classification: (MD_ClassificationCode) unclassified classificationSystem: (missing) handlingDescription: (missing) aggregationInfo: (MD_AggregateInformation) aggregateDataSetName: (CI_Citation) title: NOAA Data Management Plan (DMP) date: (unknown) identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: 49609 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49609.pdf protocol: WWW:LINK-1.0-http--link name: NOAA Data Management Plan (DMP) description: NOAA Data Management Plan for this record on InPort. function: (CI_OnLineFunctionCode) information role: (inapplicable) associationType: (DS_AssociationTypeCode) crossReference spatialRepresentationType: (MD_SpatialRepresentationTypeCode) vector language: eng; US topicCategory: (MD_TopicCategoryCode) elevation extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -71.9092352 eastBoundLongitude: -69.944377 southBoundLatitude: 41.1295003 northBoundLatitude: 41.6023329 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2012-11-11 endPosition: 2012-11-22 supplementalInformation: A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1435/supplemental/2012_USACE_PostSandy_MA_RI_footprint.KMZ return to top distributionInfo: (MD_Distribution) distributor: (MD_Distributor) distributorContact: (CI_ResponsibleParty) organisationName: NOAA Office for Coastal Management contactInfo: (CI_Contact) phone: (CI_Telephone) voice: (843) 740-1202 address: (CI_Address) deliveryPoint: 2234 South Hobson Ave city: Charleston administrativeArea: SC postalCode: 29405-2413 country: (missing) electronicMailAddress: coastal.info@noaa.gov onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov protocol: WWW:LINK-1.0-http--link name: NOAA Office for Coastal Management Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) distributor transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=1435 protocol: WWW:LINK-1.0-http--link name: Customized Download description: Create custom data files by choosing data area, product type, map projection, file format, datum, etc. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1435/index.html protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Simple download of data files. function: (CI_OnLineFunctionCode) download return to top dataQualityInfo: (DQ_DataQuality) scope: (DQ_Scope) level: (MD_ScopeCode) dataset report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Expected horizontal accuracy of elevation products for the Optech ALTM 3100 sensor, as determined from system studies and other methods, is 1/2000th of the flight height, which, in the instance of this particular project was 1,250 meters AGL, giving a horizontal tolerance of less than 0.62 meter. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: LiDAR Check Points were collected throughout the areas to assess the accuracy of the elevation data. The test points were collected in three land cover categories: - Open terrain (bare earth) - Marsh and low trees - High trees. Tested 0.214 Meter fundamental vertical accuracy at 95 percent confidence level in open terrain using RMSEz x 1.9600. Tested 0.350 Meter consolidated vertical accuracy at the 95th percentile in open terrain, marsh/low trees, and treed areas. Tested 0.265 Meter supplemental vertical accuracy at the 95th percentile in treed areas. Tested 0.397 Meter supplemental vertical accuracy at the 95th percentile in marsh and low tree areas. ; Quantitative Value: 0.109 meters, Test that produced the value: RMSE in meters result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The following methods are used to ensure LiDAR data accuracy: 1) Use of a ground control network utilizing GPS survey techniques 2) Use of airborne GPS and IMU in conjunction with the acquisition of LiDAR result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of a GPS base station at the operation airport. The following checks were performed: 1) The LiDAR data accuracy was validated by checking bare earth data against control and validation points spread throughout the project area. 2) LiDAR flightlines' overlap and edge matching were validated through visual inspection. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: LIDAR ACQUISITION: A LiDAR survey was conducted between Nov 11 and Nov 22, 2012. An Optech 3100 sensor aboard a Cessna 206/G was utilized for the survey. Flight altitude was planned at 1,250-meters. See "PROJEC REPORT" for details regarding the flight. dateTime: DateTime: 2012-11-01T00:00:00 processStep: (LI_ProcessStep) description: CHECK POINT SURVEY: A GPS survey was conducted to assess the accuracy of the LiDAR data. See "SURVEY REPORT" for details of the check point survey. dateTime: DateTime: 2012-11-01T00:00:00 processStep: (LI_ProcessStep) description: LiDAR CALIBRATION: Data collection of the survey area resulted in a total of one-hundred and five flightlines, including eight control lines, covering the project area. The range files, flight logs, raw air and ground GPS files were then taken to the office for data processing using DashMap v 5.2 (Optech, Inc.). DashMap uses the SBET to generate a set of data points for each laser return in the LAS file format. Each data point is assigned an echo value so it can be segregated based on the first and last pulse information. This project's data were processed in strip form, meaning each flight line was processed independently. Processing the lines individually provides the data analyst with the ability to QC the overlap between lines. Each strip was then imported into a project using TerraScan (Terrasolid, Ltd.) and the project management tool GeoCue (GeoCue Corp.). By creating a project the various flightlines are combined while breaking the dataset as a whole into manageable pieces. This process also converts the dataset from UTM (NAD83, 2011) to the Geographic Coordinate System (NAD 83, 2011). The ellipsoid height values were converted to NAVD88, Meters, orthometric values using Geoid 12A, provided by National Geodetic Survey (NGS). Individual lines were then checked against adjacent lines and intersecting control lines to ensure a cohesive dataset. dateTime: DateTime: 2012-12-01T00:00:00 processStep: (LI_ProcessStep) description: LiDAR CLASSIFICATION & BREAKLINE COLLECTION: A classification routine was applied to extract the initial surface model. This initial surface model was then reduced using Magnolia Rivers' proprietary methods to create the final bare-earth dataset. Upon reaching a satisfactory classification result, the bare-earth data were then checked against the control and validation points across the project area. The results of these checks showed the DEM meeting accuracy requirements. Hydro-Flattening breaklines were collected where necessary to support the final digital elevation models. A Triangular Irregular Network (TIN) was generated using the lidar ground points for each preliminary tiled deliverable and the breaklines were placed in 2D with each element's height being adjusted to the surface to create a 3D element in the MicroStation (Bentley Systems, Inc.) environment. dateTime: DateTime: 2012-12-01T00:00:00 processStep: (LI_ProcessStep) description: INTENSITY IMAGERY: The intensity images were created for this project using GeoCue (version 2012.1.27.5). The images were derived from the full LiDAR point cloud native radiometric intensity values. As per the project specifications the intensity orthos were produced at a 1-meter pixel size for the entire project. The initial GeoTIFF images were produced in UTM Zone 19N NAD83(2011) and were then transformed (reprojected) to the geographic coordinate system for delivery using Global Mapper software (version 13.2.2; Blue Marble Geographics) and clipped to the deliverable tile boundaries with an additional 2-meter buffer applied to each tile. dateTime: DateTime: 2012-12-01T00:00:00 processStep: (LI_ProcessStep) description: MODEL KEY POINTS: Model key-points were classified (ASPRS Class 8) using the TerraScan (Terrasolid Ltd.) Classify Model Keypoints routine to classify LiDAR points that fell within a specified tolerance of the full resolution ground model (i.e. all classified ground returns) resulting in a reduced resolution surface model that meets a given accuracy. An accuracy tolerance of 0.15 meters was used for this processing. dateTime: DateTime: 2012-12-01T00:00:00 processStep: (LI_ProcessStep) description: DIGITAL ELEVATION MODELS: Digital Elevation Models (DEMs) of the bare earth ground surface were generated using the TerraModeler (Terrasolid Ltd.) software. The DEMs were produced by sampling elevations at a 1-meter posting from a triangulated irregular network (TIN) model based on all classified ground returns and 3-D breakline features and output as an ESRI ASCII GRID formatted file. These ASCII GRID files were then converted to ESRI Binary GRID format. Initially, these GRIDs were generated from points and breaklines in the UTM projection (Zone 19N, NAD83(2011)). These UTM GRIDs were then transformed to geographic coordinates, using Global Mapper software, for delivery. Geographic GRIDs were clipped to the deliverable tile extents with an additional 2-meter buffer applied to each tile. dateTime: DateTime: 2012-12-01T00:00:00 processStep: (LI_ProcessStep) description: LIDAR FLIGHT LINE POLYGONS: Boundary polygons were created from the collected LiDAR swaths as ESRI shapefiles using a triangulation algorithm that produces an tight fitting outer boundary with concavities that accurately represent the swaths as flown. The planned flight line number, swath file name and date of acquisition were then added as shapefile attributes. dateTime: DateTime: 2012-12-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in NAD83 Geographic Coordinates with units of decimal degrees. The files were vertically referenced to NAVD88 using the Geoid12a model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid12a. dateTime: DateTime: 2013-01-01T00:00:00 processStep: (LI_ProcessStep) description: The vertical values in this data set have been converted to reference North American Vertical Datum of 1988 (NAVD88) (GEOID18) meters, using the GEOID18 grids provided by the National Geodetic Survey. Any datum and projection transformations were then done with the Office for Coastal Management 'datum_shift' program. Compression to an LAZ file was done with the LAStools 'laszip' program and can be unzipped with the same free program (laszip.org) Processing notes: dateTime: DateTime: 2023-07-01T05:57:28 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |