Nearshore water level, tide, and non-tidal residual future projections (2016-2050) for the North and South Carolina coasts

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

Frequently anticipated questions:


What does this data set describe?

Title:
Nearshore water level, tide, and non-tidal residual future projections (2016-2050) for the North and South Carolina coasts
Abstract:
A dataset of modeled nearshore water levels (WLs) was developed for the North and South Carolina coastlines. Water levels, defined for this dataset as the linear sum of tides and non-tidal residuals (NTR), were produced by Muis and others (2016) using a global tide and surge model (GTSM) forced by global atmospheric fields. Water level outputs were extracted from the global grid at approximately 20 km resolution along the southeast Atlantic coastline. These data were then statistically downscaled using a signal-specific set of corrections to improve skill in comparison to tide gauge observations (Parker and others, 2023). Projected water levels were forced by CMIP6 future period data. This dataset provides information on how water levels are expected to change moving towards the future. Four CMIP6 climate models were selected from the High-Resolution Model Intercomparison project (highresMIP; Haarsma and others, 2016) to sample variability in climate predictions.
Supplemental_Information:
This data release was funded by the Additional Supplemental Appropriations for Disaster Relief Act of 2019 (H.R. 2157) for North Carolina and South Carolina. Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government.
  1. How might this data set be cited?
    Parker, Kai A., Erikson, Li H., Thomas, Jennifer A., Nederhoff, Kees, Leijnse, Tim, and Hardy, Matthew W., 20230128, Nearshore water level, tide, and non-tidal residual future projections (2016-2050) for the North and South Carolina coasts: data release DOI:10.5066/P9W91314, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Barnard, Patrick L., Befus, Kevin, Danielson, Jeffrey J., Engelstad, Anita C., Erikson, Li H., Foxgrover, Amy C., Hardy, Matthew W., Hoover, Daniel J., Leijnse, Tim, Massey, Chris, McCall, Robert, Nadal-Caraballo, Norberto, Nederhoff, Kees, Ohenhen, Leonard O., O’Neill, Andrea C., Parker, Kai A., Shirzaei, Manoocher, Su, Xin, Thomas, Jennifer A., Ormondt, Maarten van, Vitousek, Sean F., Vos, Kilian, and Yawn, Madison C., 2023, Future coastal hazards along the U.S. North and South Carolina coasts: data release DOI:10.5066/P9W91314, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -80.903
    East_Bounding_Coordinate: -75.483
    North_Bounding_Coordinate: 36.489
    South_Bounding_Coordinate: 32.065
  3. What does it look like?
    WL_Tide_NTR_CMIP6Fut_StationLocations_NC_SC.jpg (JPEG)
    Map showing output station locations for water levels, tides, and non-tidal residual CMIP6 Future period projections along the coast of North and South Carolina.
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 01-Mar-2020
    Ending_Date: 15-Feb-2023
    Currentness_Reference:
    project start through publication date
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: comma-delimited text
  6. How does the data set represent geographic features?
    1. How are geographic features stored in the data set?
      This is a point data set. It contains the following vector data types (SDTS terminology):
      • point (75475301)
    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.0001. Longitudes are given to the nearest 0.0001. Latitude and longitude values are specified in Decimal degrees. The horizontal datum used is North American Datum of 1983.
      The ellipsoid used is Geodetic Reference System 80.
      The semi-major axis of the ellipsoid used is 6378137.000000.
      The flattening of the ellipsoid used is 1/298.257222.
      Vertical_Coordinate_System_Definition:
      Altitude_System_Definition:
      Altitude_Datum_Name: Mean Sea Level
      Altitude_Resolution: 0.001
      Altitude_Distance_Units: meters
      Altitude_Encoding_Method:
      Explicit elevation coordinate included with horizontal coordinates
  7. How does the data set describe geographic features?
    [WL_Tide_NTR_CMIP6Fut_NUM.csv]
    Combined in one csv file are water levels (WL), tides (tide) and non-tidal residuals (NTR), where NUM in the file name refers to the station ID along the coast (see browse graphic for more details). (Source: Producer defined)
    Year
    Year of projected data (UTC) (Source: Producer defined)
    Range of values
    Minimum:2016
    Maximum:2050
    Units:Year
    Resolution:1
    Month
    Month of projected data (UTC), where 1=January and 12=December (Source: Producer defined)
    Range of values
    Minimum:1
    Maximum:12
    Units:Month
    Resolution:1
    Day
    Day of projected data (UTC) (Source: Producer defined)
    Range of values
    Minimum:1
    Maximum:31
    Units:Day
    Resolution:1
    Hour
    Hour of projected data (UTC) (Source: Producer defined)
    Range of values
    Minimum:0
    Maximum:18
    Units:Hour in 24-hour format
    Resolution:1
    Minute
    Minute of projected data (UTC) (Source: Producer defined)
    Range of values
    Minimum:0
    Maximum:50
    Units:Minute
    Resolution:1
    HadGEM3SST_wl_[m]
    water levels for HadGEM3-GC31-HM-SST future period projections (Source: Producer defined)
    Range of values
    Minimum:-2.324
    Maximum:3.035
    Units:meters
    Resolution:0.001
    CMCC_wl_[m]
    water levels for CMCC future period projections (Source: Producer defined)
    Range of values
    Minimum:-2.108
    Maximum:2.442
    Units:meters
    Resolution:0.001
    GFDL_wl_[m]
    water levels for GFDL future period projections (Source: Producer defined)
    Range of values
    Minimum:-2.074
    Maximum:3.197
    Units:meters
    Resolution:0.001
    EcEarth_wl_[m]
    water levels for EC Earth future period projections (Source: Producer defined)
    Range of values
    Minimum:-2.156
    Maximum:2.725
    Units:meters
    Resolution:0.001
    HadGEM3SST_ntr_[m]
    non-tidal residuals for HadGEM3-GC31-HM future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.997
    Maximum:2.526
    Units:meters
    Resolution:0.001
    CMCC_ntr_[m]
    non-tidal residuals for CMCC future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.606
    Maximum:1.932
    Units:meters
    Resolution:0.001
    GFDL_ntr_[m]
    non-tidal residuals for GFDL future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.328
    Maximum:2.496
    Units:meters
    Resolution:0.001
    EcEarth_ntr_[m]
    non-tidal residuals for EC Earth future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.067
    Maximum:1.592
    Units:meters
    Resolution:0.001
    HadGEM3SST_tide_[m]
    tides for HadGEM3-GC31-HM future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.529
    Maximum:1.624
    Units:meters
    Resolution:0.001
    CMCC_tide_[m]
    tides for CMCC future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.520
    Maximum:1.592
    Units:meters
    Resolution:0.001
    GFDL_tide_[m]
    tides for GFDL future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.522
    Maximum:1.600
    Units:decimal degrees
    Resolution:0.001
    EcEarth_tide_[m]
    tides for EC Earth future period projections (Source: Producer defined)
    Range of values
    Minimum:-1.515
    Maximum:1.574
    Units:decimal degrees
    Resolution:0.001
    Lat_[Nad83]
    Latitude coordinate (Source: Producer defined)
    Range of values
    Minimum:32.065
    Maximum:36.489
    Units:decimal degrees
    Resolution:0.001
    Lon_[Nad83]
    Longitude coordinate (Source: Producer defined)
    Range of values
    Minimum:-80.903
    Maximum:-75.483
    Units:decimal degrees
    Resolution:0.001
    WL_Tide_NTR_CMIP6_Ref_StationIdsLocs_NC.csv and WL_Tide_NTR_CMIP6_Ref_StationIdsLocs_SC.csv
    Files contain the transect IDs and their locations in Latitude and Longitude coordinates. (Source: Producer defined)
    Station_ID
    transect identification number (Source: Producer defined)
    Range of values
    Minimum:7
    Maximum:47
    Units:NA
    Resolution:1
    Lat_[Nad83]
    Latitude coordinate (Source: Producer defined)
    Range of values
    Minimum:32.065
    Maximum:36.489
    Units:decimal degrees
    Resolution:0.001
    Lon_[Nad83]
    Longitude coordinate (Source: Producer defined)
    Range of values
    Minimum:-80.903
    Maximum:-75.483
    Units:decimal degrees
    Resolution:0.001
    Entity_and_Attribute_Overview: The first line of the csv file is a header line.
    Entity_and_Attribute_Detail_Citation: U.S. Geological Survey

Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)
    • Kai A. Parker
    • Li H. Erikson
    • Jennifer A. Thomas
    • Kees Nederhoff
    • Tim Leijnse
    • Matthew W. Hardy
  2. Who also contributed to the data set?
    This data release was funded by the Additional Supplemental Appropriations for Disaster Relief Act of 2019 (H.R. 2157) for North Carolina and South Carolina.
  3. To whom should users address questions about the data?
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Attn: PCMSC Science Data Coordinator
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov

Why was the data set created?

These data are intended for policy makers, resource managers, science researchers, students, and the general public. These data can be used with geographic information systems or other software to identify and assess possible areas of vulnerability. These data are not intended to be used for navigation.

How was the data set created?

  1. From what previous works were the data drawn?
    GTSM (source 1 of 2)
    Muis, Sanne, Apecechea, Maialen Irazoqui, Álvarez, José Antonio, Verlaan, Martin, Yan, Kun, Dullaart, Job, Aerts, Jeroen, Duong, Trang, Ranasinghe, Rosh, Erikson, Li, O’Neill, Andrea, Bars, Dewi le, Haarsma, Rein, and Roberts, Malcolm, 2021, Global water level change indicators from 1950 to 2050 derived from HighResMIP climate projections: Copernicus Climate Change Service (C3S) Climate Data Store (CDS), online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution: Hindcast and forecast datasets of water levels
    NOAA (source 2 of 2)
    National Oceanic and Atmospheric Administration, 2022, NOAA Tides and Currents: NOAA, online.

    Online Links:

    Type_of_Source_Media: online database
    Source_Contribution: Water level and tidal data
  2. How were the data generated, processed, and modified?
    Date: 01-Mar-2020 (process 1 of 11)
    Water levels were obtained from the Global Tide and Surge Model (GTSM) hindcast/forecast dataset for the southeast Atlantic region. GTSM was forced by CMCC-CM2-VHR4, EC-Earth3P-HR, GFDL-CM4 and HadGEM3-GC31-HM_highresSST-future atmospheric conditions from the CMIP6 High-Resolution Model Intercomparison Project. See Muis and others (2016) for information on GTSM setup. Data sources used in this process:
    • GTSM
    Date: 01-Mar-2020 (process 2 of 11)
    NOAA Tide Gauge data were obtained at all available stations along the southeast Atlantic. All available water level and tidal prediction data were download for NOAA stations: 8632200, 8638610, 8638901, 8651370, 8652587, 8654467, 8656483, 8658163, 8661070, 8662245, 8665530, 8670870, 8720030, 8720218, 8721604, 8722670, 8722956, 8723214. Data sources used in this process:
    • NOAA tide gauge
    Date: 01-Apr-2020 (process 3 of 11)
    GTSM water level data were separated into contributing signals: Non-tidal Residual, Tides, Seasonality, and Monthly Mean Sea Levels. This was accomplished using tidal analysis and band-pass filtering.
    Date: 01-Oct-2020 (process 4 of 11)
    Non-tidal residuals were correcting using quantile matching (Déqué, 2007) with the target being the average error across all tide gauge observations (see Parker and others, 2023).
    Date: 01-Oct-2020 (process 5 of 11)
    Seasonality (defined here as the annual and semi-annual harmonics) was corrected using linear regression to remove locational bias as compared to tide gauges. The amplitude and phase of the seasonal cycles were shift with latitude as a predictor variable (see Parker and others, 2023).
    Date: 01-Oct-2020 (process 6 of 11)
    Tides were corrected using an ensemble-based method. Phase and Amplitude of tidal harmonics were determined based on a weighted average of available tide information in the region with weighting determined by the average model performance in comparison to tide gauges. See Parker and others (2023) for more details.
    Date: 01-Oct-2020 (process 7 of 11)
    Monthly Mean Sea Level was corrected using a single linear shift to eliminate bias in modeled values (see Parker and others, 2023).
    Date: 01-Nov-2020 (process 8 of 11)
    Corrected water level signals were recombined and validated against all tide gauges in the region (see Parker and others, 2023).
    Date: 01-Feb-2022 (process 9 of 11)
    Water levels were packaged for data release.
    Date: 13-Mar-2023 (process 10 of 11)
    Metadata was modified to include doi# and full citation for Parker and others (2023) Cross Reference. No data information was changed. The metadata available from a harvester may supersede metadata bundled within a download file. Users are advised to compare the metadata dates to determine which metadata file is most recent. Person who carried out this activity:
    Susan A Cochran
    U.S. Geological Survey, Pacific Coastal and Marine Science Center
    Geologist
    2885 Mission Street
    Santa Cruz, CA
    USA

    (831) 460-7545 (voice)
    scochran@usgs.gov
    Date: 16-May-2023 (process 11 of 11)
    Edits were made to correct spelling in author name and to include final citation information for a Cross_Reference. No data were changed. The metadata available from a harvester may supersede metadata bundled within a download file. Users are advised to compare the metadata date of this file to any similar file to ensure they are using the most recent version. (scochran@usgs.gov)
  3. What similar or related data should the user be aware of?
    Déqué, Michael, 2007, Frequency of precipitation and temperature extremes over France in an anthropogenic scenario: Model results and statistical correction according to observed values.

    Online Links:

    Other_Citation_Details:
    Déqué, M.,2007, Frequency of precipitation and temperature extremes over France in an anthropogenic scenario: Model results and statistical correction according to observed values. Global and Planetary Change, v. 57, pp. 16–26, doi: 10.1016/j.gloplacha.2006.11.030
    Haarsma, Reindert J., Roberts, Malcolm J., Vidale, Pier Luigi, Senior, Catherine A., Bellucci, Alessio, Bao, Qing, Chang, Ping, Corti, Susanna, Fučkar, Neven S., Guemas, Virginie, Hardenberg, Jost von, Hazeleger, Wilco, Kodama, Chihiro, Koenigk, Torben, Leung, L. Ruby, Lu, Jian, Luo, Jing-Jia, Mao, Jiafu, Mizielinski, Matthew S., Mizuta, Ryo, Nobre, Paulo, Satoh, Masaki, Scoccimarro, Enrico, Semmler, Tido, Small, Justin, and Storch, Jin-Song von, 2016, High Resolution Model Intercomparison Project (HighResMIP v1.0) for CMIP6.

    Online Links:

    Other_Citation_Details:
    Haarsma, R. J., Roberts, M. J., Vidale, P. L., Senior, C. A., Bellucci, A., Bao, Q., Chang, P., Corti, S., Fučkar, N. S., Guemas, V., von Hardenberg, J., Hazeleher, W., Kodama, C., Koenigk, T., Leung, L. R., Lu, J., Luo, J-J., Mao, J., Mizielinski, M. S., Mizuta, R., Nobre, P., Satoh, M., Scoccimarro, E., Semmler, T., Small, J., and von Storch, J-S., 2016, High Resolution Model Intercomparison Project (HighResMIP v1.0) for CMIP6, Geoscientific Model Development, v. 9, pp. 4185-4208, doi: 10.5194/gmd-9-4185-2016.
    Muis, Sanne, Verlann, Martin, Winsemuis, Hessel C., Jeroen C. J. H. Aerts, and Ward, Phillip J., 2016, A global reanalysis of storm surges and extreme sea levels.

    Online Links:

    Other_Citation_Details:
    Muis, S., Verlaan, M., Winsemius, H. C., Aerts, J. C. J. H., and Ward, P. J., 2016, A global reanalysis of storm surges and extreme sea levels. Natural Communications, v. 7, pp. 1–11, doi: 10.1038/ncomms11969.
    Parker, Kai A., Erikson, Li H., Thomas, Jennifer A., Nederhoff, Kees, Barnard, Patrick, and Muis, Sanne, 2023, Relative contributions of water-level components to extreme water levels along the US Southeast Atlantic Coast from a regional-scale water level hindcast.

    Online Links:

    Other_Citation_Details:
    Parker, K.A., Erikson, L.H., Thomas, J.A., Nederhoff, K., Barnard, P.L., and Muis, S., 2023, Relative contributions of water-level components to extreme water levels along the US Southeast Atlantic Coast from a regional-scale water level hindcast: Natural Hazards, https://doi.org/10.1007/s11069-023-05939-6.

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

  1. How well have the observations been checked?
    Accuracy of modelled water level data is dependent on a variety of factors including resolution, quality of forcing inputs, numerics, and included physical processes. Validation of modeled hindcast data compared to observations from tide gauges across the study region suggests that model root mean square error is around 13 cm for water levels, 7 cm for Non-Tidal Residuals, and 9 cm for Tides.
  2. How accurate are the geographic locations?
    The reported horizontal location of data output points is approximate. Horizontal accuracy is within a kilometer, with the error depending on local mesh resolution and how close the output station happen to be to a model grid node.
  3. How accurate are the heights or depths?
    Water Level data is projected for a future period so cannot be assessed for accuracy against observations. An identical model configuration run for a hindcast period found a model root mean square error of around 13 cm for water levels, 7 cm for Non-Tidal Residuals, and 9 cm for Tides.
  4. Where are the gaps in the data? What is missing?
    Dataset is considered complete for the information presented, as described in the abstract. Users are advised to read the rest of the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    All data fall within expected ranges. Missing data have been filled with -9999 values. Missing data values were assigned for data that failed QA/QC checks, primarily due to numerical artifacts, such as instabilities.

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 USGS-authored or produced data and information are in the public domain from the U.S. Government and are freely redistributable with proper metadata and source attribution. Please recognize and acknowledge the U.S. Geological Survey as the originator of the dataset and in products derived from these data.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - CMGDS
    2885 Mission Street
    Santa Cruz, CA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov
  2. What's the catalog number I need to order this data set? These data are available in csv format in 2 zip files. The state for which the data is available is reflected in the file name [WL_Tide_NTR_CMIP6Fut_STATE.zip], where STATE can be either NC (North Carolina) or SC (South Carolina). Additionally, two reference files (WL_Tide_NTR_CMIP6_Ref_StationIdsLocs_NC.csv and WL_Tide_NTR_CMIP6_Ref_StationIdsLocs_SC.csv) are provided which contain the station IDs and the corresponding station locations.
  3. What legal disclaimers am I supposed to read?
    Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (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.
  4. How can I download or order the data?
    • Availability in digital form:
      Data format: csv files were zipped for North Carolina in format comma-delimited text Size: 1200
      Network links: https://doi.org/10.5066/P9W91314
      Data format: csv files were zipped for South Carolina in format comma-delimited text Size: 761.6
      Network links: https://doi.org/10.5066/P9W91314
      Data format: csv files contain station IDs and locations for North Carolina in format comma-delimited text Size: 0.0006
      Network links: https://doi.org/10.5066/P9W91314
      Data format: csv files contain station IDs and locations for South Carolina in format comma-delimited text Size: 0.0004
      Network links: https://doi.org/10.5066/P9W91314
    • Cost to order the data: None.

  5. What hardware or software do I need in order to use the data set?
    These data can be viewed with any text reading software.

Who wrote the metadata?

Dates:
Last modified: 16-May-2023
Metadata author:
U.S. Geological Survey, Pacific Coastal and Marine Science Center
Attn: PCMSC Science Data Coordinator
2885 Mission Street
Santa Cruz, CA

831-427-4747 (voice)
pcmsc_data@usgs.gov
Metadata standard:
Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998)

This page is <https://cmgds.marine.usgs.gov/catalog/pcmsc/DataReleases/CMGDS_DR_tool/DR_P9W91314/WL_Tide_NTR_CMIP6Fut_metadata.faq.html>
Generated by mp version 2.9.51 on Tue May 16 16:48:23 2023