Data Management Plan
GUID: gov.noaa.nmfs.inport:49695 | 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
Airborne terrestrial LiDAR was collected for St. Johns County, FL. System Parameters/Flight Plan. The LiDAR system acquisition
parameters were developed based on a maximum average ground sample distance of 2.1 feet. A Leica ALS50 LiDAR sensor was used for acquisition.
Acquisition specifications for the sensor follows: Field of View (full angle) - 24 degrees, Nominal flight altitude (AGL) - 3000 feet,
Airspeed - 130 mph (113 knots), Laser pulse rate - 100,000 Hz, Nominal swath width (on ground) - 1275 feet, Maximum cross track point
spacing - 2.07 feet, Maximum along track point spacing - 4.30 feet, Average point spacing - 1.67 feet, Flight line spacing - 970.47 feet,
Side overlap - 23.91 percent. LiDAR System Calibration. Prior to the LiDAR acquisition, the system underwent a calibration to verify the
operational accuracy and misalignment angles. Boresight calibrations were performed for the LiDAR system at the beginning and end of each
flight mission. LiDAR Data Acquisition. LiDAR data acquisition only occurred when the sky was sufficiently clear of clouds, smoke, and
atmospheric haze. The LiDAR data was processed immediately after the acquisition to verify the coverage had no voids. GPS/Inertial Measurement
Unit (IMU) Post Processing. The GPS and IMU data was post processed using differential and kalman filter algorithms to derive a best estimate
of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project. LiDAR Processing and
Classification. The LiDAR data was post processed and verified to be consistent with the project requirements in terms of post spacing and
absence of artifacts. The point cloud underwent classification to determine bare-earth points (class 2), noise points (class 7), water
returns (class 9), and unclassified data (class 1). Class 12 contains LiDAR points removed from the overlap region between adjacent flight
lines.
Original contact information:
Contact Org: St. Johns County GIS Division
Phone: 904-209-0778
Email: gis@sjcfl.us
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:
- 2008-01-06 00:00:00 - Ground (class 2) LAS points were extracted in ArcMap, using a Woolpert Team-developed VB Script, and loaded into the MASSPOINTS feature class for each area's Geodatabase as multipoint geometry.
- 2011-11-15 00:00:00 - The NOAA Office for Coastal Management received the data in LAS format. The files contained Lidar elevation and intensity measurements. The data were projected in State Plane coordinates (NAD83; Florida East) and referenced to the North American Vertical Datum of 1988 (NAVD88) using the Geoid03 model. The following processes were performed to make the data available within the Digital Coast: 1. The data were converted from state plane (NAD83; Florida East) to geographic coordinates (NAD83). 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoidal) heights using the Geoid03 model. 3. The LAS data were sorted by latitude and the headers were updated.
(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.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/1119/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;
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.