Data Management Plan
Office for Coastal Management
Data Set (DS) | Cat ID: 48219 | 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
The United States Virgin Islands Topographic LiDAR project collected topographic elevation point data derived from multiple return light detection and ranging (LiDAR) measurements on the islands of St. Thomas, St. John, St. Croix and numerous smaller islands and islets in the United States Virgin Islands. The islands of St. Thomas and St. John were acquired between November 9, 2013 and November 19, 2013. The island of St. Croix was acquired between November 27, 2013 and December 10, 2013. The entire area was comprised of 88 planned flight lines and approximately 1669 flight line kilometers. LiDAR was collected at an average of 0.7 meter point spacing for all acquired project areas. The classification classes as available from the NOAA Digital Coast are: 1 (Unclassified), 2 (Bare-earth ground), 7 (Noise), 9 (Water), 10 (Ignored Ground, points close to breakline features), 16 (Overlap Water), 17 (Overlap Unclassified), 18 (Overlap Bare-earth ground). Hydro flattened breaklines and Digital Elevation Models (DEMs) are also available for download. Please see the Supplemental Information field below for links to these data sets.
Original contact information:
Contact Org: NOAA Office for Coastal Management
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)
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.
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):
- 2014-01-01 00:00:00 - Applanix + POSPac Mobile Mapping Suite software was used for post-processing of airborne GPS and inertial data (IMU), which is critical to the positioning and orientation of the LiDAR sensor during all flights. POSPac combines aircraft raw trajectory data with stationary GPS base station data yielding a Smoothed Best Estimate Trajectory (SBET) necessary for additional post processing software to develop the resulting geo-referenced point cloud from the LiDAR missions. During the sensor trajectory processing (combining GPS and IMU datasets) certain statistical graphs and tables are generated within the Applanix POSPac processing environment which are commonly used as indicators of processing stability and accuracy. This data for analysis include: Max horizontal / vertical GPS variance, separation plot, altitude plot, PDOP plot, base station baseline length, processing mode, number of satellite vehicles, and mission trajectory. The generated point cloud is the mathematical three dimensional composite of all returns from all laser pulses as determined from the aerial mission. Point clouds were created using the Leica ALS Post Processor software. Laser point data are imported into TerraScan and a manual calibration is performed to assess the system offsets for pitch, roll, heading and scale. At this point this data is ready for analysis, classification, and filtering to generate a bare earth surface model in which the above-ground features are removed from the data set. GeoCue distributive processing software was used in the creation of some files needed in downstream processing, as well as in the tiling of the dataset into more manageable file sizes. TerraScan and TerraModeler software packages were then used for the automated data classification, manual cleanup, and bare earth generation. Project specific macros were developed to classify the ground and remove side overlap between parallel flight lines. The classes used in the dataset are as follows and have the following descriptions: Class 1 (Processed, but Unclassified) These points would be the catch all for points that do not fit any of the other deliverable classes. This would cover things like vegetation, buildings, cars, bridges, etc. Class 2 (Bare earth ground) This is the bare earth surface Class 7 (Noise) Low or high points, manually and/or automatically identified above or below the surface that could be noise points in point cloud. Class 9 (Water) Points found inside of inland lake/ponds, rivers or points on the ocean side of any shoreline feature. Class 10 (Ignored Ground) Points found to be close to breakline features. Points are typically moved to this class from Class 2. This class is ignored during the DEM creation. Class 17 (Overlap Default (Unclassified)) Points found in the overlap between flight lines. These points are created through automated processing methods and are not cleaned up during manual classification. Class 18 (Overlap Bare earth ground) Points found in the overlap between flight lines. These points are created through automated processing, matching the specifications determined during the automated process, that are close to the Class 2 dataset (when analyzed using height from ground analysis) Class 25 (Overlap Water) Points found in the overlap between flight lines that are located inside hydro features. These points are created through automated processing methods and are not cleaned up during manual classification. (Citation: LiDAR)
- 2014-01-01 00:00:00 - All overlap data was processed through automated functionality provided by TerraScan to classify the overlapping flight line data to approved classes by USGS. The overlap data was classified to Class 17 (Overlap Default) and Class 18 (Overlap Ground). These classes were created through automated processes only and were not verified for classification accuracy. Due to software limitations within TerraScan, these classes were used to trip the withheld bit within various software packages. The bare earth surface is then manually reviewed to ensure correct classification on the Class 2 (Ground) points. After the bare earth surface is finalized; it is then used to generate all hydro-breaklines through heads-up digitization. Class 2 LIDAR was used to create a bare earth surface model. The surface model and LAS intensity were then used to heads-up digitize 2D breaklines of inland streams and rivers as well as the ocean shoreline. Inland Ponds and Lakes of 2 acres or greater were also collected. All ground (ASPRS Class 2) LiDAR data inside of the collected hydro flattening breaklines were then classified to water (ASPRS Class 9) using TerraScan macro functionality. A buffer of 1 meter was also used around each hydro-flattened feature to classify these ground (ASPRS Class 2) points to Ignored ground (ASPRS Class 10). All Lake Pond Island and Double Line Drain Island features were checked to ensure that the ground (ASPRS Class 2) points were reclassified to the correct classification after the automated classification was completed. LAS data was then run through additional macros to ensure deliverable classification levels matching LAS ASPRS Classification structure. GeoCue functionality was used to ensure correct LAS Version. In house software was used as a final QA/QC check to provide LAS Analysis of the delivered tiles. (Citation: LiDAR)
- 2014-05-13 00:00:00 - The lidar files were received by the NOAA Office for Coastal Management for incorporation into the NOAA Digital Coast. The data consisted of 358 lidar files. The data were in LAS format 1.2 and were in UTM, Zone 20, NAD83, meters coordinates. The data were in Virgin Islands Vertical Datum (VIVD09), meters vertical units. The classifications of the data were: 1 (Unclassified), 2 (Ground), 7 (Noise), 9 (Water), 10 (Ignored Ground, breakline proximity), 17 (Overlap Unclassified), 18 (Overlap Ground), 25 (Overlap Water). For Digital Coast data storage and provisioning purposes, the NOAA OCM performed the following processing: 1. The data were reviewed for any elevation outliers. 2. The data were converted from UTM, Zone 20 coordinates to geographic coordinates. 3. The data were converted from VIVD09 elevations to ellipsoid elevations using Geoid12a. 4. The points that were classified as 25 (Overlap Water) were reclassified to 16 (Overlap Water). 5. The global encoding bit in the las file headers was changed from 0 to 1. 6. The data were converted from las to laz format.
(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.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.
This data can be obtained on-line at the following URL:
This data set is dynamically generated based on user-specified parameters.;
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.