Data Management Plan
GUID: gov.noaa.nmfs.inport:68532 | 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
These files contain rasterized topobathy lidar elevations generated from data collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with simultaneous topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform for use in coastal mapping and charting activities. Native lidar data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 Universal Transverse Mercator Zone 17 North (NAD83 UTM Zone 17N). Vertical positions are referenced to the NAD83 (2011) ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12B model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Once converted to orthometric heights, the data are then converted to the International Great Lakes Datum of 1985 (IGLD85) using the VDatum program from NOAA (National Oceanic and Atmospheric Administration). The 3-D position data are sub-divided into a series of LAS files, which are tiled into 1-km by 1-km boxes defined by the Military Grid Reference System.
These data were received by the NOAA Office for Coastal Management (OCM) from the USACE JALBTCX (Joint Airborne Lidar Bathymetry Technical Center of Expertise). NOAA OCM processed the data to be available for custom and bulk downloads from the NOAA Digital Coast Data Access Viewer (DAV). In addition to these bare earth Digital Elevation Model (DEM) data, the lidar point data that these DEM data were created from are also available from the NOAA Digital Coast. The link to these data are provided in the URL section of this metadata record. DEMs at a a 1 meter grid spacing, created from all classifications, are available by request at firstname.lastname@example.org.
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):
CZMIL data is processed from raw lidar waveforms to point clouds using the CZMIL HydroFusion software package. Point clouds are then classified and edited in industry-standard software packages. Derivative data products are generated through the application of gridding and contouring algorithms in a GIS environment. The data processing workflow, including software packages, algorithms and parameters are provided in detail, herein this metadata as Process Steps.
- 2021-06-04 00:00:00 - LAS files are imported into TerraScan V13 module within MicroStation V8i, classifies valid topobathy data as ground points (2) and unclassified points (1), and valid bathymetric points (29). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithm's ground surface instead of manually reclassifying those points. They are partitioned into a series of 1-km delivery boxes, one Classified LAS file per box. The format of the file is LAS version 1.2. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data), and 29 (valid bathymetric data). Vertical positions are also transformed from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Once converted to orthometric heights, the data are then converted to the International Great Lakes Datum of 1985 (IGLD85) using the VDatum program from NOAA (National Oceanic and Atmospheric Administration).
- 2021-12-27 00:00:00 - Data classified as ground points (2) and bathymetric points (29) in the las files are converted to a grid by generating a triangulated irregular network (TIN) and then extracting the grid node elevations from the TIN surface. The origin point of the grid is located at a horizontal position whose value is evenly divisible by the 1m grid resolution such that rasters from subsequent surveys have common cell boundaries. JALBTCX uses Quick Terrain Modeler V8.2.1 to perform this operation utilizing the following parameters; Legacy Triangulation, Max Sample Excursion - 500, Max Triangle Side 500, and Tiling Settings Snap to Grid (Expand). The grid is exported from Quick Terrain Modeler as a GeoTIFF 32-Bit DEM file. Utilizing an in-house python script within Jupyter Notebook, the null data values in the file are converted from -9999 to NoData with the Set Null tool from the ArcGIS Spatial Analyst Toolbox. The script also calls the Define Projection tool from the ArcGIS Data Management Toolbox to set the file's coordinate system information to The North American Datum of 1983 (2011). The raster is then multiplied against a corresponding 1m mask raster, an intermediate mask image produced from JALBTCX's 1mGrid data product, to remove interpolated areas where data does not exist.
- 2022-11-21 00:00:00 - The NOAA Office for Coastal Management (OCM) received 549 files in tif format from USACE JALBTCX for the Lake Huron coastline in Michigan. The bare earth raster files were at a 1 m grid spacing. The data were in UTM Zone 17 NAD83 (2011) meters coordinates and IGLD85 elevations in meters. OCM assigned the appropriate EPSG codes (Horiz - 6346 and Vert - 5609) and copied the raster files to https for Digital Coast storage and provisioning purposes.
(describe or provide URL of description):
JALBTCX evaluates final data coverage using techniques that are common to the lidar industry. These techniques are performed in a 3D environment for visual review of the final data coverage and verification of data alongside lidar waveforms and imagery collected concurrent with the lidar. Data reviewers perform checks to verify (1) extreme high and/or low elevation values have been invalidated, (2) elevations in areas of swath overlap are internally consistent, (3) binned standard deviation values meet CZMIL specifications, (4) point cloud classifications are valid, and (4) CZMIL processing modes are valid.
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.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.
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.
Data is available online for bulk and custom downloads.
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.