Data Management Plan
GUID: gov.noaa.nmfs.inport:49515 | Published / External
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
These files contain imagery data collected with an RCD30 camera as 8-bit RGBN TIFF images. Imagery was required 1000m seaward of the land/water interface or to laser extinction (whichever came first), while topographic lidar data were required 500m inland of the land/water interface. Data coverage generally extends along the southwest of Florida from Anclote Key to Marco Island. Horizontal positions, provided in meters, are referenced to the North American Datum (NAD83) 2011, projected to Universal Transverse Mercator (UTM) Zone 17 North in meters. Vertical positions were acquired to the NAD83 2011 ellipsoid.Imagery was rectified, upon request, using a Bare Earth elevation model in order to create mosaics with improved aesthetics. Positions of buildings could be in error and imagery should not be used for digitizing structures. The data file naming convention is based on the year, project, area name, clip boundary, product type, number of bands, and altitude and in some cases a dataset name or a number to indicate multiple files. An example file name is "2015_NCMP_FL_01_5mGrid_RGB where 2015 is the year of data collection, NCMP is the Effort under which data were collected, "RGB" is the product type, In rare cases file names may include whether data was collected at a nominal range of high tide (HT) or low tide (LT). The supplementary files are of the same name.
Original contact information:
Contact Org: JALBTCX
Title: Data Production Manager
Phone: 228-252-1131
Email: JALBTCX@usace.army.mil
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:
- 2016-10-11 00:00:00 - Imagery data collected with the RCD30 camera were extracted from the raw compressed airborne format to 8-bit RGBN TIFF images using Leica's FramePro software. Leica's IPAS CO+ was used to finalize the camera calibration. It uses orthogonal lines flown in both directions over an area containing buildings and features. In this case, orthogonal lines from the calibration flight over Falcon Field Airport were used. IPAS CO+ has an automated point matching (APM) feature that identifies the same point in overlapping images and automatically iterates to compute final misalignment and principal point offset (PPO) parameters. IPAS CO+ was then used along with the final camera calibration file and the final GNSS/IMU trajectory file to export valid exterior orientation (EO) parameters for each image. The TIFF images and the EO files were used by LSS when processing the lidar data, to colorize lidar points that overlapped the imagery with RGB values. The color values are valid for the flight time of each pulse. Where no images overlapped the lidar data, lidar points still remain but are not colored. A digital elevation model was created from the bare earth lidar data at 50cm resolution for orthorectification of the main survey line data, and at 25cm for the FNP lines. All RGBN TIFF images exported from FramePro were rectified in ERDAS IMAGINE Photogrammetry, using the DEM and the EO files created by IPAS CO+. No additional Aerial Triangulation was conducted. Individually rectified images were used to create a 15cm resolution color balanced mosaic in OrthoVista. Final 4-band RGBN mosaic images were created for each project tile in 8-bit geotiff format. It should be noted that imagery was rectified, upon request, using a bare earth elevation model in order to create mosaics with improved aesthetics. Therefore positions of buildings could be in error and imagery should not be used for digitizing structures.
(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.3. Is this a one-time data collection, or an ongoing series of measurements?
- 1.4. Actual or planned temporal coverage of the data
- 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.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
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://coast.noaa.gov/dataviewer/#/imagery/search/where:ID=6222
https://coastalimagery.blob.core.windows.net/digitalcoast/FL_Panhandle_2015_6222/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.