2015 FEMA Lidar: Ashland County, WI | spatialRepresentationInfo|
---|---|
(MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:58871 language: LanguageCode: eng characterSet: (MD_CharacterSetCode) UTF8 hierarchyLevel: (MD_ScopeCode) dataset hierarchyLevelName: Elevation 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: Website description: NOAA Office for Coastal Management Home Page function: (CI_OnLineFunctionCode) information role: (CI_RoleCode) pointOfContact dateStamp: DateTime: 2020-09-15T00:00:00 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: (MD_VectorSpatialRepresentation) topologyLevel: (MD_TopologyLevelCode) geometricObjects: (MD_GeometricObjects) geometricObjectType: (MD_GeometricObjectTypeCode) point geometricObjectCount: 10123052741 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 (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: 2015 FEMA Lidar: Ashland County, WI date: (CI_Date) date: 2015-09-24 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 58871 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9017/supplemental/Ashland_Co_WI_Post-Flight_Lidar_Report%20(1).pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download role: (inapplicable) citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9017/supplemental/55003C%20Elevation%20Data%20QA%20Report%20for%20Ashland%20County%20Wisconsin.pdf protocol: WWW:LINK-1.0-http--link name: Dataset report description: Link to data set report. function: (CI_OnLineFunctionCode) download 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: NOAA's Office for Coastal Management (OCM) Data Access Viewer (DAV) description: The Data Access Viewer (DAV) allows a user to search for and download elevation, imagery, and land cover data for the coastal U.S. and its territories. The data, hosted by the NOAA Office for Coastal Management, can be customized and requested for free download through a checkout interface. An email provides a link to the customized data, while the original data set is available through a link within the viewer. function: (CI_OnLineFunctionCode) download role: (inapplicable) presentationForm: (unknown) abstract: This task order requires lidar data to be acquired over Ashland County, Wisconsin. The total area of the Ashland AOI is approximately 1,011 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 1.0 meter. Each LAS file contains lidar point information, which has been calibrated, and controlled. Additional deliverables include lidar processing report in PDF format, FGDC project level metadata file in .xml format. Ground conditions: Water at normal levels; no unusual inundation; no snow; leaf off. TASK NAME: Ashland County Wisconsin Lidar Lidar Data Acquisition and Processing Production Task STARR Project No. 400000254 Task Order No. HSFE05-14-J-0037 Woolpert Order No. 74908 CONTRACTOR: Woolpert, Inc. This data set is comprised of lidar point cloud data, project tile index, project data extent, base station shapefile, flight line trajectories shapefile, planned flight line shapefile, and swath index shapefile This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The lidar data will be acquired and processed under the requirements identified in this task order. credit: FEMA, Woolpert 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 Oct 20, 2020 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: 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: 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://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9017/supplemental/extent_2015_Ashland_WI_m9017.kmz fileDescription: This graphic displays the footprint for this lidar data set. fileType: KML descriptiveKeywords: (MD_Keywords) keyword: Earth Science > Land Surface > Topography > Terrain Elevation keyword: Earth Science > Oceans > Bathymetry/Seafloor Topography > Bathymetry > Coastal Bathymetry keyword: Earth Science > Oceans > Coastal Processes > Coastal Elevation type: (MD_KeywordTypeCode) theme thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Science Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Continent > North America > United States Of America keyword: Continent > North America > United States Of America > U.S. Coastline keyword: Continent > North America > United States Of America > Wisconsin keyword: Vertical Location > Land Surface type: (MD_KeywordTypeCode) place thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Location Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Earth Remote Sensing Instruments > Active Remote Sensing > Profilers/Sounders > Lidar/Laser Sounders > LIDAR > Light Detection and Ranging type: (MD_KeywordTypeCode) instrument thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Instrument Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Aircraft > Aircraft type: (MD_KeywordTypeCode) platform thesaurusName: (CI_Citation) title: Global Change Master Directory (GCMD) Platform Keywords date: (missing) descriptiveKeywords: (MD_Keywords) keyword: Lidar - partner (no harvest) type: (MD_KeywordTypeCode) project thesaurusName: (CI_Citation) title: InPort date: (inapplicable) 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. | Distribution Liability: Woolpert prepared the original data as set forth in the Scope of Services, in accordance with reasonable care and due diligence as set forth in this Agreement, however, due to the easily alterable nature of electronic media, files, documents, and other deliverables, Woolpert, Inc. makes no warranties, either expressed or implied, with respect to the accuracy, completeness, merchantability, or fitness for any particular purpose, including, but not limited to, use of any/all data as described within this metadata file, by any user of this data. Any use will be at the end-user’s sole risk. Any conclusions drawn from the analysis of this information are not the responsibility of 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: 58871 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/58871.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: Microsoft Windows 7 Version 6.1 (Build 7600); ArcMap 10.2; ArcCatalog 10.2; TerraScan ver. 14.003; TerraModeler ver. 14.003; Geocue 2012.1.27.5; LP360 2011.1.54.1. Approximate size of entire delivery dataset = 300 GB extent: (EX_Extent) geographicElement: (EX_GeographicBoundingBox) westBoundLongitude: -90.951599 eastBoundLongitude: -90.256338 southBoundLatitude: 45.967043 northBoundLatitude: 46.881274 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2014-11-01 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2014-11-02 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2015-04-17 supplementalInformation: The following are the USGS lidar fields in JSON: { "ldrinfo" : { "ldrspec" : "USGS NGP Base Specifications v1", "ldrsens" : "Leica ALS70", "ldrmaxnr" : "4", "ldrnps" : "1", "ldrdens" : "1", "ldranps" : "1", "ldradens" : "1", "ldrfltht" : "2377", "ldrfltsp" : "150", "ldrscana" : "40", "ldrscanr" : "34.4", "ldrpulsr" : "230", "ldrpulsd" : "5", "ldrpulsw" : "5", "ldrwavel" : "1064", "ldrmpia" : "1", "ldrbmdiv" : "0.22", "ldrswatw" : "1731", "ldrswato" : "25", "ldrcrs" : "NAD_1983(2011)_UTM_Zone_15N_Meters", "ldrgeoid" : "GEOID12A" }, "lasinfo" : { "lasver" : "1.2", "lasprf" : "1", "laswheld" : "Geometrically unreliable points will be identified using a combination of automated and manual techniques and subsequently classified as swath overlap and or noise.", "lasolap" : "swath overlap points will be classified per contract specifications", "lasintr" : "8", "lasclass" : { "clascode" : "1", "clasitem" : "default/unclassified" } }} return to top distributionInfo: (MD_Distribution) distributionFormat: (MD_Format) name: Zip version: (missing) fileDecompressionTechnique: Zip distributionFormat: (MD_Format) name: LAZ version: (missing) 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: 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=9017 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. A new metadata will be produced to reflect your request using this record as a base. Change to an orthometric vertical datum is one of the many options. function: (CI_OnLineFunctionCode) download transferOptions: (MD_DigitalTransferOptions) onLine: (CI_OnlineResource) linkage: https://coast.noaa.gov/htdata/lidar3_z/geoid18/data/9017 protocol: WWW:LINK-1.0-http--link name: Bulk Download description: Bulk download of data files in LAZ format, geographic coordinates, orthometric heights. Note that the vertical datum (hence elevations) of the files here are different than described in this document. They will be in an orthometric datum. 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: Compiled to meet 0.42 meters horizontal accuracy at 95 percent confidence level. Quantitative value: 0.42m , Test that produced the valued: lidar system specifications are available in the project report result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The FVA accuracy is to be tested against a Triangulated Irregular Network (TIN). The TIN is constructed from lidar points where at least 5 times the NPS exists in a clear and open area, with less than 1/3 of the RMSE deviation from a low-slope plan not exceeding 10%. The FVA checkpoints should be well-distributed throughout the land cover and avoid any grounds disturbed from activity, area of low NIR reflectivity, or area that may have an obstruction 45 degrees from the horizon present that could diminish the accuracy of the TIN FVA = 4 cm RMSE (8 cm at 95% confidence level). According to USGS Specification 1.0, the Consolidated Vertical Accuracy (CVA) is the result of the LIDAR digital terrain model’s accuracy using 3-D Quality Assurance/Quality Control (QA/QC) checkpoints in multiple land cover categories, combining the SVA and the FVA. This assessment will include areas of open terrain (FVA), and areas of vegetated terrain (SVA) representative of the predominant land cover type for the tested area. The CVA is always accompanied by a separate individual measure of the FVA, which was included in section 3.7.2 Fundamental Vertical Accuracy Assessment, of the STARR document. The vertical accuracy is computed using a nonparametric testing method (95th percentile) and is to be tested between a DEM of the bare earth elevation values built from the classified LIDAR points, and the recorded elevation measures from a ground survey team. The vertical accuracy checkpoints should be well-distributed throughout the study area. CVA = 9.6 cm RMSE ( 18.9 cm at 95% confidence level). result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: The lidar data is visually inspected for completeness to ensure that are no void areas or missing data. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: All formatted data cover the entire area specified for this project and are validated using a combination of commercial lidar processing software, GIS software, and proprietary programs to ensure proper formatting and loading prior to delivery. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: Using two Leica ALS70 (lidar) systems on board a Cessna 404 and Cessna 310 aircraft, high density data, at a nominal pulse spacing (NPS) of 1.0 meter, were collected for this task order (approximately 1, square miles). AGL = 7800 feet - Aircraft Speed = 150 Knots, Field of View (Full) = 40 degrees, Pulse Rate = 230 kHz, Scan Rate = 34.4 Hz, with an average side lap of 25%. Multiple returns were recorded for each laser pulse along with an intensity value for each return. Three (3) missions were flown between November 1, 2014 and April 17, 2015. Two (2) Global Navigation Satellite System (GNSS) Base Stations were used in support of the lidar data acquisition. Specific information regarding latitude, longitude, and ellipsoid height to the L1 phase center is included in the lidar processing report. The geoid used to reduce satellite derived elevations to orthometric heights was GEOID12A. Data for the task order is referenced to the UTM Zone 15N, North American Datum of 1983 (2011) meters, and NAVD88, in US Survey Feet. Once the data acquisition and GPS processing phases are complete, the lidar data was processed immediately to verify the coverage had no voids. The GPS and IMU data was post processed using differential and Kalman filter algorithms to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. The SBET was used to reduce the lidar slant range measurements to a raw reflective surface for each flight line. The ALS70 calibration and system performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of lidar data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw lidar data is reduced using the refined misalignment angles. dateTime: DateTime: 2014-11-01T00:00:00 processStep: (LI_ProcessStep) description: The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. The surveyed ground control points provided by Compass Data are used to make vertical adjustments to the data set and to perform the accuracy checks and statistical analysis of the lidar dataset. This LAS 1.2 dataset contains return numbers beyond a 5th return (6th, 7th, 8th, etc). A fully compliant LAS 1.2 file only supports the encoding of up to and including 5 returns in the LAS header information. Any subsequent returns (6th, 7th, 8th, etc) cannot be encoded in the header and most lidar processing software will generate a warning stating "Number of points by return not equal point record count". The scan angle rank in point data record is the angle at which the laser point was output from the laser system includes roll of the aircraft added by roll compensation. Due to the tiled nature of the LAS data, some LAS files may exhibit a lower scan angle rank than what the overall project was acquired at and/or contain only negative or positive scan angle ranks. This is due to the fact that when swath data is imported to a tiled format that tile assumes whatever scan angle rank values that fall within that tile boundary. Scale Factor- The vertical scale factor of this lidar dataset is 0.01. The LAS generating software defaults the vertical scale factor to 0.001. The Z-value of a lidar point at 50.53 ft is stored by the software as 50.530 ft. This is what is known as “fluff”. There is nothing wrong with the data only that most lidar processing softwares are able to detect this “fluff” and display a warning. Supervisory QC monitoring of work ensured consistency of calibration and adjustments in adherence to project requirements across the entire project area. The resulting deliverables for this task order consist of unclassified LAS 1.2 files provided in a tiled format, fgdc metadata, and a post-flight aerial acquisition and calibration report. As part of this report, additional shape files were delivered and include flight line trajectories, planned flight lines, swath index, base station locations, tile index, and buffered AOI. dateTime: DateTime: 2015-04-16T00:00:00 processStep: (LI_ProcessStep) description: Tile Size: 1,500m x 1,500m. The tile file name was derived from the southwest corner of each tile. dateTime: DateTime: 2014-11-01T00:00:00 processStep: (LI_ProcessStep) description: NOAA OCM retrieved 1,276 las files from the WisconsinView wbestie (https://wisconsinview.org/). The files had intensity values, were in UTM 15N projection referenced to NAD83(2011) with linear units in meters, and orthometric heights having used geoid 12A with vertical units in US Survey feet. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The las files were converted from las to laz format using LASTools laszip. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 3. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 12A model, to convert from UTM 15N (NAD83 2011) coordinates in meters to geographic coordinates, to convert vertical units from feet to meters, to assign the geokeys, to sort the data by gps time and zip the data to database and to http. processor: (CI_ResponsibleParty) organisationName: Office for Coastal Management role: (CI_RoleCode) processor source: (LI_Source) description: Source Contribution: This data set is the project specified acquired point cloud data. sourceCitation: (CI_Citation) title: Lidar acquisition date: (CI_Date) date: 2015-04-28 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Woolpert role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2014-11-01 source: (LI_Source) description: Source Contribution: This data set is the project specified lidar deliverables. sourceCitation: (CI_Citation) title: Lidar deliverable processing date: (CI_Date) date: 2015-05-28 dateType: (CI_DateTypeCode) publication citedResponsibleParty: (CI_ResponsibleParty) organisationName: Woolpert role: (CI_RoleCode) originator sourceExtent: (EX_Extent) temporalElement: (EX_TemporalExtent) extent: TimeInstant: timePosition: 2014-11-02 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: 2020-10-20T05:12:15 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor |