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 LiDAR dataset was created for the City of Eureka, California covering approximately 105 square miles of the city and its environs. The origin data was collected on September 24th, 2019 using a Leica Hyperion LiDAR mapping unit and associated ground control was collected by a California Certified PLS. All data was acquired and processed in California Zone 1 State Plane, NAD83(2011), NAVD88 in US Survey Feet. Datasets included 12 ppsm Bare Earth Classified LAS, 1-Foot DEM and a 1-Foot Interval Contour Extraction.
The lidar point, DEM, and imagery data was provided to the Office for Coastal Management (OCM) by the City of Eureka, CA for inclusion in the Data Access Viewer (DAV). OCM processed the lidar point, DEM, and imagery data to the DAV.
In addition to this lidar point data, the imagery and the DEM data that were created from the lidar point data, are also available. These data are available for custom download at the links provided in the URL section of this metadata record.
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):
Data collected by Access Geographic, Inc., for the City of Eureka, CA.
- LiDAR Acquisition Specifications & Tolerance: - Leica Hypersion 2 Sensor - 1500m AGL - 130 Knots - 2M Pulse Rate - Gateless Laser Mode - 150 Scan Rate - Circular Scan Pattern - 20 Degree Scan Angle - 30 Percent Sidelap - 17ppsm (Planned) - 9 SNR (Minimum) LiDAR Extraction & Deliverables: - Bare Earth Classified LAS: 1) Processed, but Unclassified 2) Bare Earth 7) Low Noise 9) Water 10) Ignored Ground 17) Bridge Decks 18) High Noise - DEM (1-Meter Posting) - 1-Foot Contour Extraction
- 2020-03-19 00:00:00 - The NOAA Office for Coastal Management (OCM) received 558 files in las format from the City of Eureka, CA. The lidar data had elevation and intensity measurements. The data were in CA State Plane, Zone 0401, NAD83 (2011), US survey foot coordinates and NAVD88 (assumed GEOID12B) elevations in feet. The data were classified as: 1 - Unclassified, 2 - Ground, 7 - Noise, 9 - Water, 17 - Bridge Decks, 18 - High Noise. There were also a minimal number of points in many other random classes. OCM processed the 1, 2, 7, 9, 17, and 18 classifications of points to the Digital Coast Data Access Viewer (DAV). OCM performed the following processing on the data for Digital Coast storage and provisioning purposes: 1. The data were converted to laz format using laszip 2. The data were converted from gps week time to adjusted gps time using LAStools las2las 3. An internal OCM script was run to check the number of points by classification and by flight ID and the gps and intensity ranges. 4. File U_17 was determined to be corrupt. A replacement file was provided by Access Geographic, Inc, but this file was also found to be corrupt. OCM used Global Mapper to remove the offending points from the file. 5. Internal OCM scripts were run on the laz files to convert from orthometric (NAVD88) elevations to ellipsoid elevations using the Geoid12B model, to convert from CA State Plane Zone 0401 (NAD83 2011), US survey foot coordinates to geographic coordinates, to convert from vertical units of feet to meters, to assign the geokeys, to sort the data by gps time and zip the data to database and to http.
(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.
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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.