Data Management Plan
GUID: gov.noaa.nmfs.inport:48170 | 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
The data were acquired in March 2005 using the NASA Experimental Advanced Airborne Research Lidar (EAARL)
platform in Sussex County, Delaware. Once acquired, the data were processed by USGS personnel into both 2-foot contours
and digital elevation models. Multiple returns were recorded for each laser pulse. This is a bare earth data set. The points
have approximately a 3 m ground spacing. Water points remain in the bare earth data set, they have not been classified as water.
Original contact information:
Contact Org: Delaware Geological Survey
Phone: 302-831-2833
Email: delgeosurvey@udel.edu
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:
- 2005-01-01 00:00:00 - Data were collected by NASA EAARL (Experimental Advanced Airborne Lidar) during March of 2005. Flying was done out of Salisbury, Maryland. Nominal post spacing was approximately 3 meters, with data denser in areas of flight line overlap. A GPS base station was established and operated for 1 hour prior to, during, and for at least 30 minutes after completion of data collection flights (take off to touch down). The GPS collected data at 1 Hz intervals. GPS data were used for aircraft location correction. Lidar data collected for cross tracks were flown during each data collection flight. Preliminary fundamental vertical accuracy testing was performed against data collected by NRCS surveyors. Three landuse classes were tested woods, roads, and farm lanes with the aggregate average RMSe being 0.102m and the greatest RMSe observed was 0.148m. Processing was done in Airborne Lidar Processing Software (ALPS) by USGS personnel in Reston VA. Final bare-earth point data inspection and clean up was manually performed by USGS personnel in Dover Delaware and Baltimore, MD using ArcMap.
- 2009-03-31 00:00:00 - The NOAA Office for Coastal Management (OCM) received the data in shapefile format with x, y, and z. The x, y, and z values were extracted from the shapefiles and converted to ASCII formatted text using a processing loop in arc/info. The ASCII files were then converted to LAS format using an internal processing script. OCM then performed the following processing on the data to make it available within the Digital Coast: 1. The data were converted from State Plane coordinates to geographic coordinates. 2. The data were converted from orthometric to ellipsoid heights using Geoid03. 3. The LAS header fields were sorted by latitude and updated. 4. The data were filtered to eliminate outliers.
(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/111/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;
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.