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 metadata record describes the DTM comprised of classified aerial lidar elevation points, photogrammetrically compiled breaklines and the derived TIN for Dekalb County, GA
Original contact information:
Contact Name: Stacy Grear
Contact Org: Dekalb County GIS Department
Title: Acting Director
Email: email@example.com will change to firstname.lastname@example.org on July 1, 2010
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.
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):
- 2010-01-01 00:00:00 - At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.
- 2010-01-01 00:00:00 - New LiDAR data is captured for the project area using a Leica ALS60 LiDAR instrument in conjunction with a POSAV Applanix GPS/INS system mounted within a Piper Navajo twin engine airplane.
- 2010-01-01 00:00:00 - New aerial digital imagery with airborne GPS/IMU data is acquired for the project area.
- 2010-01-01 00:00:00 - The airborne GPS data is processed in Terratec TerraPos software and then combined with the IMU data in Applanix PosPAC software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey. The same GPS/IMU processing is performed for the digital imagery to define the orientation parameters of the images to be used in stereo compilation of terrain breaklines.
- 2010-01-01 00:00:00 - LiDAR data is processed using the GPS/INS solution. Data is classified to produce: Class 1: unclassified points Class 2: ground points Class 9: water points Class 12: overlap points
- 2010-01-01 00:00:00 - The ground class of the processed lidar data is then compared to the ground control and elevation differences between the lidar surface and surveyed elevation are recorded in tabular form. Vertical accuracy statistices are then developed to produce vertical RMSE and overall accuracy estimates and reports.
- 2010-01-01 00:00:00 - Photogrammetrically compiled breaklines are compiled to supplement the lidar ground points.
- 2010-01-01 00:00:00 - Water polygons are buffered to remove any lidar points within the polygon to flatten these surfaces.
- 2010-01-01 00:00:00 - Breaklines are buffered to remove lidar surface points on or near the breakline.
- 2010-01-01 00:00:00 - The Traingulated Irregular Network is generate with ESRI ArcGIS software.
- 2013-08-09 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 projected Georgia State Plane West Zone 1002 coordinates and were vertically referenced to NAVD88. The vertical units of the data were feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The LAS files were processed through a lastools program known as LASGround, where an algorithm further processes any unclassified points to the ground class, ignoring pre-exisint ground points. 2. All files were then horizontally shifted from the projected GA_W (1002) state place coordinates (in feet) to geographic NAD83 coordinates (decimal degrees) 3. All files were then vertically shifted from from orthometric NAVD88 heights (feet) to ellipsoidal NAD83 (meters) using GEOID09 (assumed based on processing date)
(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.
- 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.
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.
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
The data set is dynamically generated based on user-specified parameters.
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.