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:
2012 USACE Post Sandy Topographic LiDAR: Coastal Connecticut
1.2. Summary description of the data:

This data has been acquired and developed by the U.S. Corps of Engineers ST. Louis District to collect and deliver topographic elevation point data derived from multiple return light detection and ranging (LiDAR)

measurements for the 116 sq. mile project area encompassing the entire coastal region of the State of Connecticut. Fugro EarthData, Inc. acquired 46 flight lines in 4 lifts from November 14, 2012 to December 16, 2012.

LiDAR data collection was performed with a Cessna 310 twin engine aircraft, utilizing a Leica ALS60 MPiA sensor; collecting multiple return x, y, and z as well as intensity data. The classified LiDAR point cloud data are

delivered in LAS 1.2 format: 1 unclassified, 2 ground, 7 low points, 8 model keypoints, 9 water, and 10 ignored points. Specialized in-house and commercial software processes the native LiDAR data into 3-dimensional

positions that can be imported into GIS software for visualization and further analysis.

Original contact information:

Contact Org: USACE, St. Louis District

Phone: 314-331-8389

Email: ted.e.stanton@usace.army.mil

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:
2012-11-14 to 2012-11-16
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: -73.661202, E: -71.847828, N: 41.396254, S: 40.951486
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:

  • 2012-11-18 00:00:00 - All acquired LiDAR data went through a preliminary review to assure that complete coverage was obtained and that there were no gaps between flight lines before the flight crew left the project site. Once back in the office, the data is run through a complete iteration of processing to ensure that it is complete, uncorrupted, and that the entire project area has been covered without gaps between flight lines. There are essentially three steps to this processing: 1) GPS/IMU Processing - Airborne GPS and IMU data was immediately processed using the airport GPS base station data, which was available to the flight crew upon landing the plane. This ensured the integrity of all the mission data. These results were also used to perform the initial LiDAR system calibration test. 2) Raw LiDAR Data Processing - Technicians processed the raw data to LAS format flight lines with full resolution output before performing QC. A starting configuration file was used in this process, which contains the latest calibration parameters for the sensor. The technician also generated flight line trajectories for each of the flight lines during this process. 3) Verification of Coverage and Data Quality - Technicians checked flight line trajectory files to ensure completeness of acquisition for project flight lines, calibration lines, and cross flight lines. The intensity images were generated for the entire lift at the required post spacing for the project. The technician visually checked the intensity images against the project boundary to ensure full coverage. The intensity histogram was analyzed to ensure the quality of the intensity values. The technician also thoroughly reviewed the data for any gaps in project area. The technician generated a few sample TIN surfaces to ensure no anomalies were present in the data. Turbulence was inspected for and if it affected the quality of the data, the flight line was rejected and reflown. The technician also evaluated the achieved post spacing against project specified post spacing.
  • 2012-11-19 00:00:00 - The boresight for each lift was done individually as the solution may change slightly from lift to lift. The following steps describe the Raw Data Processing and Boresight process: 1) Technician processed the raw data to LAS format flight lines using the final GPS/IMU solution. This LAS data set was used as source data for boresight. 2) Technician first used commercial software to calculate initial boresight adjustment angles based on sample areas selected in the lift- mini project. These areas cover calibration flight lines collected in the lift, cross tie and production flight lines. These areas are well distributed in the lift coverage and cover multiple terrain types that are necessary for boresight angle calculation. The technician then analyzed the result and made any necessary additional adjustment until it is acceptable for the mini project. 3) Once the boresight angle calculation was done for the mini project, the adjusted settings were applied to all of the flight lines of the lift and checked for consistency. The technician utilized commercial and proprietary software packages to analyze the matching between flight line overlaps for the entire lift and adjusted as necessary until the results met the project specifications. 4) Once the boresight adjustment was completed for each lift individually, the technician ran a routine to check the vertical misalignment of all flight lines in the project and also compared data to ground truth. The entire dataset was then adjusted to ground control points. 5) The technician ran a final vertical accuracy check between the adjusted data and surveyed ground control points after the z correction. The result was analyzed against the project specified accuracy to make sure it meets the project requirements
  • 2012-11-27 00:00:00 - Once boresighting is complete for the project, the project was set up for classification. The LiDAR data was cut to production tiles. The flight line overlap points, Noise points and Ground points were classified automatically in this process. Fugro EarthData, Inc. has developed a unique method for processing LiDAR data to identify and re-classify elevation points falling on vegetation, building, and other above ground structures into separate data layers. The steps are as follows: 1) Fugro EarthData, Inc. utilized commercial software as well as proprietary software for automatic filtering. The parameters used in the process were customized for each terrain type to obtain optimum results. 2) The Automated Process typically re-classifies 90-98% of points falling on vegetation depending on terrain type. Once the automated filtering was completed, the files were run through a visual inspection to ensure that the filtering was not too aggressive or not aggressive enough. In cases where the filtering was too aggressive and important terrain features were filtered out, the data was either run through a different filter or was corrected during the manual filtering process. 3) Interactive editing was completed in 3D visualization software which also provides manual and automatic point classification tools. Fugro EarthData, Inc. used commercial and proprietary software for this process. Vegetation and artifacts remaining after automatic data post-processing were reclassified manually through interactive editing. The hard edges of ground features that were automatically filtered out during the automatic filtering process were brought back into ground class during manual editing. Auto-filtering routines were utilized as much as possible within fenced areas during interactive editing for efficiency. The technician reviewed the LiDAR points with color shaded TINs for anomalies in ground class during interactive filtering. 4) All LAS tiles went through peer review after the first round of interactive editing was finished. This helps to catch misclassification that may have been missed by the interactive editing. 5) Upon the completion of peer review and finalization of bare earth filtering, the classified LiDAR point cloud work tiles went through a water classification routine based on the collected water polygons. 6) The time stamps for all points were converted to Adjusted Standard GPS time using proprietary software developed by Fugro EarthData, Inc. The data collection date and the current GPS time stamp were used in calculating the Adjusted Standard GPS time. 7) The classified point cloud data were packaged into geographic Coordinates, NAD83(NA2011) in meters and the vertical datum is the North American Vertical Datum of 1988 (NAVD88) in meters using GEIOD09 for delivery. The data was also cut to the approved tile layout and clipped to the approved project boundary. The technician checked the output LAS files for coverage and format; d) the technician then QCd the dataset for quality assurance and enhanced the Bare Earth classification in the project area for consistent data quality; ie) these final LiDAR tiles were then used in the hydro flattening process. 8) classified LiDAR point cloud data are delivered in LAS 1.2 format: 1 unclassified, 2 ground, 7 low points, 8 model keypoints, 9 water, and 10 ignored points.
  • 2013-01-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received topographic files in LAS format. The files contained lidar elevation and intensity measurements. The data were received in Geographic (NAD83) coordinates and were vertically referenced to NAVD88 using the Geoid12a model. The vertical units of the data were meters. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The topographic las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid12a.
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:

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=1434

;

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