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:
2018 USGS/NRCS Lidar: Southwest Florida
1.2. Summary description of the data:

The Project data set consists of the Classified Point Cloud. The Geographical Extent of this dataset extends to the entirety of the Southwest FL LiDAR boundary Delivery, approximately 2,347 square miles of the AOIs. Ground Conditions: water at normal levels; no unusual inundation; no snow; leaf off. How the Withheld Points are Identified: Withheld (ignore) points were identified in the files using the standard LAS Withheld bit.

This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.

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?
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.
1.4. Actual or planned temporal coverage of the data:
2018-05-08 to 2019-03-01
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: -82.28745, E: -81.250146, N: 26.79471, S: 25.821722
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.)
Model (digital)
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?
Yes
4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):
Unknown

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

Lineage Statement:
The NOAA Office for Coastal Management (OCM) ingested references to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.

Process Steps:

  • 2018-10-29 00:00:00 - Aerial LiDAR Acquisition: Aerial data collection was acquired, in Nighteen (19) Missions, using the Leica ALS80 SN# 8137, SN# 8235 and SN#8253 at an altitude of 3669 feet AGL for QL1. This was to support a 8.0 ppm^2 for QL1 LiDAR point cloud. Airborne GPS and IMU data was collected during the acquisition and supported by Leica GS15 and GPS 1200 base stations that occupied temporary monuments in conjunction with CORS stations, Data acquisition started May 08, 2018 and it was completed March 1, 2019. Ground Control Survey: A survey was performed to support the acquisition of Light Detection and Ranging (LiDAR). The control network involved a total of One-hundred Thirty-nine (139) check points (79 NVA + 60 VVA). The points were a combination of the following ground cover classification: Open Terrain, Urban Terrain, Bare Earth, High Grass, and Low Trees. All field survey observations were conducted between May 07, 2018 and it was completed May 09, 2018 with Leica GPS GS15 and 1200 equipment.
  • 2019-03-01 00:00:00 - LiDAR Pre-processing: Airborne GPS and IMU data were merged to develop a Smooth Best Estimate of Trajectory (SBET) of the LiDAR system for each mission. LiDAR ranging data were initially calibrated using previous best parameter for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections derived. This process was repeated interactively until residual errors between overlapping swaths, across all project lifts, was reduced to 2 cm or less. Raw data NVA were checked using surveyed check points.
  • 2018-11-30 00:00:00 - RAW Data Processing: The Initial processing of the GPS data was processed using Inertial Explorer producing a solution file for each mission. Leica CloudPro software was then used to generate georeferenced laser returns into LAS 1.4 file format for each flight-line per each mission, this went through an initial Quality Control of the overlap between the flight-line swaths.
  • 2019-01-25 00:00:00 - LiDAR Post-processing: The calibrated and controlled LiDAR swaths were processed using automatic point classification routines in TerraSolid software. These routines operate against the entire collection (all swaths, all lifts), eliminating character differences between files. Data were then distributed as virtual tiles to experienced LiDAR analysts for localized automatic classification, manual editing, and peer-based QC checks. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project. All classification tags are stored in the original swath files. After completion of classification and final QC approval, the NVA and VVA for the project are calculated. Sample areas for each land cover type present in the project were extracted and forwarded to the client, along with the results of the accuracy tests. Upon acceptance, the complete classified LiDAR swath files were delivered to the client.
  • 2019-03-07 00:00:00 - LiDAR Classification: The calibrated LiDAR data went through automated classification routines and then manually edited and checked. The LiDAR point cloud data was classified into the following classes: 1-unclassified*, 2-ground, 7-low noise, 9-water, 17-bridges, and 18-high noise, 20-Ignored Ground, 21-Snow, 22-Temporal Exclusion
  • Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical elevations in NAVD88 (GEOID12B).
  • 2024-01-25 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_FL_Southwest_A_2018_LAS_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_FL_Southwest_B_2018_LAS_2019/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/USGS_LPC_FL_Southwest_B_TL_2018_LAS_2019/ept.json
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
  • 5.2. Quality control procedures employed
  • 7.1.1. If data are not available or has limitations, has a Waiver been filed?
  • 7.4. Approximate delay between data collection and dissemination
  • 8.3. Approximate delay between data collection and submission to an archive facility
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?
Yes
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:

Data is available online for bulk or custom downloads

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

Data is backed up to tape and to cloud storage.

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