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 metadata record describes the bare-earth hydro-flattened Digital Elevation Model (DEM) for the Western Block of the 2017 Texas Coastal LiDAR project. The Western Block AOI covers approximately 289 square miles, including the cities of Liberty, Hankamer, and Anahuac in southeast Texas. This point cloud AOI was collected to meet the density of 8 points per meter. Total area covers equals approximately 1.130 square miles. The DEM has 50 cm horizontal resolution, is in UTM Zone 15 projection, horizontal datum is the North American Datum of 1983 (NAD83 (2011)), vertical datum is North American Vertical Datum of 1988 (NAVD88) using the latest geoid (Geoid12b) for converting ellipsoidal heights to orthometric heights. Units - Meters
Sanborn Map Company was contracted by Texas Water Development Board (TWDB) in cooperation with the Trinity River Authority (TRA) to perform 2017 LiDAR aerial surveys of Texas coastal area of about 1130 square miles. Collections was completed utilizing multi-return systems, Light Detection and Ranging (LiDAR) data in the form of 3-dimensional positions of a dense set of mass points between February 22nd and March 23rd, 2017. ALS70 LiDAR was flown to produce four (4) points and eight (8) points per square meter return density or 0.5 meters and 0.35 meters respectively Nominal Point Spacing (NPS)
Note, The Eastern Block covers approximately 841 square miles, including the cities of Beaumont, Port Arthur, and Nederland in southeast Texas. This point cloud AOI was collected to meet the density of 4 points per meter. It is linked in the 'Related Items' section, below.
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):
- 2017-01-01 00:00:00 - 8PPM LiDAR data was collected over the West Texas AOI. Multiple returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in ten missions between March 15th and March 23rd, 2017. During the LIDAR campaign, the Sanborn field crew conducted a GPS field survey to establish final coordinates of the ground base stations for final processing of the base-remote GPS solutions. (Citation: LiDAR Data)
- 2017-01-01 00:00:00 - Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a Smoothed Best Estimate of Trajectory (SBET). IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. Airborne GPS is differentially processed using the Inertial Explorer software by Leica Geosystems.
- 2017-01-01 00:00:00 - Leica's CloudPro software then combined the SBET and Raw Laser (.scn) files to produce raw point cloud swath data in LAS v1.4 format.
- 2017-01-01 00:00:00 - The raw swath point cloud data was then calibrated using TerraMatch, a TerraSolid software, to correct relative bias in conjoining swaths that include roll, pitch, heading, Scale, and elevation. The swath data is then compared against the calibration control points and adjusted vertically to exceed the vertical accuracy requirements for the project.
- 2017-01-01 00:00:00 - The georeferenced lidar data is then classified and edited in Terrasolid Terrascan software. Data is classified to produce: Class 1: unclassified, Class 2: ground, Class 3: low veg, Class 4: med veg, Class 5: high veg, Class 6: building, Class 7: low point, Class 9: water, Class 10: ignored ground, Class 13: bridge deck, Class 14: culverts
- The NOAA Office for Coastal Management (OCM) received the files in the proprietary ERDAS IMG format. The files were converted to floating point GeoTIFF format in vertical meters using gdal_translate from GDAL version 3.0.2.
(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
- 5.2. Quality control procedures employed
- 7.1.1. If data are not available or has limitations, has a Waiver been filed?
- 7.4. Approximate delay between data collection and dissemination
- 8.3. Approximate delay between data collection and submission to an archive facility
(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.
Data is available online for bulk or custom downloads
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
Data is backed up to tape and to cloud storage.
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.