Data Management Plan
GUID: gov.noaa.nmfs.inport:49697 | 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
SWFWMD regularly uses digital topographic information to support regulatory, land management and acquisition, planning, engineering and habitat restoration projects. LiDAR data will support hydrologic modeling activities associated with the FederalEmergency Management Agency (FEMA), and in the creation of Digital Flood Insurance Rate Maps(DFIRM). The LiDAR data will support the creation of Federal Emergency Management AgencyFlood Insurance Rate Maps (FEMA FIRM) and an integrated ground and surface water model for thePeace River watershed. The data were classified into 7 classifications; (1) unclassified, (2) ground, (6) buildings, (9) water, (11) wetlands (reclassed by OCM to 18), (13) bridges (reclassed by OCM to 15), and (20) buffer points (reclassed by OCM to 10).
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:
- 2009-01-01 00:00:00 - LIDAR data were collected using Merrick's ALS50 Phase 2 sensor. The raw data were verified in MARS software for complete coverage of the project area, and boresighted to align the flightlines. Raw data files were parsed into manageable client-specific tiles. These tiles were then processed through automated filtering to separate the data into different classification groups: unclassified points, ground points, low points and water. The data were next taken into Merrick Advanced Remote Sensing (MARS) to reclassify the erroneous points that may remain in the LIDAR point cloud after auto filter. The building and bridge lidar points were manually re-classified based off of imagery and creating profiles using MARS. The buffer points (class 20) were reclassified using a x/y filter in MARS (any ground points within 5 feet of a break line point were classified as class 20)..
- 2009-01-01 00:00:00 - Breaklines were created utilizing MARS software and imagery supplied from SWFWMD (LIDARmetric techniques).
- 2014-09-24 00:00:00 - The NOAA Office for Coastal Management (OCM) received the topographic lidar files in LAS format from SWFWMD. The files contained lidar easting, northing, elevation, intensity, return number, etc. The data was received in Florida State Plane West 0902 (US ft) and NAVD88 (US ft). OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The files were reviewed and erroneous elevations were removed. 2. Class 11 points (wetland) were reclassified to Class 18 (as needed) to fit OCM DAV class scheme. 3. Class 13 points (bridges) were reclassified to Class 15 (as needed) to fit OCM DAV class scheme. 4. Class 20 points (reserved for ASPRS definition) were reclassified to Class 10 (ground within 10 ft of a breakline) to fit OCM DAV class scheme.
(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.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/3691/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=3691;
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.