Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:73607 | Published / External
InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
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
Original Dataset: This task is for a high-resolution data set of lidar covering the entire Lucas County area (+/- 347.1 sq. mi). The lidar was collected and processed to meet a maximum Nominal Post Spacing (NPS) of 0.25 meter (16ppsm). Lidar data is a remotely sensed high resolution elevation data collected by a Leica CityMapper digital sensor active scanning (lidar) sensor. Lidar was collected between March 15, 2022, and March 21 2022 while no snow was on the ground, leaf-off and rivers were at or below normal levels. The lidar systems collect data point clouds that are used to produce highly detailed Digital Elevation Models (DEMs) of the earth's terrain, man-made structures, and vegetation. The data was developed based on a horizontal datum/projection of NAD 83(HARN) State Plane Ohio North FIPS 3401 and a vertical datum of NAVD88 in units of US Survey Feet. Lidar data was delivered as processed LAS version 1.4 files formatted to 6.647 individual 1,250' x 1,250' tiles.
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):
Lineage Statement:
The NOAA Office for Coastal Management (OCM) downloaded the Lucas County, Ohio lidar data from the Ohio Geographically Referenced Information Program (OGRIP). NOAA OCM processed the data to make it available for custom downloads from the NOAA Digital Coast Data Access Viewer and for bulk downloads from AWS S3.
Process Steps:
- 2022-12-01 00:00:00 - Using City Mapper lidar sensors to acquire high density data, at a nominal pulse spacing (NPS) of 0.25 meters, were collected for this task order in 3 total missions. Multiple returns were recorded for each laser pulse along with an intensity value for each return. The survey crews were on-site, operating a Global Navigation Satellite System (GNSS) Base Station for the airborne GPS support.
- 2022-12-01 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 homogenous 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 Default (Class 1), Bare-earth (Class 2), Low Vegetation (Class 3), Medium Vegetation (Class 4), High Vegetation (Class 5), Building (Class 6), Noise (Class 7), Overlap Default (Class 17), and Overlap Ground (Class 18). The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify the quality of the DEM as well as a peer-based QC review. This included a review of the DEM surface to remove artifacts and ensure topographic quality. The overlap classes were determined by first identifying the overlapping areas and reclassifying the LAS data by offset from a corridor. This allows the returns located on the edge of the swath to be removed from the bare earth coverage in an effort to produce a more uniform data density. The returns determined to be overlap including overlap default and ground are then applied an overlap flag and reclassified to their respective standard classification value. The surveyed ground control points are used to make vertical adjustments to the data set and to perform the accuracy checks and statistical analysis of the lidar dataset. Supervisory QC monitoring of work in progress and completed editing ensured consistency of classification character and adherence to project requirements across the entire project area. The resulting deliverables for this task order consist of classified LAS file in LAS 1.2 format and 2.5 feet pixel size DEM files in Erdas IMG format. All data was manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Global Mapper was used as a final check of the bare earth dataset. GeoCue was then used to create the deliverable industry-standard LAS files. Woolpert proprietary software and LP360 was used to perform final statistical analysis of the classes in the LAS files, on a per tile level to verify final classification metrics and full LAS header information.
- 2024-10-04 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded the Lucas County, OH lidar data from the Ohio Geographically Referenced Information Program (OGRIP). The data were in Ohio State Plane North NAD83 HARN, US survey feet coordinates and in NAVD88 (Geoid03) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 3 - Low Vegetation, 4 - Medium Vegetation, 5 - High Vegetation, 6 - Building Rooftops, 17- Overlap Default. OCM processed all classifications of points to the Digital Coast Data Access Viewer (DAV). Classes available on the DAV are: 1, 2, 3, 4, 5, 6, 17. OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 2. Internal OCM scripts were run on the laz files to: a. Convert the files from OH State Plane North NAD83 HARN, US survey feet coordinates to geographic coordinates b. Convert the files from NAVD88 (Geoid03) elevations to ellipsoid (NAD83 2011) elevations c. Convert the files from elevations in feet to meters d. Filter out points whose location did not fall within the following geographic bounding box: -85,40,-82.5,43 e. Filter out points whose elevation values were less than -100 feet or greater than 2000 feet f. Assign the geokeys, to sort the data by gps time and zip the data to database and to AWS S3
(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
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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.
This data set is in the public domain, and the recipient may not assert any proprietary rights thereto nor represent it to any one as other than a data set produced by Lucas County and the Ohio Statewide Imagery Program.
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/10185/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for bulk and custom downloads.
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
Data is backed up to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.
