electronic storage and interchange of geotechnical engineering data jennifer d. mcphail
TRANSCRIPT
Geotech XML (GML) Project
• What the GML Project is.
• Why the GML Project is so important.
• The capabilities of the GML Project.
• Fruition of the GML Project.
Contributions to the Project
• Provided a global review of the current state of affairs concerning geotechnical data processing.
• Established a need for a standard concerning the storage and transfer of geotechnical engineering data.
• Identified geotechnical data sources and the geotechnical data interchange process.
• Established design goals.
• Proposed a standard.
• Identified the logical structure of geotechnical data.
• Identified core tags of the GML language.
• Recognized privacy and authenticity issues concerning geotechnical data.
• Proposed the method to continue the GML language by adding “fourth level tags”.
Office
• Bid proposals• Project planning and
scheduling • Work delegation• Project design• Decision-making• Computations
performed
Field• Plans implemented• Progress takes place• Site characterization• Investigations
performed• In-situ soil tests
performed• Samples obtained• Tests conducted
Future Scenario
Better Judgements for the Continuation of the ProjectData Made Publicly AvailableData Captured for Research
The Proposed Standard• Design Goals• A First Step into the
Proposed Standard• A Tagged Data
Scheme• “<“ and “>” Identify
a Tag• “</” and “>” Identify
Closing of Tag
<Project> <Client> City of Stillwater </Client> <Engineer> Prime Geotechnical </Engineer > <Consultant> Geotechs-R-Us </Consultant ></Project>
Logical Structure of Data
• The “Three-Plus-Site” Model Used
• Categories Established• First Level of
Geotechnical Data Structure
• Second Level of Geotechnical Data Structure
Geotechnical Data Structure:
• SITE 1. The typical tasks performed in the office include:
• Preparations <Prep>
– Reconnaissance survey with maps and available reports
– Site visit records and report
• Plans and Specs <Specs>
– Boring locations and depths
– Sampling locations and sample types
– Tests to be performed in the field
– Tests to be performed in the laboratory
• Results/ Reports <Reports>
– Field work reports
– Lab work reports
– Analyses, including consultants' work
• Recommendations / Final Report
• SITE 2. The typical tasks performed in the field include:
• Borings <Borings>
• Sampling <Samples>
– ID, location, depth, diameter, method
– Borehole ID, depth, method, day/time, company, technician names,…
• Field tests <FieldTests>
– SPT
– CPT
– GWT
– Dilatometer
– Pressuremeter
– Cross-hole, etc.
• Plate Load Test (historic)
Geotechnical Data Structure:
• SITE 3. Some tasks performed in the laboratory are
• Index property tests <Index>
– Sieve analysis
– Hydrometer analysis
– Atterberg Limits
– Natural water content
– Specific gravity
– Void ratio
• Engineering/Mechanical Property Tests <Mechanical>
– Compaction and relative density determination by the standard Proctor compaction test
– Permeability tests
– Shear strength determination
– Direct shear test
– Unconfined compression test
– Triaxial tests
• Compressibility and consolidation tests
• Special tests <Special>
• Chemical tests and special triaxial tests and others
<GML>
<Prolog> <Project> <Name> </Name> <Date> <SecurityLevel> <Status> </Project> <Authorization> <AuthorizationCode code/> <AuthorizedBy> </AuthorizedBy> <Security> </Security> </Authorization></Prolog>
<Office> <Prep> </Prep> <Specs> </Specs> <Reports> </Reports></Office>
<Field> <Borings> <boring> (ID, depth, method, day/time, company, responsible technician name) </boring> </Borings>
<Samples> <sample> (HoleID, depth, type, method) </sample> </Samples>
<FieldTests> (SPT, CPT, GWT, etc.) </FieldTests></Field>
<Laboratory> <Index> (LL, PL, SL, PI, w, etc.) </Index> <Mechanical> (Triaxial, direct shear, consolidation, permeability, etc.) </Mechanical> <Special> (Chemical tests, etc.) </Special></Laboratory>
</GML>
Privacy and Authenticity of Data
• Maintaining Privacy by Using Public Key and Private Key System
• Maintaining Authenticity by Using a Digital Signature
• Examples of Tags
<Prolog> <Project> <Name> <Date> <SecurityLevel> <Status> </Project>
<Authorization> <Signature> <AuthorizationCode> <AuthorizedBy> </Authorization>
<Security> <SecurityMethod> <PublicKey> </Security></Prolog>
The Future Possibilities
• How Fourth Level GML Tags Can Be Selected
• Definition Process of New Tags
• Dr. Toll’s Work at Durham College