Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:73890 | Published / External
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.
1. General Description of Data to be Managed
NOAA Project MD2201-TB-C was located on the Eastern portion of the Delmarva Peninsula, approximately 426 sq miles and 7 flight lines. Data was collected on May 22, 2023 using Woolpert, Inc Cessna 404 (N404CP) and the Leica ADS100 Airborne Digital Sensor. Data was collected in coordination of +/- 3 hours of low tide. The data was developed based on a horizontal reference system of NAD83 (2011) projection of UTM Zone 18N, epoch: 2010, Meters, EPSG 6347. Vertical reference will be NAVD88 Geoid 18, Meters.
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):
Process Steps:
- 2023-06-23 00:00:00 - The Leica ADS100 Airborne Digital Sensor is a push-broom geometry sensor, collecting 12-bit data with 20,000 pixel swath. The sensor is capable of collecting multiple spectral bands and angles simultaneously. Leica ADS100 collects twelve bands of imagery simultaneously: four Red Blue Green and Near infrared CCD lines capture information in the forward, nadir and backward views from the aircraft. The imagery for this task order was acquired using the Leica ADS100 multispectral scanner. The ADS100 utilizes the Leica Inertial Explorer direct positioning and orientation system that is based on airborne GPS and inertial measurement unit (IMU) technology. The Inertial Explorer data were reduced using Leica Inertial Explorer software package. All of the source imagery was processed using the Leica XPRO software package. This package provides the capability to perform digital image processing, aerial triangulation, and image rectification.
- 2023-06-23 00:00:00 - Stereo imagery, or L1s as they are referred to in Leica XPRO manual, are generated in full strips of imagery along with any of the support files needed to reconstruct within the stereo environment. Each nadir view angle is accompanied by a forward and backward strip and together which effectively create stereo models. Support files are created from Leica XPRO processing software in place of traditional frame sensor EO format. The software can re-project from latitude and longitude to the coordinate reference projection required for this project. In this case that would be a horizontal projection of UTM Zone 18N, NAD83 (2011) epoch: 2010, Meters, EPSG 6347. Vertical reference will be NAVD88 Geoid 18, Meters. The final support files include: .ads, .odf.adj, .cam, and .sup files
- 2023-06-23 00:00:00 - The individual rectified strips of ortho rectified imagery were then mosaicked together to form a seamless imagery database over the entire task order area using the OrthoVista software by Inpho GmbH. The final digital orthophoto imagery (DOI) were extracted using OrthoVista. Final orthophoto non-overlapping tiles were produced in GeoTIFF format using a cell size of 25 cm and a tile size of 3000 m x 3000 m.
(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)
- 2.4. Point of Contact Email
- 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.
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://coastalimagery.blob.core.windows.net/digitalcoast/OceanCityMD_RGBN_2023_10220/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 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.