Exporting Data to EQuIS for gINT

<< Click to Display Table of Contents >>

Navigation:  Professional > Interfaces > EQuIS for gINT >

Exporting Data to EQuIS for gINT

gINT Queries (.gdx) File

Use EQuIS for gINT Interface

 

The EQuIS for gINT Interface makes creating borehole logs, fence diagrams, reports, and tables quick and easy. In addition to creating static "snapshot" databases, output defined in the gINT library can be created automatically, sometimes in only one click!

 

In order to create output, a gINT data template (.gdt) and gINT library (.glb) are required. The corresponding template (gint std us.gdt) and library (gint std us.glb) are installed with the EQuIS for gINT Interface and can be found in the "C:\Program Files\EarthSoft\EQuIS\Tutor\GeoTechnical\gINT" directory.

 

The following message may occur on 64-bit machines running the EQuIS for gINT export.

 

...System.Exception: Unable to initialize connection ---> System.Runtime.InteropServices.COMException (0x800A0E7A): Provider cannot be found. It may not be properly installed....

 

To address this message, EQuIS for gINT should be launched through EQuIS_x86.exe (found in Program Files\EarthSoft\EQuIS directory). The 64-bit version of Professional EQuIS_x86 executable was created for use with third party 32-bit (x86) applications such as gINT that are not able to host 64-bit (x64) DLLs.

 

gINT Queries (.gdx) File

 

One additional file, the gINT queries file, is also required. This file is not used by gINT itself, but is required by the EQuIS for gINT interface, because it contains the queries necessary to extract the data out of the EQuIS Database and make it usable by gINT. The gINT queries file must have the same name and exist in the same directory as the template. For example, the installed gINT queries file, "gint std us.gdx", can be found in the same location as the "gint std us.gdt".

 

The queries file is simply an XML based text file that includes the queries utilized by the interface. (In earlier versions of the interface, these queries were contained within the EQuIS Database. An example showing the POINT query as it has been defined in the EQuIS Database and how it is now defined in the .gdx file). Maintaining the queries in the .gdx file affords several advantages and increased flexibility to the user.

 

Note: The PointID field should not be renamed in the gint std us.gdx. This field is used in the interface to filter from the Point table to all other tables.

 

Use EQuIS for gINT Interface

To launch the EQuIS for gINT Interface, click the gINT icon button in the Plus section of the Graphics tab in EQuIS Professional.

 

If no gINT button is visible, follow the instructions here to restore the button.

 

Note: In order to open any files located in the "C:\Program Files\. . ." folder, EQuIS must be run as an administrator.

 

If the interface has not previously been opened on this machine, please do the following:

 

1.If user has administrator permissions on their machine, skip this step. If user does not have administrator permissions on their machine, as discussed in the above gray Note box, first copy the gINT folder under "C:\Program Files\EarthSoft\EQuIS\Tutor\" and paste it to a different location on the computer where Administrator permission is not needed, such as the Desktop, Documents, or Downloads folders.

 

2.The interface will first require that the user select the gINT data template file (.gdt). Browse to the gINT data template, "C:\Program Files\EarthSoft\EQuIS\Tutor\gINT\gint std us.gdt", or to its new file path from step 1. Several tabs should now be populated with data exactly as gINT will see that information.

 

2.Under "gINT Library (.glb)" on the right side, click <Browse>...
 

3.Browse to the gINT library, "C:\Program Files\EarthSoft\EQuIS\Tutor\gINT\gint std us.glb", or to its new file path from step 1. Once the gINT library has been selected, the various types of output defined in that library are listed in the Generate Output section of the gINT Interface.
 
All output formats contained in the library are listed, regardless of the data available. For example, even though a moisture content histogram requires laboratory data, which is not part of the gint std us.gpj (or, consequently, the EQuIS gINT Database generated by EQuIS), it is still displayed and is an available option in the interface. Clicking the Moisture Content histogram will produce the histogram, but as there are no data to support that output, it will essentially be blank.

 

Create CPT Log

 

oSelect CPT-1 on the POINT tab and click CPT in the Logs section.

 

Clicking on the output option desired under Generate Output first creates a temporary gINT Database. (database is saved in user's EQuIS Work directory under name of database, and then name of facility. In this example, the file would be found in C:\Documents and Settings\ [User Name]\My Documents\My EQuIS Work\gINT\gINT Example). The temporary gINT Database is then processed by gint std using a gINT scripting (.gsc) file, saved in the same directory. Finally, the output, saved as a PDF document, is opened in the default system reader of .pdf files, typically Adobe Acrobat.

 

Create Environmental Borehole Log

 

Select B-1 on the POINT tab and click ENVIRONMENTAL BH in the Logs section.

 

Create Geotechnical Borehole Log

 

Select B-3 on the POINT tab and click GEOTECH BH COLUMNS or GEOTECH BH PLOTS in the Logs section.

 

Create Fence Diagram

 

Select B-1, B-2, and B-3 on the POINT tab; click STRATIGRAPHY & GW - A Size in the Fences section.

 

Create Site Map

 

Select all locations on the POINT tab and click SITE MAP in the Graphs section.

 

Create Project Summary Document

 

Click PROJECT SUMMARY in the Text Docs section

 

Note: The EQuIS Professional installation has been updated to include an import format file and export mapping file (.gdx) that correspond to the gINT std us tutorial gINT project (older gINT and gINT_Lab formats have been removed). It is recommended that the EQuIS Database contain the geotechnical schema for best results when importing data using the gINT std us format.