Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:76171 | Published / External
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. For more information, consult the help guides on the new Data Management Plan as well as how to convert this Legacy DMP to the new format.
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
Original Data:
These files contain 48-band Hyperspectral orthorectified mosaic imagery tiles generated from data collected using a ITRES Compact Airborne Spectrographic Imager (CASI) 1500 hyperspectral sensor. This wide-array hyperspectral VNIR imager collected imagery data in tandem with the Coastal Zone Mapping and Imaging Lidar bathymetric sensor and a Phase One 150-F full-frame mapping camera 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 48-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 UTM Zone 16 NAD83 (2011) meters coordinates at the 2010.00 epoch. 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, 2024_NCMP_FL_16RFU9899_HSI, where 2024 is the year of data collection, NCMP is the effort under which data were collected, FL is the area of data collection 16RFU9899 is the box number and HSI is the data product type.
The NOAA Office for Coastal Management (OCM) received the data from the USACE Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). NOAA OCM processed the data to the NOAA Digital Coast Data Access Viewer (DAV) to make the data publicly available for bulk and custom downloads.
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.
Data extent for Block 24428
W: -85.00441, E: -84.62675, N: 30.87702, S: 30.68801Data extent for Block 24426
W: -84.70032, E: -84.52926, N: 30.98956, S: 30.8108Data extent for Block 24429
W: -85.0315, E: -84.89802, N: 31.01548, S: 30.83348Data extent for Block 24427
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):
Lineage Statement:
CASI-1500 hyperspectral data were converted from RAW (*.raw) files created during the data collection to unrectified radiometrically corrected PCIDSK (*.pix) file using command line RADCOR processing executable utility developed by ITRES. 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 SBET was convert to a format recognizable by ITRES's MAKEGPS executable. Navigation sync and correction was applied using ITRES' ATTSYNC, FORMNAV, and NAVCOR. A Digital Elevation Model (DEM) was generated from lidar data collected concurrently with the imagery using an adjacent sensor in tandem with the CASI-1500 on a single remote sensing platform. The unrectified PIX files, navigation data, DEM file, and camera calibration parameters were given as input to the HydroFusion, a Teledyne Optech software package for processing lidar, true color imagery and hyperspectral imagery. Using HydroFusion, the data was geometrically corrected using ITRES's GEOCOR utility, atmospheric correction, glint reduction, color balancing, and mosaicking. The mosaic data were exported from HydroFusion as ENVI IMG (*.img) files in a single block according as collected. Image footprint shapefiles were used to extract 1 km MGRS grid cells. Finally, the block mosaic was clipped to each representative 1km MGRS grid. 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 also used to calculate statistics and build pyramids internally using the accepted Cloud Optimized TIFF format, 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.
The NOAA Office for Coastal Management (OCM) received the data from the USACE Joint Airborne Lidar Bathymetry Technical Center of Expertise (JALBTCX). NOAA OCM processed the data to the NOAA Digital Coast Data Access Viewer (DAV) to make the data publicly available for bulk and custom downloads.
Process Steps:
- These data were collected using the ITRES CASI-1500 hyperspectral imager. The camera is owned by the U.S. Army Corps of Engineers (USACE) Joint Airborne Lidar Bathymetry Technical Center of eXpertise (JALBTCX) and operated through contract with Woolpert, Inc. The CASI-1500 is ITRES's flagship wide-array airborne hyperspectral VNIR push-broom imager specifically designed for remote sensing applications. The CASI-1500 can capture high-resolution spectral imagery from 350nm to 1050nm with up to 288 spectral channels and a total field of view of 40 degrees. The imagery was collected with an aperture of 4 and an integration time 10ms at 48-Band. Aircraft position, velocity, and acceleration information was collected as raw POS data using the Applanix POS AV 610 (Position and Orientation System Airborne Vehicles) system. The POS AV 610 creates a GNSS-IMU solution for airborne direct georeferencing which precisely measures the position and orientation of the onboard aerial sensors hundreds of times per second and accounts for all motion variables at the exact moment of data capture. All raw data streams from the collected mission, including the RAW files from the CASI-1500 hyperspectral imager and the POS data from the Applanix POS AV 610 system, were then transferred from the field to the office for downloading, duplicating, and processing.
- 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, lever arms and mounting angles were verified to match the values of current camera installation. At this stage, an automated primary GNSS lever arm calibration was performed to check auto-calibration values against original lever arm values to ensure no unexpected offset or drift in misalignment values had occurred. Using the original lever arm values, 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 reviewed with special attention paid to error RMS from each of the north, east, and down positions as referenced by 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. 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. 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 copy of the raw CASI-1500 data was transferred to a Windows PC capable of running Hydrofusion software. Hydrofusion is a GUI interface that allows the user to set parameters as input to the ITRES command line tools. Raw data was radiometrically corrected using ITRES' RADCOR tool. The resulting output is a radiometrically corrected *.pix image file and a *.att navigation information file.
- SBET data was converted to a format recognized by ITRES' navigation tools using MAKEGPS. Furthermore, navigation correction was achieved using ATTSYNC, FORMNAV, NAVCOR and NAV2ASC tools. Descriptions of these tools are out of scope for this metadata. More information can be found on ITRES' website, itres.com.
- The unrectified PIX image and navigation files were then used to create geospectral coordinates using ITRES's GEOCOR utility in Hydrofusion. The image pixel data was atmospherically corrected, had glint reduction applied, color balanced, and mosaicked. Hydrofusion algorithms use a combination of TAFKAA and a proprietary Down Scattering Angle for atmospheric correction. Each pixel is then placed into the mosaic based on it's geospectral coordinates and whether the pixel is land based or water based. Land-based pixels are placed according to closest to Nadir where as water-based pixels paricularily in overlap regions can be selected as optional brightest, darkest or last-in pixels. Finally, if multiple data collections occur in a flight block, mosaics from each data collection are merged using a collection of L3Harris ENVI mosaic tools.
- Export and merged mosaics were used to create image footprint shapefiles on a block by block basis. Image footprint shapefiles were used to extract 1 km MGRS grid cells. Finally, the block mosaic was clipped to each representative 1km MGRS grid. The mosaic image tiles were simultaneously 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 also used to calculate statistics and build pyramids internally using the accepted Cloud Optimized TIFF format, while ArcGIS was used to create metadata for each image tile.
- 2025-06-20 00:00:00 - The NOAA Office for Coastal Management (OCM) received 510 img files (Blk 24426 - 224, Blk 24427 - 122, Blk 24428 - 40, Blk 24429 - 124) from USACE JALBTCX for the area around Lake Seminole in Georgia and Florida. The data were in UTM Zone 16 (NAD83 2011) meters coordinates. NOAA OCM converted the data to GeoTIFF format using an internal script and processed the data to the NOAA Digital Coast Data Access Viewer (DAV) to make the data publicly available for bulk and custom downloads.
(describe or provide URL of description):
JALBTCX evaluates final data coverage using techniques that are common to the imagery industry. These techniques included visual review of the final data coverage and verification of the data alongside lidar elevation data collected concurrently with the imagery.
During inspection and quality control of the imagery data, flightline to flightline accuracies met specifications.
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)
- 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?
(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. 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.
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/LakeSeminole_GA_HSI_2024_10350/index.html
Notes: All URLs listed in the Distribution Info section will be included. 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.
(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.