Data Management Plan
GUID: gov.noaa.nmfs.inport:50069 | 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 data contained in these files contain topographic data collected by the CHARTS system along Lake Michigan, Indiana. The data are broken into boxes. The box layout index is provided by the shape file, "in_boxes.shp", and the box numbers for labels are in the "Box" field of the shape file. The data file names are based on the year, project, area name, box number, and product type. An example of the file name is "2008_NCMP_IN_Michigan_07_02DS08070_006_080916_1955_A_00452.las." The 14th digit within the file name corresponds with the box names used. The data was collected and processed in geographic coordinates and ellipsoid heights. The positions are relative to NAD83 in decimal degrees of longitude and latitude. The heights were converted from ellipsoid to orthometric heights using the Geoid03 model with the results in meters. The date and time of each point are also MM:SS.SSSSSS. The format of the file is LAS version 1.0
Original contact information:
Contact Org: JALBTCX
Title: Data Production Manager
Phone: 228-252-1111
Email: shoals-info@sam.usace.army.mil
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:
- 2009-01-01 00:00:00 - These data were collected using the CHARTS surveys system. It is owned by the Naval Oceanographic Office and Operated through contract. The system collects topographic lidar data at 20kHz and hydrographic data at 3kHz. The system also collects RGB imagery at 1Hz. A CASI-1500 hyperspectral line scanner is integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a combination of Novatel and POS A/V equipment. Raw data are collected and transferred to the office for downloading and processing in SHOALS GCS software. GPS data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. These data are edited using Fledermaus software where anomalous data are removed from the dataset. The edited data are written to 5 km tiles along the shoreline using chartsLAS, a program written by NAVO. This program reads data from the original binary format files and produces separate ASCII files for first and last return data. The data are converted from ellipsoid to orthometric heights, based on the GEOID03 model, within the chartsLAS program.
- 2011-05-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the data as unclassified files in ASCII format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data for data storage and Digital Coast provisioning: 1. The data were converted from ASCII to las format. 2. The data were classified as 1 for the topo data (no bare earth) using the topo last (TL) elevation and 11 for the hydro data. 3. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03. 4. The LAS header fields were sorted by latitude and updated.
- 2014-01-09 00:00:00 - Times had originally been stored as POSIX seconds when converted to LAS. This was switched to adjusted GPS time (GPS seconds - 1e9) to conform to the LAS 1.2 standard.
(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/geoid18/588/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;
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.