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 County of Cecil Maryland requested delivery of three dimensional classified point cloud and contour data derived from LiDAR(Light Detection and Ranging) technology for the entirety of Cecil County, MD. Remotely sensed, geographically referenced elevation measurements were collected by Axis Geospatial, LLC using airborne LiDAR sensors.
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):
- 2013-02-14 00:00:00 - Using a Trimble Harrier 68i High Definition LiDAR sensor on board a Cessna 206, 191 flight lines of high-density data were collected during 15 separate missions, flown as close together as the weather conditions permitted, to ensure consistent ground conditions across the project area, at a nominal pulse spacing (NPS) of 0.46 m achieved a point density of 4.73 ppm2, were collected by Axis Geospatial, LLC covering Cecil County, MD (approximately 473 square miles). Data Acquisition Height = 2,034 feet Above Ground Level (AGL) - Aircraft Speed = 116 Knots. Multiple returns were recorded for each laser pulse along with an intensity value for each return. A total of 15 missions were flown from December 20, 2013 to January 20, 2014. The presence of a strong CORS (Continuously Operating Reference Station) configuration allowed for the LiDAR to be acquired with Global Navigation Satellite System (GNSS) techniques and procedures. 58 ground control points were surveyed through RTK and static methods. The GEOID used to reduce satellite-derived elevations to orthometric heights was GEOID12A. Data for the task order is referenced to the Maryland State Plane, North American Datum of 1983 (NAD83), and North American Vertical Datum of 1988 (NAVD88), in US Survey Feet. Airborne GPS data was differentially processed and integrated with the post-processed inertial measurement unit (IMU) data to derive a smoothed best estimate of trajectory (SBET). The SBET was used to reduce the lidar slant range measurements to a raw reflective surface for each flight line. The coverage was classified to extract a bare earth digital elevation model (DEM) and separate last returns.
- 2013-02-14 00:00:00 - During the project data acquisition by Axis Geospatial, LLC, East-West cross flights were flown over each of the 6 delivery block areas in order to tie the data together from multi-day North-South collections.
- 2013-02-14 00:00:00 - Once the data acquisition and GPS processing phases are complete, the lidar data were processed immediately by Axis Geospatial, LLC to verify the coverage had no voids. The GPS and IMU data were post-processed using ApplanixPOSPac v.6.1 software to derive a best estimate of trajectory. The quality of the solution was verified to be consistent with the accuracy requirements of the project.
- 2014-12-31 00:00:00 - The individual flight lines were inspected by Axis Geospatial, LLC to ensure the systematic and residual errors have been identified and removed. Then, the flight lines were compared to adjacent flight lines for any mismatches to obtain a homogenous coverage throughout the project area. Axis Geospatial, LLC compared LiDAR intensity values against known control point locations that were on defineable features such as the end of a paint line and measured the apparent offsets; these values were then averaged to come up with the X and Y values used for the horizontal correction. Additionally Axis Geospatial, LLC compared a TIN (Triangulated Irregular Network) of LiDAR points within 25 feet of each surveyed control point and measured the apparent vertical offsets; these values were then averaged to come up with the Z value used for the vertical correction. Next the point cloud underwent a classification process to determine bare-earth points and non-ground points utilizing TerraSolid, TerraScanLiDAR processing and modeling software. v. 014.013. This process determined Default (Class 1), Ground (Class 2), and Noise (Class 7), classifications. The bare-earth (Class 2 - Ground) lidar points underwent a manual QA/QC step to verify that artifacts have been removed from the bare-earth surface. The surveyed ground control points are used to perform the accuracy checks and statistical analysis of the lidar dataset.
- 2014-12-31 00:00:00 - Applanix software (PosPAC MMS) was used in the post processing of the airborne GPS and inertial data, which are critical to the positioning and orientation of the sensor during all flights. POSPac MMS provides the smoothed best estimate of trajectory (SBET) that is necessary for the post processor to develop the point cloud from the lidar missions. The point cloud is the mathematical three-dimensional collection of all returns from all laser pulses as determined from the aerial mission. The GEOID used to reduce satellite derived elevations to orthometric heights was GEOID12A. Data for the task order is referenced to the Maryland State Plane, NAD83, and NAVD88, in US Survey Feet. At this point the data are 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. The point cloud was manipulated by the Trimble LPMaster software; GeoCue, TerraScan, and TerraModeler software were used for the automated data classification, manual cleanup, and bare-earth generation from the data. Project specific macros were used to classify the ground. All data were manually reviewed and any remaining artifacts removed using functionality provided by TerraScan and TerraModeler. Data were then run through additional macros to ensure deliverable classification levels matching the ASPRS LAS Version 1.2 Classification structure. GeoCue functionality was then used to ensure correct LAS Versioning. In-house software was used as a final QA/QC check to provide LAS Analysis of the delivered tiles. QA/QC checks were performed on a per tile level to verify final classification metrics and full LAS header information. Axis Geospatial, LLC located a total of 58 check points for use in the analysis of the lidar data quality. The points were located on relatively flat terrain on surfaces that generally consisted of grass, gravel, or bare earth. The final vertical accuracy (RMSEz x 1.96) of the following landcover types were tested; Bare Earth-FVA (Fundamental Vertical Accuracy), CVA (Consolidated Vertical Accuracy), Crop/Weeds SVA (Supplemental Vertical Accuracy), and Wooded SVA (Supplemental Vertical Accuracy). The final results for FVA (based on 24 points) was found to be 0.17 feet; SVA Crop/Weeds (based on 10 points) was found to be 0.27 feet; and SVA Woods (based on 24 points) was found to be 0.52 feet. The CVA was found to be .37 feet.
- 2018-03-08 00:00:00 - NOAA OCM downloaded the data from Maryland iMap (imap.maryland.gov) in October 2017. Data were converted from Maryland State Plane (1900) with NAVD88 (geoid12a) vertical feet to geographic coordinates with height above the ellipsoid in vertical meters. Data were ingested into the Digital Coast Data Access Viewer for custom distribution.
(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.
Notes: All URLs listed in the Distribution Info section will be included. This field is required if applicable.
Data is available online for 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
9. Additional Line Office or Staff Office Questions
Line and Staff Offices may extend this template by inserting additional questions in this section.