Data Management Plan
GUID: gov.noaa.nmfs.inport:58244 | 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 mosaic image contained in this file is comprised of multiple true color (RGB) images that were collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system along the shoreline of Virginia. CZMIL integrates a lidar sensor with topographic and bathymetric capabilities, an Leica RCD30 Digital camera, and a Itres' CASI-1500 hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. The Leica camera imagery was collected at an altitude of 400m with a ground swath of 400m and delivered with a resolution of 5cm to 20cm ground sample distance (GSD). Native RCD30 imagery data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages process the imagery data into GIS-compatible products for visualization and further analysis. Horizontal positions, projected in Universal Transverse Mercator (UTM), are referenced to the North American Datum of 1983 (NAD83 2011). Vertical positions are referenced to the NAD83 ellipsoid. Individual image frames have been rectified and mosaicked into blocks commensurate with the collection blocks. Delivered data has been clipped to boundaries of Military Grid Reference System (MGRS). The data file naming convention is based on the year, project, area name, clip boundary, and product type. These file have been separated and delivered by JALBTCX collection blocks. An example file name is "2017_NCMP_VA_18SVF1370_RGBN.tif", where 2017 is the year of data collection, NCMP is the Effort under which data were collected, VA is the area of data collection, the associated MGRS grid, and "RGBN" is the product type. In rare cases file names may include whether data was collected at a nominal range of high tide (HT) or low tide (LT). The supplementary files are of the same name.
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):
- 2017-10-19 00:00:00 - These data were collected using a Leica RCD30 Digital Camera owned by the USACE Army Corps of Engineers Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) and operated through contract. The RCD30 is a high quality, 60MP digital frame camera. All raw data streams were transferred to the office for downloading and processing. Leica's FramePro software was used to develop and in some cases color-balance the raw data into unrectified true color JPEG format images. All Iimage timing, position and rotational information was stored in Exterior Orientation (EO) file. The exterior orientation file along with the developed JPG or TIF images and CZMIL Lidar based DEM were ingested into SimActive Correletor 3D. "SimActive’s Correlator3D™ software is a patented end-to-end photogrammetry solution for the generation of high-quality geospatial data from satellite and aerial imagery, including UAVs. Correlator3D™ performs aerial triangulation (AT) and produces dense digital surface models (DSM), digital terrain models (DTM), point clouds, orthomosaics and vectorized 3D features. Powered by GPU technology and multi-core CPUs, Correlator3D™ ensures matchless processing power to support rapid production of large datasets." Correlator 3D uses computer vision algorithms to refine the positional and rotational information of each frame relative to the surrouding frames. The result is a seamless, accurate, color balanced and tiled image mosaic. Tiles were generated from MGRS grids. The final mosaics were QA/QC ArcMAP.
(describe or provide URL of description):
These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.
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.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
- 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.3. Data access methods or services offered
- 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. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.
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.
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.