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 is a bare earth data set that was collected 24-25 March 2008 along the shoreline of the Assateague Island National Seashore in
Maryland and Virginia. The data falls in these counties: Worcester (MD) and Accomack (VA). A footprint of the data coverage may be
viewed at: ftp://ftp.coast.noaa.gov/pub/crs/beachmap/kmzs/USGS_Assateague_Island_National_Seashore_Lidar.kmz
ASCII xyz point cloud data were produced from remotely sensed, geographically referenced elevation measurements cooperatively
by the U.S. Geological Survey (USGS), the National Park Service (NPS), and National Aeronautics and Space Administration (NASA).
Elevation measurements were collected over the area using the NASA Experimental Advanced Airborne Research Lidar (EAARL); a pulsed
laser ranging system mounted onboard an aircraft to measure ground elevation, vegetation canopy, and coastal topography. The system
uses high-frequency laser beams directed at the Earth's surface through an opening in the bottom of the aircraft's fuselage.
The laser system records the time difference between emission of the laser beam and the reception of the reflected laser signal in
the aircraft. The plane travels over the target area at approximately 50 meters per second at an elevation of approximately 300 meters.
The EAARL, developed by NASA at Wallops Flight Facility in Virginia, measures ground elevation with a vertical resolution of 15 centimeters.
A sampling rate of 3 kilohertz or higher results in an extremely dense spatial elevation dataset. Over 100 kilometers of coastline can be
easily surveyed within a 3- to 4-hour mission. When subsequent elevation maps for an area are analyzed, they provide a useful tool to
make management decisions regarding land development.
Original contact information:
Contact Name: Amar Nayegandhi
Contact Org: Jacobs Technology, U.S. Geological Survey, FISC, St. Petersburg, FL
Title: Computer Scientist
Phone: 727-803-8747 (x3026)
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.
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):
- 2008-09-15 00:00:00 - The data are collected using a Cessna 310 aircraft. The NASA Experimental Advanced Airborne Research Lidar (EAARL) laser scanner collects the data using a green (532-nm) raster scanning laser, while a digital camera acquires a visual record of the flight. The data are stored on hard drives and archived at the U.S. Geological Survey office in St. Petersburg, Florida and the NASA office at Wallops Flight Facility in Virginia. The navigational data are processed at Wallops Flight Facility. The navigational and raw data are then downloaded into the Airborne Lidar Processing System (ALPS). Data are converted from units of time to x, y, z points for elevation. The derived surface data can then be converted into raster data (GeoTIFFs).
- 2008-09-15 00:00:00 - Metadata imported into ArcCatalog from XML file.
- 2010-02-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data to make it available within Digital Coast: 1. The data were converted from UTM, Zone 18 coordinates to geographic coordinates. 2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03. 3. The LAS header fields were sorted by latitude and updated.
(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.
- 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.
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.
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.