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 - 2017 NRCS 30 County MI Lidar

Taken From: Item Identification | Title

1.2. Summary description of the data:

This metadata record describes the Classified Point Cloud (LAS) for the 2016 - 2017 Michigan LiDAR project. The data collection was funded by NRCS and USGS and the State of Michigan was in charge of collection. Thirty counties were collected in total, though not all are available yet. This record will be updated as more counties are added.

The NOAA Office for Coastal Management (OCM) downloaded USGS_LPC_MI_31Co laz files from this USGS site:

ftp://rockyftp.cr.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/ and processed the data to the Data Access Viewer (DAV) and to https.

Counties included:

Arenac, Barry, Bay, Chippewa, Clinton, Eaton, Gladwin, Hillsdale, Huron, Ingham, Ionia, Iosco, Isabella, Jackson, Kent, Lenawee, Livingston, Macomb, Mason, Midland, Monroe, Oakland, Oceana, Ogemaw, Ottawa, Sanilac, St. Clair, Tuscola, Washtenaw

Taken From: Item Identification | Abstract
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.

1.4. Actual or planned temporal coverage of the data:

2015-03-24 to 2015-04-17, 2016-04-15 to 2018-04-21, 2016-11-11 to 2016-11-14, 2016-11-29 to 2017-05-03, 2016-11-29 to 2017-11-24, 2017-03-23 to 2017-04-23, 2017-03-24 to 2017-05-07, 2017-03-29 to 2017-05-03, 2017-04-01 to 2017-04-24, 2017-04-02 to 2017-04-24, 2017-04-08 to 2017-04-09, 2017-04-16 to 2017-04-18, 2017-04-17 to 2017-04-24, 2017-04-19 to 2017-04-24, 2017-04-28 to 2017-05-06, 2017-04-28 to 2017-05-03, 2017-05-04 to 2017-05-11, 2017-11-20 to 2018-05-02, 2017-11-26 to 2018-05-02, 2017-11-29 to 2017-12-01, 2017-12-01 to 2018-04-23, 2017-12-02 to 2018-04-22

Taken From: Extents | Time Frame - Start, Time Frame - End
Notes: All time frames from all extent groups are included.

1.5. Actual or planned geographic coverage of the data:

W: -86.551555, E: -82.49499, N: 46.545735, S: 41.717544

Taken From: Extents | Geographic Area Bounds, Geographic Area Description
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.)

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.)

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.

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.

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.

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?

Yes

Taken From: Data Management | Have resources for management of these data been identified?

4.2. Approximate percentage of the budget for these data devoted to data management (specify percentage or "unknown"):

Unknown

Taken From: Data Management | Approximate percentage of budget for these data devoted to data management

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):

Lineage Statement:
Lidar data were collected via an airborne platform and lidar sensor. They were then processed to a classified point cloud.

Process Steps:

2017-01-01 00:00:00 - At selected locations throughout the site, accurate GPS coordinates and elevations are surveyed and the points are marked with targets.
2017-01-01 00:00:00 - New LiDAR data is captured for the project area using a Leica ALS70 LiDAR instrument an integrated IPAS20 GPS/INS system mounted within a Aero Commander twin engine airplane.
2017-01-01 00:00:00 - The airborne GPS data is post-processed in Inertial Explorer software and LEICA CloudPro software to determine the LiDAR sensor's angle and orientation in the terrain (project) coordinate system and datums during the survey.
2017-01-01 00:00:00 - The post processed GPS/INS solution is applied to the raw lidar data to orient and project the data points into the project area reference system as an unclassified point cloud.
2017-01-01 00:00:00 - The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software. Data is classified to produce: Class 1: unclassified, Class 2: ground, Class 7: low point, Class 9: water, Class 10: ignored ground, Class 11: withheld.
2017-01-01 00:00:00 - The classified lidar data is exported as 2500 X 2500 foot tiles in the LAS format with any or all classes required to produce derivative products.
2018-12-18 00:00:00 - Data for Oceana County were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan South State Plane (ft) coordinates with vertical feet NAVD88 (Geoid12b). Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. Classes listed in step 5 were noted to be incorrect. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise (Citation: Classified lidar)
2019-04-05 00:00:00 - Data for Mason and Ottawa counties were downloaded from the USGS Rocky ftp site in NAD83 (2011) Michigan South State Plane (ft) coordinates (Ottawa) and Michigan Central State Plane (ft) coordinates (Mason) with vertical feet NAVD88 (Geoid12b). Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2019-06-07 00:00:00 - Data for Chippewa County were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan North State Plane (ft) coordinates with vertical feet NAVD88 (Geoid12b). Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2019-06-14 00:00:00 - Data for Arenac and Iosco counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan Central State Plane (ft) coordinates with vertical feet NAVD88 (Geoid12b). Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2019-06-21 00:00:00 - Data for Macomb, Monroe, and Sanilac counties were downloaded from the USGS Rocky ftp site in NAD83 (2011) Michigan South State Plane (ft) coordinates in NAVD88 (Geoid 12b) vertical feet. Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2019-12-19 00:00:00 - Data for Bay, Huron, St. Clair, and Tuscola counties were downloaded from the USGS Rocky ftp site in NAD83 (2011) Michigan South State Plane (ft) coordinates in NAVD88 (Geoid 12b) vertical feet. Data were converted to geographic coordinates and ellipsoid heights for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2020-08-14 00:00:00 - Data for Hillsdale, Kent and Oakland counties were downloaded from the USGS Rocky ftp site in NAD83 (2011) Michigan South State Plane (ft) coordinates in NAVD88 (Geoid 12b) vertical feet. Data were converted to geographic coordinates, from feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2020-08-21 00:00:00 - Data for Ogemaw county was downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan Central State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2020-08-28 00:00:00 - Data for Livingston, Midland, and Washtenaw counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan South State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2020-09-10 00:00:00 - Data for Isabella, Jackson, and Lenawee counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan South State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2020-10-22 00:00:00 - Data for Clinton, Eaton, and Ingham counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan South State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2020-10-23 00:00:00 - Data for Ingham county was downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan Central State Plane (Int ft) coordinates with vertical feet NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise
2022-04-07 00:00:00 - Data for Eaton (EatonB folder) and Arenac (Arenac_TL folder) counties were downloaded from the USGS Rocky ftp site in NAD83(2011) Michigan South & Central State Plane (Int ft) coordinates with vertical feet in NAVD88 (Geoid12b) elevations. Data were converted to geographic coordinates, from vertical feet to meters, and to ellipsoid heights (using Geoid 12b) for ingest in the NOAA Digital Coast Data Access Viewer. The observed classes fit the USGS LBS 1.2 with 1 = unclassified, 2 = ground, 7 = low noise, 9 = water, 10 = ignored ground near breakline, 17 = bridge deck, 18 = high noise

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):

No information found

Taken From: Data Quality | Quality Control Procedures Employed

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
5.2. Quality control procedures employed
7.4. Approximate delay between data collection and dissemination
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:

https://www.fisheries.noaa.gov/inport/item/55315

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):

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?

Yes

Taken From: Data Management | Do these data comply with the Data Access directive?

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

Taken From: Data Management | Is access to the data limited based on an approved waiver?

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:

U.S. Geological Survey

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.

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.

7.2.2. URL of data access service, if known:

https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=8660
https://rockyweb.usgs.gov/vdelivery/Datasets/Staged/Elevation/LPC/Projects/

Taken From: Distribution Info | Download URL
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

Taken From: Data Management | Approximate delay between data collection and dissemination

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.

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)

NCEI_CO

Taken From: Data Management | Actual or planned long-term data archive location

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.

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.

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.

8.3. Approximate delay between data collection and submission to an archive facility:

No information found

Taken From: Data Management | 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?
Discuss data back-up, disaster recovery/contingency planning, and off-site data storage relevant to the data collection

No information found

Taken From: Data Management | How will the data be protected from accidental or malicious modification or deletion prior to receipt by the archive?

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