Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:48143 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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 sets are generated using the OPTECH ALTM 70 kHz LIDAR system mounted onboard AeroMap's twin-engine
Cessna 320 aircraft. Classified data sets such as this one may have varying posting due to some LIDAR pulses not
reaching the ground caused by data anomalies. Accuracy statements are based on areas of moderate terrain. Diminished
accuracies are to be expected in areas of extreme terrain and dense vegetation. The accuracy of each point is expected
to meet the vertical accuracy standard; however, derived products may be less accurate in extreme terrain and dense
vegetation due to a lesser number of points defining the bare-earth in these areas. The data were QA/QC'ed but some
data holidays still exist. This data represents the last return data only.
Original contact information:
Contact Org: NOAA Office for Coastal Management
Phone: 843-740-1202
Email: coastal.info@noaa.gov
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:
- 2006-03-24 00:00:00 - The raw points for the point cloud data product were captured using AeroMap U.S.'s twin-engine Cessna equipped with our OPTECH ALTM 70 kHz LIDAR data acquisition system. The system includes differential GPS and inertial measurement systems to provide superior accuracy. The flying height is 1200 & 2000 meters Above Mean Terrain (AMT). These data were post-processed utilizing Optech's REALM (Version 3.5.4) software, which applies AeroMap U.S.'s Applanix Inertial Measurement Unit (IMU) values to the acquired Airborne Global Positioning Systems (ABGPS) data. These results are then applied to the acquired LIDAR data points and output to a LIDAR accuracy standard (LAS) format in a WGS 84, Universal Transverse Mercator (UTM), Zone 3, Meters coordinate system. Using Bentley's Microstation V8 LIDAR these data were imported in LAS format. Using TerraSolid's TerraScan (version 6.04) software, these data were imported into a TerraScan project files (PRJ) and converted (on import) to a binary files, no data were classified, all original "point cloud" data as output from REALM. These data were then output to the deliverable ASCII, space delimited, CTIXYZ format, (see attribute section for explanation of ASCII file syntax).
- 2006-03-24 00:00:00 - Created initial metadata (Citation: Lidar point cloud)
- 2007-02-09 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. All data points in the ASCII files were projected geographic decimals degrees using the USGS General Cartographic Transformation Package (GCTP) software. 2. All ASCII files containing points collected on the same date were combined into a single file and sorted by latitude. 3. The sorted files were then converted to binary LAS files and the las header fields were updated. 4. Data was QA/QC'ed and many points removed - there still remains several 'data holidays' as unique outliers in otherwise ordered areas. They can be manually edited by user if required. This data represents the last return data only. (Citation: Lidar point cloud)
(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/geoid12b/23/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
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.