45122-C5-1_Landslide_Heads-Flanks

Metadata also available as

Frequently-anticipated questions:


What does this data set describe?

Title: 45122-C5-1_Landslide_Heads-Flanks
Abstract:
This layer is an inventory of existing landslide head flanks in the Oregon City USGS quadrangle. Each landslide deposit shown on this map has been classified according to a number of specific characteristics identified at the time recorded in the GIS database. The classification scheme was developed by the Oregon Department of Geology and Mineral Industries (Burns and Madin, 2009). Several significant landslide characteristics recorded in the database are portrayed with symbology on this map. The specific characteristics shown for each landslide are the activity of landsliding, landslide features, deep or shallow failure, type of landslide movement, and confidence of landslide interpretation. These landslide characteristics are determined primarily on the basis of geomorphic features, or landforms, observed for each landslide.
  1. How should this data set be cited?

    Oregon Department of Geology and Mineral Industries, 2009, 45122-C5-1_Landslide_Heads-Flanks: DOGAMI Interpretive Map Series 26, Oregon Department of Geology and Mineral Industries, Portland, Oregon, USA.

    Online Links:

    Other_Citation_Details: Public domain.
    This is part of the following larger work.

    Oregon Department of Geology and Mineral Industries, MM/DD/YYYY, Landslide Inventory of the Northwest Quarter of the Oregon City Quadrangle, Clackamas County, Oregon: Interpretive Map Series IMS-XX, Oregon Department of Geology and Mineral Industries, Portland, Oregon, USA.

    Online Links:

    Other_Citation_Details: Public domain.

  2. What geographic area does the data set cover?

    West_Bounding_Coordinate: -122.627153
    East_Bounding_Coordinate: -122.560855
    North_Bounding_Coordinate: 45.375300
    South_Bounding_Coordinate: 45.311568

  3. What does it look like?

  4. Does the data set describe conditions during a particular time period?

    Calendar_Date: MM/DD/YYYY
    Currentness_Reference: publication date

  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):

      • G-polygon (168)

    2. What coordinate system is used to represent geographic features?

      The map projection used is Lambert Conformal Conic.

      Projection parameters:
      Standard_Parallel: 43.000000
      Standard_Parallel: 45.500000
      Longitude_of_Central_Meridian: -120.500000
      Latitude_of_Projection_Origin: 41.750000
      False_Easting: 1312335.958005
      False_Northing: 0.000000

      Planar coordinates are encoded using coordinate pair
      Abscissae (x-coordinates) are specified to the nearest 0.000000
      Ordinates (y-coordinates) are specified to the nearest 0.000000
      Planar coordinates are specified in international feet

      The horizontal datum used is D_North_American_1983_HARN.
      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.

  7. How does the data set describe geographic features?

    45122-C5-1_Landslide_Heads-Flanks

    FID
    Internal feature number. (Source: ESRI)

    Sequential unique whole numbers that are automatically generated.

    Shape
    Feature geometry. (Source: ESRI)

    Coordinates defining the features.

    UNIQUE_ID

    DESCRIPT

    ID

    QUAD


Who produced the data set?

  1. Who are the originators of the data set? (may include formal authors, digital compilers, and editors)

  2. Who also contributed to the data set?

    William J. Burns and Ian P. Madin

  3. To whom should users address questions about the data?

    William J. Burns
    Oregon Department of Geology and Mineral Industries
    Engineering Geologist
    800 NE Oregon Street #28, Suite 965
    Portland, Oregon 97232
    USA

    971-673-1538 (voice)
    971-673-1562 (FAX)
    bill.burns@dogami.state.or.us

    Hours_of_Service: 8am - 5pm


Why was the data set created?

The landslide inventory is one of the essential data layers used to delineate regional landslide susceptibility. This landslide inventory is not regulatory, and revisions can happen when new information regarding landslides is found or future (new) landslides occur. Therefore, it is possible that landslides within the map area were not identified or occurred after the map was prepared.
This inventory map was prepared by following the Protocol for Inventory Mapping of Landslide Deposits from Light Detection and Ranging (Lidar) Imagery developed by Burns and Madin (2009). The three primary tasks included compilation of previously mapped landslides (including review of SP-34 (Hofmeister, 2000) and SLIDO (Burns and others, 2008)), lidar-based morphologic mapping of landslide features, and review of aerial photographs. Landslides identified by these methods were digitally compiled into a GIS database at varying scales. The recommended map scale for this data is 1:8,000 as displayed on this map. Each landslide was also attributed with classifications for activity, depth of failure, movement type, and confidence of interpretation. The landslide data is displayed on top of a base map that consists of an aerial photograph (orthorectified) overlain on the lidar-derived hillshade image.
This landslide inventory map is intended to provide users with basic information regarding landslides within the quadrangle. The geologic, terrain, and climatic conditions that led to slope failures in the past may provide clues to the locations and conditions of future slope failures, and it is intended that this map will provide useful information to develop regional landslide susceptibility maps, guide site-specific investigations for future developments, assist in regional planning, and mitigation of existing landslides.


How was the data set created?

  1. From what previous works were the data drawn?

    (source 1 of 1)
    Source_Scale_Denominator: 8,000

  2. How were the data generated, processed, and modified?

    Date: 17-Nov-2008 (process 1 of 3)
    Dataset copied.

    Data sources used in this process:

    • C:\Jed\GIS\Metadata_Review\Burns_20081117\IMS_XX_NW_Oregon_City_Landslide_Head_Flank

    Date: 16-Dec-2008 (process 2 of 3)
    Dataset copied.

    Data sources used in this process:

    • F:\Oregon City\Final GIS landslide files OC_NWquarter\45122-C5-1_Landslide_Heads-Flanks

    Date: 20-Mar-2009 (process 3 of 3)
    Metadata imported.

    Data sources used in this process:

    • C:\DOCUME~1\BILLBU~1\LOCALS~1\Temp\xmlAE.tmp

  3. What similar or related data should the user be aware of?

    Oregon Department of Geology and Mineral Industries, 2009, DOGAMI Special Paper 42, Protocol for Inventory Mapping of Landslide Deposits from Light Detection and Ranging (Lidar) Imagery.

    Other_Citation_Details:
    By William J. Burns and Ian P. Madin. The SP-42 file set consists of: a. Text report (print and onscreen versions), 30 pp. b. "geodatabase_template" folder: - Landslide_Inventory_Template-ArcInfo.gdb - includes relationship classes between the feature classes - Landslide_Inventory_Template-ArcView.gdb - sr_Toolbox.tbx - additional tools: Find Unmatched Features and Unjoin Layers c. Readme.txt file


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?

  3. How accurate are the heights or depths?

  4. Where are the gaps in the data? What is missing?

  5. How consistent are the relationships among the observations, including topology?

    CONFIDENCE OF INTERPRETATION: Each landslide should be classified according to a "confidence" that the mapper assigns based on the likelihood that the landslide actually exists. Landslides are mapped on the basis of characteristic morphology, and the confidence of the interpretation is based on the visual strength of the morphologies. As a landslide ages, after its most recent movement, weathering (primarily through erosion) degrades the morphologies produced by landsliding. With time, landslide morphologies may become so subtle that they resemble morphologies produced by geologic processes and conditions unrelated to landsliding. Some landslides have several different types of morphologies associated with them. A good way to define certainty is through a simple point system (see table below) associated with these features. The point system used is based on a ranking of four primary landslide features with a ranking of 0 to 10 points per feature. For example, if during mapping, the head scarp and toe of a landslide were identifiable and had very strong visual strength, the mapper would apply 10 points for the head scarp and 10 points for the toe equaling 20 points, which would be associated with a moderate certainty of identification.


How can someone get a copy of the data set?

Are there legal restrictions on access or use of the data?

Access_Constraints:
This map depicts an inventory of existing landslides based on published and unpublished reports and interpretation of topography derived from lidar data and air photos. The inventory was created following the protocol defined by Burns and Madin (2009). This map cannot serve as a substitute for site-specific investigations by qualified practitioners. Site-specific data may give results that differ from those shown on this map.
Use_Constraints:
Restrictions and legal prerequisites for using the data set after use is granted. These include any access constraints applied to assure the protection of privacy or intellectual property, and any special restrictions or limitations on using the data set. The maps cannot serve as a substitute for site-specific investigations by qualified practitioners. Site-specific data may give results that differ from those shown on the maps.

  1. Who distributes the data set? (Distributor 1 of 1)

    Nature of the Northwest Information Center
    c/o Donald Haines
    Manager
    800 N.E. Oregon Street, Suite 177
    Portland, Oregon 97232
    USA

    503-872-2750 (voice)
    971-673-1562 (FAX)
    don.haines@dogami.state.or.us

    Hours_of_Service: 9 am to 5 pm PST
  2. What's the catalog number I need to order this data set?

    Spatial data files available in shape file (.shp) format (ESRI).

  3. What legal disclaimers am I supposed to read?

    Although these data have been processed successfully on a computer system at the Oregon Department of Geology and Mineral Industries (DOGAMI), no warranty expressed or implied is made regarding the accuracy 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. This disclaimer applies both to individual use of the data and aggregate use with other data. It is strongly recommended that these data are directly acquired from DOGAMI, and not indirectly through other sources which may have changed the data in some way. It is also strongly recommended that careful attention be paid to the contents of the metadata file associated with these data. The Oregon Department of Geology and Mineral Industries shall not be held liable for improper or incorrect use of the data described and/or contained herein.

  4. How can I download or order the data?

  5. What hardware or software do I need in order to use the data set?

    Geographic Information System software


Who wrote the metadata?

Dates:
Last modified: 21-Mar-2009
To be reviewed: None planned
Metadata author:
William J. Burns
Oregon Department of Geology and Mineral Industries
Engineering Geologist
800 NE Oregon Street #28, Suite 965
Portland, Oregon 97232
USA

971-673-1538 (voice)
971-673-1562 (FAX)
bill.burns@dogami.state.or.us

Hours_of_Service: 8am - 5pm
Metadata standard:
FGDC Content Standards for Digital Geospatial Metadata (FGDC-STD-001-1998)
Metadata extensions used:


Generated by mp version 2.9.6 on Sat Mar 21 09:25:39 2009