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 U.S. Army Corps of Engineers collects and maintains LiDAR data including orthophotos in coastal areas of the United States and its territories. The Corps acquires this data in the course of performing its mission of Flood Control, Navigation, Environmental Engineering, and support for the Army and others. These data were collected along the Indiana, Michigan, Ohio and Pennsylvania coasts of the Great Lakes using the CHARTS (Compact Hydrographic Airborne Rapid Total Survey) system and industry based coastal mapping and charting systems.
Original contact information:
Contact Org: NOAA Office for Coastal Management
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):
- Acquisition - Data were acquired using a SHOALS-1000T. Sensor orientation was measured using a POS AV 410, while images were acquired at 1Hz using a Duncantech DT4000 digital camera. Prior to survey PDOP was checked and missions planned to avoid PDOP greater than 3.5. During survey the plane was always within 30km of a GPS ground control point, to provide a good quality position solution. Final positions were determined using a post-processed inertially aided Kinematic GPS (KGPS) solution. GPS ground control data were acquired at 1Hz. Data received by the airborne system were continually monitored for data quality during acquisition operations. Display windows showed coverage and information about the system status. In addition, center waveforms at 5Hz were shown. All of this information allowed the airborne operator to assess the quality of data being collected. The data were 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 geoid heights (NAVD88) using the Geoid03 model with the results in meters. Data were processed in the field to verify coverage and data quality.
- Processing - Data were processed using the SHOALS Ground Control System (GCS). The GCS includes links to Applanix POSPac software for GPS and inertial processing, and IVS Fledermaus software for data visualization, 3D editing and tie-line analysis. Data were processed in NAD83 horizontal and vertical datum. Data were later converted to the NAVD88 vertical datum using the GEOID03 model. The date and time of each point are also MM:SS.SSSSSS. Fugro in-house utilities were used to extract XYZ data from the native LiDAR files and split the data in to pre-defined boxes, each covering approximately 5km of shoreline. ASCII files include: Longitude, Latitude, Elevation, Date, Time, and Intensity.
- 2007-06-15 00:00:00 - Files converted to LDART LAS format (geographic coords, ellipsoid heights,using GEOID03), sorted by latitude and filtered to eliminate outliers.
- 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.
- 2013-07-01 00:00:00 - NOAA OCM received the data in LAS v1.2 format. For data storage and Digital Coast provisioning purposes, the data were processed as follows: 1. Heights were converted Ellipsoid heights, horizontal coordinates were converted to geographic coordinates. 2. lastools's Lasground processed the all unclassifed points to have ground classified points as well. 3. LAS files were converted to LAZ and sorted.
(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.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.
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.
This data can be obtained on-line at the following URL:
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.