Statewide adaptive translative transportation geotechnical ... · PDF fileStatewide adaptive translative transportation geotechnical DBMS (GDBMS ... engineering design and analysis

Statewide adaptive translative transportation geotechnical DBMS (GDBMS) framework for Virginia, USA

J. Yoon Department of Civil and Environmental Engineering, Old Dominion University, Norfolk, Virgina, USA

Abstract

A Geotechnical Engineering Database Management System (GDBMS) Framework for transportation infrastructure planning and design was conceptualized, developed and implemented to facilitate the access to and utilization of historical and current geotechnical data specific to the Virginia Department of Transportation's (VDOT) Hampton Road Third Crossing (HR3X) and Woodrow Wilson Bridge (WWB) projects at Washington, D.C. The GDBMS framework implementation is largely based on an Internet-based, adaptive translative framework concept to allow actual heterogeneous geotechnical data to be used “as-is” without retrofitting them for the GIS spatial database, so therefore provides rapid implementation and flexible modification and expansion. The Framework automatically identifies the type and characteristic of the "as-is" geotechnical data and subsequently translates it dynamically to various output data formats to make it available to the users via standard web browser interfaces. Furthermore, the GDBMS framework facilitates additional engineering design and analysis capabilities including generation of dynamic cross-sectional borehole fence diagrams over the Internet through a standard GIS user interface for road and bridge site selection and design. Keywords: adaptive framework and modeling, distributed GIS, geotechnical database management system (GDBMS), borehole fence diagram.

1 Introduction

In 2002, a pilot study to implement an Internet-based, spatiotemporal Geotechnical Database Management System (GDBMS) Framework was

© 2004 WIT Press, www.witpress.com, ISBN 1-85312-728-0Management Information Systems, C. A. Brebbia (Editor)

conducted for the Virginia Department of Transportation (VDOT) using a distributed Geographical Information System (GIS) methodology for geotechnical data archival and retrieval. Previously, a feasibility study [1] was conducted to identify a number of GDBMS implementation alternatives, and the GIS-based strategy was recommended as the most viable implementation model in terms of ease of use, cost-effectiveness, flexibility and future expandability. Main objectives of this pilot GDBMS Framework study were to conceptualize, design, develop and implement an Internet-based GDBMS Framework to facilitate VDOT geotechnical engineers to access and utilize historical and current geotechnical data specific to the Hampton Road Third Crossing (HR3X) project. Hampton Road Third Crossing project is aimed to relieve congestion at the existing Interstate 64 Hampton Roads Bridge Tunnel in Norfolk, Virginia. Proposed Third Crossing bridge site is located in the near west of the Craney Island Dredged Material Management Area (CIDMMA) where the U.S. Army Corps of Engineers (USACE) has the jurisdiction over. The CIDMMA is a 2,500-acre, confined dredged material disposal site approved by the Congress under the River and Harbor Act of 1946, and it had been receiving maintenance, private, and permit dredged material from numerous dredging projects in the Hampton Roads area since 1959. HR3X project is a new multi-billion dollar project, and preliminary engineering activities have already started in the fall of 2002 with General Engineering Consultant (GEC) to design five discrete sections of the proposed bridge, tunnel and connecting roads. Geotechnical engineering component of the HR3X project would require multiple deep channel drilling explorations that may cost $10,000 per day. Reflecting to such high-cost project requirements, one of main objectives of the GDBMS Framework pilot study was to develop and implement a GDBMS Framework component specific to the HR3X project by using existing VDOT's geotechnical data as well as applicable Corps' CIDMMA data. Thus resulting GDBMS Framework implementation would be capable of facilitating dynamic interpolation and generation of cross-sectional boring fence diagrams in the deep channel section instead of recursively spending time and money all over again to collect new in-field deep channel drilling geotechnical data. In 2003, site-specific HR3X GDBMS Framework pilot study implementation was substantially expanded to facilitate a Virginia statewide-scale GDBMS Framework. To demonstrate its new scalability, a new project site, Woodrow Wilson Bridge (WWB) Route 1 Interchange (R1I) site, Washington, D.C. was added to the statewide GDBMS Framework [2].

2 Organization of geotechnical DBMS (GDBMS) framework

GDBMS Framework concept lies in a “container” programming approach enmeshing two core components of GIS and geotechnical data, and an external application, gINT software [3] over the distributed network system, i.e., Internet. Here, the concept of a “container” reflects a number of key innovations

300 Management Information Systems


such as a standard, non-proprietary, open-system architecture [4], an easily updateable and expandable architecture [5] that enables seamless access to and retrieval of geotechnical data from both database (= attributal/temporal) and GIS (=map/spatial). GDBMS Framework consists of four modular components; (i) geotechnical data, (ii) adaptive translative Framework layer, (iii) analysis and design application and (iv) HyperText Transfer Protocol daemon (httpd), i.e., an ArcIMS [6] GIS-enabled web server as an Internet GDBMS Framework engine. Data used in GDBMS Framework are categorized into two types – geotechnical data and spatial map data. Geotechnical data portion was compiled from existing and current VDOT geotechnical data and Corps’ CIDMMA geotechnical data in a gINT or equivalent format that contain standard boring, STP (Standard Penetration Test), CPT (electric Cone Penetrometer Test), DMT (Dilatometer Test), VibraCore (sediment sampling) logs. Spatial map portion of the GDBMS Framework data was prepared from various spatial database sources including VDOT GIS layers and USGS color digital orthophotographs. These two main data components of the GDBMS Framework were then georeferenced and integrated by an adaptive translative Framework layer to provide a standard web browser-based user interface commonly accessible by Internet Explorer or Netscape. Figure 1 illustrates the concept behind the statewide GDBMS Framework.

Project SiteModule (WWB)Project Site

Module (HR3X)

CoreTables

(9 Tables)

Categorical Geotechnical Sub-Datasets

AdditionalProject Site

Modules

Project SiteModule (WWB)Project Site

Module (HR3X)

CoreTables

(9 Tables)

Categorical Geotechnical Sub-Datasets

AdditionalProject Site

Modules

Figure 1: Concept of scalable statewide GDBMS framework.

GDBMS Framework utilizes a distributed Geographic Information System (GIS) approach to bind its module components. GIS is, in a simplistic manner, a suite of computer programs and hardwares that facilitates capture, storage, query, retrieval and analysis of spatial and attributal information. [6][7] Furthermore, in an engineering application context, a GIS can be viewed as a special case of

Management Information Systems 301


information systems where the database consists of observation on spatially distributed features, activities or events, which are definable in space as point, lines or areas, both in visual (i.e., map) and in textual (i.e., tabular) display orientation. Thus GIS manipulates data about these points, lines, and areas to retrieve data for ad hoc queries and analyses to solve problems, come up with the answers, or try out a possible solution [8]. As a result, GIS often provides easy modification and flexibility, and native porting and linkage to other software applications in case of a specific need arises. [9]

Figure 2: GDBMS Framework user interface.

ArcIMS (Internet Map Server) [10] is an extension of a standard ESRI ArcGIS GIS application suite. Traditionally, the modus operandi of ArcGIS applications has been either stand-alone system or client-server architecture over a dedicated LAN (i.e., thin client) orientation. However since late 90’s, a heavy emphasis has been given to Internet-based GIS application through ArcIMS. Figures 2 and 3 show the GDBMS Framework user interfaces.



Figure 3: Dynamic boring sites display and selection.

3 Adaptive translative framework and its layers

In regard to characteristics of data, geotechnical data and spatial map data, these two data types are intrinsically heterogeneous. Linking and dynamically cross-referencing both data in a useable context was accomplished by dynamically translating these data with the adaptive translative Framework layers within the GDBMS Framework as shown in Figure 4. Benefits of the adaptive translative Framework layer include the elimination of retrofitting existing geotechnical data and the reduction of the project time required for development and implementation. Most common problem encountered in integrating existing data to a “system” is the requirement of modifying or retrofitting existing data to a new or “ideal” format retrospectively. Such retrofitting efforts usually demand exorbitant amount of resources and time, at the same time, do not guarantee any future expandability or flexibility of



the “system.” To obviate such problem, GDBMS Framework was conceptualized and designed to identify particular data origin and format using a number of data signature filters. Then subsequently translate the identified data dynamically or “on-the-fly” to a standardized or common data format without physically retrofitting data itself so that engineers can use the data and information for actual analysis and design rather than spending time and efforts to interpret such heterogenous data each time. This adaptive translative Framework approach is a tremendous advantage over typical proprietary engineering database systems in terms of usability, flexibility, stability and future expansion of the implemented system.

Web Server(httpd)

Web Browsers(IE/NS)

Second TierFramework

Third TierData

Php/JSXML/DHTML

ArcIMS/Servelet Spatial Map data(GIS)

GeotechnicalData

+Map

Geotechnicaldata

(VDOT+USACE)

Analysis and Design(gINT - Fence Diagram)

Adaptive Translative Framework Layer

Internet

Second TierFramework

First TierEnd-User

Web Server(httpd)

Web Browsers(IE/NS)

Second TierFrameworkSecond TierFramework

Third TierData

Third TierData

Php/JSXML/DHTML

ArcIMS/Servelet Spatial Map data(GIS)

GeotechnicalData

+Map

Geotechnicaldata

(VDOT+USACE)

Analysis and Design(gINT - Fence Diagram)

Adaptive Translative Framework Layer

Internet

Second TierFrameworkSecond TierFramework

First TierEnd-UserFirst Tier

End-User

Figure 4: Schematic of the adaptive translative Framework layer within the GDBMS Framework.

Output data of dynamically translated geotechnical data by the GDBMS Framework include boring, standard penetration test (STP), electric cone penetrometer test (CPT), dilatometer test (DMT), sediment sampling (VibraCore) logs, location-specific gINT project file translated in a standard data format and Excel CSV (Comma Separated Values) format as shown in Figure 5. Furthermore, the GDBMS Framework layer facilitates additional design and analysis capabilities including dynamic cross-sectional borehole fence diagram generation over the Internet using gINT software residing in the GDBMS Framework server (Figure 6). Therefore it effectively provides a valuable geotechnical analysis and design tools to the users, relieves the users from the steep learning curve for using gINT software, at the same time eliminating expensive and complicated software requirement at each end-user’s computer. All these output data are available to the users via a standard web browser interface, such as Internet Explorer or Netscape.



Figure 5: Dynamic adaptive translation to standardized outputs.

4 Data ROI and open system architecture concept

Majority of current engineering GIS applications require all the pertinent data, regardless of data types and formats, to be explicitly included in the their native, intrinsic GIS spatial database format, and are mainly used for retrieval and display of such data solely within the GIS. Thus, enormous amount of preparation, modification, conversion and pre-processing of source data into a specific format understood by the GIS application is essential requirement in GIS-based application. Usefulness and effectiveness of an engineering GIS application is directly proportional to the flexibility, size and quality of its database.



Figure 6: Design and analysis Framework layer - dynamic cross-sectional borehole fence diagram generation.

Consequently, time and resource required for such data conversion into GIS data format has been a major huddle for any engineering GIS application in term of ROI (Return On Investment) turnaround, particularly in time-sensitive project management situation – it easily takes years of data preparation and once it is completed, usually the data becomes already obsolete. Instead of binding all pertinent geotechnical data into the GIS, the GDBMS Framework flexibly links geotechnical data to skeleton GIS internal database, so that managing additional geotechnical data after system implementation become a matter of copying and dropping data files “as-is” to GDBMS Framework directory – flexibility and expandability -- therefore provides a rapid implementation of useable data through GIS methodology. The adaptive translative Framework layer was based on the open system architecture principle with standard XML (Extensible Markup Language) [11],



ArcXML (Arc Extensible Markup Language) [12], Php (Hypertext Preprocessor) [13], DHTML (Dynamic Hyper Text Markup Language) [14], Javascript script programming languages to ensure flexibility, expandability, portability and scalability of the Framework. All these programming languages are public domain, and all are freely available. Choice of script programming languages for the GDBMS Framework was to create a non-proprietary implementation so that in case of any future need, the GDBMS Framework can be easily modifiable and portable without repeating a new development and implementation cycle.

5 Summary and conclusion

An Internet-based, spatiotemporal Geotechnical Database Management System (GDBMS) Framework was conceptualized, designed, developed and implemented using a distributed Geographical Information System (GIS) methodology to facilitate accessing, retrieval and utilizing historical and current geotechnical data specific to the Virginia Department of Transportation’s (VDOT) Hampton Road Third Crossing (HR3X) project. This adaptive translative GDBMS Framework was designed and implemented from the user’s perspective instead of the developer’s so that it would satisfy followings characteristics; usability and ease of use, compatibility (with existing implementation), reliability and robustness, and flexibility and expandability. Utilization of heterogenous geotechnical data was facilitated through dynamic, adaptive translative GDBMS Framework layer, not through static, proprietary, hard-coded applications. Such static application approaches often impose precondition for existing geotechnical data to be retrofitted or re-processed, and certainly incur unnecessary time, efforts and high resources commitment. On the contrary, the adaptive translative Framework layer allows actual geotechnical data to be used “as-is” without retrofitting, therefore it rapidly provides valuable data for intended analysis and design. Although this pilot study emphasizes the GDBMS Framework methodology to the Hampton Road Third Crossing (HR3X) and Woodrow Wilson Bridge (WWB) projects at Washington, D.C. projects, the very Framework methodology can be applicable to any future geotechnical and other spatial database managements and engineering design and analysis in general.

References

[1] Ishibashi, I and Yoon, J., Feasibility Study of VDOT Geotechnical Database Management System (GDBMS), VTRC Contract Research Report, Virginia Transportation Research Council, Charlottesville, VA, February, 2002.

[2] Yoon, J. Implementation of Statewide VDOT Geotechnical Database Management System (GDBMS) Framework: The Woodrow Wilson Bridge (WWB) Route 1 Interchange (R1I) Site, VA, VTRC Contract Research Report, Virginia Transportation Research Council, Charlottesville, VA, October 2003.



[3] Geotechnical Computer Applications (GCA), 2002, gINT 5.0, Geotechnical and Geoenvironmental Software System, Windsor, CA.

[4] Mallach, E.G., 2000, Decision Support and Data Warehouse Systems, McGraw-Hill Publishing Company, New York, NY.

[5] Umar, A., 1997, Object-Oriented Client/Server Internet Environments, Prentice Hall Professional Technical Reference Series, New York, NY.

[6] Bernhardsen, T., 2002, Geographic Information Systems: An Introduction, 3rd Ed., Norwegian Mapping Authority (Distributed by John Wiley & Sons).

[7] Clarke, K.C., B.O. Parks, and M.P. Crane, 2002, Geographic Information Systems and Environmental Modeling, Prentice Hall Publishing, New York, NY.

[8] Duecker, K.J., 1979, Land resource information systems: a review of fifteen years' experience, Geo-Processing, 1(2):105-128.

[9] Connolly, T.M. and C.E. Begg, 2001, Database Systems: A Practical Approach to Design, Implementation, and Management, 3rd Ed., Addison-Wesley Publishing, New York, NY.

[10] East, R., R. Goyal, A. Haddad, A. Konovalov, A. Rosso, M. Tait, and J. Theodore, 2001, The Architecture of ArcIMS, a Distributed Internet Map Server Advances in Spatial and Temporal Databases, Lecture notes in computer science. no.2121: 387-403, Springer-Verlag.

[11] World Wide Web Consortium (W3C), 2001, Extensible Markup Language (XML), XML 1.1 W3C Recommendation, November 2001, Institut National de Recherche en Informatique et en Automatique, Keio University.

[12] ESRI Press, 2001, ArcXML Programmer's Reference Guide, ArcIMS 3, ESRI Press, Redlands, CA.

[13] Gutmans, A and Z. Suraski, 1997, Php: Hypertext Preprocessor, Apache Software Foundation (ASF).

[14] World Wide Web Consortium (W3C), 2000, Dynamic Hyper Text Markup Language (DHTML) W3C DOM level 2 (DOM2), Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University.



Documents

Statewide adaptive translative transportation geotechnical ... · PDF fileStatewide adaptive translative transportation geotechnical DBMS (GDBMS ... engineering design and analysis