11.0 APPENDIX D: SLIDO-3.0 GEODATABASE STRUCTURE AND UPDATE PROCEDURE

Transcription

1 11.0 APPENDIX D: SLIDO-3.0 GEODATABASE STRUCTURE AND UPDATE PROCEDURE 11.1 Structure We created the SLIDO-3.0 file geodatabase with Esri ArcView version 10.0 software. The projection is NAD- 1983HARN Oregon Statewide Lambert International Feet. Metadata are embedded in the geodatabase. The file structure of SLIDO-3.0 is shown in Figure D1 Figure D1. SLIDO-3.0 geodatabase file structure. Historic_Landslide_Points feature data set (points). Contains historical landslide points. REF_ID_COD String 50 unique code assigned by data steward to each original reference map UNIQUE_ID String 50 unique code assigned by data steward to each data point in database DATA_SOURC String 100 the original source that provided the data LOC_METHOD String 100 landslide mapping method ORIG_ID String 100 unique ID from original study SLIDE_NAME String 50 landslide name DATE String 25 landslide failure date LENGTH_ft Single 4 landslide length in feet WIDTH_ft Single 4 landslide width in feet DEPTH_ft Single 4 landslide failure depth in feet SLOPE Single 4 adjacent slope angle in degrees TYPE_MOVE String 50 type of landslide movement for example flow or slide MOVE_CLASS String 50 movement classification which includes type of material and type of landslide movement CONTR_FACT String 100 factors contributing to slide TYPE_MTRL String 25 type of slide material AREA_ft2 Single 4 size of landslide deposit VOLUME_ft3 Single 4 volume of landslide deposit DEEP_SHAL String 25 deep or shallow seated slide DAMAGES String 254 direct and Indirect damages caused by the slide LOSSES Single 4 monetary value associated with damages from the landslide (table continued on next page) 30 Oregon Department of Geology and Mineral Industries SLIDO 3.0 Appendix D: Geodatabase Structure

2 COMMENTS String 254 additional comments or attributes Annual_Cost Single 4 estimated monetary value spent in maintaining the stability of each landslide yearly Repair_Cost Single 4 initial monetary value spent repairing and stabilizing the landslide Landslide_Deposit_Polygons feature dataset.(polygons). Contains mapped landslide deposits and other landslide features. Deposits feature class. Polygons. Landslide deposits. SHAPE geometry geometry type UNIQUE_ID string 50 unique code assigned by data steward to each landslide polygon in database TYPE_MOVE string 25 type of landslide movement for example flow or slide MOVE_CLASS string 50 movement classification which includes type of material and type of landslide movement MOVE_CODE string 50 classification code based on type of material and type of landslide movement CONFIDENCE string 25 confidence of identification high, moderate, low AGE string 25 estimated age historical landslide age less than 150 years; prehistorical greater than 150 years DATE_MOVE string 50 date of last known movement NAME string 50 landslide name GEOL string 50 geologic Unit that the landslide occurred in SLOPE single 4 adjacent slope angle in degrees HS_HEIGHT single 4 change in elevation from bottom to top of head scarp FAN_HEIGHT single 4 change in elevation from top to toe of fan FAIL_DEPTH single 4 estimated and/or calculated slope normal thickness of failure depth DEEP_SHAL string 25 deep or shallow seated slide HS_IS1 single 4 horizontal distance from head scarp to internal scarp no. 1 IS1_IS2 single 4 horizontal distance from internal scarp no. 1 to internal scarp no. 2 IS2_IS3 single 4 horizontal distance from internal scarp no. 2 to internal scarp no. 3 IS3_IS4 single 4 horizontal distance from internal scarp no. 3 to internal scarp no. 4 HD_AVE single 4 calculated average horizontal distance between scarps DIRECT single 4 direction of movement AREA single 4 size of landslide deposit VOL single 4 Volume of landslide deposit QUADNAME string minute quadrangle name MAP_UNIT_L string 50 map unit label reference map unit label symbol taken from the original source map Descrip string 25 unit descriptor landslide, flow, talus-colluvium Shape_Area double area of shape in square feet Oregon Department of Geology and Mineral Industries SILDO-3.0 Appendix D: Geodatabase Structure 31

3 Photos feature class (points). Rasters of aerial or other photographs documenting the landslide deposit. LATITUDE double latitude in decimal degrees LONGITUDE double longitude in decimal degrees Photo raster actual raster Landslide_ UNIQUE_ID Photo_ Description text 30 unique code assigned by data steward to each landslide in database (identical to the UNIQUE_ID for the landslide polygon in the Deposits feature class) text 254 description Scarp_Flanks feature class (polygons). Landslide scarp and flank polygons. UNIQUE_ID string 50 same unique code assigned by data steward to each landslide polygon in database Shape_Area double area of shape in square feet Scarps feature class (polylines). Landslide scarp polylines. Index_Detailed_Landslide_Studies feature class (points). Index of deposit points for detailed landslide studies in Oregon. REFERENCE string 400 original reference for data 32 Oregon Department of Geology and Mineral Industries SLIDO 3.0 Appendix D: Geodatabase Structure

4 Index_Reference_Map feature class (polygons). Extents of studies included in Landslide_Deposit_Polygons., in form: SCALE string 25 original map scale PURPOSE string 25 geologic hazard specific mapping or not Shape_Area double area of shape in square feet References table. Complete list of original source data included in SLIDO-3.0. Also see Appendix C. SCALE string 25 original map scale REFERENCE string 400 original reference for data 11.2 Update Procedure Geodatabase stewards at DOGAMI use the following method when updating the SLIDO geodatabase. Read the SP-42 protocol (Burns and Madin, 2009) and the SLIDO-3.0 metadata for more detailed field information. Note about the REF_ID_COD field. The REF_ID_COD format identifies the reference author by the first four letters of the last name, followed by first and middle initials, followed by the year of work or the unpublished status (unpub), followed by the plate or figure information (if any). Add a sequential letter (b, c,...) to the end of the REF_ID_COD if more than one publication by the same author in the same year is being added. Attach a map identifier, e.g., sheet1, figure3, plate2a, etc., to the end of Ref_ID_COD only if there is more than one separate map from a publication that includes several maps that are to be used. If the material being added is unpublished, the year the work was done may be added to after unpub. Examples: BurnWJ2012 note: if you know there is a second 2012 reference, you may optionally add a to the first one BurnWJ2012b BurnWJ2012cbplate1 BurnWJ2012cplate2a BurnWJunpub BurnWJunpub2013 BurnWJunpub2014 BurnWJunpub2014b Historic Points When adding new historic points to the SLIDO geodatabase, update two data sets: 1. References table Update the References table by adding a new record for each new historic point study. Each record must have a REF_ID_COD, map SCALE, and full REFERENCE formatted in U.S. Geological Survey reference style. If REFERENCE exceeds 255 characters, abbreviate as needed. 2. Historic_Landslide_Points feature class First, make sure the new study data set is formatted to match the Historic_Landslide_Points feature class structure. Take care that field matching is done in a way that does not misplace or delete data. Add the REF_ID_COD to each landslide record and populate a UNIQUE_ID. Be sure to fill in the DATA_ SOURC and LOC_METHOD. You can generally find this information by reading the report attached to the new data set. Once the new input data are correctly formatted, simply copy and paste the new data into the Historic Landslide Points feature class while in edit mode. Oregon Department of Geology and Mineral Industries SILDO-3.0 Appendix D: Geodatabase Structure 33

5 Landslide Deposits When adding new landslide deposits to the SLIDO geodatabase, up to five data sets must be updated. Depending on the source data, there may or may not be data for all five of these data sets. 3. References table Update the References table by adding a new record for each historic point study to be added. Each record must have a REF_ID_COD, map SCALE, and full REFERENCE. 4. Index_Reference_Map feature class For each new study, add a polygon of the extent of the new study to the index reference map feature class dataset. Fill in the REF_ID_COD, map SCALE, and mapping PURPOSE fields. 5. Deposits feature class Two types of data sets go into this feature class: 1) data created by following the DOGAMI Special Paper 42 protocol (Burns and Madin, 2009), and 2) data from other mapping, generally geologic mapping. After determining which type of data you have, add the data by following one of these procedures: 3a. For SP-42 type data This type of source data will populate three feature class data sets: Deposits, Scarp_Flanks, and Scarps. The data should already be in a database format that matches SLIDO. Deposits, scarp flanks, and scarps from adjacent studies may be included in a database because they cross over the study extent. Remove these data from all three data sets prior to adding data to SLIDO to eliminate duplicate data. Duplicates in Deposits and Scarp_Flanks are generally easily identified from the UNIQUE_ID, but Scarp duplicates (line data) can be difficult to identify due to the lack of a UNIQUE_ID. Inspect these individually to identify the ones within the Deposit and Scarp_Flanks data from prior studies. While in edit mode, copy and paste scarp data into the Scarps feature class data set and scarp flank data into the Scarp_Flanks feature class data set. However, make sure that all fields have the appropriate data, especially the UNIQUE_ID. If you have photographs of the landslide, copy and paste those data while in Edit mode. Adding deposit polygon data is a little more complicated (Figure D2). First, examine the new study extent polygon to delete all older landslide deposit polygons inside the extent that are to be replaced with new data. Some older polygons will likely cross from inside to outside the extent. Cut so that only the outside portions of these polygons remain. Then inspect the outside boundary of the study extent for cases where new landslide polygons are mapped inside and cross outside the study extent. In these areas where there is new data, the old landslide polygon (which should already be cut so that only the part outside the new study extent remains) should be deleted completely. Finally, while in edit mode, copy and paste the new deposit polygons into the Deposits feature class data set. Fill in the DESCRIPT (landslide description) and QUADNAME (the quadrangle name or study name). If the study is of quadrangle, use the quadrangle name; if the study covers more than a quadrangle (for example, a watershed), use the study name. 3b. For non SP-42 type data This type of source data will populate one feature class data set: Deposits. It should already be in a database format that matches SLIDO. While in edit mode, copy and paste new deposit polygons into the Deposits feature class data set. Fill in the DESCRIPT (landslide description) and QUADNAME (the quadrangle name or study name). If the study is of quadrangle, use the quadrangle name; if the study covers more than a quadrangle (for example, a watershed), use the study name. 34 Oregon Department of Geology and Mineral Industries SLIDO 3.0 Appendix D: Geodatabase Structure

6 Legend Legend Index Reference Map New Deposits Being Added to SLIDO Deposits Already in SLIDO Portion of Existing Deposits to be Deleted New Deposits Being Added to SLIDO Index Reference Map Deposits Already in SLIDO Portion of Existing Deposits to be Deleted LIDAR BASEMAP EXISTS FOR THIS STUDY EXTENT LIDAR BASEMAP EXISTS FOR THIS STUDY EXTENT LIDAR BASEMAP EXISTS FOR THIS STUDY EXTENT OLDER STUDY WITH NO LIDAR BASE Figure D2. Examples of how to add landslide polygon data to the SLIDO geodatabase in areas where older data exist. (left) New mapping extends beyond the older study extent but both studies were made using a lidar basemap. Delete the entire older polygon, including the parts outside the new study extent. (right) New study made using lidar basemap overlaps older study made without a lidar basemap. Retain the older polygon portions outside the new study extent where lidar was not available at the time the new polygons were created. Oregon Department of Geology and Mineral Industries SILDO-3.0 Appendix D: Geodatabase Structure 35