Data Management Plan
GUID: gov.noaa.nmfs.inport:49763 | 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
Indiana's Statewide LiDAR data is produced at 1.5-meter average post spacing for all 92 Indiana Counties covering more than 36,420 square miles. New LiDAR data was captured except where previously captured LiDAR data exists, or the participating County bought-up to a higher resolution of 1.0-meter average post spacing LiDAR data. Existing LiDAR data exists for: Porter, Steuben, Noble, De Kalb, Allen, Madison, Delaware, Hendricks, Marion, Hancock, Morgan, Johnson, Shelby, Monroe, and portions of Vermillion, Parke, Vigo, Clay, Sullivan, Knox, Gibson, and Posey. These existing LiDAR datasets were seamlessly integrated into this new statewide dataset. From this seamless LiDAR product a statewide 5-foot post spacing hydro-flattened DEM product was created and is also available. See the FGDC Metadata provided for more details. This statewide project is divided into three geographic areas captured over a 3-year period (2011-2013). Area 1: St. Joseph, Elkhart Area 2 (2012): LaGrange, Area 3 (2013): Lake, Porter, LaPorte
Original contact information:
Contact Org: Indiana Office of Information Technology
Title: State of Indiana GIS Officer
Phone: (317) 234-5889
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):
- 2012-04-30 00:00:00 - Block 7(partial) and 8 - Using an Optech Gemini LiDAR system, 152 flight lines of high density data, at a nominal pulse spacing (NPS) of 1.5 meter (1.0 meters for Floyd and Dearborn Counties)and Blocks 5, 6, and 7(partial) - Using Leica ALS LiDAR systems, 219 flight lines of high density data were collected, at a nominal pulse spacing (NPS) of 1.5 meter. Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of thirty (30) missions were flown January 31, 2012 December 13, 2012. Eleven (11) airborne global positioning system (GPS) base stations were used in support of the LiDAR data acquisition. 248 ground control points were surveyed through static methods. The geoid used to reduce satellite derived elevations to orthometric heights was Geoid09. The horizontal datum used for this survey is North American Datum 1983 (NSRS2007), Indiana State Plane Coordinate System, East Zone, and expressed in US Survey Feet. The vertical datum used for this survey is North American Vertical Datum 1988 (NAVD88), and expressed in US Survey Feet. Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. System Parameters: - Type of Scanner = Optech Gemini - Data Acquisition Height = 7,380-feet AGL - Scanner Field of View = 20 degrees - Scan Frequency = 32 Hertz - Pulse Repetition Rate - 100.0 Kilohertz - Aircraft Speed = 150 Knots - Swath Width = 5374 feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = Varies. System Parameters: - Type of Scanner = Leica ALS50-II / ALS60 / ALS70 - Data Acquisition Height = 7800 feet AGL - Scanner Field of View = 40 degrees - Scan Frequency = Varies - Pulse Repetition Rate - 99 Kilohertz - Aircraft Speed = Varies - Swath Width = 5678 feet - Number of Returns Per Pulse = Maximum of 4 - Distance Between Flight Lines = Varies.
- 2011-01-01 00:00:00 - The Optech Gemini and Leica systems' LiDAR system calibration and performance is verified on a periodic basis using Woolpert's calibration range. The calibration range consists of a large building and runway. The edges of the building and control points along the runway have been located using conventional survey methods. Inertial measurement unit (IMU) misalignment angles and horizontal accuracy are calculated by comparing the position of the building edges between opposing flight lines. The scanner scale factor and vertical accuracy is calculated through comparison of LiDAR data against control points along the runway. Field calibration is performed on all flight lines to refine the IMU misalignment angles. IMU misalignment angles are calculated from the relative displacement of features within the overlap region of adjacent (and opposing) flight lines. The raw LiDAR data is reduced using the refined misalignment angles.
- 2012-03-02 00:00:00 - Once the data acquisition and GPS processing phases are complete, the LiDAR data was processed immediately to verify the coverage had no voids. 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.
- 2012-04-03 00:00:00 - The individual flight lines were inspected to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogeneous coverage throughout the project area. The point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing "first and only" as well as "last of many" LiDAR returns. This process determined bare-earth points (Class 2), noise (Class 7), water (Class 9) ignored ground (Class 10), unclassified data (Class 1), overlap points (Class 12), and bridges (Class 13). The bare-earth (Class 2 - Ground) LiDAR points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the LiDAR dataset.
- 2012-04-30 00:00:00 - Breaklines defining lakes, greater than two acres, and double-line streams, wider than 100 feet (30.5 meters), were compiled using digital photogrammetric techniques as part of the hydrographic flattening process and provided as ESRI Polyline Z and Polygon Z shape files. Breaklines defining water bodies and streams were compiled for this task order. The breaklines were used to perform the hydrologic flattening of water bodies, and gradient hydrologic flattening of double line streams. Lakes, reservoirs and ponds, at a nominal minimum size of two (2) acres or greater, were compiled as closed polygons. The closed water bodies were collected at a constant elevation. Rivers and streams, at a nominal minimum width of 100 feet (30.5 meters), were compiled in the direction of flow with both sides of the stream maintaining an equal gradient elevation. The hydrologic flattening of the LiDAR data was performed for inclusion in the National Elevation Dataset (NED).
- 2013-09-04 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in laz format. The files contained Lidar elevation and intensity measurements. The Indiana East State Plane counties of Elkhart, St. Joseph and LaGrange were received in Indiana State Plane projection east (1301) in feet and NAVD88 Geoid 09 vertical datum. The Indiana West State Plane counties of LaPorte, Porter and Lake were said to be in Indiana State Plane west (1302) akin to the eastern counties however at closer inspection these tiles did not align with the eastern counties after transformation to geographic coordinates and ellipsoidal heights. It was then discovered that the tiles were in fact already in geographic WGS84. Therefore a transformation of horizontal coordinates was completed on the eastern counties and all counties received an ellipsoidal transformation. The resulting tiles align to each other and to existing OCM Lake Michigan bathymetry/topographical collections and Ohio topographical data. OCM performed the following processing to the data to make it available within the Digital Coast: 1. The eastern Indiana county data were converted from State Plane coordinates to geographic coordinates. 2. The data were converted from NAVD88 (orthometric) heights to GRS80 (ellipsoid) heights using Geoid 09. 3. The high and low error outlier elevations were removed and variable length records (vlr) were removed. 4. Originally classed points as bridges (classification 13) were moved to class 15 to avoid conflict in the Data Access Viewer system.
- 2021-06-23 00:00:00 - Class 15 was returned to the original class 13 (bridges). A few scattered points were found in classes that were not specified/defined. These were reclassed into class 1.
(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.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.
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 set is dynamically generated based on user-specified parameter
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.