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
The mosaic image contained in this file is comprised of RGB imagery collected by the Leica ADS40 sensor along the coast of California. Data coverage generally extends along the coastline from the waterline inshore 500 meters. The sensor produces 12-bit data with three color bands that are not generally in a format accessible to most Geographical Information Systems (GIS). Specialized in-house and commercial software packages processes the imagery data into GIS-compatible products for visualization and further analysis. Horizontal positions, provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). Vertical positions are referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID09 model is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88). Imagery have been ortho-rectified and mosaiced into boxes that extend approximately 5 km along shore. The file index is provided by the shape file, "CA_boxes" and the numbers used to identify files are in the "Box" field of the shape file. The data file naming convention is based on the year, project, area name, "Box" number, and product type. An example file name is "2009_NCMP_CA_###_RGB_ADS40.tif," where (2009) is the year of data collection, (NCMP) is the project under which data were collected, (CA) is the area of data collection, (###) is the "Box" number, and "(RGB_ADS40)" is the product type.
Original contact information:
Contact Org: JALBTCX
Title: Data Production Manager
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.
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):
- EarthData utilized an InfoTerra Pixel Factory workflow for processing the aerotriangulation for the orthoimagery covering the project area. The airborne GPS data was processed and integrated with the inertial measurement unit (IMU). The resulting imagery and control were imported into the InfoTerra Pixel Factory system for use in the aerotriangulation. The ADS40 imagery was downloaded onto the EarthData server and brought over to the UNIX basedInfoTerra Pixel Factory system. The ground control was used in conjunction with the processed airborne global positioning system (ABGPS) results for the aerotriangulation. The ground control points were read in all available imagery and tie points between flight lines were selected. A fully analytical bundle adjustment was run. The properly formatted InfoTerra Pixel Factory results were used for subsequent processing. All final results were output into an AT report which is being delivered with the final orthoimagery."
- InfoTerra Pixel Factory was used in the processing of the DSM for orthorectification of the imagery covering the Orchard Hills Training Site, Idaho project area. InfoTerra Pixel Factory digital surface modeling is based on an auto correlated pixel-matching system within the InfoTerra Pixel Factory software. The auto correlated digital surface model (DSM) surface represents the initial surface model. The following is the process used. 1. Using the DSM InfoTerra Pixel Factory data set created, the technician performed a visual inspection of the data to verify that the flight lines met correctly. The technician also verified that there were no voids, and that the data covered the project limits. The technician then selected a series of areas from the dataset and inspected them where adjacent flight lines met. 2. This DSM surface is used in the rectification of the orthoimagery.
- The digital orthophotography is comprised of 24 bit natural color RGB bands and a 0.30 meter pixel resolution ground orthos for the project area. The InfoTerra Pixel Factory was used in the generation of the orthoimagery covering all project tiles. The radiometric adjustments and color balancing were performed on the raw 16 bit format imagery for each flight line prior to the import to the Pixel Factory. FEDI uses proprietary software developed specifically to adjust the radiometry of the imagery of the push broom three lines scanner such as the ADS40. The rectification process was then run using the processed DSM surface and the radiometrically balanced imagery on each flight line. The quicklook (reduced resolution rectification) ortho for all flight lines then used to generate the automatic mosaic lines. . which were placed, to mosaic the full resolution ortho of the ADS40 imagery strips. An initial QA/QC was performed by the technician to ensure that the mosaic lines were appropriately placed and that there was appropriate imagery coverage. The final imagery data set is removed from the InfoTerra environment in a process called """"packaging"""" where the individual tiles are created. All data processing in the InfoTerra system is performed in UTM meters; it is during packaging that final datum and projection are defined. The created tiles are reviewed again for anomalies and interactive radiometric adjustment applied where needed. QA/QC was performed looking for anomalies, smears and other indications of problems within the digital Orthophoto creation process, interactive radiometric adjustment applied where needed. Two additional radiometric adjustments are applied to the completed orthos in Adobe Photoshop. The first is a sharpening mask filter; this filter is used to help increase sharpness of a digital image. The basis for this filter is to locate pixels that differ in value from surrounding pixels by the threshold specified. It then increases the pixels' contrast by the value identified. For neighboring pixels specified by the threshold, the lighter pixels get even lighter and the darker pixels get even darker based on the specified amount. The changes made maintained the integrity of the original histogram curve.
(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.
- 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.
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.
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.