Data Management Plan
GUID: gov.noaa.nmfs.inport:49828 | 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
This task is issued under USGS Contract No. G10PC00057, Task Order No. G15PD00091. This task order requires lidar data to be acquired over approximately 5981 square miles. The lidar was collected and processed to meet a maximum Nominal Post Spacing (NPS) of 0.7 meter. The NPS assessment is made against single swath, first return data located within the geometrically usable center portion (typically ~90%) of each swath.
The data was collected using a Leica ALS70 500 kHz Multiple Pulses in Air (MPiA) lidar sensor and a Chiroptera II sensor.
The ALS70 sensor collects up to four returns per pulse, as well as intensity data, for the first three returns. If a fourth return was captured, the system does not record an associated intensity value.
The Chiroptera II sensor provides 35 kHz bathymetric data and up to 500 kHz topographic data. The system acquires bathymetric lidar, topographic lidar and 4-band 80 MP digital camera imagery simultaneously. For this project, the flight parameters were used to provide 100% coverage. Two multiple pulse in air zones were used.
The Coastal delivery was processed and projected in Mississippi State Plane East Zone, NAD83(2011). The vertical datum used for the task order was referenced to NAVD88, GEOID12A/12B in units of US Survey Feet. These data were converted to geographic coordinates with elevation in meters above the ellipsoid for ingest into the NOAA Digital Coast. Further projection and datum processing may have occurred (see process descriptions).
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:
- 2015-01-01 00:00:00 - All airborne GNSS and IMU data was post-processed and quality controlled using Applanix MMS software. GNSS data was processed at a 1 and 2 Hz data capture rate and the IMU data was processed at 200 Hz. Position and orientation data were acquired in the aircraft using a NovAtel SPAN with LCI-100C IMU. All data were post-processed using NovAtel Inertial Explorer software to provide a tightly-coupled kinematic position and orientation solution.
- 2015-01-01 00:00:00 - When the sensor calibration, data acquisition, and GPS processing phases were complete, the formal data reduction processes by Woolpert lidar specialists included: - Processed individual flight lines to derive a raw "Point Cloud" LAS file. Matched overlapping flight lines, generated statistics for evaluation comparisons, and made the necessary adjustments to remove any residual systematic error. - Calibrated LAS files were imported into the task order tiles and initially filtered to create a ground and non-ground class. Then additional classes were filtered as necessary to meet client specified classes. - Once all project data was imported and classified, survey ground control data was imported and calculated for an accuracy assessment. As a QC measure, Woolpert has developed a routine to generate accuracy statistical reports by comparisons against the TIN and the DEM using surveyed ground control of higher accuracy. The lidar is adjusted accordingly to meet or exceed the vertical accuracy requirements. - The lidar tiles were reviewed using a series of proprietary QA/QC procedures to ensure it fulfills the task order requirements. A portion of this requires a manual step to ensure anomalies have been removed from the ground class. - The lidar LAS files are classified into the Default (Class 1), Ground (Class 2), Low Noise (Class 7), Water (Class 9), Ignored Ground (Class 10), Bridge Decks (Class 17) and High Noise (Class 18) classifications. - FGDC Compliant metadata was developed for the task order in .xml format for the final data products. - The horizontal datum used for Coastal delivery was referenced to Mississippi State Plane East Zone, NAD83(2011). The vertical datum used for the task order was referenced to NAVD88, GEOID12A/12B in units of US Survey Feet.
- 2017-04-01 00:00:00 - The NOAA Office for Coastal Management received the LAS files in from Mississippi DEQ. The data was received in Mississippi State Plane East (zone 2301) horizontal coordinates in US survey feet with vertical coordinates referenced to NAVD88 (Geoid12a) in feet. The Digital Coast performed the following processing for data storage and Digital Coast provisioning purposes: 1. Data were reprojected to geographic NAD83(2011) coordinates in decimal degrees. 2. The vertical coordinates were transformed to ellipsoidal heights in meters using Geoid12a.
(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.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/5168/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=5168;
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.