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
Digital Mapping Inc. collected lidar data for the Federal Emergency Management Agency (FEMA) in Region 9, Modoc, CA. The dataset encompasses 43 square miles, while the derived bare earth digital elevation model covers a 21 square mile subset of this area (linked in the Related Items section, below). Nominal pulse spacing of collection was <1 m.
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):
- 1-Acqusition: Modoc LIDAR acquisition consisted of 26 flight lines with 2 cross flights. Alturas Airport was flown for the airport calibration. Two base stations were used for the project. The LIDAR misson was flown in 05/04/2011. ALTM Gemini was used as the LIDAR scanner. LIDAR flight settings were: Altitude (m): 1200 System PRF (kHz): 70 Scan Freq (Hz): 39 Scan Angle +/-: 17 Desired Res (m): 0.804 PPM^2: 1.55 2-Processing: LIDAR data were processed and fit to the ground using DASHMap, GeoCue, TerraScan and TerraMatch softwares. All the data were calibrated to determine and eliminate systematic biases that might occur within the hardware of the ALTM Gemini system. A total of 11 aerial targets were surveyed and used to fit the LIDAR data to the ground. Ground point were removed from the top of bridges. LAS tiles that touch processing limit are classified however QA\QC of the ground points were done to the data which were within processing limit. LAS tiles are classified into 6 classes: 1 processed, but unclassified 2 bare-earth ground 7 noise 9 water 10 ignored 11 withheld 3-Breaklines: Breaklines were compiled for streams, lakes, ponds and man-made features -bridges, culverts- that constrict or control the flow of water in 3D data collection mode from LIDAR data. Breaklines were not collected for the areas outside the processing limit. Ponds and lakes are collected as polygons. They have constant elevation and they have elevation values less than the surrounding ground points. For dry streams and streams narrower than 50 feet single stream breaklines were collected. For streams wider than 50 feet edges of the streams were collected along with stream centerline. The project area was relatively flat which made it some of the streams having single elevation across. Stream breaklines were broken at culverts and not broken at bridges. Culvert breaklines snap to stream endpoints on both sides and have the same elevation as the stream breakline at the snapping location. Top and bottom of the bridge breaklines were collected. Breaklines are delivered as ESRI geodatabase file format. Topology rules were applied to the breaklines. Breaklines snap to each other, split at intersections, not self-intersect or overlap each other. 4-Low Confidence Areas: Areas that may not meet the data accuracy requirements due to heavy vegetation were compiled as 2D polygon. Special effort was given to minimize these areas. Ground points were tried to be classified from dense vegetation areas where possible using manual techniques.
- NOAA Office for Coastal Management (OCM) received 92 lidar point cloud files in las format. The files contained lidar elevation and intensity measurements. The data were in California State Plane Zone 1 (NAD83), international feet coordinates and NAVD88 (Geoid03) elevations in international feet. The data were classified as: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10-Ignored Ground & 11-Withheld. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid 03 model, to convert to geographic coordinates, to convert from vertical units feet to meters, to 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.
- 1.7. Data collection method(s)
- 3.1. Responsible Party for Data Management
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 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.
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.
Data is available online for bulk or 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
Data is backed up to tape and to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.