Data Management Plan (Deprecated)
2016 3DEP Lidar: Douglas County, WI
|
Data Set
(DS)
| OCM Partners
GUID: gov.noaa.nmfs.inport:50444 | Published / External
GUID: gov.noaa.nmfs.inport:50444 | Published / External
Deprecated Version
This is an outdated version of the NOAA Data Management Plan template. 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. Please see the Data Management Plan Help Guide to learn more.
This is an outdated version of the NOAA Data Management Plan template. 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. Please see the Data Management Plan Help Guide to learn more.
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.
URL of higher-level DM Plan (if any) as submitted to DM Plan
Repository:
Always left blank
1. General Description of Data to be Managed
1.1. Name of the Data, data collection Project, or data-producing
Program:
2016 3DEP Lidar: Douglas County, WI
Taken From: Item
Identification | Title
1.2. Summary description of the data:
EagleView acquired highly accurate Light Detection and Ranging (LiDAR) elevation data at the USGS QL2 guidelines for the County of Douglas, Wisconsin in November 2016. This data set represents County of Douglas, comprised of approximately 1,333 square miles. LiDAR for this data set was classified and quality controlled by EagleView. Products were generated by Ground Point and subsequently quality controlled by EagleView.
The NOAA Office for Coastal Management (OCM) downloaded the lidar and breakline data from the City of Superior, WI site, processed it, and made it available on the the NOAA Digital Coast. The breakline data has not been reviewed and is made available at the user's discretion.
Taken From: Item
Identification | Abstract
Notes: Only a maximum of 4000 characters will be included.
Notes: Only a maximum of 4000 characters will be included.
1.3. Is this a one-time data collection, or an ongoing series of
measurements?
One-time data collection
Taken From: Extents / Time
Frames | Time Frame Type
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
Notes: Data collection is considered ongoing if a time frame of type "Continuous" exists.
1.4. Actual or planned temporal coverage of the data:
2016-11-06 to 2016-11-26
Taken From: Extents | Time Frame
- Start, Time Frame - End
Notes: All time frames from all extent groups are included.
Notes: All time frames from all extent groups are included.
1.5. Actual or planned geographic coverage of the data:
W: -92.296, E: -91.55, N: 46.758, S: 46.156
Taken From: Extents | Geographic
Area Bounds, Geographic Area Description
Notes: All geographic areas from all extent groups are included.
Notes: All geographic areas from all extent groups are included.
1.6. Type(s) of data:
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
(e.g., digital numeric data, imagery, photographs, video, audio, database, tabular data, etc.)
Point Cloud (digital)
Taken From: Data Set
Information | Data Presentation Form
1.7. Data collection method(s):
(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.)
(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.)
No information found
Taken From: Acquisition
Information | Instruments, Platforms
1.8. If data are from a NOAA Observing System of Record, indicate
name of system:
Always left blank due to field exemption
1.8.1. If data are from another observing system, please
specify:
Always left blank due to field exemption
2. Point of Contact for this Data Management Plan (author or maintainer)
2.1. Name:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles
(Metadata Contact) | Person
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 Person of the most recent Support Role of type "Metadata Contact" is used. The support role must be in effect.
2.2. Title:
Metadata Contact
Always listed as "Metadata Contact"
2.3. Affiliation or facility:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles
(Metadata Contact) | Organization
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
Notes: The name of the Organization of the most recent Support Role of type "Metadata Contact" is used. This field is required if applicable.
2.4. E-mail address:
coastal.info@noaa.gov
Notes: The email address is taken from the address listed for the Person
assigned as the Metadata Contact in Support Roles.
2.5. Phone number:
(843) 740-1202
Notes: The phone number is taken from the number listed for the Person
assigned as the Metadata Contact in Support
Roles. If the phone number is missing or incorrect, please contact your Librarian to
update the Person record.
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.
3.1. Name:
No information found
Taken From: Support Roles
(Data Steward) | Person
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.
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.
3.2. Position Title:
Data Steward
Always listed as "Data Steward"
4. Resources
Programs must identify resources within their own budget for managing the data they produce.
4.1. Have resources for management of these data been
identified?
No information found
4.2. Approximate percentage of the budget for these data devoted
to data management (specify percentage or "unknown"):
No information found
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.
5.1. Processing workflow of the data from collection or acquisition to making it publicly
accessible
(describe or provide URL of description):
(describe or provide URL of description):
Process Steps:
- 2016-11-22 00:00:00 - Lidar Preprocessing: Airborne GPS and IMU data were merged to develop a Single Best Estimate of Trajectory (SBET) of the lidar system trajectory for each lift. Lidar ranging data were initially calibrated using previous best parameters for this instrument and aircraft. Relative calibration was evaluated using advanced plane-matching analysis and parameter corrections were derived. This relative calibration was repeated iteratively until residual errors between overlapping swaths, across all project lifts, was reduced to 3 cm or less. Data were then block adjusted to match surveyed calibration control.
- 2016-12-13 00:00:00 - Lidar Post-Processing: After generation of the calibrated point cloud data in LAS format from Optech's Lidar Mapping Suite (LMS), the data is imported into the TerraSolid software suite (running under Bentleys MicroStation) for matching and classification. Upon import, the data is divided into tiles for the purpose of creating more manageable data. Once imported to TerraSolid, blocks of data containing overlapping flight lines are selected. The data in these blocks is analyzed by TerraMatch and adjustments to the roll, pitch, heading, and scale that minimize any data misalignment between the flight lines are computed. These adjustments are then applied to the entire missions worth of data. Data across the mission is then manually reviewed to ensure proper alignment between flightlines has been achieved. This process is then repeated for each mission; once complete, intra-sortie alignment is verified
- 2017-11-20 00:00:00 - The NOAA Office for Coastal Management (OCM) downloaded the lidar point cloud and breakline data from the City of Superior, WI site on Oct 20, 2017. The files contained lidar elevation and intensity measurements. The data were in WISCRS Douglas feet (NAD83 2011) coordinates and NAVD88 (Geoid12b) elevations in feet. OCM did the following processing to the data for Digital Coast storage and provisioning purposes: 1. Converted the lidar point cloud data from WISCRS Douglas ft (NAD83 2011) coordinates to geographic coordinates 2. Converted the lidar point cloud data from NAVD88 (Geoid12b) elevations to NAD83 (2011) ellipsoid elevations using Geoid12b grids 3. Converted the lidar point cloud data from ft to meters 4. Copied the lidar point cloud laz files to database and https 5. Created an OGC GeoPackage (gpkg) version of the breaklines from the ESRI GeoDatabase (gdb) and copied it and the gdb to https
Taken From: Lineage | Lineage
Statement, Process Steps (Process Date/Time, Source Citation Title, Description)
5.1.1. If data at different stages of the workflow, or products
derived from these data, are subject to a separate data management plan, provide
reference to other plan:
Always left blank
5.2. Quality control procedures employed
(describe or provide URL of description):
(describe or provide URL of description):
No information found
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.
6.1. Does metadata comply with EDMC Data Documentation
directive?
No
Notes: All required DMP fields must be populated and valid to comply with
the directive.
6.1.1. If metadata are non-existent or non-compliant, please
explain:
Missing/invalid information:
- 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?
Notes: Required DMP fields that are not populated or invalid are listed
here.
6.2. Name of organization or facility providing metadata
hosting:
NMFS Office of Science and Technology
Always listed as "NMFS Office of Science and Technology"
6.2.1. If service is needed for metadata hosting, please
indicate:
Always left blank
6.3. URL of metadata folder or data catalog, if known:
Always listed as the URL to the InPort Data Set record
6.4. Process for producing and maintaining metadata
(describe or provide URL of description):
(describe or provide URL of description):
Metadata produced and maintained in accordance with the NOAA Data Documentation Procedural
Directive:
https://nosc.noaa.gov/EDMC/DAARWG/docs/EDMC_PD-Data_Documentation_v1.pdf
Always listed with the above statement
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.
7.1. Do these data comply with the Data Access directive?
No information found
7.1.1. If the data are not to be made available to the public at
all, or with limitations, has a Waiver (Appendix A of Data Access directive) been filed?
No information found
7.1.2. If there are limitations to public data access, describe
how data are protected from unauthorized access or disclosure:
None
Taken From: Access Info |
Data Access Constraints
7.2. Name of organization of facility providing data access:
NOAA Office for Coastal Management (NOAA/OCM)
Taken From: Support Roles
(Distributor) | Organization
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: 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.
7.2.1. If data hosting service is needed, please indicate:
Taken From: Data
Management | If data hosting service is needed, please indicate
Notes: This field is required if a Distributor has not been specified.
Notes: This field is required if a Distributor has not been specified.
7.2.2. URL of data access service, if known:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8405
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8405/index.html
https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/8405/index.html
Taken From: Distribution
Info | Download URL
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
7.3. Data access methods or services offered:
Data is available online for bulk and custom downloads
Taken From: Access Info |
Data Access Procedure
7.4. Approximate delay between data collection and
dissemination:
No information found
7.4.1. If delay is longer than latency of automated processing,
indicate under what authority data access is delayed:
Taken From: Data
Management | If delay is longer than latency of automated processing, indicate under
what authority data access is delayed
Notes: This field is required if applicable.
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.
8.1. Actual or planned long-term data archive location:
(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)
(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)
No information found
8.1.1. If World Data Center or Other, specify:
Taken From: Data
Management | Actual or planned long-term data archive location
Notes: This field is required if archive location is World Data Center or Other.
Notes: This field is required if archive location is World Data Center or Other.
8.1.2. If To Be Determined, Unable to Archive or No Archiving
Intended, explain:
Taken From: Data
Management | If To Be Determined, Unable to Archive or No Archiving Intended,
explain
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
Notes: This field is required if archive location is To Be Determined, Unable to Archive, or No Archiving Intended.
8.2. Data storage facility prior to being sent to an archive
facility (if any):
Office for Coastal Management - Charleston, SC
Taken From: Physical
Location | Organization, City, State, Location Description
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
Notes: Physical Location Organization, City and State are required, or a Location Description is required.
8.3. Approximate delay between data collection and submission to
an archive facility:
No information found
8.4. How will the data be protected from accidental or malicious modification or deletion
prior to receipt by the archive?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection
No information found
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.
Always left blank