Data Management Plan
GUID: gov.noaa.nmfs.inport:49495 | 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
This data set contains imagery from the National Agriculture
Imagery Program (NAIP). NAIP acquires digital ortho imagery
during the agricultural growing seasons in the continental U.S..
A primary goal of the NAIP program is to enable availability of
of ortho imagery within one year of acquisition. NAIP provides
four main products: 1 meter ground sample distance (GSD) ortho
imagery rectified to a horizontal accuracy of within +/- 5
meters of reference digital ortho quarter quads (DOQQ's) from
the National Digital Ortho Program (NDOP); 2 meter GSD
ortho imagery rectified to within +/- 10 meters of reference
DOQQs; 1 meter GSD ortho imagery rectified to within +/- 6
meters to true ground; and, 2 meter GSD ortho imagery rectified
to within +/- 10 meters to true ground. The tiling format of
NAIP imagery is based on a 3.75' x 3.75' quarter quadrangle
with a 300 meter buffer on all four sides. NAIP quarter quads
are formatted to the UTM coordinate system using NAD83. NAIP
imagery may contain as much as 10% cloud cover per tile.
Original contact information:
Contact Org: Aerial Photography Field Office (APFO)
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):
- 2012-01-12 00:00:00 - The imagery was collected using ADS40-SH52 digital sensors.\n Collection was performed using a combination of twin-engine\n aircraft flying at an average flying height of 17500 and\n 27000 ft above mean terrain, with nominal sidelap of 21%,\n giving the collected data nominal ground sampling distance\n of 0.55 and 0.75 meters. Based-upon the CCD Array\n configuration present in the ADS40 digital sensor, imagery\n for each flight line is 12,000-pixels in width. Red, Green,\n Blue, Near-Infrared and Panchromatic image bands were\n collected.\n Collected data was downloaded to portable hard drives and\n shipped to the processing facility daily. Raw flight data\n was extracted from external data drives using GPro software.\n Airborne GPS / IMU data was post-processed using IPAS, PosPac\n and/or TerraPos software and reviewed to ensure sufficient\n accuracy for project requirements.\n Using Pictovera software, planar rectified images were\n generated from the collected data for use in image quality\n review. The planar rectified images were generated at five\n meter resolution using a two standard deviation histogram\n stretch. Factors considered during this review included but\n were not limited to the presence of smoke and/or cloud cover,\n contrails, light conditions, sun glint and any sensor or\n hardware-related issues that potentially could result in\n faulty data. When necessary, image strips identified as not\n meeting image quality specifications were re-flown to obtain\n suitable imagery.\n Aerotriangulation blocks were defined primarily by order of\n acquisition and consisted of four to seventeen strips.\n Image tie points providing the observations for the least\n squares bundle adjustment were selected from the images using\n an autocorrelation algorithm. Photogrammetric control points\n consisted of photo identifiable control points, collected\n using GPS field survey techniques. The control points were\n loaded in to a softcopy workstation and measured in the\n acquired image strips. A least squares bundle adjustment\n of image pass points, control points and the ABGPS was\n performed to develop an aerotriangulation solution for each\n block using Pictovera software. Upon final bundle\n adjustment, the triangulated strips were ortho-rectified to\n the USGS NED DEM for the project area. The images were\n re-sampled from the raw resolution of 0.55 or 0.75 meters to\n the required resolution of 1.0 meters.\n Positional accuracy was reviewed in the rectified imagery\n by visually verifying the horizontal positioning of the\n known photo-identifiable survey locations using ArcGIS\n software.\n The red, green, blue, and NIR bands were combined to\n generate a final ortho-rectified image strip. The ADS40\n sensor collects twelve bit image data which requires\n radiometric adjustment for output in standard eight bit\n image channels. The ortho-rectified image strips were\n produced with the full 12 bit data range, allowing\n radiometric adjustment to 8 bit range to be performed on\n a strip by strip basis during the final mosaicking steps.\n The imagery was mosaicked using manual seamline generation\n in Orthovista Seam Editor (OVSE). The 12 bit data range was\n adjusted for display in standard eight bit image channels by\n defining a piecewise histogram stretch using OrthoVista\n software. A constant stretch was defined for each image\n collection period, and then strip by strip adjustments were\n made as needed to account for changes in sun angle and\n azimuth during the collection period. Strip adjustments were\n also made to match the strips histograms as closely as\n possible to APFO specified histogram metrics and color\n balance requirements. Automated balancing algorithms\n were applied to account for bi-directional reflectance as\n a final step before the conversion to 8 bit data range.\n APFO specified DOQQs were extracted from the final mosaic\n in GeoTIFF format. 4-Band DOQQs were produced and 3-B
(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.
There are no limitations for 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.