Development of a comprehensive geotechnical database for risk management of highway landslide problems is described. Computer software selected to program the client/server application in a data window, components and structure of the geotechnical database, and some of the primary factors considered in constructing the database are discussed. In the establishment of a large database that will be used widely, it is extremely important to select development software that will allow simultaneous use of the database by numerous users. Major integrated components of the database include landslide, rock slope, and soil and rock engineering data. This report mainly focuses on the landslide component. The landslide database module provides programmed procedures for gathering field data and rating the severity of landslides. Secondary components of the database include statistical analyzers and engineering applications for performing “on-line” analysis of data, developing correlation between different soil parameters, and performing engineering analysis and designs. Procedures for entering historical soil and rock engineering data have been developed. Procedures for entering and retrieval of landslide and rock slope data have been developed. Methods for “capturing” geotechnical data in a “real-time” mode, which will allow the storage of geotechnical data as it is generated, are currently being programmed. Issues concerning database security, engineering units, and storing and displaying maps, graphics, and photographs are discussed. The database contains procedures for dynamically overlaying the locations of landslides, rock slopes, and borings onto embedded roadway and digitized geological maps. Latitudes and longitudes of rock slopes and landslides were determined using Global Positioning System equipment (sub-meter accuracy). Strategies and illustrations of graphical user interfaces for data entry and retrieval are discussed. Some 1,400 highway landslides were identified and rated using a simple system devised by the University of Kentucky Transportation Center and the Kentucky Transportation Cabinet.

Report Date


Report Number


Digital Object Identifier



The contents of this report reflect the views of the authors, who are responsible for the facts and accuracy of the data presented herein. The contents do not necessarily reflect the official views or policies of the University of Kentucky, the Kentucky Transportation Cabinet, nor the Federal Highway Administration. This report does not constitute a standard, specification, or regulation.