Data Management Plan
GUID: gov.noaa.nmfs.inport:49682 | 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
This dataset is the bare earth lidar data for St. Johns County, Florida, acquired in early January and February of 2004. This data was collected to develop comprehensive countywide base mapping and perform other GIS enhancements to support master drainage planning, transportation planning, preliminary engineering and wetland preservation studies. The surveyed area included all of St. Johns County, approximately 610 square miles. Eighty-seven (87) flight lines of high density lidar data (average GSD is 3.3 feet) were obtained at an altitude of 3000 feet AGL. This data set contains only model keypoints (points that are a thinned data set that is intended to remove extraneous data such as trees and points that are deemed redundant to the final bare earth product) that are classified as ground points. As a result, there are a lower number of points than in a full mass point lidar data set; and it is recommended that the data be downloaded as points and used with a TIN (Triangulated Irregular Network) or similar algorithm to produce a bare earth surface.
This data was collected on the 1990 realization of NAD83. However, there is no EPSG code for that realization and the data have been tagged with the 1996 realization.
Original contact information:
Contact Name: Mike Campbell
Contact Org: St. Johns County Florida GIS
Title: St. Johns County GIS Manager
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:
- 2004-01-01 00:00:00 - The LiDAR data was acquired in 93 flight lines acquired in 6 sessions between January 17 and February 7, 2004 from an altitude of 3,000 feet above ground level (AGL) to provide an average ground sample distance (GSD) of 3.3 feet. Three concurrent airborne GPS base stations were used for each acquisition session. The ABGPS data were reduced using the GrafNav software package by Waypoint Consulting, Inc. The IMU data was reduced using the PosProc software package by Applanix Corporation. The initial lidar "point cloud" was derived through the ALS Post Processor software package by Leica Geosystems. The aircraft, lidar system and associated computer hardware and software are owned and operated by Woolpert LLP. Once the initial lidar "point cloud" was derived, Woolpert performed QC to look for any systematic error within the lidar flights using proprietary software. After systematic error was identified and removed, the individual lidar flights were clipped to remove overlap between adjacent flight lines and provide a homogeneous coverage over the project extents. Using the homogeneous coverage, above ground features were classified and removed using proprietary software to produce the bare-earth coverage.
- 2008-11-03 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in ASCII format. The data was in Florida State Plane Projection, NAVD88 vertical datum and the vertical units of measure were feet. OCM performed the following processing to the data to make it available within Digital Coast: 1. The data were converted from Florida State Plane East, Zone 0901 coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 03. 3. The vertical unit of measure for the data was converted from feet to meters. (Citation: 2004 St. Johns County, Florida Lidar)
- 2023-10-30 00:00:00 - Data were converted to Cloud Optimized Point Cloud format to facilitate streaming .
(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.6. Type(s) of 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?
(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/100/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.