| 2009-2010 USACE Vicksburg District Lidar: Mississippi Phase II | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49818 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:36 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(NSRS2007) 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/4759/export/?format=gml role: (missing) code: urn:ogc:def:crs:EPSG:4759 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: 2009-2010 USACE Vicksburg District Lidar: Mississippi Phase II alternateTitle: ms20092010_usace_phaseII_m2600_metadata date: (CI_Date) date: 2013-12-20 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49818 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49818 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: Phase two will consist of post processing of the data collected. Aeroquest Optimal, Inc. shall process the digital elevation data from a precision airborne (LIDAR) survey within the entire project area. The proposed project area is approximately 6.3 million acres. The purpose of the survey is to obtain measurements of the bare ground surface, as well as top surface feature elevation data for providing geometry input to USACE hydraulic modeling program. This project for USACE, Vicksburg District was to provide digital orthophotography using DMC imagery for approximately 4,120 square miles located in NW Mississippi at a 2-foot pixel resolution. Original contact information: Contact Name: Elijah C. Hunt Contact Org: U.S. Army Corps of Engineers, Vicksburg District Phone: (601) 631-7040 Email: elijah.c.hunt@us.army.mil This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: The purpose of this survey is to provide the Vicksburg District with bare earth and top surface elevation data for providing geometry input to USACE hydraulic modeling programs. 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/2600/supplemental/ms2009_2010_usace_phaseII.KMZ fileDescription: This graphic shows the lidar coverage for the 2009-2010 Phase II collection area in Mississippi. fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: LAZ type: (MD_KeywordTypeCode) theme 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]: 2009-2010 USACE Vicksburg District Lidar: Mississippi Phase II [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49818. 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 Aeroquest Optimal, Inc., MDEQ, USACE, 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: 49818 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49818.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: -90.0886487 eastBoundLongitude: -88.8334027 southBoundLatitude: 33.6759277 northBoundLatitude: 34.981004 temporalElement: (EX_TemporalExtent) extent: TimePeriod: description: | Currentness: Ground Condition beginPosition: 2009-12-17 endPosition: 2010-07-09 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/2600/supplemental/ms2009_2010_usace_phaseII.KMZ Reports explaining collection and quality assurance is available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2600/supplemental/ms2009_2010_usace_phaseII.pdf return to top contentInfo: (MD_FeatureCatalogueDescription) complianceCode: false language: LanguageCode: eng includedWithDataset: false featureCatalogueCitation: (CI_Citation) title: none date: (unavailable) 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=2600 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/2600/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: Elevations are recorded in floating-point meters and the vertical datum is ellipsoidal (GEOID03). result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Horizontal Positional Accuracy evaluationMethodDescription: Expected accuracies are not tested accuracies. OPTECH ALTM 3100 LiDAR Sensor - Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/2,000th of the flight height, which, in the instance of this particular project, was 3,280 U.S. survey feet (1,000 meters) AGL, giving a horizontal tolerance of less than 1.640 U.S. survey feet (0.500 meters). OPTECH ALTM 3100EA LiDAR Sensor - Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/5,500th of the flight height which, in the instance of this particular project, was 3,280 U.S. survey feet (1,000 meters) AGL, giving a horizontal tolerance of less than 0.596 U.S. survey feet (0.182 meters). OPTECH ALTM Gemini LiDAR Sensor - Expected horizontal accuracy of elevation products as determined from system studies and other methods is 1/11,000th of the flight height, which, in the instance of this particular project, was 5,905 U.S. survey feet (1,800 meters) AGL, giving a horizontal tolerance of less than 0.537 U.S. survey feet (0.164 meters). Horizontal positional accuracy for LiDAR is dependent upon the quality of the GPS/INS solution, sensor calibration and ground conditions at the time of data capture. The standard system results for horizontal accuracy are less than 1 meter. Not tested therefore horizontal accuracy is assumed as 1.0 m. ; Quantitative Value: 1.0 meters, Test that produced the value: See LiDAR data report. result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: The LiDAR data was tested against control points established using RTK GPS techniques. Six-hundred and seventy-nine (679) test points were collected throughout the project area in several vegetation categories. The RMSE calculations were performed on the bare-earth, orthometric surface and determined for each of the four LiDAR acquisition areas separately. ; Quantitative Value: 0.11 meters, Test that produced the value: The following statements are derived in accordance with the ASPRS Guidelines for Vertical Accuracy Reporting for LiDAR Data (Flood, M., 2004). Tested 0.365 U.S. survey feet (0.111 meters) fundamental vertical accuracy at the ninety-five percent confidence level in open terrain using RMSEz x 1.9600. Tested 0.431 U.S. survey feet (0.131 meters) consolidated vertical accuracy at the ninety-five percent confidence level in open terrain, high grass and trees using RMSEz x 1.9600. result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: LiDAR data has been collected and processed for all areas within the project study area. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: Analysis of parallel acquisitioned EO shows a RMS of 1.801ft , 2.101 ft and 3.100 ft for XYZ, respectively. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: During acquisition, two base stations were used to support the precise positioning and orientation of the LiDAR sensor head. At times an additional base station set at the Oxford Airport was used as a back-up. The base stations were positioned so that the aircraft would be no further than 20-miles from a single base station at any time during the flight and were placed on the control points established by Maptech during the ground control phase of the project. The LiDAR acquisition commenced on December 17, 2009 and was completed on March 5, 2010. Initial processing of the LiDAR data determined that reflights were necessary; in part because of sensor or base station malfunctions. The reflights occurred between June 27, 2010 and July 9, 2010. To achieve better penetration of the vegetation during the reflights, two passes were conducted over the reflight area; one in each direction. Detailed flight information and flight logs can be found in the separate Flight Report submitted with the project. dateTime: DateTime: 2010-03-05T00:00:00 processStep: (LI_ProcessStep) description: For redundancy and accuracy purposes, the airborne GPS data were processed from two base stations using POSGPS from Applanix, Inc. The agreement between a minimum of two solutions checked or combined between a minimum of two stations was better than 10 cm in each of X, Y, and Z. These trajectories were used in the processing of the inertial data. The inertial data were processed using POSProc from Applanix, Inc. This software produces an SBET ("smooth best estimate of trajectory") using the GPS trajectory from POSGPS and the roll, pitch and heading information recorded by the POS (Position Orientation System). 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 the geographic coordinate system (NAD83) to the State Plane Coordinate System (NAD83), Mississippi West, Feet, and utilizing standard ESRI transformations. The ellipsoid height values were converted to NAVD88, Feet, orthometric values using Geoid03, provided by NGS. Individual lines were then checked against adjacent lines and intersecting control lines to ensure a cohesive dataset. The data from each line were then combined and LiDAR intensity images were produced to visually check the horizontal positioning of the LiDAR data. Stereo pairs were generated from the LiDAR intensity data using Geocue and LiDAR1CuePac (Geocue Corp.). LiDARgrammetry was then utilized to collect breaklines where necessary along hydro features to support the contour generation. These breaklines were collected as a 3D element in the MicroStation (Bentley Systems, Inc.) environment utilizing ISSD (Z/I Imaging). A Triangular Irregular Network (TIN) was generated using the final surface data. Contours were then created from the TIN utilizing TerraModeler (Terrasolid, Ltd.). processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files in text format from the Mississippi Department of Environmental Quality (MDEQ). The files contained lidar easting, northing and elevation. The data were received in Mississippi State Plane West 2302, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid03 model. The vertical and horizontal units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The ASCII files were converted from txt format to las format using LASTools' txt2las 2. The LAS tiles were retiled to remove the buffer, then duplicate points were removed 3. The LAS tiles were then run through LASGround in order to extract surface classifications. 4. The las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid03. 5. The las files' vertical units were converted from feet to meters, removing bad elevations. 6. The las files were converted from a Projected Coordinate System (MS SP West) to a Geographic Coordinate system (NAD83) 7. The las files' horizontal units were converted from feet to decimal degrees and converted to laz format. dateTime: DateTime: 2013-12-20T00: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-01T06:28:07 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |