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
LIDAR data is remotely sensed high-resolution elevation data collected by an airborne collection platform. Using a
combination of laser rangefinding, GPS positioning and inertial measurement technologies; LIDAR instruments are able to make
highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures and vegetation. This data was
collected at submeter resolution to provide nominal 1m spacing of collected points. Two returns were recorded for each pulse
in addition to an intensity value.
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):
- 2004-10-01 00:00:00 - Data Collection: Using a LH Systems ALS50 Light Detection and Ranging (LiDAR) system, 41 flight lines of high density (submeter ground sample distance) data were collected over areas in coastal Connecticut (approximately 300 square kilometers). Two returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in one (1) mission on October 8, 2004. Three (3) airborne global positioning system (GPS) base stations were used to support the LiDAR data acquisition: Moriches 1 continuously operating reference station (CORS) ARP, NGS point P36, and one station Woolpert located using static GPS positioning methods, Madison CP. In addition, twenty-two control points were surveyed through fast-static GPS methods to support the final accuracy analysis and tied into the National Geodetic Survey (NGS) points Moriches CORS and P36.
- 2004-11-01 00:00:00 - Airborne GPS Processing: Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. The overlap between flight lines was removed to provide a homogeneous coverage, and the coverage was classified to extract a bare earth digital elevation model (DEM). Airborne GPS is differentially processed using the GrafNAV V4.10 software by Waypoint Consulting of Calgary, Alberta, Canada. The PDOP and distance separation is as follows: P36: Maximum PDOP = 3.58 (maximum) Average Distance Separation: 17 km Madison CP: Maximum PDOP = 3.58 (maximum) Average Distance Separation: 19 km IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia. The classification and quality control (QC) of LiDAR data is carried out using a combination of proprietary software and TerraScan software by Terrasolid Limited of Helsinki, Finland. Two (2) coverages were delivered in the LAS file format: bare-earth and above ground features.
- 2004-11-01 00:00:00 - IMU data Processing: IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada.
- 2004-11-01 00:00:00 - Reflective Surface Generation: The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia.
- 2004-12-01 00:00:00 - LIDAR Point Classification The classification and quality control (QC) of LiDAR data is carried out using a combination of proprietary software and TerraScan software by Terrasolid Limited of Helsinki, Finland.
- 2005-01-01 00:00:00 - Output LAS Files Random LIDAR points maintained in UTM coordinate system converted to Geographic projection with units of Decimal Degrees
- 2005-01-01 00:00:00 - Transfer to delivery media: Data is transferred from hard-disk to DVD delivery media using a Primera Bravo DVD/CDROM disc publishing hardware.
- 2006-09-27 00:00:00 - The NOAA Office for Coastal Management (OCM) received files in LAS format. The files contained LiDAR intensity and elevation measurements. OCM performed the following processing on the data to make it available within the LiDAR Data Retrieval Tool (LDART): 1. The las files were converted from State Plane coordinates to Geographic coordinates. 2. The las header fields were sorted by latitude and updated.
- 2008-01-01 00:00:00 - For data management purposes, the Office for Coastal Management (OCM) converted the data from NAVD88 heights to ellipsoid heights using Geoid 03.
(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: 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.