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:
2011 Alaska Matanuska and Susitna Boroughs Lidar Point Clouds
1.2. Summary description of the data:

The Matanuska Susitna Borough LiDAR/Imagery Project covers 3680 sq/mi of the Matanuska-Susitna Borough in Alaska. Project parnters and funding sources include: Coastal Impact Assistance Program, Alaska Industrial Development and Export Authority, Alaska Energy Authority, United States Geological Survey, Matanuska Susitna Borough, United States Army Corps of Engineers, United States Fish and Wildlife Service, The Nature Conservancy, National Oceanic and Atmospheric Administration, Mat-Su Salmon Partnership, and Alaska Pacific University.

This dataset contains lidar point clouds in LAS 1.2 format, originally classified in the following manner. Class 1: Unclassified Class 2: Ground, Class 3: Low Vegetation (less than 6 feet above ground surface), Class 4: Medium Vegetation (between 6 and 15 feet above ground surface), Class 5: High Vegetation (greater than 15 feet above ground surface), Class 6: Buildings, Class 7: Error Points, Class 8: Contour Keypoints, Class 9: Water, Class 10: Breakline proximity ground points, Class 11: Powerlines, Class 13: Noise (unclassifed data 1 foot or less above ground), Class 14: Bridge Deck. Classifications were modified slightly by changing class 10 to class 2 with user bytes set to 2, changing class 11 to 16, and changing class 13 to 15.

The following are the collection parameters and equipment used to create these data sets. The Leica sensor was used for flights in the northern half of the Core Area. All other flights were flown with Optech sensors.

Aircraft: Cessna 310(N7516Q), Piper Navajos (N6GR,T73TM and 812TB), Beechcraft KingAir (N898WW)

Lidar Systems: Optech ALTM Gemini (03SEN145 and 07SEN201) and Leica ALS 70

Approximate Collection Altitude (Above Mean Terrain): Optech--1400 meters, Leica--2200 meters

Ground Speed: Optech--150 kts, Leica--160 kts

Pulse Rate Frequency: Optech--70 kHz, Leica--163.6 kHz

Mirror Scan Frequency: Optech--40 Hz, Leica--41 Hz

Scan Angle (+/-): Optech--17 degrees, Leica--16 Degrees

Beam Divergence: Narrow (0.3 mrad)

Accuracy statements are based on areas of moderate terrain, with points classified as ground. Diminished accuracies are to be expected in areas of extreme terrain and dense vegetation. The accuracy of each point is expected to meet the vertical accuracy standard, derived products may be less accurate in areas of extreme terrain and dense vegetation due to a lesser number of points defining the ground in these areas.

Classified data sets such as this one may have varying posting due to some pulses not reaching the ground.

Original contact information:

Contact Name: Lidar Manager

Contact Org: Aerometric, Inc.

Title: Lidar Manager

Phone: (907) 272-4495

Email: aerometric@aerometric-ak.com

Taken From: Item Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Edit
1.3. Is this a one-time data collection, or an ongoing series of measurements?
One-time data collection
Taken From: Extents / Time Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Edit
1.4. Actual or planned temporal coverage of the data:
2011-05-10 to 2011-11-12
Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Edit
1.5. Actual or planned geographic coverage of the data:
W: -150.758042, E: -147.236006, N: 62.900371, S: 61.229401
Taken From: Extents | Geographic Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Edit
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
digital point data
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.
Edit
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.
Edit
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.
Edit
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:

  • 2011-10-12 00:00:00 - Create a smoothed-best estimated trajectory (SBET) of the sensor at a rate of 200 Hz, by integrating the airborne GPS and IMU data The basis of the GPS coordinates were provided to Aero-Metric by Lounsbury, Inc., and were referenced to NAD83 (CORS96) with GEOID09 derived orthometric heights. The maximum baseline distance for this area was 15 km, the average base line length was 5 km. The mean GPS positional accuracy for this area was +/- 0.06 meters.
  • 2011-10-12 00:00:00 - Integrate SBET and raw laser data to produce point cloud data in LAS 1.2 format for each flight line.
  • 2011-10-12 00:00:00 - Data Calibration: An in-situ calibration was performed using the data collect for this project. The data was classified in each line separately for ground and other common features between lines, such as building roofs. This data was processed in TerraMatch 11.001 (TerraSolid, Ltd.), to compute corrections for roll, pitch, heading, and mirror scale. These corrections are applied in order to minimize discrepancies between flight lines.
  • 2011-12-12 00:00:00 - Automated classification of the bare-earth data from the lidar point cloud using a series of algorithms customized for the types of terrain encountered in the project.
  • 2012-04-15 00:00:00 - Manual classification of any data which appears to be properly classified using the automated methods.
  • 2012-11-20 00:00:00 - Create point cloud data, by tile in LAS 1.2 format with absolute GPS timestamps
  • 2013-11-26 00:00:00 - Data for the MatSu Bugoughs was downloaded from matsu.gina.alaska.edu/LiDAR for all areas available
  • 2013-12-18 00:00:00 - Data were modified to work with the Digital Coast Data Access Viewer in the following ways: 1) projection was changed from Alaska State Plane to Geographic coordinates; 2) Vertical datum was changed from NAVD88 to NAD83 ellipsoid using NGS GEOID09; 3) the global encoding byte in LAS format was set to indicate adjusted GPS time instead of GPS seconds of the week; and 4) the classification table was modified to avoid classes already used as a standard within Digital Coast. The classification changes were for ground points near breaklines (original class 10 moved to class 2 with user byte set to 2), powerlines (original class 11 moved to class 16), and near ground noise (original class 13 moved to class 15). Data were also compressed to LAZ format using laszip from laszip.org. Data from multiple deliveries were combined and metadata rewritten to cover them all (Caswell Lakes, Core Area, Matanuska, North Susitna, Point MacKenzie, and Willow were the original delivery groups).
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.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:

Public

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.
Edit
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.
Edit
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.
Edit
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=2609

;

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