Hurricane Matthew Assessment of Potential Coastal Change Impacts: NHC Advisory 037, 800 AM EDT FRI OCT 07 2016

Metadata also available as - [Outline] - [Parseable text] - [XML]

Frequently anticipated questions:

What does this data set describe?

Title:
Hurricane Matthew Assessment of Potential Coastal Change Impacts: NHC Advisory 037, 800 AM EDT FRI OCT 07 2016
Abstract:
This dataset defines storm-induced coastal erosion hazards for the Florida, Georgia, South Carolina and North Carolina coastline. The analysis was based on a storm-impact scaling model that used observations of beach morphology combined with sophisticated hydrodynamic models to predict how the coast would respond to the direct landfall of Hurricane Matthew in October 2016. Storm-induced water levels, due to both surge and waves, were compared to beach and dune elevations to determine the probabilities of the three types of coastal change: collision (dune erosion), overwash, and inundation. All hydrodynamic and morphologic variables are included in this dataset.
  1. How might this data set be cited?
    Birchler, Justin J., Doran, Kara S., Stockdon, Hilary F., and Schreppel, Heather A., 20190619, Hurricane Matthew Assessment of Potential Coastal Change Impacts: NHC Advisory 037, 800 AM EDT FRI OCT 07 2016: U.S. Geological Survey Data Release doi:10.5066/P9Z362BC, U.S. Geological Survey, St. Petersburg, FL.

    Online Links:

    This is part of the following larger work.

    U.S. Geological Survey, 2019, USGS Coastal Change Hazards Portal.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -81.459
    East_Bounding_Coordinate: -75.4759
    North_Bounding_Coordinate: 35.5018
    South_Bounding_Coordinate: 25.7599
  3. What does it look like?
  4. Does the data set describe conditions during a particular time period?
    Calendar_Date: 07-Oct-2016
    Currentness_Reference:
    ground condition
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: vector digital data
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a Vector data set. It contains the following vector data types (SDTS terminology):
      • String (1488)
    2. What coordinate system is used to represent geographic features?
      Horizontal positions are specified in geographic coordinates, that is, latitude and longitude. Latitudes are given to the nearest 0.0197863028. Longitudes are given to the nearest 0.0228701634. Latitude and longitude values are specified in Decimal Degrees. The horizontal datum used is D_WGS_1984.
      The ellipsoid used is WGS_1984.
      The semi-major axis of the ellipsoid used is 6378137.0.
      The flattening of the ellipsoid used is 1/298.257223563.
  7. How does the data set describe geographic features?
    Matthew_PCOI_line
    Probabilities of hurricane-induced coastal erosion, dune morphology, and hurricane hydrodynamic data (Source: USGS)
    FID
    Internal feature number. (Source: Esri) Sequential unique whole numbers that are automatically generated.
    Shape
    Feature geometry. (Source: ESRI) Coordinates defining the features.
    DHIGH
    Elevation of dune crest, in meters, using the North American Vertical Datum of 1988 (NAVD88). Extracted from lidar surveys collected from August 2009 to July 2014. (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:1.7105
    Maximum:9.468
    Units:meters NAVD88
    DLOW
    Elevation of the dune toe, in meters NAVD88. Extracted from lidar surveys collected August 2009 to July 2014. (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:1.0386
    Maximum:4.8546
    Units:meters NAVD88
    DHIrms
    Root mean squared error of dune crest elevation measurements (square meters). (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0.232370
    Maximum:1.845242
    Units:square meters
    DLOrms
    Root mean square error of dune toe elevation measurements (square meters). (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0.082870
    Maximum:1.200408
    Units:square meters
    SURGE
    Storm surge water level (Source: NOAA)
    Range of values
    Minimum:0.46195
    Maximum:3.3544
    Units:meters NAVD88
    RUNUP
    Wave runup water level (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0.81433
    Maximum:5.9195
    Units:meters NAVD88
    SETUP
    Wave setup water level (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0.068096
    Maximum:2.4385
    Units:meters NAVD88
    PCOL
    Probability of collision (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:6.8908
    Maximum:100
    Units:percent
    POVW
    Probability of overwash (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0
    Maximum:100
    Units:percent
    PIND
    Probability of inundation (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0
    Maximum:99.9998
    Units:percent
    MEAN
    Mean water level (surge + setup) (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:0.66958
    Maximum:5.5226
    Units:meters NAVD88
    EXTREME
    Extreme water level (surge + runup). (Source: USGS)
    ValueDefinition
    -999Null value
    Range of values
    Minimum:1.3023
    Maximum:9.0036
    Units:meters NAVD88
    TIDE
    Predicted tide water level (Source: USGS)
    Range of values
    Minimum:0
    Maximum:0
    Units:meters NAVD88

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Justin J. Birchler
    • Kara S. Doran
    • Hilary F. Stockdon
    • Heather A. Schreppel
  2. Who also contributed to the data set?
    The predicted elevations of storm surge were extracted from the National Oceanic and Atmospheric Administration’s (NOAA) Sea, Lake, and Overland Surges from Hurricanes (SLOSH) model, which has been employed by NOAA in inundation risk studies and operational storm surge forecasting. Wave runup and setup conditions were generated using NOAA's WaveWatch III model.
  3. To whom should users address questions about the data?
    U.S. Geological Survey
    Attn: Hilary Stockdon
    600 4th Street South
    Saint Petersburg, FL
    UNITED STATES

    727-502-8074 (voice)
    727-502-8182 (FAX)
    hstockdon@usgs.gov

Why was the data set created?

To provide data on the probability of storm-induced coastal erosion hazards for the Florida, Georgia, South Carolina and North Carolina coast post-Hurricane Matthew.

How was the data set created?

  1. From what previous works were the data drawn?
    Psurge (source 1 of 5)
    National Hurricane Center, National Oceanic and Atmospheric Administration, 20161007, Probabalistic Storm Surge.

    Online Links:

    Type_of_Source_Media: Online digital data
    Source_Contribution:
    Data provides water levels that have a 1 in 10 chance of being exceeded during the next 3 days.
    WW3 (source 2 of 5)
    NOAA National Weather Service Environmental Modeling Center, 20161007, NOAA Wavewatch III.

    Online Links:

    Type_of_Source_Media: Online digital data
    Source_Contribution:
    Model that was used to estimate wave setup and runup conditions for Hurricane Matthew.
    USACE South Florida 2009 (source 3 of 5)
    U.S. Army Corps of Engineers (USACE), 201109, 2009 USACE Topo/Bathy lidar: East Coast of Florida.

    Online Links:

    Other_Citation_Details: Geographic Coverage: FL (Key Biscayne to Melbourne)
    Type_of_Source_Media: Online digital data
    Source_Contribution:
    A lidar survey that was used to estimate dune morphology variables.
    USACE Southeast 2010 (source 4 of 5)
    USACE, 20141114, 2010 USACE Lidar: Southeast Atlantic Coast.

    Online Links:

    Other_Citation_Details:
    Geographic Coverage: FL (Melbourne to FL/GA border), GA, SC (GA/SC border to Winyah Bay)
    Type_of_Source_Media: Online digital data
    Source_Contribution:
    A lidar survey that was used to estimate dune morphology variables.
    NOAA 2014 SC-NY (source 5 of 5)
    Department of Commerce (DOC), National Oceanic and Atmospheric Administration (NOAA), National Ocean Service (NOS), National Geodetic Survey (NGS), Remote Sensing Division, 20160523, 2014 NOAA Post Hurricane Sandy Topobathymetric LiDAR Mapping for Shoreline Mapping.

    Online Links:

    Other_Citation_Details:
    Geographic Coverage: SC (Winyah Bay to SC/NC border), NC, VA, MD, DE, NJ, NY
    Type_of_Source_Media: Online digital data
    Source_Contribution:
    A lidar survey that was used to estimate dune morphology variables.
  2. How were the data generated, processed, and modified?
    Date: 2016 (process 1 of 4)
    Process_Description: For dune morphology data: Elevation data from lidar surveys were interpolated in MATLAB (version 2017a) to a gridded domain that was rotated parallel to the shoreline and had a resolution of 10 m in the longshore direction and 2.5 m in the cross-shore direction. The interpolation method applied spatial filtering with a Hanning window that was twice as wide as the grid resolution. Dune morphology data were extracted from the elevation grid in MATLAB. Dune morphology data were then summarized to 1 km sections. Sections with greater than 75 percent of data missing were flagged with the invalid number of -999. The 1-km smoothed dune crest (DHIGH), toe (DLOW) and root mean square (RMS) error for each (DHIrms and DLOrms) were written to line shapefiles using MATLAB's shapewrite.m script. Person who carried out this activity:
    U.S. Geological Survey
    Attn: Justin Birchler
    600 4th Street South
    Saint Petersburg, FL
    UNITED STATES

    727-502-8019 (voice)
    727-502-8182 (FAX)
    jbirchler@usgs.gov
    Data sources used in this process:
    • USACE South Florida 2009
    • USACE Southeast 2010
    • NOAA 2014 SC-NY
    Data sources produced in this process:
    • Dune morphology (DHIGH, DLOW, DHIrms, DLOrms)
    Date: 07-Oct-2016 (process 2 of 4)
    For hydrodynamic data: Water level was computed in MATLAB by adding storm surge from NOAA’s Probabilistic Tropical Storm Surge (P- Surge) model (https://slosh.nws.noaa.gov/psurge2.0/) to wave setup and runup. The wave height and period used for calculating wave runup and setup came from the Wavewatch III model. Hydrodynamic parameters were calculated in MATLAB and exported into ArcGIS shapefile format. For details on modeling parameterization, see: Stockdon, H.F., Doran, K.J., Thompson, D.M., Sopkin, K.L., Plant, N.G., and Sallenger, A.H., 2012, National assessment of hurricane-induced coastal erosion hazards: Gulf of Mexico: U.S. Geological Survey Open-File Report 2012-1084, 51 p. https://pubs.usgs.gov/of/2012/1084/ Person who carried out this activity:
    U.S. Geological Survey
    Attn: Justin Birchler
    600 4th Street South
    Saint Petersburg, FL
    UNITED STATES

    727-502-8019 (voice)
    727-502-8182 (FAX)
    jbirchler@usgs.gov
    Data sources used in this process:
    • Psurge
    • WW3
    Data sources produced in this process:
    • Hydrodynamics (SURGE, SETUP, RUNUP)
    Date: 07-Oct-2016 (process 3 of 4)
    Probabilities of coastal erosion hazards were based on estimating the likelihood that the beach system would experience erosion and deposition patterns consistent with collision (PCOL), overwash (POVW), or inundation (PIND) regimes. The regimes were calculated by using values of dune morphology and mean and extreme water levels for each 1 km section, such that the probability of collision (PCOL) occurs when extreme water levels reach the dune toe; overwash (POVW) when extreme water levels reach the dune crest; and inundation (PIND) when mean water levels reach the dune crest. Probabilities were calculated in MATLAB and exported using MATLAB's shapewrite.m script. For details on modeling parameterization, see: Stockdon, H.F., Doran, K.J., Thompson, D.M., Sopkin, K.L., Plant, N.G., and Sallenger, A.H., 2012, National assessment of hurricane-induced coastal erosion hazards: Gulf of Mexico: U.S. Geological Survey Open-File Report 2012-1084, 51 p. https://pubs.usgs.gov/of/2012/1084/ Person who carried out this activity:
    U.S. Geological Survey
    Attn: Justin Birchler
    600 4th Street South
    Saint Petersburg, FL
    UNITED STATES

    727-502-8019 (voice)
    727-502-8182 (FAX)
    jbirchler@usgs.gov
    Data sources used in this process:
    • Dune morphology
    • Hydrodynamics
    Data sources produced in this process:
    • Probabilities (PCOL, POVW, PIND)
    Date: 13-Oct-2020 (process 4 of 4)
    Added keywords section with USGS persistent identifier as theme keyword. Person who carried out this activity:
    U.S. Geological Survey
    Attn: VeeAnn A. Cross
    Marine Geologist
    384 Woods Hole Road
    Woods Hole, MA

    508-548-8700 x2251 (voice)
    508-457-2310 (FAX)
    vatnipp@usgs.gov
  3. What similar or related data should the user be aware of?

How reliable are the data; what problems remain in the data set?

  1. How well have the observations been checked?
  2. How accurate are the geographic locations?
    Horizontal accuracy was not estimated.
  3. How accurate are the heights or depths?
    Vertical accuracy for hydrodynamic measurements (surge, setup, and runup) is dependent on input data. SLOSH model accuracy is estimated to be +/- 20 percent of the calculated value. No other accuracy checks were performed. Vertical accuracy for dune morphology (dune crest and toe elevation) data is dependent on the positional accuracy of the lidar data. Estimated accuracy of lidar surveys are +/- 15 centimeters. However, vertical accuracies may vary based on the type of terrain (for example, inaccuracies may increase as slope increases or with the presence of extremely dense vegetation), the accuracy of the global positioning system (GPS), and aircraft-attitude measurements.
  4. Where are the gaps in the data? What is missing?
    This dataset includes dune morphology and hurricane hydrodynamic data used to generate probabilities of hurricane-induced erosion, elevation data from lidar surveys are not included. Measurements were collected approximately every 10 meters (m) and summarized to 1-kilometer (km) segments.
  5. How consistent are the relationships among the observations, including topology?
    No additional checks for consistency were performed on this data.

How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?
Access_Constraints: None
Use_Constraints:
Public domain data from the U.S. Government are freely redistributable with proper metadata and source attribution. The U.S. Geological Survey requests to be acknowledged as originators of the data in future products or derivative research.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey
    Attn: Justin Birchler
    600 4th Street South
    Saint Petersburg, FL

    727-502-8019 (voice)
    727-502-8182 (FAX)
    jbirchler@usgs.gov
  2. What's the catalog number I need to order this data set?
  3. What legal disclaimers am I supposed to read?
    Although these data have been processed successfully on a computer system at the USGS, no warranty expressed or implied is made regarding the display or utility of the data on any other system, or for general or scientific purposes, nor shall the act of distribution constitute any such warranty. The USGS shall not be held liable for improper or incorrect use of the data described and/or contained herein. Any use of trade, firm, or product names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  4. How can I download or order the data?

Who wrote the metadata?

Dates:
Last modified: 13-Oct-2020
Metadata author:
U.S. Geological Survey
Attn: Justin Birchler
600 4th Street South
Saint Petersburg, FL
UNITED STATES

727-502-8019 (voice)
727-502-8182 (FAX)
jbirchler@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)
This page is <https://cmgds.marine.usgs.gov/catalog/spcmsc/Matthew_PCOI_line_metadata.faq.html>
Generated by mp version 2.9.50 on Tue Sep 21 18:18:51 2021