Data Management Plan
GUID: gov.noaa.nmfs.inport:48145 | Published / External
Data Management Plan
DMP Template v2.0.1 (2015-01-01)
Please provide the following information, and submit to the NOAA DM Plan Repository.Reference to Master DM Plan (if applicable)
As stated in Section IV, Requirement 1.3, DM Plans may be hierarchical. If this DM Plan inherits provisions from a higher-level DM Plan already submitted to the Repository, then this more-specific Plan only needs to provide information that differs from what was provided in the Master DM Plan.
1. General Description of Data to be Managed
Atlantic was contracted to acquire high resolution topographic LiDAR (Light Detection and Ranging) data
located in Mobile County, Alabama. The intent was to collect one (1) Area of Interest (AOI) that
encompasses Mobile County. The total client defined AOI was 1,402 square miles or 3,361
square kilometers. The data were collected from January 12 - 22, 2014. Classifications of data available from NOAA OCM are: 1 (Unclassified, 2 (Ground), 3 (Low Vegetation), 7 (Low Noise), 8 (Model Key Points), 9 (Water), 10 (Ignored Ground, Breakline Proximity). Low vegetation points were removed as they were incorrect and not required for delivery.
Digital Elevation Models (DEMs) created from this lidar data are available for download. They are available at: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=5169 . Breaklines are available at: https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4966/supplemental/breaklines
Original contact information:
Contact Name: Scott Kearney
Contact Org: City of Mobile
Phone: (251) 208-7942
Email: kearney@cityofmobile.org
Notes: Only a maximum of 4000 characters will be included.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: All time frames from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., satellite, airplane, unmanned aerial system, radar, weather station, moored buoy, research vessel, autonomous underwater vehicle, animal tagging, manual surveys, enforcement activities, numerical model, etc.)
2. Point of Contact for this Data Management Plan (author or maintainer)
Notes: The name of the Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
3. Responsible Party for Data Management
Program Managers, or their designee, shall be responsible for assuring the proper management of the data produced by their Program. Please indicate the responsible party below.
Notes: The name of the Person of the most recent Support Role of type "Data Steward" is used. The support role must be in effect.
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
5. Data Lineage and Quality
NOAA has issued Information Quality Guidelines for ensuring and maximizing the quality, objectivity, utility, and integrity of information which it disseminates.
(describe or provide URL of description):
Process Steps:
- 2014-05-10 00:00:00 - Ground Control This Geodetic Control Survey was conducted to support Light Detection and Ranging (LiDAR) data in accordance with the National Digital Elevation Program (NDEP) and the American Society for Photogrammetry and Remote Sensing (ASPRS) guidelines. A GPS control network was performed for the purposes of establishing a three-dimensional coordinates on each of the base station locations. The control network included a combination of a National Geodetic Survey (NGS) Control Monument (MOB AP STA A1), National Geodetic Survey (NGS) CORS (AL84, AL90, AL92, ALDI, ALM) ,Mobile Control Monuments (MCC1062, MCC1067, MCC1070, MCC1072, MCC1073, MOB1000, MOB1008, MOB1009, MOB1011, MOB1023, MOB1031, MOB1034) and a capped iron found (CIPF). GPS observations at all ground control points in the network were made with Leica System 500 dual frequency GPS-receivers w/ Leica AT502 antenna and a NovAtel DL 4=L1L2 receiver w/ NovAtel NOV702 3.00 antenna between April 30, 2014 and May 2, 2014.
- 2014-01-22 00:00:00 - Aerial LiDAR Acquisition: Aerial data collection was acquired, in one (9) mission, using the ALS70 SN# 7123 at an altitude of 5500 ft. MSL. This was to support a 2.0 ppm^2 LiDAR point cloud. Airborne GPS and IMU data was collected during the acquisition and supported by Topcon Viper GPS base station that occupied NGS monument MOBARP. Data acquisition was collected January 12, 2014 through January 22, 2014.
- 2014-06-11 00:00:00 - LIDAR PROCESSING: - LiDAR Calibration:Initial processing of the GPS data was processed using Inertial Explorer. The solution file was generated and ALSPP software was used to generate georeferenced laser returns which were then processed in strip form allowing for the QC of the overlap between strips (lines). The data from each line were combined and automated classification routines run to determine the initial surface model. This initial surface model was then verified to the LiDAR test points. LiDAR Classification: The calibrated LiDAR data was run through automated classification routines and then manually checked. The data was classified into the following classes: 1-unclassified, 2-ground, 3-lowpoints/noise, 9-water
- 2015-11-30 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in las format from the City of Mobile GIS office. The files contained lidar elevation and intensity measurements. The data were in Alabama State Plane West coordinates (0102, feet) and NAVD88 heights (Geoid12A, feet). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. LAS files were compressed to laz format using laszip. 2. Elevation outliers were eliminated, above 2,000 ft and below -50 ft, as these were deemed erroneous. 3. Class 3 (low vegetation) was removed as it was not part of the project specifications, furthermore these points were found to only be located in open water. 4. Reclassified all Class 11 points to Class 15 as this does not match the NOAA OCM classification scheme. 5. Data were converted from Alabama State Plane West coordinates (ft) with NAVD88 heights (ft) to geographic coordinates (decimal degrees) with ellipsoid heights (m). (Citation: Mobile County LiDAR)
(describe or provide URL of description):
6. Data Documentation
The EDMC Data Documentation Procedural Directive requires that NOAA data be well documented, specifies the use of ISO 19115 and related standards for documentation of new data, and provides links to resources and tools for metadata creation and validation.
Missing/invalid information:
- 1.6. Type(s) of data
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 4.1. Have resources for management of these data been identified?
- 4.2. Approximate percentage of the budget for these data devoted to data management
- 5.2. Quality control procedures employed
- 7.1. Do these data comply with the Data Access directive?
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.1.2. If there are limitations to data access, describe how data are protected
- 7.4. Approximate delay between data collection and dissemination
- 8.1. Actual or planned long-term data archive location
- 8.3. Approximate delay between data collection and submission to an archive facility
- 8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
(describe or provide URL of description):
7. Data Access
NAO 212-15 states that access to environmental data may only be restricted when distribution is explicitly limited by law, regulation, policy (such as those applicable to personally identifiable information or protected critical infrastructure information or proprietary trade information) or by security requirements. The EDMC Data Access Procedural Directive contains specific guidance, recommends the use of open-standard, interoperable, non-proprietary web services, provides information about resources and tools to enable data access, and includes a Waiver to be submitted to justify any approach other than full, unrestricted public access.
None
Notes: The name of the Organization of the most recent Support Role of type "Distributor" is used. The support role must be in effect. This information is not required if an approved access waiver exists for this data.
Notes: This field is required if a Distributor has not been specified.
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/4966/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
This data can be obtained on-line at the following URL:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=4966
The data set is dynamically generated based on user-specified parameters.;
Notes: This field is required if applicable.
8. Data Preservation and Protection
The NOAA Procedure for Scientific Records Appraisal and Archive Approval describes how to identify, appraise and decide what scientific records are to be preserved in a NOAA archive.
(Specify NCEI-MD, NCEI-CO, NCEI-NC, NCEI-MS, World Data Center (WDC) facility, Other, To Be Determined, Unable to Archive, or No Archiving Intended)
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.