Data Management Plan
GUID: gov.noaa.nmfs.inport:66400 | 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 topographic and bathymetric lidar elevations generated from data collected by the SHOALS-1000T bathymetric and the Leica ALS60 topographic lidar systems along the coast of Oregon and Washington. Lidar data coverage normally extends along the coastline from the waterline inland 500 meters (topography) and offshore 1,000 meters or to laser extinction. An exception to topographic coverage was made during the field data acquisition where the 500 m corridor was shifted toward the ocean to include the large occurrence of exposed rocks off the Oregon coastline. In this case the final topographic data coverage corridor was reduced to a range of 100 m to 150 m to include coverage over rocks offshore. In Washington, additional bathymetric survey areas in Puget Sound and San Juan de Fuca Strait were added on later in the field campaign to replace areas with persistent unfavorable survey conditions (weather and water clarity); topographic lidar data collection was not performed on the additional areas.
Native lidar data is not generally in a format accessible to most Geographical 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. The 3-D position data are used to generate a series of gridded file products, with each covering approximately 5 kilometers of shoreline. The grid file index is provided by the shape file, "OR_Boxes", and the numbers used to identify files are in the "Box" field of the shape file. The data file naming convention is based on the year, project, area name, vertical datum, "Box" number and product type. An example file name is "2010_NCMP_OR_001_Grid.tif", where <2010> is the project year, <NCMP> is the project under which data were collected, <OR> is the area of data collection, <001> is the "Box" number and <Grid> is the product type (bare earth DEM or first return DSM). On bare earth DEM, interpolation has occurred over removed building footprints to fill in elevations.
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. These data are available for custom download at the link provided in the URL section of this metadata record.
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):
The USACE collected, processed, and provided the data to the NOAA Office for Coastal Management (OCM). OCM received the data and processed it to be available for custom download from the Data Access Viewer (DAV) and for bulk download from https.
- These data were collected using the SHOALS-1000T and ALS60 systems. They are owned by Fugro and operated through contract. The ALS60 system collects topographic lidar data at maximum pulse rate of 200 kHz in a wavelength of 1064 nm with a CASI-1500 hyperspectral line scanner integrated with the system. The SHOALS collects bathymetric lidar data at 1kHz, RGB imagery at 1Hz and a CASI-2 hyperspectral line scanner integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a Novatel and POS A/V 410 equipment (SHOALS) and the onboard GPS/IMU system (ALS60). SHOALS raw data streams are transferred to the office for downloading and processing in SHOALS GCS software. ALS60 raw data were also transferred to the office and processed in IPAS software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus (SHOALS), GeoCue and TerraScan (ALS60), anomalous data are flagged as invalid. FPI Workbench and Fugro's proprietary software convert all valid data from ellipsoid to orthometric heights based on the NGS' GEOID09 model and exports data as a series of first return topography and bathymetry ASCII files. The bathymetry files contain only the returns below the water surface (no topography).
- The topographic first return and bathymetry point clouds, where both exist, are combined into a single file to create a surface model grid (DSM); bathymetric data have been limited to data below the water surface. On bare earth DEM, topographic data has been filtered to include ground returns only; These datasets are combined to create the elevation model. The raster grids are created by generating a triangulated irregular network (TIN) and then extracting the grid node elevations from the TIN surface; in the bare earth DEM, interpolation fills in elevation values over building footprints. 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. Fugro uses FPI Workbench and ArcGIS to perform this operation utilizing TIN area delineation method: "max edge length 10m"; this also secures elevations will not be interpolated more than 5m away from actual data points (except when interpolating over building footprints). The grid is converted to a TIFF raster within ArcGIS. The projection is defined as "North American Datum of 1983" using the DefineProjection command within ArcToolbox; statistics are also generated with Calculate_Statistics tool to display the grid's elevations range properly. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). Vertical positions are referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID09 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88).
- 2022-01-10 00:00:00 - The NOAA Office for Coastal Management (OCM) received GeoTiff format files from USACE JALBTCX for the Oregon and Washington coastline project area. The bare earth raster files were at a 1 m grid spacing. The data were in geographic NAD83 coordinates and NAVD88 (Geoid09) elevations in meters. OCM assigned the appropriate EPSG codes (Horiz - 4269, Vert - 5703) and copied the raster files to https for Digital Coast storage and provisioning purposes.
(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.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.
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.