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
LiDAR data collection was performed utilizing a Leica ALS-50 sensor, collecting multiple return x, y, and z data as well
as intensity data. LiDAR data was processed to achieve a bare ground surface, and was delivered in LAS format. Classified LAS
data was also used as a base for collection of hydro features, delivered in MicroStation v8 format. The dates of collection are:
1. JASPER COUNTY (full county): 20061227 to 20070216
2. COLLETON COUNTY (full county: 20070216 to 20070323
3. CHARLESTON COUNTY (Partial County): 20070222 to 20070223
Original contact information:
Contact Org: NOAA Office for Coastal Management
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):
- 2007-03-23 00:00:00 - JASPER COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Jasper County, South Carolina. Data was collected in a total of 111 flightlines at a pulse rate of 75,000 points per second. COLLETON COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Colleton County, South Carolina. Data was collected in a total of 160 flightlines at a pulse rate of 75,000 points per second. CHARLESTON COUNTY: Utilizing Photo Science's two ALS-50 LiDAR sensors, data was collected to cover Charleston County, South Carolina. Data was collected in a total of 77 flightlines at a pulse rate of 75,000 points per second.
- 2007-10-30 00:00:00 - Raw LiDAR data (collected as Process Step 1) was processed to create a bare ground surface. Process included calibration of LiDAR data to remove systematic errors (utilizing Leica's ALS Processor software), adjustment of elevation data to control positions (utilizing TerraScan software for control comparisons and adjustments), and both automatic and manual editing to correctly classify ground and non-ground data (utilizing TerraScan and TerraModeler software). In addition, QC steps were performed before and after processing. QC steps included line-to-line vertical comparisons and coverage checks, and were performed with TerraScan and GeoCue software.
- 2007-10-30 00:00:00 - Following bare ground surface creation (Process Step 2),Photo Science utilized the resulting dataset as a source for collection of hydrographic features, including double-line drains, single-line drains, and bodies of water. Hydro features were collected from bare ground surface models in MicroStation v8 software. After collection was complete, Photo Science adjusted elevation of all hydro features to ensure proper monotonicity using FME and proprietary software.
- 2008-03-21 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 the LiDAR Data Retrieval Tool (LDART) 1. The data were converted from UTM (Zone 17) coordinates to geographic coordinates. 2. The LAS data were sorted by latitude and the headers were 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.
The data set is dynamially 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.