Search Help Show/Hide Menu

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.

URL of higher-level DM Plan (if any) as submitted to DM Plan Repository:
Always left blank

1. General Description of Data to be Managed

1.1. Name of the Data, data collection Project, or data-producing Program:
2013 Puget Sound LiDAR Consortium (PSLC) Topographic LiDAR: Tulalip Partnership
1.2. Summary description of the data:

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).

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of measurements?
No information found
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
No information found
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -123.5796125, E: -122.9079181, N: 48.4311248, S: 47.7515734
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
las
1.7. Data collection method(s):
(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.)
No information found
1.8. If data are from a NOAA Observing System of Record, indicate name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please specify:
Always left blank due to field exemption

2. Point of Contact for this Data Management Plan (author or maintainer)

2.1. Name:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Person
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.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
coastal.info@noaa.gov
Notes: The email address is taken from the address listed for the Person assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
(843) 740-1202
Notes: The phone number is taken from the number listed for the Person assigned as the Metadata Contact in Support Roles. If the phone number is missing or incorrect, please contact your Librarian to update the Person record.

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.

3.1. Name:
No information found
Taken From: Support Roles (Data Steward) | Person
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"

4. Resources

Programs must identify resources within their own budget for managing the data they produce.

4.1. Have resources for management of these data been identified?
No information found
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
No information found

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.

5.1. Processing workflow of the data from collection or acquisition to making it publicly accessible
(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.
5.1.1. If data at different stages of the workflow, or products derived from these data, are subject to a separate data management plan, provide reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
No information found

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.

6.1. Does metadata comply with EDMC Data Documentation directive?
No
Notes: All required DMP fields must be populated and valid to comply with the directive.
6.1.1. If metadata are non-existent or non-compliant, please explain:

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?
Notes: Required DMP fields that are not populated or invalid are listed here.
6.2. Name of organization or facility providing metadata hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural Directive: https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement

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.

7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe how data are protected from unauthorized access or disclosure:

None

7.2. Name of organization of facility providing data access:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles (Distributor) | Organization
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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
Taken From: Distribution Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:

This data can be obtained on-line at the following URL:https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2614;

7.4. Approximate delay between data collection and dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing, indicate under what authority data access is delayed:

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.

8.1. Actual or planned long-term data archive location:
(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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving Intended, explain:
Taken From: Data Management | If To Be Determined, Unable to Archive or No Archiving Intended, explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive facility (if any):
Office for Coastal Management - Charleston, SC
Taken From: Physical Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found

9. Additional Line Office or Staff Office Questions

Line and Staff Offices may extend this template by inserting additional questions in this section.

Always left blank