Search Help Show/Hide Menu

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:
2022 USACE FEMA NCMP Phase One Natural Color 8 Bit Imagery: Post Hurricane Nicole, FL
1.2. Summary description of the data:

These files contain 3-band RGB orthorectified mosaic imagery tiles generated from data collected using a Phase One iXM-150F digital camera. This full frame medium-format aerial survey camera collected imagery data in tandem with a bathymetric lidar sensor and a hyperspectral imager on a single remote sensing platform. Native imagery data is not generally in a format accessible to most Geographic Information Systems (GIS). Specialized in-house and commercial software packages were used to process the native imagery data into 3-band orthorectified mosaic imagery that can be imported into GIS software for visualization and further analysis. Trajectories were transformed into positional coordinates using the HTDP (Horizontal Time-Dependent Positioning) software to maintain consistency with the NGS (National Geodetic Survey) reference to the North American Datum of 1983 (NAD83) and the North American tectonic plate coordinates realized from the National Adjustment of 2011, or NAD83 (2011). Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to NAD83 (2011) at the 2010.00 epoch. Vertical positions, provided in meters, are referenced to the NAD83 (2011) ellipsoid. NGS hybrid geoid model GEOID12B was used to transform the vertical positions from ellipsoidal heights to orthometric heights referenced to the North American Datum of 1988 (NAVD88). The imagery data are in TIF files tiled using 1 km boxes defined by the Military Grid Reference System (MGRS). The file naming convention references the year, effort, area, box number, and data product type. An example file name is, 2022_FEMA_FL_17RMN7399_RGB.tif, where 2022 is the year of data collection, FEMA is the effort under which data were collected, FL is the area of data collection, 17RMN7399 is the box number and RGB is the data product type.

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:
2022-11-24
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: -81.407, E: -80.715, N: 30.286, S: 28.77
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.)
Map (digital)
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
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?
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):

Process Steps:

  • 2022-11-01 00:00:00 - Phase One iXM-150F data were converted from raw Intelligent Image Quality (IIQ) files created during the data collection to unrectified TIF images using the Capture One Processing Engine (COPE) which is a command line file processing utility developed by Phase One as part of their software development toolkit (SDK). A Smoothed Best Estimate of Trajectory (SBET) solution was resolved from the raw aircraft GNSS-IMU positional data using the Applanix POSPac Mobile Mapping Suite (MMS) software package. The Exterior Orientation (EO) parameters and camera misalignments for the imagery were then computed using the Leica IPAS CO+ software package where the values were checked against the known current calibration values for this camera installation. A Digital Elevation Model (DEM) was generated from lidar data collected concurrently with the imagery using an adjacent sensor in tandem with the digital camera on a single remote sensing platform. The unrectified TIF files, EO data, DEM file, SimActive Tile Definition File (TDF), and camera calibration file were given as input to the SimActive Correlator3D software package for processing. Using Correlator3D, the data went through Aerial Triangulation (AT), orthorectification, color balancing, and mosaicking. The mosaic data were exported from Correlator3D as TIF files tiled according to 1 km MGRS grid cells. The mosaic image files were compressed using Geospatial Data Abstraction Library (GDAL) tools by applying the LZW lossless compression method. The compressed mosaic image files were finalized using GDAL and the Esri ArcGIS Desktop software package. GDAL was used to calculate statistics and build pyramids, while ArcGIS was used to create metadata for each image tile. The data processing workflow, including software packages, algorithms and parameters are provided in detail, within this metadata as Process Steps.
  • 2022-11-01 00:00:00 - After collection, the navigation data was refined with the Applanix POSPac Mobile Mapping Suite (MMS) software package. A copy of the raw POS data from the Applanix POS AV 610 system was used as input for the navigation post-processing. A reference to the Applanix POSPac Trimble Post-Processed CenterPoint RTX (PP-RTX) correction service was downloaded for kinetic processing. POSPac PP-RTX is a cloud based global GNSS correction service which utilizes Trimble’s RTX technology to provide centimeter level post-processed positioning accuracy without base stations. The Trimble RTX technology utilizes data from a dedicated global network of tracking stations to compute corrections to satellite orbit and clock information as well as atmospheric delay models. After PP-RTX completed, the lever arms and mounting angles were verified to match the values of the current camera installation. At this stage, an automated primary GNSS lever arm calibration was performed to check the auto-calibration values against the original lever arm values to ensure no unexpected offset or drift in the misalignment values had occurred. Using the original lever arm values, the data was then processed using the integrated GNSS-IMU and other aiding sensor data to compute forward-reverse processing, run smoother processing to compute smoothed states, write a Smoothed Best Estimate of Trajectory (SBET) file, and generate Quality Control (QC) reports. The QC reports were then reviewed with special attention paid to the error RMS from each of the north, east, and down positions as referenced by the smoothed performance metrics; Position Dilution of Precision (PDOP) error caused by the relative position of the satellites; and the forward-reverse separation throughout the flight as refined by PP-RTX. Upon satisfactory review, an SBET file was exported from POSPac MMS using the default World Geodetic System 1984 (WGS 84) method where the position data was referenced to the ITRF00 datum with an epoch targeting the mission date. An ITRF (International Terrestrial Reference Frame) is a realization of the ITRS (International Terrestrial Reference System) which through various scales, rotations, and rates applied to its origin are updated for geodetic use as time goes on by producing new solutions every few years. Over time, the WGS 84 reference coordinate system used by the Global Positioning System (GPS) has had several re-adjustments to keep it in line with ITRF updates.
  • 2022-11-01 00:00:00 - POSPac MMS transformations are based on the NNR-MORVEL56 (No-Net-Rotation Mid-Ocean Ridge VELocity) tectonic plate model. NNR-MORVEL56 is a set of angular velocities that describe the motions of 56 plates relative to a no-net-rotation reference frame. This SBET file was then transformed from the ITRF00 datum with an epoch corresponding to the mission date to the North American Datum of 1983 (NAD83) and the North American tectonic plate coordinates realized from the National Adjustment of 2011, or NAD83 (2011) at the 2010.00 epoch. The National Geodetic Survey (NGS) has produced several adjustment realizations to NAD83, including NAD83 (2011). While WGS 84 is updated to match ITRF realizations, NAD83 is tied to the North American tectonic plate where its coordinates have been gradually drifting farther from the WGS 84 and ITRF adjustments with the passage of time. Trajectories were transformed into positional coordinates using the HTDP (Horizontal Time-Dependent Positioning) software to maintain consistency with the NGS (National Geodetic Survey) reference to the North American Datum of 1983 (NAD83) and the North American tectonic plate coordinates realized from the National Adjustment of 2011, or NAD83 (2011). Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to NAD83 (2011) at the 2010.00 epoch. Vertical positions, provided in meters, are referenced to the NAD83 (2011) ellipsoid. NGS hybrid geoid model GEOID12B was used to transform the vertical positions from ellipsoidal heights to orthometric heights referenced to the North American Datum of 1988 (NAVD88).
  • 2022-11-01 00:00:00 - The copy of the raw Phase One iXM-150F data was converted from raw Intelligent Image Quality (IIQ) files created during the data collection to unrectified TIF images using the Capture One Processing Engine (COPE) which is a command line file processing utility developed by Phase One as part of their software development toolkit (SDK). Using custom Python scripts, associated data was extracted from the raw camera data to derive the event file, photo ID file, preliminary Exterior Orientation (EO) file, KML (Keyhole Markup Language) files and scaled JPEG images resampled from the TIF images. The KML and JPEG data was used to check the imagery for major collection issues such as coverage discrepancies before further processing. Using Leica’s IPAS CO+ software package, the SBET file was converted to a solution file format usable by IPAS CO+. This solution file, event file, photo ID file, and valid lever arm misalignment values were used by IPAS CO+ to create and export the finalized Exterior Orientation (EO) values as a text file. Using a custom Python script, this text file was then restructured into a format usable by Correlator3D. The unrectified TIF imagery was then subjected to image processing using the SimActive Correlator3D software package. The TIF images, concurrent DEM image, EO file, SimActive Tile Definition File (TDF), and camera installation file were used to build a project in Correlator3D. Aerial Triangulation (AT), orthorectification, color balancing, mosaicking, and tiling were done in a preliminary manner and the data was reviewed. The AT report was reviewed to ensure a satisfactory quality assessment and limited projection error. The automatically generated seamlines were manually adjusted to correct unsatisfactory mosaicking patterns. Next, the corrected mosaic data were exported from Correlator3D as TIF files tiled according to 1 km MGRS grid cells. The mosaic image files were compressed using Geospatial Data Abstraction Library (GDAL) tools by applying the LZW lossless compression method. GDAL was then used to calculate statistics and build pyramids on the compressed mosaic image tiles. The Esri ArcGIS Desktop software package was then used to create metadata for each image tile.
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):

These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

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
  • 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.3. Data access methods or services offered
  • 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):
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. These data have been developed from the best available sources. Although efforts have been made to ensure that the data are accurate and reliable, errors and variable conditions originating from physical sources used to develop the data may be reflected in the data supplied. Users must be aware of these conditions and bear responsibility for the appropriate use of the information with respect to possible errors, scale, resolution, rectification, positional accuracy, development methodology, time period, environmental and climatic conditions and other circumstances specific to these data. The user is responsible for understanding the accuracy limitations of the data provided herein. The burden for determining fitness for use lies entirely with the user. The user should refer to the accompanying metadata notes for a description of the data and data development procedures.

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.
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:
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:
No information found
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:

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

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