Data Management Plan
GUID: gov.noaa.nmfs.inport:56038 | 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 Erie in New York and Pennsylvania. The data points representing bare earth have been classified as such using TerraScan with results provided in the classified las files. Classification value "1" means "Unclassified", "29" valid bathymetric, and a value of "2" means "Ground."
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:
- 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 data are converted from ellipsoid to orthometric heights, based on the GEOID03 model, within the chartsLAS program. The heights were converted from ellipsoid to orthometric heights (NAVD88) using NGS' Geoid03 model file "g2003u08.bin" with the results in meters. Once converted to orthometric heights, the data were then converted to IGLD85 using the VDatum program from NOAA (National Oceanic and Atmospheric Administration). The LAS files output form chartsLAS were read into TerraScan and filters were applied to classify ground points. Points designated as ground are assigned a classification value "2" and all other points are assigned the classification value "1" which represents an unclassified state. Once classified, the points were exported through TerraScan and converted to .las format.
- 2019-04-12 00:00:00 - This data set was received from JALBTCX in 2018. This is 2007 data that JALBTCX reprocessed (converted to las format and reclassed to 1 - Unclassified, 2 - Ground, and 29 - Bathymetric Point). The NOAA Office for Coastal Management (OCM) received 23 las files from USACE JALBTCX. The lidar data had elevation and intensity measurements. The data were in geographic coordinates and IGLD85 elevations in meters. The data were classified as: 1 - Unclassified, 2 - Ground, 29 - Bathymetric Point. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 29. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The LAStools software scripts lasinfo and lasvalidate were run on the las files to check for errors. 2. An internal OCM script was run to check the number of points by classification and by flight ID and the gps time and intensity ranges. 3. The LAStools software script laszip was run to convert the las files to laz format. 4. The files were converted from IGLD85 to NAVD88 (Geoid12b) elevations using the NOAA VDatum tool. 5. Internal OCM scripts were run on the laz files to convert from NAVD88 elevations to ellipsoid elevations using Geoid12b, assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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
- 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/8714/index.html
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.