1 dataset found
  1. u

    Utah Landslide Compilation Debris Flow Paths

    • opendata.gis.utah.gov
    • gis-support-utah-em.hub.arcgis.com
    • +1more
    Updated Nov 22, 2019
    Share
    FacebookFacebook
    TwitterTwitter
    Email
    Click to copy link
    Link copied
    Close
    Cite
    Utah Automated Geographic Reference Center (AGRC) (2019). Utah Landslide Compilation Debris Flow Paths [Dataset]. https://opendata.gis.utah.gov/datasets/utah-landslide-compilation-debris-flow-paths
    Explore at:
    Dataset updated
    Nov 22, 2019
    Dataset authored and provided by
    Utah Automated Geographic Reference Center (AGRC)
    License

    Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
    License information was derived automatically

    Area covered
    Description

    Landslide Compilation Debris Flow Path feature class represents debris-flow paths throughout Utah, is the result of multiple landslide compilations (that include debris-flow paths) and digitizing efforts by the Utah Geological Survey (UGS), and is not new landslide-specific mapping. Harty (1992, 1993) produced a statewide landslide debris-flow path compilation on 46 30’ x 60’ quadrangle maps at 1:100,000 scale. Landslide debris-flow paths were compiled from all known pre-1989 published and unpublished references available at the time (Harty, 1992, 1993). The Utah Automated Geographic Reference Center (AGRC) digitized the 30’ x 60’ Harty (1992, 1993) quadrangle maps to create a statewide landslide debris-flow path feature class. Elliott and Harty (2010) updated the AGRC feature class by adding additional landslide debris-flow paths from 1989 to mid-2007 geologic maps and internal UGS landslide investigations. Elliott and Harty (2010) also added additional fields to the feature class. As a compilation, this data represents existing mapping from multiple sources, at a variety of scales and accuracies, and not new detailed comprehensive mapping of landslides. The feature class only shows mapped debris-flow paths from references available at the time of compilation and not all debris-flow paths that may be present.

  2. Not seeing a result you expected?
    Learn how you can add new datasets to our index.

Share
FacebookFacebook
TwitterTwitter
Email
Click to copy link
Link copied
Close
Cite
Utah Automated Geographic Reference Center (AGRC) (2019). Utah Landslide Compilation Debris Flow Paths [Dataset]. https://opendata.gis.utah.gov/datasets/utah-landslide-compilation-debris-flow-paths

Utah Landslide Compilation Debris Flow Paths

Explore at:
Dataset updated
Nov 22, 2019
Dataset authored and provided by
Utah Automated Geographic Reference Center (AGRC)
License

Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically

Area covered
Description

Landslide Compilation Debris Flow Path feature class represents debris-flow paths throughout Utah, is the result of multiple landslide compilations (that include debris-flow paths) and digitizing efforts by the Utah Geological Survey (UGS), and is not new landslide-specific mapping. Harty (1992, 1993) produced a statewide landslide debris-flow path compilation on 46 30’ x 60’ quadrangle maps at 1:100,000 scale. Landslide debris-flow paths were compiled from all known pre-1989 published and unpublished references available at the time (Harty, 1992, 1993). The Utah Automated Geographic Reference Center (AGRC) digitized the 30’ x 60’ Harty (1992, 1993) quadrangle maps to create a statewide landslide debris-flow path feature class. Elliott and Harty (2010) updated the AGRC feature class by adding additional landslide debris-flow paths from 1989 to mid-2007 geologic maps and internal UGS landslide investigations. Elliott and Harty (2010) also added additional fields to the feature class. As a compilation, this data represents existing mapping from multiple sources, at a variety of scales and accuracies, and not new detailed comprehensive mapping of landslides. The feature class only shows mapped debris-flow paths from references available at the time of compilation and not all debris-flow paths that may be present.

Search
Clear search
Close search
Google apps
Main menu