| 2011 MDEQ Tennessee-Tombigbee Waterway Lidar Survey | spatialRepresentationInfo|
|---|---|
| (MI_Metadata) fileIdentifier: gov.noaa.nmfs.inport:49820 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(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 MDEQ Tennessee-Tombigbee Waterway Lidar Survey alternateTitle: ms2011_mdeq_tenn_tombigbee_m2560_metadata date: (CI_Date) date: 2013-09-16 dateType: (CI_DateTypeCode) publication identifier: (MD_Identifier) authority: (CI_Citation) title: NOAA/NMFS/EDM date: (inapplicable) code: Anchor: InPort Catalog ID 49820 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inport/item/49820 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: Collect and deliver high-density elevation point data derived from multiple-return light detection and ranging (LiDAR) measurements for use in supporting topographic analysis, including applications such as flood plain mapping. The Nominal Point Spacing Value for the final lidar is 3.2 ft (~1 m). Deliver LiDAR Bare Earth and Contour lines within the areas designated in areas of Clay, Itawamba, Monroe, and Lowndes Counties to aid in visual interpretation of Flood Basin elevations and for addition to the MDEM elevation dataset. Comply with mapping guidelines and specifications as stated in the FEMA Procedure Memorandum No. 61 This data set is an LAZ (compressed LAS) format file containing LIDAR point cloud data. purpose: Updating DFIRM maps, hydrologic modeling, transportation routing, floodplain mapping and assessment of natural hazards. Furthermore, the data sets can be utilized by the general public including engineers, surveyors, appraisers and others interested parties to evaluate transportation and land use planning. credit: Bryan Daniel (Atlantic Group), Josh Helton (Atlantic Group), Patrick Robinson (Atlantic Group), Paul Weyant (Atlantic Group), Barbara Yassin (MDEQ) 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) asNeeded graphicOverview: (MD_BrowseGraphic) fileName: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/supplemental/ms2011_mdeq_tenn_tombigbee.KMZ fileDescription: This graphic shows the lidar coverage for portions of the following counties in Minnesota: Olmsted County, Wabasha County, Goodhue County, St. Louis County, Fillmore County, Pine County, Kanabec County, Morrison County, Mille Lacs County, Waseca County, Blue Earth County, Steele County, Dodge County, Nicollet County, Sibley County, Freeborn County, Faribault County, Mower County, Isanti County, Anoka County, Ramsey County, Dakota County, Wright County, Scott County, Washington County, Rice County, Hennepin County, Le Sueur County, Carver County, Benton County, Sherburne County, Chisago County, Koochiching County, Itasca County, Crow Wing County, Aitkin County, Carlton County, Winona County, Houston County, Cook County, Lake County fileType: kmz descriptiveKeywords: (MD_Keywords) keyword: Bare Earth keyword: Ground Control keyword: Land Surface keyword: Light Detection and Ranging keyword: Point Cloud type: (MD_KeywordTypeCode) theme descriptiveKeywords: (MD_Keywords) keyword: Fall keyword: Winter keyword: lead off type: (MD_KeywordTypeCode) temporal 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 MDEQ Tennessee-Tombigbee Waterway Lidar Survey [Data Date Range], https://www.fisheries.noaa.gov/inport/item/49820. 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 the following: MDEQ, The Atlantic Group, 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: 49820 citedResponsibleParty: (CI_ResponsibleParty) organisationName: (inapplicable) contactInfo: (CI_Contact) onlineResource: (CI_OnlineResource) linkage: https://www.fisheries.noaa.gov/inportserve/waf/noaa/nos/ocmp/dmp/pdf/49820.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: -89.639595 eastBoundLongitude: -87.274625 southBoundLatitude: 33.372751 northBoundLatitude: 34.514993 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-03-22 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-03-23 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-03-24 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-03-24 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-03-24 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-04-01 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-04-03 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-04-09 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-04-10 temporalElement: (EX_TemporalExtent) extent: TimeInstant: description: | Currentness: Ground Condition timePosition: 2011-04-11 supplementalInformation: Reflective surface data represents the DEM created by laser energy reflected from the first surface encountered by the laser pulse. Some energy may continue beyond this initial surface to be reflected by a subsequent surface as represented by the last return data. Intensity information is captured from the reflective surface pulse and indicates the relative energy returned to the sensor as compared to the energy transmitted. The intensity image is not calibrated or normalized but indicates differences in energy absorption due to the interaction of the surface materials with laser energy at the wavelength transmitted by the sensor. Points are classified as water, bare ground or not bare ground to support creation of a bare earth model from the data. A footprint of this data set may be viewed in Google Earth at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/supplemental/ms2011_mdeq_tenn_tombigbee.KMZ The MDEQ Tennessee-Tombigbee report may be accessed at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2560/supplemental/ms2011_mdeq_tenn_tombigbee.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=2560 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/2560/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: LiDAR data horizontal accuracy is met as contracted. The Nominal Point Spacing Value for the final LiDAR is 3.2 ft (0.97 m).; Quantitative Value: 0.649 meters, Test that produced the value: Horizontal point accuracy is a function of angular origination of the pulse; IMU orientation; the scanner encoder and ranging function and will vary depending on the proposed point density selected for the collection. Statistically, the error is roughly 1/3 of the illuminated foot print on the ground and is a function of the beam divergences. This gives a final horizontal accuracy value of 2.13 feet (0.649 m). result: (missing) report: (DQ_AbsoluteExternalPositionalAccuracy) nameOfMeasure: Vertical Positional Accuracy evaluationMethodDescription: LiDAR vertical data accuracy determination shall employ the National Standard for Spatial Data Accuracy (NSSDA).The Nominal Point Spacing Value for the final LiDAR is 3.2 ft.; Quantitative Value: 0.07 meters, Test that produced the value: Based on the vertical accuracy testing conducted by The Atlantic Group, LLC using NSSDA methodology, the dataset tested for vertical accuracy at 95% confidence level in open terrain, based on open terrain. This gives a final vertical accuracy value of 0.24 feet (0.07 m). result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Measure evaluationMethodDescription: Cloud Cover: 0 result: (missing) report: (DQ_CompletenessCommission) nameOfMeasure: Completeness Report evaluationMethodDescription: All data is complete to standards as specified. LIDAR raster data is visually inspected for completeness to ensure that any gaps between flight lines of required collection area. LIDAR is self-illuminating and has minimal cloud penetration capability. Water vapor in steam plumes or particulates in smoke may cause reflection of LIDAR signals and loss of elevation information beneath these plumes. Glass structures and roofs may appear transparent to the LIDAR signal and therefore may not register on the reflective surface. result: (missing) report: (DQ_ConceptualConsistency) nameOfMeasure: Conceptual Consistency evaluationMethodDescription: QC/QA process includes review of flight alignments and completeness of supporting data. The MDEQ or its designee may perform additional QC/QA testing. The root mean square error (RMSE) is used to estimate both horizontal and vertical accuracy. RMSE is the square root of the average of the set of squared differences between dataset coordinate values and coordinate values from an independent source. Bare-earth processed data for this acquisition block comply with the following accuracy requirements for Artifact/Feature removal: artifacts - 90%; outliers - 95%; vegetation - 95%; buildings - 98%. All LAS formatted LIDAR data are validated using commercial GIS software to ensure proper formatting and loading before delivery. This validation procedure ensures that data on delivery media is in correct physical format and is readable. Higher accuracy for identical points. If those differences are normally distributed and average zero, 95 percent of any sufficiently large sample should be less than 1.96 times the RMSE. Therefore 9-centimeter RMSE can be referred to as "18-centimeter accuracy at the 95-percent confidence level." Following that convention, the vertical accuracy of any DEM is defined as 1.96 times the RMSE of linearly interpolated elevations in the DEM, as compared with known elevations from high-accuracy test points. DEMs should have a maximum RMSE as specified to meet its required vertical accuracy. result: (missing) lineage: (LI_Lineage) statement: (missing) processStep: (LI_ProcessStep) description: The ABGPS, IMU, and raw Optech LiDAR data are integrated into the Optech post processor software. The resultant file is in a LAS binary file format. The LAS file version 1.2 formats can be easily transferred from one file format to another. It is a binary file format that maintains information specific to the LiDAR data (return#, intensity value, xyz, etc.). The resultant points are produced in the geodetic coordinates referenced to the NAD83 horizontal datum and NAVD88 2004.65 vertical datum. dateTime: DateTime: 2011-06-01T00:00:00 processStep: (LI_ProcessStep) description: The unedited data are classified to facilitate the application of the appropriate feature extraction filters. A combination of proprietary filters is applied as appropriate for the production of bare earth digital terrain models (dtms). Interactive editing methods are applied to those areas where it is inappropriate or impossible to use the feature extraction filters, based upon the design criteria and/or limitations of the relevant filters. These same feature extraction filters are used to produce elevation height surfaces. The LiDAR mass points were delivered in American Society for Photogrammetry and Remote Sensing LAS 1.2 format. The header file for each dataset is complete as define by the LAS 1.2 specification. The data was classified as follows: Class 1 = Unclassified. This class includes all non-ground classified points. Class 2 = Ground. Class 7 = Low Points. Class 9 = water. Class 9 = water. Class 10 = Ignored. Class 11 = Overlap Points. dateTime: DateTime: 2011-06-01T00:00:00 processStep: (LI_ProcessStep) description: Conversion from Geodetic coordinates NAD83 into Mississippi state plane zone 16 East using NAD83 and conversion from ellipsoid heights (us feet) into orthometric heights using NAVD88 (US Survey Foot). Files are orthogonally tiled based to a 1500m x1500m extent, and labeled with a "Tile_ID" attribute. dateTime: DateTime: 2011-06-01T00:00:00 processStep: (LI_ProcessStep) description: The NOAA Office for Coastal Management (OCM) received topographic files in .laz format from the Mississippi Department of Environmental Quality (MDEQ). The files contained lidar elevation measurements. The data were received in Mississippi State Plane East 2301, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid09 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic laz files were converted from a Projected Coordinate System (Mississippi State Plane East 2301) to a Geographic Coordinate system (NAD 83). 2. The topographic laz files' horizontal units were converted from feet to decimal degrees. 3. The topographic laz files were cleaned of error points above 535 ft and below 100 ft. 4. The topographic laz files' were converted from NAVD88 elevations to NAD83 ellipsoidal elevations using Geoid03 5. Classification 11 was moved to classification 12 due to OCM system requirements (class 11 is reserved for bathy points, though these points are overlap points, Class 12). dateTime: DateTime: 2013-09-16T00:00:00 source: (LI_Source) description: Source Contribution: Delivery of LiDAR data, Contours data, Digital Elevation Model (DEM) data, and Breaklines. | Source Geospatial Form: vector digital data | Type of Source Media: digital tape media sourceCitation: (CI_Citation) title: Tennessee-Tombigbee Study Basin, Northeastern Mississippi date: (CI_Date) date: 2012-07-31 dateType: (CI_DateTypeCode) publication 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:19:39 processor: (CI_ResponsibleParty) individualName: NOAA Office for Coastal Management contactInfo: (CI_Contact) address: (CI_Address) electronicMailAddress: coastal.info@noaa.gov role: (CI_RoleCode) processor | |