Data Management Plan
GUID: gov.noaa.nmfs.inport:50127 | 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
Dewberry collected LiDAR for ~3,341 square miles in various Virginia Counties, a part of Worcester County, and Hoopers Island. The acquisition was performed by Terrapoint. This metadata covers the LiDAR produced for the King William project area. The nominal pulse spacing for this project is 1.6 ft (0.5 meters). This project was collected with a sensor which collects intensity values for each discrete pulse extracted from the waveform. GPS Week Time, Intensity, Flightline and echo number attributes were provided for each LiDAR point. Dewberry used proprietary procedures to classify the LAS according to contract specifications: 1-Unclassified, 2-Ground, 7-Noise, 9-Water, 10-Ignored Ground due to breakline proximity, and 11-Withheld (reclassed to 15 by NOAA OCM). Dewberry produced 3D breaklines and combined these with the final LiDAR data to produce seamless hydro flattened DEMs for the 774 tiles (5000 ft x 5000 ft) that cover the project area.
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):
- 2012-01-01 00:00:00 - Establishment of survey points to support the LiDAR data collection. two existing published NGS stations (FX5374, FX5377) were observed in a GPS control network and used to establish one new point for the primary control for this site. FX5374, FX5377, 239DEB05 were observed and used to control all flight missions and static ground surveys. The following are the final coordinates of the control points used for this project: SurveyBlock, Station, Latitude(D M S Hem), Longitude(D M S Hem), H-Ell(m), H-MSL(m) Counties South, 239DEB05, 36 50 47.15799, -76 59 00.22918, -14.6087, 20.3903 Counties South, FX5374, 36 48 32.84206, -76 37 15.00850, -28.4893, 7.6452 Counties South, FX5377, 36 41 06.67117, -77 06 58.40345, -7.2248, 27.6380
- 2012-01-01 00:00:00 - Airborne acquisition of Lidar GeoDigital used one Optech ALTM 3100EA system to collect the data. The Optech System was configured in the following method: Aircraft Speed 150 knots Data Acquisition Height 950 m AGL Swath Width 691.54 m Distance between Flight Lines 300.00 m Overlap 55 percent Scanner Field Of View 22 +/- degrees (+/-2 degrees flagged as withheld) Pulse Repetition Rate 70 KHz Scan Frequency 40 Hz Number of Returns per Pulse 4 Discrete returns Beam Divergence 0.3 mRad Flight Line Length shorter than 70km Base Station Distance shorter than 40km Resultant Raw Point Density ~2 pt/m2 with overlap Aircraft platforms were used in the collection of this project: A Cessna 310 aircraft was used to conduct the aerial survey. The Cessna 310 is a fixed wing aircraft that have an endurance of approximately 5 hours. -GPS-IMU: High accuracy IMU (200Hz) and GPS information (1Hz) concerning the attitude and position of the sensor were acquired at the same time as the Laser data. Ground based GPS stations also acquired consecutive GPS information for the duration of the flights. A combination of Sokkia GSR 2600 and NovAtel DL-4+ dual-frequency GPS receivers were used to support the airborne operations of this survey. - Flights and Flight Lines The area is covered by several missions, a mission is defined as the block of acquisition between aircraft take-off and landing flown under good meteorological and GPS conditions, and each mission includes multiple flightlines. Number Of Missions: 18 List Of Missions: o112005a o112006a o112006b o112007a o112007b o112008a o112008b o112010a o112010b o112012a o112013a o112014a o112014b o112015a o112015b o112016a o112016b o112018a Number Of Flight Lines: 219
- 2012-01-01 00:00:00 - - Airborne GPS Kinematic processing Airborne GPS kinematic data was processed on-site using GrafNav kinematic On-The-Fly (OTF) software. Flights were flown with a minimum of 6 satellites in view (13o above the horizon) and with a PDOP of better than 4. Distances from base station to aircraft were kept to a maximum of 40 km, to ensure a strong OTF (On-The-Fly) solution. For all flights, the GPS data can be classified as excellent, with GPS residuals of 3cm average but no larger than 10 cm being recorded. The Geoid09 geoid model, published by the NGS, was used to transform all ellipsoidal heights to orthometric.
- 2012-01-01 00:00:00 - - Generation and Calibration of laser points Laser data points are generated using Optechs software Dashmap. Those software combine the raw laser range and angle data file with the finalized GPS/IMU trajectory information. Each mission is evaluated in Terrasolids Terramatch software to correct any residual roll pitch heading misalignments, if necessary those values are to the data. The resulting point cloud is projected into the desired coordinate system and created in LAS format. One file per swath, files bigger than 2Gb split in 2. On a project level, a coverage check is carried out to ensure no slivers are present.
- 2012-01-01 00:00:00 - - Mission to mission adjustments of Lidar data All missions are validated and adjusted against the adjoining missions for relative vertical biases and collected GPS static and kinematic ground truthing points for absolute vertical accuracy purposes.
- 2012-01-01 00:00:00 - -Deliverable Product Generation Raw Lidar point are projected were reprojected from UTM zone 18 to the delivery projection State Plane Virginia, US Survey Feet. *Raw Calibrated LIDAR Point Cloud Raw LiDAR point cloud, was provided in the following formats/parameters: - LAS V1.2, point record format 1, Adjusted GPS time, georeferencing information populated in header - The following fields are included in the LAS file: 1. Adjusted GPS time reported to the nearest microsecond 2. Flight line ID 3. Easting (reported to the nearest 0.01ft) 4. Northing (reported to the nearest 0.01ft) 5. Elevation (reported to the nearest 0.01ft) 6. intensity 7. Echo number 8. Classification 9. Scan angle 10. Edge of scan 11. Scan direction - Full swaths, all collected points delivered (except discarded flightline) - The Withheld bit flags the last 2 degrees of the swath (Additional areas are classified with the withheld in areas where wind or vegetation affected the quality of the data long the edge of the flight line. The classification of the additional withheld areas does not affect the density of the data.) - 1 file per swath, 1 swath per file (except when swath had to be divided in section for size or calibration)
- 2014-11-07 00:00:00 - The NOAA Office for Coastal Management (OCM) received the topographic lidar files in LAZ format. The files contained lidar easting, northing, elevation, intensity, return number, etc. The data was received in Virginia State Plane SOuth 4502 (US ft) and NAVD88 (US ft). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The files were reviewed and erroneous elevations were removed. 2. Class 11 points (Withheld) were reclassified to Class 15 (As Needed).
(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
- 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.