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). The 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 ortho imagery within one year of
acquisition. The NAIP provides two main products: 1
meter ground sample distance (GSD) ortho imagery
rectified to a horizontal accuracy within +/- 5 meters
of reference digital ortho quarter quads (DOQQ's) from
the National Digital Ortho Program (NDOP) or from the
National Agriculture Imagery Program (NAIP); 1 meter
or 60cm GSD ortho imagery rectified within +/- 6
meters to true ground. The tiling format of NAIP imagery is
based on a 3.75' x 3.75' quarter quadrangle with a 300
pixel buffer on all four sides. The NAIP imagery is
formatted to the UTM coordinate system using the North
American Datum of 1983 (NAD83). The NAIP imagery may
contain as much as 10% cloud cover per tile. This file
was generated by compressing NAIP imagery that covers
the county extent. Two types of compression may be
used for NAIP imagery: MrSID and JPEG 2000. The target
value for the compression ratio is 15:1 for the 1 meter
imagery and 60:1 for the 60cm imagery.
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):
- 2016-11-16 00:00:00 - Digital imagery was collected at a nominal GSD of 80cm or 40cm using nine Cessna 441 aircraft flying at an average flight height of 8400m AGL for 80cm acquistion and 4400m AGL for 40cm acquisition. Aircraft flew with Leica Geosystem's ADS100/SH100 digital sensors with firmware 4.54 or ADS100/SH120 digital sensors with firmware 4.54. Each sensor collected 12 image bands Red,Green,Blue and Near-infrared at each of three look angles; Backward 19 degrees, Forward 26 degrees and Nadir for the SH100. Backward 10 degrees, Forward 14 degrees, and Nadir for the SH120. The Nadir Green band was collected in high resolution mode effectively doubling the resolution for that band. The ADS100 spectral ranges are; Red 619-651nm,Green 525-585nm, Blue 435-495nm and Near-infrared at 808-882nm. The CCD arrays have a pixel size of 5.0 microns in a 20000x1 format at nadir; a 18000x1 format at the backward look angle and a 16000x1 format at the forward look angle. The CCD's have a dynamic range of 72db and the A/D converters have a resolution of 14bits. The ADS is a push-broom sensor the ground footprint of the imagery is approximately 8km wide at a nominal 40cm GSD and 16km wide at a nominal 80cm GSD by the length flightline. The maximum flightline length is limited to approximately 240km. The factory calibrations and IMU alignments for each sensor (Serial Numbers: 10511,10512,10514,10522, 10527,10530,10531,10534,10540,10554,12502 ) were tested and verified by in-situ test flights before the start of the project. The Leica MissionPro Flight Planning Software is used to develop the flight acquisition plans. Flight acquisition sub blocks are designed first to define the GNSS base station logistics, and to break the project up into manageable acquisition units. The flight acquisition sub blocks are designed based on the specified acquisition season, native UTM zone of the DOQQs, flight line length limitations (to ensure sufficient performance of the IMU solution) as well as air traffic restrictions in the area. Once the sub blocks have been delineated they are brought into MissionPro for flight line design. The design parameters used in MissionPro will be 30% lateral overlap and 40cm or 80cm resolution. The flight lines have been designed with a north/south orientation.
- 2016-11-16 00:00:00 - The design takes into account the latitude of the state, which affects line spacing due to convergence as well as the terrain. SRTM elevation data is used in the MissionPro design to ensure the 50cm GSD is achieved over all types of terrain. The raw data was downloaded from the sensors after each flight using Leica XPro software. The imagery was then georeferenced using the 200Hz GPS/INS data creating an exterior orientation for each scan line (x/y/z/o/p/k). Leica Xpro APM software was used to automatically generate tiepoint measurements between the foward, nadir and backward look angles for each line and to tie all flight lines together. The resulting point data and exterior orientation data were used to perform a full bundle adjustment using ORIMA software. Blunders were removed, and additional tie points measured in weak areas to ensure a robust solution. Once the point data was clean and point coverage was acceptable, photo-identifiable GPS-surveyed ground control points were introduced into the block adjustment. The bundle adjustment process produces revised exterior orientation data for the sensor with GPS/INS, datum, and sensor calibration errors modeled and removed. Using the revised exterior orientation from the bundle adjustment, orthorectified image strips were created with Xpro software and the June 2014 USGS 10m NED DEM. The Xpro orthorectification software applies an atmospheric-BRDF radiometric correction to the imagery. This correction compensates for atmospheric absorption, solar illumination angle and bi-directional reflectance. The orthorectified strips were then overlaid with each other and the ground control to check accuracy. Once the accuracy of the orthorectified image strips were validated the strips were then imported into Inpho's OrthoVista 7.0 package which was used for the final radiometric balance, mosaic, and DOQQ sheet creation. The final DOQQ sheets, with a 300m buffer and a ground pixel resolution of 1m or 60cm were then combined and compressed to create the county wide CCMs.
(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.