Data Management Plan
GUID: gov.noaa.nmfs.inport:48369 | 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
EarthData International collected ADS-40/ISTAR-derived orthophotos at a 50 centimeter pixel resolution to produce natural color and color infrared ortho photo tiles. The period of aerial collection was 14 DEC 2004 to 15 DEC 2004 with a reflight of several lines conducted on 1 FEB 2006. During the time of image acquisition two dual frequency GPS receivers were utilized. One receiver was operated on board the aircraft with the dual frequency antenna located directly over the camera. The second receiver was used as a base station.These receivers were in constant operation during the imagery mission and GPS phase data was collected at an epoch rate of 1 second. The airborne GPS data and IMU were used in combination with ground surveyed points to control the imagery. The imagery fully encompasses the project boundary. The DTM deliverable for this project was manually compiled using stereo pairs generated from the orthophoto flight. The DEM masspoint grid used to rectify the orthophotography was derived from the compiled DTM. All data produced for this project was referenced horizontally to NAD83, and vertically to Mean Sea Level(MSL), NAVD 88 in UTM meters.
Original contact information:
Contact Name: Harold Rempel
Contact Org: EarthData International, Inc.
Title: Director of Program Management
Phone: 301-948-8550
Email: hrempel@earthdata.com
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:
- 2005-06-16 00:00:00 - The airborne GPS data were processed and integrated with the IMU. The results were imported into the ISTAR system for use in the aerotriangulation. The ADS40 imagery was downloaded onto the EarthData server and brought over to the UNIX based ISTAR system. The ground control was used in conjunction with the processed ABGPS results for the aerotriangulation. The properly formatted ISTAR results were used for subsequent processing.
- 2005-06-22 00:00:00 - This process describes the import and QC of the photogrammetrically-derived DEM surface from stereo pairs for use in the ISTAR processing system. 1. Using the DEM data set, 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. A process, which utilizes 3-D Analyst and EarthData's proprietary software was run to detect and color code the differences in elevation values and profiles. The technician reviewed this information and located the areas that contained systematic errors or distortions that were introduced by the auto correlation. 2. Systematic distortions highlighted in step 1 were removed and the data were re-inspected. Corrections and adjustments can involve the application of angular deflection or compensation for curvature of the ground surface that can be introduced by crossing from one type of land cover to another. 3.The data were checked against the control network to ensure that vertical requirements were maintained.
- 2005-06-30 00:00:00 - The digital orthophotography is comprised 50 centimeter pixel Ground Orthos. Once the DEM data was integrated into the ISTAR system the initial radiometric adjustments were performed on the imagery for each flight line attempting to reach the best possible histogram. The rectification process was run using the processed DEM surface and the radiometrically balanced imagery on each flight line. A second set of radiometric adjustments were made and mosaic lines were placed. QA/QC was performed looking for smears and other indications of problems within the digital orthophoto creation process. The final imagery data set is removed from the ISTAR environment in a process called "packaging" where the individual tiles are created. The created tiles are reviewed again for anomalies and interactive radiometric adjustment applied where needed. The final product was GeoTIFF format digital orthos.
(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.6. Type(s) of 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.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=124/details/124
https://coast.noaa.gov/dataviewer/#/lidar/search/where:id=135/details/135
https://coastalimagery.blob.core.windows.net/digitalcoast/FreeportFL_CIR8_2004_125/index.html
https://coastalimagery.blob.core.windows.net/digitalcoast/FreeportFL_RGB8_2004_124/index.html
https://noaa-nos-coastal-lidar-pds.s3.us-east-1.amazonaws.com/dem/FreeportFL_DEM_2004_135/index.html
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Custom data creation available by contract;
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.