Data Management Plan (Deprecated)
GUID: gov.noaa.nmfs.inport:49864 | Published / External
This is an outdated version of the NOAA Data Management Plan template. InPort now supports a dedicated Data Management Plan Catalog Item type, which is up-to-date with the latest NOAA DMP template. The ability to generate Data Management Plans from Data Sets will be discontinued in a future release. Please see the Data Management Plan Help Guide to learn more.
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
In February 2014, Quantum Spatial, Inc. (QSI) was contracted by the New Jersey Meadowlands Commission (NJMC) to collect Light Detection and Ranging (LiDAR) data in the spring of 2014 for the Hackensack Meadowlands site in New Jersey
Original contact information:
Contact Org: NJ Sports and Exposition Authority (NJSEA)
Title: GIS Program Administrator
Phone: 202-423-5089
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:
- 2014-04-01 00:00:00 - In preparation for data collection, QSI reviewed the project area and developed a specialized flight plan to ensure complete coverage of the Hackensack Meadowlands LiDAR study area at the target point density of equal-to-less-than 8.0 points/m2 (0.74 points/ft2). Acquisition parameters including orientation relative to terrain, flight altitude, pulse rate, scan angle, and ground speed were adapted in order to optimize flight paths and flight times while meeting all contract specifications. Factors such as satellite constellation availability and weather windows must be considered during the planning stage. Logistical considerations including private property access and potential air space restrictions were reviewed. Water levels and tidal conditions along the Hackensack River and surrounding Meadowlands were monitored to ensure airborne acquisition was completed during tidal periods below predicted Mean Sea Level (MSL). Any weather hazards or conditions affecting the flight were continuously monitored due to their potential impact on the daily success of airborne and ground operations
- 2014-04-01 00:00:00 - The Hackensack Meadowlands LiDAR survey was accomplished using a Leica ALS50 phase II system mounted in a Cessna Caravan. Table 3 summarizes the settings used to yield an average pulse density of less than 8.0 pulses/m2 (0.74 pulses/ft2) over the Hackensack Meadowlands project area. The Leica laser system records up to four range measurements (returns) per pulse. It is not uncommon for some types of surfaces (e.g., dense vegetation or water) to return fewer pulses to the LiDAR sensor than the laser originally emitted. The discrepancy between first return and overall delivered density will vary depending on terrain, land cover, and the prevalence of water bodies. All discernible laser returns were processed for the output dataset.
- 2014-07-01 00:00:00 - 1. Resolve kinematic corrections for aircraft position data using kinematic aircraft GPS and static ground GPS data. Develop a smoothed best estimate of trajectory (SBET) file that blends post-processed aircraft position with sensor head position and attitude recorded throughout the survey. 2. Calculate laser point position by associating SBET position to each laser point return time, scan angle, intensity, etc. Create raw laser point cloud data for the entire survey in *.las (ASPRS v. 1.3) format. Convert data to orthometric elevations by applying a geoid12a correction. 3. Import raw laser points into manageable blocks (less than 500 MB) to perform manual relative accuracy calibration and filter erroneous points. Classify ground points for individual flight lines. 4. Using ground classified points per each flight line, test the relative accuracy. Perform automated line-to-line calibrations for system attitude parameters (pitch, roll, heading), mirror flex (scale) and GPS/IMU drift. Calculate calibrations on ground classified points from paired flight lines and apply results to all points in a flight line. Use every flight line for relative accuracy calibration. 5. Classify resulting data to ground and other client designated ASPRS classifications. Assess statistical absolute accuracy via direct comparisons of ground classified points to ground control survey data. 6. Generate bare earth models as triangulated surfaces. Generate highest hit models as a surface expression of all classified points. Export all surface models as ESRI GRIDs in EDRAS Imagine (.img) format at a 2.0 foot pixel resolution. 7. Correct intensity values for variability and export intensity images as GeoTIFFs at a 2.0 foot pixel resolution.
- 2015-12-10 00:00:00 - The NOAA Office for Coastal Management (OCM) received LAS point clouds from the New Jersey Office of Information Technology in February 2015. The files contained lidar elevation and intensity measurements. The data were in New Jersey State Plane coordinates (ft) and orthometric elevations (ft). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. LAS files were compressed to LAZ format using laszip. 2. LAS files were voided of points below -25 m and as assumed to be error. 3. LAS points were converted to adjusted GPS time. 4. LAS files were transformed from New Jersey State Plane horizontal coordinates (ft) and NAVD88 orthometric vertical heights (ft) to geographic coordinates (decimal degrees) and ellipsoidal heights (meters).
(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/4983/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=4983
The 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.