Data Management Plan
GUID: gov.noaa.nmfs.inport:50121 | 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 elevation data derived from a lidar survey approximately 300m wide of the Gulf of Mexico shoreline in the
Northeast Lake Como quarter-quadrangle on Galveston Island Texas. The geographic extent of the data set is equivalent to the
quarter-quadrangle plus 30 meters of overedge. The data is created by combining data collected using an Optech Inc. Airborne Laser
Terrain Mapper (ALTM) 1225 in combination with geodetic quality Global Positioning System (GPS) airborne and ground-based receivers.
The Bureau of Economic Geology, the University of Texas at Austin owns and operates an ALTM 1225 system (serial number 99d118).
This system is installed in a single engine Cessna 206 (tail number N4589U) owned and operated by the Texas State Aircraft Pooling
Board. The lidar data described by this document was collected on 18 September 2002 (26102) between 20:34 and 00:08 UTC
(actual data collection). Conditions on that day were low clouds at 335m Above Ground Level (AGL), haze, and occasional showers.
99d118 instrument settings for this flight were; laser pulse rate: 25kHz, scanner rate: 26Hz, scan angle: +/-20deg, beam divergence:
wide, altitude: 300-490m AGL, and ground speed: 70-106kts. Three GPS base stations, 2 Ashtech and 1 Trimble 4000SSI receivers (backup),
were operating during the survey. The three base stations were at the following locations: one 3.5km south of San Luis Pass, one at the
Scholes International Airport Galveston, and one on the seawall at Rollover Pass. This data set consists of 1687100 records of x,y,
and z values. The data set was generated from a larger data set and includes all valid points within the requested geographic bounds.
Original contact information:
Contact Name: Jim Gibeaut
Contact Org: Bureau of Economic Geology University of Texas at Austin
Title: Research Associate
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):
- 2002-09-18 00:00:00 - Transfer raw ALTM 1225 flight data, airborne GPS data collected at 1 Hz using Ashtech receiver, and ground-based GPS data collected at 1 Hz using Ashtech and Trimble 4000SSI receivers to NT workstation. Generate decimated lidar point file from above three data sets using Optech's Realm 2.27 software. This is a 9-column ASCII data set with the following format: time tag; first pulse Easting, Northing, HAE; last pulse Easting, Northing, HAE; first pulse intensity; and last pulse intensity. View decimated lidar point file to check data coverage (i.e. sufficient overlap of flight lines and point spacing). Compute base station coordinates using National Geodetic Survey's PAGES software. Computed aircraft trajectories for both base stations using National Geodetic Survey's KINPOS software. Coordinates for base stations and trajectories are in the International Terrestrial Reference Frame of 2000 (ITRF2000) datum. Trajectories from both base stations were merged into one. Weighting for trajectory merge is based upon baseline length (distance from base station) and solution RMS. Transformed trajectory solution from ITRF2000 to North American Datum of 1983 (NAD83). Use NAD83 trajectories and aircraft inertial measurement unit data in Applanix's POSProc version 2.1.4 to compute an optimal 50Hz inertial navigation solution. Substitute the aircraft position and attitude information from the inertial navigation solution into Realm 2.27. Extract calibration area data set from lidar point file for quality control and instrument calibration checks. If necessary, use multiple iterations to adjust calibration parameters (pitch, roll, and scale) and reprocess sample data set. Then generate entire lidar point file (9-column ASCII file). Transfer point file from NT workstation to UNIX workstation. Parse the 9-column lidar point file into 3.75-minute quarter-quadrangle components and apply elevation bias correction (determined during calibration step). There are some points in the file that only contain 5-columns. These are points that either the first or last pulse was not recorded. Processing occurred 20020918-20030211.
- 2003-02-24 00:00:00 - The 9-column post-processed data from University of Texas were provided in UTM projection (Zone 15) referenced to NAD83 with vertical elevations in meters referenced to the Geodetic Reference System 80 (GRS80) ellipsoid. The xyz values for the last return were extracted from the 9-column file. The data were converted to geographic coordinates using General Cartographic Transformation Program software developed by the United States Geological Survey. A vertical datum transformation was performed to convert vertical elevations referenced to GRS80 ellipsoid to NAVD88 using National Geodetic Survey (NGS) GEOID99 grids. The data were then converted to a binary format and loaded into the LIDAR Data Retrieval Tool (LDART) database.
(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.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.
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.
This data can be obtained on-line at the following URL:
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.