Projected groundwater emergence and shoaling in coastal areas around Puget Sound, Washington

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

Frequently anticipated questions:

What does this data set describe?

Title:
Projected groundwater emergence and shoaling in coastal areas around Puget Sound, Washington
Abstract:
Groundwater emergence and shoaling extents are derived from water table depth GeoTIFFs, which are calculated as steady-state groundwater model heads subtracted from high-resolution topographic digital elevation model (DEM) land surface elevations. Results are provided as shapefiles of water table depth in specific depth ranges.
Supplemental_Information:
Any use of trade, product, or firm names is for descriptive purposes only and does not imply endorsement by the U.S. Government. Although this Federal Geographic Data Committee-compliant metadata file is intended to document the dataset in nonproprietary form, as well as in Esri format, this metadata file may include some Esri-specific terminology.
  1. How might this data set be cited?
    Befus, Kevin M., Hoover, Daniel J., Grossman, Eric E., and Barnard, Patrick L., 20240427, Projected groundwater emergence and shoaling in coastal areas around Puget Sound, Washington: data release DOI: 10.5066/P946YX5G, U.S. Geological Survey, Pacific Coastal and Marine Science Center Santa Cruz, California.

    Online Links:

    This is part of the following larger work.

    Befus, Kevin, Hoover, Daniel J., Grossman, Eric E., and Barnard, Patrick L., 2024, Future coastal groundwater hazards in the Puget Sound region, Washington, U.S.A.: data release DOI: 10.5066/P946YX5G, U.S. Geological Survey, Pacific Coastal and Marine Science Center, Santa Cruz, CA.

    Online Links:

    Other_Citation_Details:
    Suggested Citation: Befus, K.M., Hoover, D.J., Grossman, E.E., and Barnard, P.L., 2024, Future coastal groundwater hazards in the Puget Sound region, Washington, U.S.A.: U.S. Geological Survey data release, https://doi.org/10.5066/P946YX5G.
  2. What geographic area does the data set cover?
    West_Bounding_Coordinate: -124.764478
    East_Bounding_Coordinate: -121.431864
    North_Bounding_Coordinate: 49.002088
    South_Bounding_Coordinate: 46.761722
  3. What does it look like?
    GWHazards_WTdepth_binned_browse_graphic.png (PNG)
    Map showing binned modeled water table depths along the Puget Sound coast for the K x 1 and present-day sea-level rise (0m) scenario. Colors represent water table depth relative to the ground surface (red = emergent, orange = very shallow (0-1m depth), yellow = shallow (1-2m depth), pink = moderate (2-5m depth), green = deep (>5m depth).
  4. Does the data set describe conditions during a particular time period?
    Beginning_Date: 2008
    Ending_Date: 2024
    Currentness_Reference:
    oldest dataset used through year of publication
  5. What is the general form of this data set?
    Geospatial_Data_Presentation_Form: GeoTiff
  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.
    2. What coordinate system is used to represent geographic features?
      Grid_Coordinate_System_Name: Universal Transverse Mercator
      Universal_Transverse_Mercator:
      UTM_Zone_Number: 10
      Transverse_Mercator:
      Scale_Factor_at_Central_Meridian: 0.999600
      Longitude_of_Central_Meridian: -123.000000
      Latitude_of_Projection_Origin: 0.000000
      False_Easting: 500000.000000
      False_Northing: 0.000000
      Planar coordinates are encoded using row and column
      Abscissae (x-coordinates) are specified to the nearest 10.000000
      Ordinates (y-coordinates) are specified to the nearest 10.000000
      Planar coordinates are specified in meters
      The horizontal datum used is GCS WGS 1984.
      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.257224.
      Vertical_Coordinate_System_Definition:
      Depth_System_Definition:
      Depth_Datum_Name: NAVD88
      Depth_Resolution: 1.0
      Depth_Distance_Units: meters
      Depth_Encoding_Method: Implicit coordinate
  7. How does the data set describe geographic features?
    projected water table depths
    shapefiles of projected water table depths for the County, SLR, and K case specified. (Source: originators at United States Geological Survey, Pacific Coastal and Marine Science Center)
    FID
    Object ID (Source: Esri) automatically generated unique identifiers
    Shape
    Feature Geometry (Source: Esri) polygon type vector object
    fbin_m
    Depth range code (Source: producer defined)
    ValueDefinition
    -1marine/tidal
    00 m; emergent
    10-1 m; very shallow
    21-2 m; shallow
    52-5 m; moderate
    7
    5 m; deep
    type
    type of polygon: terrestrial or marine/tidal (Source: producer defined)
    ValueDefinition
    terrestrialterrestrial groundwater polygon
    marine/tidalsurface flooding polygon associated with marine inundation due to sea-level rise, or with tidal flooding associated with the Mean Higher-High Water coastal boundary condition.
    wtdepth
    Water table depth associated with specific fbin_m code (Source: producer defined)
    ValueDefinition
    marine/tidalsurface flooding of marine or tidal origin (fbin_m code -1)
    0m, emergentsurface flooding associated with terrestrial groundwater emerging at the ground surface (fbin_m code 0).
    0-1m, very shallowgroundwater table between the ground surface and 1m below the surface (fbin_m code 1).
    1-2m, shallowgroundwater table between 1 and 2m below the ground surface (fbin_m code 2).
    2-5m, moderategroundwater table between 2 and 5m below the ground surface (fbin_m code 5).
    >5m, deepgroundwater table greater than 5m below the ground surface (fbin_m code 7).
    Entity_and_Attribute_Overview:
    Zip files of binned water table depths in polygon shapefile format.
    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)
    • Kevin M. Befus
    • Daniel J. Hoover
    • Eric E. Grossman
    • Patrick L. Barnard
  2. Who also contributed to the data set?
  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
    US

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

Why was the data set created?

Projections for future sea-level rise provide emergency responders and coastal planners with critical hazards information that can be used to increase public safety, mitigate physical damages, and more effectively manage and allocate resources within complex coastal settings. 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?
    water table depth (source 1 of 1)
    Befus, Kevin M., Hoover, Daniel J., Grossman, Eric, and Barnard, Patrick L., 2024, Projected water table depths in coastal areas around Puget Sound, Washington: U.S. Geological Survey, online.

    Online Links:

    Type_of_Source_Media: digital dataset
    Source_Contribution:
    raster depths that were converted to polygons by depth range (from this same data release)
  2. How were the data generated, processed, and modified?
    Date: 11-Jan-2024 (process 1 of 1)
    Using water table depth raster data, polygon shapefiles were created for inundated (marine) areas and for water table depths in specific depth ranges (emergent, 0-1m, 1-2m, 2-5m, >5m), using a two-dimensional Gaussian filter (Gaussian2DKernel from the astropy.convolution Python library), with a 10-m (one cell wide) standard deviation kernel used to smooth water table depth values and greatly reduce the file size. This smoothing step results in some loss of detail in the shapefiles relative to the WT Depth rasters. Data sources used in this process:
    • water table depth
  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?
    Attribute values are model-derived water table depths for present-day and future sea-level rise conditions. The model uses parameters from calibrated and published groundwater models and is intended to show the general response of the shallow coastal water table to sea-level rise. Water table depths are calculated relative to the best-available ground surface elevations from available digital elevation models (DEMs), but DEM inaccuracies introduce additional uncertainty into calculated water table depths. Projected water tables for future sea-level rise conditions cannot be validated against observations.
  2. How accurate are the geographic locations?
    Data are concurrent with topographic digital elevation model (DEM) locations.
  3. How accurate are the heights or depths?
    Model-derived head elevations are accurate within the limitations of the model. The model uses parameters from calibrated, published groundwater models, but limitations due to model resolution and uncertainty in model parameter values may significantly affect modeled head elevations. For water table depths, modeled heads are subtracted from land surface elevations from the best available digital elevation models (DEMs). DEM inaccuracy will introduce additional uncertainty into water table depth results. As a result, water table depth results are intended to show only the general response of the shallow coastal water table to sea-level rise.
  4. Where are the gaps in the data? What is missing?
    Dataset is considered complete for the information presented. Users are advised to read the metadata record carefully for additional details.
  5. How consistent are the relationships among the observations, including topology?
    Data have undergone quality checks and meet standards.

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 and the University of Arkansas as the originators of the dataset and in products derived from these data. This information is not intended for navigation purposes.
  1. Who distributes the data set? (Distributor 1 of 1)
    U.S. Geological Survey - CMGDS
    2885 Mission Street
    Santa Cruz, CA
    USA

    831-427-4747 (voice)
    pcmsc_data@usgs.gov
  2. What's the catalog number I need to order this data set? Zip files (GWHazards_EmergShoaling_Clallam.zip, GWHazards_EmergShoaling_Island.zip, GWHazards_EmergShoaling_Jefferson.zip, GWHazards_EmergShoaling_King.zip, GWHazards_EmergShoaling_Kitsap.zip, GWHazards_EmergShoaling_Mason.zip, GWHazards_EmergShoaling_Pierce.zip, GWHazards_EmergShoaling_San_Juan.zip, GWHazards_EmergShoaling_Skagit.zip, GWHazards_EmergShoaling_Snohomish.zip, GWHazards_EmergShoaling_Thurston.zip, GWHazards_EmergShoaling_Whatcom.zip) contain shapefiles of binned water table depth projections for the County in the file name. When unzipped, individual groundwater emergence and shoaling shapefiles have filenames with the structure "puget_(Cty_abbrev)_Kzell(K#)_slr(SLR#)m_10m_wtbins", where Cty_abbrev is the abbreviated County name (clallam, island, jefferson, king, kitsap, mason, pierce, san_juan, skagit, snohomish, thurston, whatcom), K# is 0p1, 1, or 10, and SLR# is 0p00, 0p25, 0p50, 1p00, 1p50, 2p00, 2p50, or 3p00. The "p" in file names is used in place of a decimal point. File sizes are in MB.
  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: The .zip file (GWHazards_EmergShoaling_Clallam.zip) contains 24 GeoTIFF files for Clallam County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 211.2
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Island.zip) contains 24 GeoTIFF files for Island County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 28.6
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Jefferson.zip) contains 24 GeoTIFF files for Jefferson County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 54.8
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_King.zip) contains 24 GeoTIFF files for King County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 139.3
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Kitsap.zip) contains 24 GeoTIFF files for Kitsap County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 70.9
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Mason.zip) contains 24 GeoTIFF files for Mason County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 144.1
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Pierce.zip) contains 24 GeoTIFF files for Pierce County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 123.2
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_San_Juan.zip) contains 24 GeoTIFF files for San Juan County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 42.7
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Skagit.zip) contains 24 GeoTIFF files for Skagit County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 126.4
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Snohomish.zip) contains 24 GeoTIFF files for Snohomish County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 169.3
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Thurston.zip) contains 24 GeoTIFF files for Thurston County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 84.5
      Network links: https://doi.org/10.5066/P946YX5G
      Data format: The .zip file (GWHazards_EmergShoaling_Whatcom.zip) contains 24 GeoTIFF files for Whatcom County (3 K cases x 8 SLR cases). in format Shapefile (version ArcGIS 10.8.1) Features are shapefiles and are projected in UTM Zone 10 coordinates, with horizontal datum GCS_WGS_1984 and vertical datum NAVD88. Size: 131.3
      Network links: https://doi.org/10.5066/P946YX5G
    • Cost to order the data: none

Who wrote the metadata?

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

831-460-4747 (voice)
831-427-4748 (FAX)
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_P946YX5G/GWHazards_EmergShoaling_metadata.faq.html>
Generated by mp version 2.9.51 on Wed May 1 11:00:27 2024