Data Management Plan
GUID: gov.noaa.nmfs.inport:50096 | 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
These files contain classified topographic and bathymetric lidar data as unclassified valid topographic data (1) and valid
topographic data classified as ground (2), Classes 1 and 2 are defined in accordance with the American Society for
Photogrammetry and Remote Sensing (ASPRS) classification standards. The data were collected on November 16, 2012 and cover
portions of the following counties:
New Jersey - Bergen, Essex, Hudson, Middlesex, Monmouth, Ocean, Union
New York - Bronx, Kings, Nassau, New York, Queens, Richmond, Suffolk, Westchester
These data were collected by the Coastal Zone Mapping and Imaging Lidar (CZMIL) system. CZMIL integrates a lidar sensor with
topographic and bathymetric capabilities, a digital camera and a hyperspectral imager on a single remote sensing platform
for use in coastal mapping and charting activities. Native lidar data is not generally in a format accessible to most Geographic
Information Systems (GIS). Specialized in-house and commercial software packages are used to process the native lidar data
into 3-dimensional positions that can be imported into GIS software for visualization and further analysis. Horizontal positions,
provided in decimal degrees of latitude and longitude, are referenced to the North American Datum of 1983 (NAD83). Vertical
positions are referenced to the NAD83 ellipsoid and provided in meters. The National Geodetic Survey's (NGS) GEOID12A model
is used to transform the vertical positions from ellipsoid to orthometric heights referenced to the North American Vertical
Datum of 1988 (NAVD88).
For data storage and Digital Coast provisioning purposes, the NOAA Office for Coastal Management converted
the data from orthometric heights referenced to the North American Vertical Datum of 1988 (NAVD88) to ellipsoid heights using
the NGS GEOID12A model.
Original contact information:
Contact Org: JALBTCX
Title: Data Production Manager
Phone: 228-252-1121
Email: JALBTCX@usace.army.mil
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:
- 2012-12-23 00:00:00 - These data were collected using the CZMIL system. It is owned and operated by the U.S. Army Corps of Engineers (USACE). The system collects lidar data at 10 kHz and RGB imagery at 2 Hz. A CASI-1500 hyperspectral line scanner is integrated with the system as well. Aircraft position, velocity and acceleration information are collected through a combination of Novatel and POS A/V 510 equipment. All raw data streams are transferred to the office for downloading and processing in CZMILs Hydro Fusion software. Aircraft position data are processed using POSPac software and the results are combined with the lidar data to produce 3-D positions for each lidar shot. Upon inspection and QA/QC in the software packages Fledermaus and PFM_ABE, anomalous data are flagged as invalid. NOAAs VDatum software then converts all valid data from ellipsoid to orthometric heights based on the NGS' GEOID12A model and exports valid lidar data as a series of unclassified ascii xyz files.
- The flightline LAS files are imported into GeoCue [V2012], which is a geospatial workflow production and management software tool employed by JALBTCX to perform and monitor production of data products. Upon import into GeoCue, the flightline LAS files are divided into a series of boxes, each of which are 1500 meters in length and width. A customized classification macro, built upon the TerraScan [V12] module within Microstation V8i, classifies valid topographic data as ground points (2) and unclassified points (1). Upon completion the macro, the classification results undergo quality control and any misclassified points are manually edited. In areas of dense vegetation the bare earth ground points might be incorrectly classified due to the inability of the laser to penetrate the canopy and reach the bare ground. In these areas, JALBTCX defaults to the algorithms ground surface instead of manually reclassifying those points. The final classification results are comprised of individual lidar points with classifications of ground (2) or unclassified (1). They are partitioned into a series of USGS quarter quad delivery boxes, one Classified LAS file per box. The format of the file is LAS version [1.2]. Data are classified as 1 (valid non-ground topographic data), 2 (valid ground topographic data).
- 2013-04-01 00:00:00 - The NOAA Office for Coastal Management (OCM) received the files in LAS v1.2 format. The files contained lidar elevation and intensity measurements. The data were received in geographic coordinates (NAD83) and vertically referenced to NAVD88 using the Geoid12A model. The vertical units were meters. The data were classified according to ASPRS LAS classification scheme (1 = unclassified, 2 = ground). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The las files were converted from orthometric (NAVD88) heights to ellipsoidal heights using Geoid12A.
(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://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2478/index.html
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:
https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2478
;
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.