Data Management Plan
GUID: gov.noaa.nmfs.inport:49602 | 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
USGS Contract Number: 01CRCN0014
In Spring, 2006 Sanborn was contracted by the USGS to survey aprocimately 1,735 square miles of western Whatcom and Skagit Counties in Washington state. All data was collected during ideal conditions (rivers at or below mean level,
leaf off, etc.).
For this collect two sensors were used: The Leica ALS-50 (High Relief Collection) and Optech 2050 (High and Low Relief Collection). LiDAR calibrations were performed to determine and therefore eliminate systematic
biases that occur between the the two sensors. Once the biases were determined they were modeled out. The Leica ALS-50 produced an average point spacing of 1.4 meters. The Optech 2050 produced an average point spacing
of 1.3 meters. All points are classified as Class 2 (Ground) which includes water points and any possibly remaining artifacts.
Leica ALS-50 LiDAR Acquisition Paramters:
Avg. Altitude: 1,500 meters AGL
Airspeed: ~120 Knots
Scan Freq: 36 Hertz
Scan Width Half Angle: 36 Degrees
Pulse Rate: 60,000 Hertz
Overlap: 44-60%
Optech 2050 LiDAR Acquisition Parameters:
Avg. Altitude: 1,200 meters AGL
Airspeed: ~120 Knots
Scan Freq: 30 Hertz
Scan Width Half Angle: 40 Degrees
Pulse Rate: 50,000 Hertz
Overlap: 30-50%
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:
- 2006-01-01 00:00:00 - Final post-processing of LiDAR data involves several steps. The airborne GPS data was post-processed using Waypoint's GravNAVTM software (version 7.5). A fixed-bias carrier phase solution was computed in both the forward and reverse chronological directions. The data was processed for both base stations and combined. In the event that the solution worsened as a result of the combination of both solutions the best of both solutions was used to yield more accurate data. The GPS trajectory was combined with the raw IMU data and post-processed using Applanix Inc.'s POSPROC (version 4.3) Kalman Filtering software. This results in a two-fold improvement in the attitude accuracies over the real-time INS data. The best estimated trajectory (BET) and refined attitude data are then reintroduced into the LEICA ALS post processor or REALM Survey Suite OPTECH to compute the laser point-positions. The trajectory is then combined with the attitude data and laser range measurements to produce the 3-dimensional coordinates of the mass points. All return values are produced within ALS Post Processing software or REALM Survey Suite OPTECH software. The multi-return information minus the last return provides a useful depiction of the "canopy" within the project area. The last return is further processed to obtain the "Bare Earth Dataset" as a deliverable. All LiDAR data is processed using the binary LAS format 1.0 file format. LiDAR filtering was accomplished using TerraSolid, TerraScan LiDAR processing and modeling software. The filtering process reclassifies all the data into classes within the LAS formatted file based scheme set using the LAS format 1.0 specifications or by the client. Once the data is classified, the entire data set is reviewed and manually edited for anomalies that are outside the required guidelines of the product specification or contract guidelines, whichever apply. The coordinate and datum transformations were then applied to the data set to reflect the required deliverable projection, coordinate and datum systems as provided in the contract. The final data is in State Plane Washington North Coordinate System with the horizontal and vertical units being in feet.
- 2013-01-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received topographic file in ASCII .XYZ format. The files contained lidar elevation measurements. The data were received in Washington State Plane North Zone 4601, NAD83 coordinates and were vertically referenced to NAVD88 using the Geoid99 model. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The ASCII .XYZ files were converted to LAS version 1.1 using Global Mapper. 2. All points in Class 0 (Never Classified) were changed to Class 2 (Ground). This includes water points. 3. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid99. 4. The topographic las files were converted from a Projected Coordinate System (WA SP North) to a Geographic Coordinate system (GCS). 5. The topographic las files' vertical units were converted from feet to meters. 6. The topographic las files' horizontal units were converted from feet to decimal degrees.
(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/1451/index.html
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/#/lidar/search/where:ID=1451
;
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.