Data Management Plan
GUID: gov.noaa.nmfs.inport:48242 | 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
Many different partners and groups, and several Center-led data projects, have contributed to the lidar data collection housed and distributed by the NOAA Office for Coastal Management. The data span more than two decades and were collected using many different sensors. The collection includes data from topographic and bathymetric lidar sensors. Data are available for all of the coastal states and range from shoreline strips to full county coverage. The products have been delivered to the Center in various formats, projections, datums, and units. Once received, the data are reviewed, checked for errors, and standardized to LAZ format, geographic coordinates and ellipsoid heights in meters. Data are on a NAD83 or ITRF realization depending upon the collection specifics.
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.
W: 144.6166666666, E: 144.9625, N: 13.68583333333, S: 13.22416666667
Guam
W: 145.11666666667, E: 146.08333333333, N: 16.03, S: 14.0475Commonwealth of the Northern Marianas Islands
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):
Lineage Statement:
Data are received from contracted collections, other NOAA offices, or other federal, state, or local agencies. The data are standardized for ingest into the Digital Coast Data Access Viewer and made available to the public.
Process Steps:
- Lidar data are obtained from another source or through NOAA contract. Information about the data is gathered, usually from metadata and project reports from the lidar provider. The primary information necessary includes: 1) projection 2) datums 3) geoid model 4) acquisition dates 5) units 6) classification scheme 7) vertical accuracy
- Data are standardized to geographic coordinates of the horizontal datum they originated in. Vertical values are converted to ellipsoid heights in meters by reversing the datum operation that was originally applied. Data are converted to LAZ format if they are not already in it.
- Data are ingested into the Digital Coast Data Access Viewer. This includes: 1) verification that the point classifications found match the expected classifications based on the metadata or reports. 2) data fall within the expected bounds. 3) vertical ranges are recorded for each data tile and point class. 4) geographic bounds for each tile are recorded. 5) point classification table used is recorded.
(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.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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/index.html
https://coast.noaa.gov/dataviewer
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Lidar data can be obtained on-line at the following URL: http://www.coast.noaa.gov/dataviewer/ The lidar data 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
Source data are backed up to the Azure cloud or the received hard drives are stored. After ingestion, data are also backed up to Azure on a weekly basis.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.