Data Management Plan
GUID: gov.noaa.nmfs.inport:70282 | 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
LIDAR-derived binary (.las) files ASPRS version 1.4 format containing classified points of all returns. There are 11 classifications: Unclassified, Ground, Automated Low Veg [0.5-5 feet], Automated Medium Veg [5-20 feet], Automated High Veg [>20 feet], Automated Buildings, Low Noise, Water, Bridge Decks, High Noise and Ignored Ground (breakline proximity). The files are delivered in 2000 ft by 2000 ft tiles. These files adhere to the USGS-NGP Lidar Base Specification 2021 rev. A, Quality Level 2 (QL2) standards. The contractual aggregate nominal pulse spacing (ANPS) is less than or equal to 0.5 m. The contractual aggregate nominal point density (ANPD) is 4.0 points or greater per square meter.
This dataset covers approximately 9013 square miles in north central Illinois and consists of 4 deliveries or blocks.
IL_MidNorth_1 (Work Unit 229055) - Approximately 3410 square miles, including Fulton (partial), Henderson, Knox (partial), McDonough, Mercer, and Warren counties
IL_MidNorth_2 (Work Unit 300135) - Approximately 3161 square miles, including Fulton (partial), Knox (partial), Marshall, Peoria, Putnam, Stark, Tazewell, and Woodford counties
IL_MidNorth_3 (Work Unit 300136) - Approximately 2126 square miles, including DeWitt, McLean, and Platt counties
IL_MidNorth_4 (Work Unit 300137) - Approximately 369 square miles, including DuPage county
This metadata record supports the data entry in the NOAA Digital Coast Data Access Viewer (DAV). For this data set, the DAV is leveraging the Entwine Point Tiles (EPT) hosted by USGS on Amazon Web Services.
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.
IL_MidNorth_1
W: -90.1, E: -88.91, N: 41.34, S: 40.26IL_MidNorth_2
W: -89.29, E: -88.45, N: 40.77, S: 39.79IL_MidNorth_3
W: -88.27, E: -87.9, N: 42, S: 41.68IL_MidNorth_4
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) ingested references to the USGS Entwine Point Tile (EPT) files hosted on Amazon Web Services (AWS) into the Digital Coast Data Access Viewer (DAV). The DAV accesses the point cloud as it resides on AWS under the usgs-lidar-public-container.
Process Steps:
- 2022-12-28 00:00:00 - LIDAR data was collected using the Optech Galaxy sensor. The raw data was verified in MARS software for complete coverage of the project area, and boresighted to align the flightlines. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering that separates the data into different classification groups: unclassified points, ground points, low veg [0.5-5 feet], medium veg [5-20 feet], high veg [>20 feet], automated buildings, low noise, water, bridge decks, high noise and ignore ground (breakline proximity). The data was next taken into MARS to reclassify the erroneous points that may remain in the LIDAR point cloud after auto filter. Four points or greater per square meter (QL2+) ASPRS ver 1.4 format.
- 2022-12-28 00:00:00 - LiDAR swath data was measured to have an aggregate of 0.349 meter nominal pulse spacing and 8.224 pulses per meter. The method used was counting first return points within the each swath then dividing by the area of the extent of the corresponding swath to get density. NPS was mathematically derived from this density number. This was performed on each swath then averaged to generate the two numbers above. This USGS method does not consider swath sidelap in these calculations.
- Original point clouds in LAS/LAZ format were restructured as Entwine Point Tiles and stored on Amazon Web Services. The data were re-projected horizontally to WGS84 web mercator (EPSG 3857) and no changes were made to the vertical elevations in NAVD88 (GEOID18).
- 2023-07-13 00:00:00 - The NOAA Office for Coastal Management (OCM) created references to the Entwine Point Tile (EPT) files that were ingested into the NOAA Digital Coast Data Access Viewer (DAV). No changes were made to the data. The DAV will access the point cloud as it resides on Amazon Web Services (AWS) under the usgs-lidar-public container. These are the AWS URLs being accessed: https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_MidNorth_1_D22/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_MidNorth_2_D22/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_MidNorth_3_D22/ept.json https://s3-us-west-2.amazonaws.com/usgs-lidar-public/IL_MidNorth_4_D22/ept.json
(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.
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://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/IL_MidNorth_D22/
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 tape and 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.