Data Management Plan
GUID: gov.noaa.nmfs.inport:50174 | 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
In October 2012, WSI (Watershed Sciences, Inc.) was contracted by the Puget Sound LiDAR Consortium (PSLC)to collect Light Detection and Ranging (LiDAR) data on a 5-year cycle for sites in Washington. The Tulalipsite in northwestern Washington is one of these sites. Unclassified (1), Ground (2) and Snow (14).
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:
- Planning.In preparation for data collection, WSI reviewed the project area using Google Earth,and flightlines were developed using a combination of specialized software. Carefulplanning by acquisition staff entailed adapting the pulse rate, flight altitude, scanangle, and ground speed to ensure complete coverage of the study area at thetarget point density of 11.43 points per square meter (ground points only were calculated at0.83 points per square meter). Efforts are taken to optimize flight paths by minimizingflight times while meeting all accuracy specifications.Factors such as satellite constellation availability and weather windows mustbe considered during the planning stage. Any weather hazards or conditions affectingthe flight were continuously monitored due to their potential impact on the dailysuccess of airborne and ground operations. In addition, a variety of logisticalconsiderations required review including private property access, potential airspace restrictions, and availability of company resources (both staff andequipment).Special care was taken to acquire the tidal flats at low tide wherepossible.
- LiDAR Processing Steps:1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPSand static ground GPS data.Software - Waypoint GPS v.8.3 Trimble Business Center v.3.00 Geographic Calculator 20132. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processedaircraft position with attitude data. Sensor head position and attitude are calculatedthroughout the survey. The SBET data are used extensively for laser point processing.Software - IPAS TC v.3.13. Calculate laser point position by associating SBET position to each laser point returntime, scan angle, intensity, etc. Create raw laser point cloud data for the entire surveyin *.las (ASPRS v. 1.2) format. Data are converted to orthometric elevations (NAVD88) byapplying a Geoid12 correction.Software - ALS Post Processing Software v.2.744. Import raw laser points into manageable blocks (less than 500 MB) to perform manualrelative accuracy calibration and filter erroneous points. Ground points are thenclassified for individual flight lines (to be used for relative accuracy testingand calibration).Software - TerraScan v.13.0085. Using ground classified points per each flight line, the relative accuracy is tested.Automated line-to-line calibrations are then performed for system attitude parameters(pitch, roll, heading), mirror flex (scale) and GPS/IMU drift.Calibrations are calculated on ground classified points from paired flight lines andresults are applied to all points in a flight line. Every flight line is used forrelative accuracy calibration.Software - TerraMatch v.13.0026. Classify resulting data to ground and other client designated ASPRSclassifications (Table 7). Assess statistical absolute accuracy via direct comparisonsof ground classified points to ground RTK survey data.Software - TerraScan v.13.008 TerraModeler v.13.0027. Generate bare earth models as triangulated surfaces. Highest hit models were createdas a surface expression of all classified points (excluding the noise and withheldclasses). All surface models were exported as ESRI grids at a 3-foot pixel resolution.Software - TerraScan v.13.008 ArcMap v. 10.1 TerraModeler v.13.002
- 2014-01-14 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded topographic files in LAZ format from PSLC's website.The files contained lidar easting, northing, elevation, intensity, return number, class, scan angleand GPS time measurements. Entiat data were received in Washington State Plane North, 4601 (feet) andreferenced to NAVD88 (feet).OCM performed the following processing for data storage and Digital Coast provisioning purposes:1. The All-Return LAZ files were cleared of variable lengths records.2. The All-Return LAZ files were converted from a Projected Coordinate System (State Plane 4601)to a Geographic Coordinate system (NAD83).3. The All-Return LAZ files were converted from NAVD88 to ellipsoidal heights using Geoid03.
(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.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the 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.
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/2614/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=2614;
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.