| 2011 - 2012 New York State Department of Environmental Conservation (NYSDEC) Lidar: Coastal New York (Long Island and along the Hudson River) | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49888 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:38 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: 2011 - 2012 New York State Department of Environmental Conservation (NYSDEC) Lidar: Coastal New York (Long Island and along the Hudson River) alternateTitle: ny2011_hudson_longisland_m1408_metadata date: (CI_Date) date: 2012-11 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49888 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49888 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) abstract: Light Detection and Ranging (LiDAR) data is remotely sensed high-resolution elevation data collected by an airborne collection platform. This LiDAR dataset is a survey of areas of coastal New York, including Long Island, eastern Westchester, and the tidal extents of the Hudson River. The project area consists of approximately 950 square miles. The project design of the LiDAR data acquisition was developed to support a nominal post spacing of 1.0 meter or better (1.0 meter GSD). The LiDAR data vertical accuracy is in compliance with the National Standard for Spatial Data Accuracy (NSSDA) RMSE estimation of elevation data in support of 1 ft. contour mapping products. GMR Aerial Surveys Inc. d/b/a Photo Science, Inc. acquired 740 flight lines in 63 lifts between November 2011 and April 2012, while no snow was on the ground, rivers were at or below normal levels, no strong onshore winds, high waves, floods, or other anomalous weather conditions. Specified areas of the project were collected at a tide stage where water levels are at least 1-foot below mean sea level (MSL). This collection was a joint effort by the NOAA Office for Coastal Management (OCM) and the New York State Department of Environmental Conservation. The data collection was performed with three Cessna 206 single engine aircrafts, utilizing Optech Gemini sensors; collecting multiple return x, y, and z as well as intensity data. The data were classified as Unclassified (1), Ground (2), Low Point (Noise) (7), Water (9), Breakline Edge (10), Withheld (11), Tidal Water (14), Overlap Default (17), and Overlap Ground (18), Overlap Water (25), and Overlap Tidal Water (30). Upon receipt, the NOAA Office for Coastal Management (OCM), for data storage and Digital Coast provisioning purposes, converted these classifications to the following: 1 - Unclassified 2 - Ground 7 - Low Point (Noise) 9 - Water NOAA tide gauges were used as the basis for flight planning the tidally coordinated areas. The Stevens Institute NY Harbor Observation and Prediction System (NYHOPS) data were used to confirm accuracy of NOAA predicted tides in Hudson. Some areas were collected using tidal restraints as listed below: Tidal Wetlands and tributary mouths selected for tidal coordination at Mean Sea Level (MSL) minus 1 foot were: Rondout Creek Outlet; Vanderburg Cove, Moodna Creek, Constitution Marsh, Iona Marsh, Annsville Creek, Croton River Outlet, Marlboro Marsh, Manitou Marsh, Fishkill Creek Outlet, and Wappingers Creek Outlet. The Upper Hudson area from North of Goose Island was also collected to the same specification. Tidal Wetlands and tributary mouths selected for tidal coordination at Mean Sea Level (MSL) were Haverstraw at Minisceongo Creek and Piermont Marsh. On Long Island the following areas were collected at MSL: 1) the northern shore of Nassau and Suffolk counties from approximately Glen Cove on the western boundary to Nissequogue on the eastern boundary 2) the Peconic Bay from Riverhead on the western boundary to the east end of Shelter Island and Accabonac Harbor on the eastern boundary 3) western Great South Bay. The remainder of the project area had no tidal restrictions for collection. LAS tiles indicate if they are tidally coordinated or not. If tidal coordination only covers part of the tile the tile will be labeled tidally coordinated (i.e.MSL-1). In order to post process the LiDAR data to meet task order specifications, Photo Science, Inc. established a total of 81 control points that were used to calibrate the LiDAR to known ground locations established throughout the New York project area. Trimble R8-3 GNSS receivers were used to complete the collection. Real Time Kinematic (RTK) survey methodology was typically performed using the New York State Spatial Reference Network (NYSNet), a CORS/Real Time GPS Network. Additionally, control values from various other projects completed by Photo Science in and around the project area, were used as supplemental control points to assist in the calibration of the LiDAR dataset. The dataset was developed based on a horizontal projection/datum of UTM NAD83 (NSRS2007), UTM Zone 18, meters and vertical datum of NAVD1988 (GEOID09), meters. Upon receipt, for data storage and Digital Coast provisioning purposes, the NOAA Office for Coastal Management converted the data to GRS80 Ellipsoid (GEOID09) heights, to geographic (NAD83, NSRS2007) coordinates, and from las format to laz format. LiDAR data were collected in RAW flightline swath format, processed to create Classified LAS 1.2 files formatted to 2093 individual 750m x 750m tiles, Hydro Flattening Breaklines in ESRI shapefile format, 1.0 meter gridded Tidal Water ERDAS IMAGINE (.img) files formatted to 670 individual 3000m x 3000m tiles, and 1.0 meter gridded V-Datum ERDAS IMAGINE (.img) files formatted to the same 3000m x3000m tile schema. LiDAR data were originally delivered to NOAA/Dewberry for quality control validation under Delivery Lots 1 and 2. The lineage (data quality), positional, content (completeness), attribution, logical consistency, and accuracies of all digital elevation data produced conform to the specifications stipulated in NOAA Task Order EA133C11CQ0009 - T011. This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The project was developed by the National Oceanic and Atmospheric Administration's (NOAA) Office for Coastal Management in partnership with the New York State Department of Environmental Conservation (NYSDEC) to collect and deliver topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements for areas of coastal New York including Long Island, eastern Westchester, and the tidal extents of the Hudson River. Data are intended for use in coastal management decision making, including applications such as detailed mapping of areas at risk of sea level rise according to projections developed by NYS and the remapping of Coastal Erosion Hazard Areas. Classified LAS files are used to show the manually reviewed bare earth surface. This allows the user to create Intensity Images, Breaklines and Raster DEM. credit: New York State Department of Environmental Conservation (NYSDEC) The custom download may be cited as National Oceanic and Atmospheric Administration (NOAA) Digital Coast Data Access Viewer. Charleston, SC: NOAA Office for Coastal Management. Accessed Jul 01, 2023 at https://coast.noaa.gov/dataviewer. 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) unknown graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1408/supplemental/2011_2012_NYSDEC_Lidar_Long_Island_and_Hudson_River.kmz fileDescription: This graphic shows the lidar coverage for this data set in Long Island, New York and along the Hudson River. fileType: kmz 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]: 2011 - 2012 New York State Department of Environmental Conservation (NYSDEC) Lidar: Coastal New York (Long Island and along the Hudson River) [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49888. 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: None 1. The NYS DEC / NOAA asks to be credited in derived products. 2. Any documentation provided is an integral part of the data set. Failure to use the documentation in conjunction with the digital data constitutes misuse of the data. 3. Although every effort has been made to ensure the accuracy of information, errors may be reflected in the data supplied. The user must be aware of data conditions and bear responsibility for the appropriate use of the information with respect to possible errors, original map scale, collection methodology, currency of data, and other conditions. 4. Users should be aware that temporal changes may have occurred since this data set was collected and that 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. | Distribution Liability: Any conclusions drawn from the analysis of this information are not the responsibility of NYSDEC, 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: 49888 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49888.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 environmentDescription: MicroStation Version 8; TerraScan Version 12; TerraModeler Version 12; GeoCue Version 2011.1.20.4 (64-bit); ESRI ArcGIS 10.0; Global Mapper 13; Optech DashMAP 5.2000 extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -74.078028 eastBoundLongitude: -71.828074 southBoundLatitude: 40.558624 northBoundLatitude: 42.786433 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-11-26 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-12-12 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-12-13 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-12-14 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-12-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-12-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-12-19 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-07 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-11 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-15 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-16 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-20 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-25 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-28 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-30 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-01-31 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-03 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-04 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-05 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-10 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-13 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-14 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-17 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-18 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-19 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-20 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-22 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-02-23 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-04-06 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2012-04-07 supplementalInformation: Lifts were flown out of specific airports at which base stations were set up and, sometimes, specific tide stations were used, creating another break in areas. 1B1 contained 46 flight lines and was flown on January 9, 2012 and January 11, 2012 with Optech SN247 in N2448G. 20N contained 39 flight lines and was flown on February 19-20, 2012 with Optech SN247 in N2448G. ALB contained 31 flight lines and was flown on January 7, 2012 and January 9, 2012 with Optech SN247 in N2448G. FRG-NOAA contained 144 flight lines flown on February 2-6, 2012; February 9, 2012; February 13-14, 2012 with Optech SN247 in N2448G. GON contained 15 flight lines flown on November 26, 2011 with Optech SN240 in N9471R. HTO contained 92 flight lines flown on January 15-16, 2012; January 18, 2012; and January 20, 2012 with Optech SN247 in N2448G. HWV contained 110 flight lines flown on January 25, 2012; January 28, 2012; January 30-31, 2012 with Optech SN247 in N2448G. POU contained 94 flight lines flown on December 12-14, 2012; and December 16, 2012 with Optech SN240 in N9471R. SWF-NOAA contained 32 flight lines flown on December 18-19, 2011 with Optech SN240 in N9471R. HPN contained 37 flight lines flown on April 6-7, 2012 with Optech SN246 in N7266Z. 1B1-TID-HUDSON contained 5 flight lines and was flown on February 20, 2012 with Optech SN247 in N2448G. HPN-TID-CROTON contained 5 flight lines flown on February 19, 2012 with Optech SN247 in N2448G. HPN-TID-HARVEST contained 6 flight lines flown on February 19, 2012 with Optech SN247 in N2448G. HPN-TID-PIERMON contained 4 flight lines flown on February 18, 2012 with Optech SN247 in N2448G SWF-TID-IONA-MA contained 9 flight lines flown February 17, 2012 with Optech SN247 in N2448G. SWF-TID-MARL-WA contained 5 flight lines flown February 17, 2012 with Optech SN247 in N2448G. SWF-TID-MOOD-FI contained 7 flight lines flown February 17, 2012 with Optech SN247 in N2448G. A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1408/supplemental/2011_2012_NYSDEC_Lidar_Long_Island_and_Hudson_River.kmz The Lidar Quality Assurance (QA) Report for the Hudson River area of this data set may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1408/supplemental/Coastal_NY_Priority1_Dewberry_QA_Report.pdf The Lidar Quality Assurance (QA) Report for the Long Island area of this data set may be viewed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/1408/supplemental/Coastal_NY_Priority2_Dewberry_QA_Report.pdf 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=1408 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/1408/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_QuantitativeAttributeAccuracy) nameOfMeasure: Accuracy evaluationMethodDescription: The project area required LiDAR to be collected on 1.0 meter GSD or better and processed to meet a bare earth vertical accuracy of 15.0 centimeters RMSEz or better. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Data collected to meet 50 cm RMSE. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: Deliverables were tested by Photo Science for both vertical and horizontal accuracy. All data is seamless from one tile to the next, no gaps or no data areas. Although collected on a tile-by-tile basis, breaklines are merged together to produce a single deliverable dataset. Checks are done to ensure that the data is seamless from one tile to the next before being combined and that breaklines meeting the project requirements have been collected across the entire project area. The vertical unit of the data file is in decimal meters with 2-decimal point precision. Combining the breaklines with LiDAR data to create other deliverables is another check of the data. The reported RMSEz value was determined using the calibration control points, and not the Blind Control. The calibration control points are the same points that were used to remove any bias in the dataset before bare earth editing. The listed RMSEz value shown below was calculated from the ground (ASPRS Class 2) data in the final Classified LAS file. ; Quantitative Value: 0.09 meters, Test that produced the value: RMSE in meters, as calculated from Classified LAS files result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: Datasets contain complete coverage of project area and tiles. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Raw Flightlines, Classified LAS files, Breaklines, and Raster DEMs were tested by Photo Science for both vertical and horizontal accuracy. Although collected on a tile-by-tile basis, breaklines are merged together to produce a single deliverable dataset. Checks are done to ensure that the data is seamless from one tile to the next before being combined and that breaklines meeting the project requirements have been collected across the entire project area. Combining the breaklines with LiDAR data to create other deliverables is another check of the data. All data are seamless from one tile to the next, no gaps or no data areas. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Control Process: Photo Science, Inc. established a total of 81 control points that were used to calibrate the LiDAR to known ground locations established throughout the New York project area to be used in the post processing of the LiDAR data. The points were located on relatively flat terrain on surfaces that generally consisted of grass, gravel, pavement or bare earth and were in well- defined discrete locations. Additionally, points collected for Photo Science from various projects located in the region were also used to adjust the LiDAR data to the final elevation. Surveyed points were used from the Northeast LiDAR and Fire Island, NY LiDAR projects for United States Geological Survey (USGS). See Final Survey Reports for additional collection parameters and methodologies. Raw Flight Line Process: Applanix software was used in the post processing of the airborne GPS and inertial data that is critical to the positioning and orientation of the sensor during all flights. POSPac MMS provides the smoothed best estimate of trajectory (SBET) that is necessary for Optech's post processor to develop the point cloud from the LiDAR missions. The point cloud is the mathematical three dimensional collection of all returns from all laser pulses as determined from the aerial mission. At this point this data is ready for analysis, classification, and filtering to generate a bare earth surface model in which the above ground features are removed from the data set. The point cloud was manipulated within the Optech software; GeoCue, TerraScan, and TerraModeler software was used for the automated data classification, manual cleanup, and bare earth generation from this data. Project specific macros were used to classify the ground and to remove the side overlap between parallel flight lines. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Classified LAS Process: All ground (ASPRS Class 2) LiDAR data inside of the Lake Pond and Double Line Drain hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro flattened feature to classify these ground (ASPRS Class 2) points to ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) were reclassified to the correct classification after the automated classification was completed. A class has been added to the dataset to represent the tidal water of the ocean/tidal areas collected throughout the project area. ASPRS Class 14 is being used to represent the tidal water ocean surface. While attempts were made to remove all extraneous features above the surface of the water, there may be above surface features classified to this class. Some islands below the required collection specifications have been classified to this class as well. This class was also used during the creation of the ERDAS Imagine Tidal Water Raster DEM files. The Tidal Water breaklines were used to complete the automated classification of these classes within the final LAS files. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified to Class 17 (USGS Overlap Default) and Class 18 (USGS Overlap Ground). These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the Withheld bit within various software packages. These processes were reviewed and accepted by NOAA through numerous conference calls and pilot study areas. Data was then run through additional macros to ensure deliverable classification levels matching the ASPRS LAS Version 1.2 Classification structure. GeoCue functionality was then used to ensure correct LAS Versioning. In-house software was used as a final QA/QC check to provide LAS Analysis of the delivered tiles. QA/QC checks were performed on a per tile level to verify final classification metrics and full LAS header information. All ground (ASPRS Class 2) LiDAR data inside of the collected inland breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro flattened feature. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10). All ground (ASPRS Class 2) LiDAR data inside of the collected tidal/ocean breaklines were then classified to tidal water (USGS Class 14) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro flattened feature. These points were moved from ground (ASPRS Class 2) to Ignored Ground (ASPRS Class 10). A manual QA review of the tiles was completed using in-house proprietary software to ensure full coverage, correct deliverable classification within the project area. dateTime: DateTime: 2012-01-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received the data in las format. The files contained lidar elevation and intensity measurements. The data were received in UTM, Zone 18 coordinates and vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. Files were filtered for elevation outliers. 2. Files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid09. 3. Files were converted from UTM, Zone 18 coordinates to geographic (NAD83, NSRS2007) coordinates 4. Classifications were changed from Unclassified (1), Ground (2), Low Point (Noise) (7), Water (9), Breakline Edge (10), Withheld (11), Tidal Water (14), Overlap Default (17), and Overlap Ground (18), Overlap Water (25), and Overlap Tidal Water (30) to Unclassified (1), Ground (2), Low Point (Noise) (7), and Water (9). dateTime: DateTime: 2012-11-01T00:00:00 source: (LI_Source) description: Source Contribution: Control points are used as a known elevation to adjust the LiDAR data to the surface. | Source Geospatial Form: digital data | Type of Source Media: hard drive sourceCitation: (CI_Citation) title: Control date: (CI_Date) date: 2011-01-01 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2011 source: (LI_Source) description: Source Contribution: LiDAR points were used to produce the deliverables. | Source Geospatial Form: digital data | Type of Source Media: hard drive sourceCitation: (CI_Citation) title: LiDAR date: (CI_Date) date: 2012-01-01 dateType: (CI_DateTypeCode) publication sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimePeriod: beginPosition: 2011-11-26 endPosition: 2012-04-07 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:51:48 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |