Overview

This tutorial explains how to complete a series of typical tasks for data entry, reporting and analysis. When you have completed this tutorial, you will have gained enough skills to begin entering and importing data from a range of sources, and generating reports.

gINT Program Overview

• Overview of gINT Features and Capabilities
• Database manager for subsurface exploration
• Storing, validating, manipulating and reporting data
• Graphic Tools available in gINT
  • gIDraw
  • Symbols
• Grid Input and Graphical Data Input
• How gINT communicates with other programs
  • Data import and export
  • Graphical import and export
• gINT's Application Groups and layout of program:
  • Input
  • Output
  • Data Design
  • Report Design
  • Symbol Design
  • Drawings
  • Utilities
• gINT Products
  • Logs
  • Professional
  • Professional Plus
  • gINT Civil Tools
• Bentley SES license system
• Help menu

Preliminary settings

1. Install and license gINT and the DGDT DLL program.
2. For the tutorial copy the dgdt user gINT files (*.gpj, *.gdt, *.glb, *.gcx, *.gci, *.gas) to a folder titled c:\Datgel Training\.
3. Open gINT.
4. Open the dgdt-p lib #.##.#.glb library using the command File > Change Library. If you are running an evaluation or trial version, the library is read-only and the design applications are hidden.
5. Launch File > System Properties, and configure the following on the first tab.
   
6. Refer to section Configure Optimal System Properties for further instruction.

Data entry of a borehole

Make a new project by cloning data template

To make a new Access Project File:

1. Select INPUT | File > New Project or the (new) icon > Clone Data Template…
2. Browse to the data template dgdt-p #.##.#.gdt, and click Open.
3. Name the new project file Tutorial.gpj, and click Save.

General

Progress through the INPUT application entering data displayed in the screen shots.
You can change tables or tabs by clicking on the tabs at the top of the screen or using the tree navigation on the left. To enable and disable the tree navigation click on the button: .

Data is saved when you initiate the save by clicking on the save icon, pressing Ctrl+S, or automatically when you change tabs, or change the object selector item (yellow drop down list), or before some commands run. It is recommended that you save data after entering a few lines.

There is not a multi step undo like in Word.  The closest option is Cancel changes since last save, which is the save like icon with the red arrow in the top right of the screen.  

Project

Set the Project Type and SPT Pen Values to match you standard. If you are using BS, then both SPT Pen fields should be 75, other standards should have 150 and empty cell.

Project Options

• The settings on this table generally depend upon the logging standards in use, and it is critical the relevant values are set for Classification_Standard, List_Filter and Localisation_List_Filter.
• Enable Specimen Description Calc – check
• Note the Graphic Log option controls the log report column, set it to Graphic.

Point

• Use Tab or right arrow to move to the next cell.
• Press F2 to make a cell editable.
• Press Ctrl+Enter to move to next line.

• To rename a PointID, change the name in the POINT table PointID field.
• Set Depth Borehole / Corehole Break, to define the depth that the non cored log ends and cored log starts

Strata Main

Speed up selection by using lookup lists. F2 makes the list expand. If you type into fields, matching items are selected automatically.

If you follow Australian or New Zealand practice, at this point you'd enter data into tables:

• Main Group | Moisture Condition
• Main Group | Consistence/Density
• Rock Coring | Rock Strength
• Rock Coring | Weathering
• Rock Coring | Defects
• Rock Coring | Fractures

Component Description tables

The DGDT incorporates component description tables for AS, NZGS, BS and ASTM. Data in the component description tables will be displayed in priority over data in Stata Main.
Enter one description in the component description tables for soil and rock that best matches the standard you log to.

Geology Unit

You will find the Geology Unit 1 and 2 lookup lists empty. In this example a standard list of units from Singapore is applicable, and these can be imported from the example project dgdt-p #.##.#.gpj. Select File > Import/Export > Import from Database…, and configure the options as in the following screen shot, then click OK.

SPT

• Do not enter data in the green fields, these will calculate when the grid saves.
• If your logging standard uses 3 intervals, then enter data in columns 1, 3, and 5.
• If you enter a Recovered_Sample_Length, then a corresponding record will be created on the Sample table.

BS

AS / NZGS / ASTM

Core

• Enter data in the Length fields, and the result fields will be calculated.
• Unless you check the box, corresponding same records will be made.

Sample

Other than the TW type records, the data was automatically created by the DGDT program. You can edit the data without it being overwritten, since the same function only runs when new records are created on the SPT and Core tables.

Other common logging tables

At this point you may like to enter data for these tables

• Method, Shoring, Hole Info at Depth
• Water Strike/Inflow
• Progress & Drilling Fluid Levels
• Rotary Flush
• Point Load Strength, which is under Lab-Rock.  See Lab data entry section below.

Shear Vane

Pressuremeter

In Situ Permeability

Piezometer data entry

The DGD Tool allows the storage of piezometer data and includes log reports that display piezometer installation.

A procedure about how to enter the piezometer data into the database is detailed in the Monitoring Tool User Guide.

Log reports that present piezometer data include:

• IS AU BOREHOLE CONTAM 1
• IS AU HYBRID BOREHOLE 1
• IS AU PIEZOMETER INSTALLATION 2
• IS NZ BOREHOLE CONTAM 1
• IS NZ DRILLHOLE 1
• IS NZ DRILLHOLE 2

Selected lab results

Make Specimen records

First create specimen table records – this is the bottom half of the Sample tab:

1. Go to the SAMPLE tab
2. On the top half of the screen click on the Depth = 6 m row
3. Then on the bottom half of the screen enter 6 in the Specimen_Depth box. You may optionally enter a value in Specimen_Number
4. On the top half of the screen click on the Depth = 3 m row
5. Then on the bottom half of the screen enter 3 in the Specimen_Depth box. You may optionally enter a value in Specimen_Number

Enter Moisture Content Data

Enter Density Data

Enter Atterberg Data

• PI and LI are calculated.

Enter Sieve Data

• Hydrometer results can also be entered on the Sedimentation tables
• Ensure you have made a specimen at 3.00 m before continuing.

Enter Triaxial Effective Stress Data

Lab Data Entry Add-In

The Lab Data Entry feature provides the user with an option to efficiently enter and edit multiple lab results in one table interface. The procedure is as follows:

1. Navigate to INPUT | Lab-General | Lab Data Entry.
2. Select the desired PointID.
3. Call the command, Add-Ins > Datgel DGD Tool > Pre-populate Lab Data Entry Table. This causes all existing lab data within the scope of the table to display.
4. You can now complete any of these activities:
   1. Enter/edit data on existing records.
   2. Create new records and enter data. Select a Sample and enter a value for Specimen_Depth and optionally Specimen_Number.
   3. Delete a record by checking the delete check box.
5. When the table saves a message box displays, enabling you to choose whether to update, discard, or return to the grid continue editing.

Graphical Data Input

Graphical Data Input (GDI) allows you to edit data and then instantly see the change on an interactive log report. Data entry using this interface is not as fast as Grid Input, but is ideal for data entry in the field on a tablet device, for new gINT database users who are not familiar with the fields, or when reviewing and making minor changes to data.
Click  :

• To avoid a defect, click on the log report to make the grid window display, before using a zoom command.
• Change reports by selecting File > Select reports for Input
• Change PointID: Click anywhere on the page, and click the Select button.
• Make a new PointID: Click anywhere on the page, and click the New button.

Preview from INPUT

A fast way to preview reports while entering data is to use File > Print > Preview, or the toolbar icon . You are prompted to assign a report to the table if one is not already assigned. The assigned report can be changed on the table properties form, launched by the toolbar icon .

Formatting

Format Menu

Try out some of the Format menu commands to create:

<<CLR!16711680,Very Light Blue>><<DMK!BETA LC>><<G>>=<<G>>5°<<CLR!-1>>
2<<G>>m<<SUP>>2<<SUP>>

Change the text case in the Description field, double-click on the text and highlight a word or phrase. Select Format > Upper Case and notice that all of the selected words are now in upper case letters.

Interface changes

• Modifying Field Properties
• Modifying Table Properties
• Column width
• Column Order
• Row Height
• Table order
• Group order
• Assigning a table to a group can only be done in DATA DESIGN | Project Database
• Adding Fields and Tables

Input tools

• Short cut keys and scanning through records
• Text Macros
• Spell check
• View Entire Table
• Edit Entire Table
• Point Sort Field
• Comparing Databases

Replicating a Point

Use this feature to copy the currently selected PointID and all of its dependent.

1. Click on the Point tab and select Tools > Replicate Point. You see the Replicate Current Point and Dependent Data dialog box:
   
2. Type BH102, BH103 in the text box to copy the current Point. The Point IDs can be separated with commas and/or carriage returns.
3. When you click OK, all your new points will be defined with the common data. You can apply data changes to each PointID.

Importing/Exporting Data

gINT can interop with a wide range of file formats. These commands are located in the File menu.

Exporting Data

Now export some data to Excel.

1. Select the File > Import/Export > Export to Excel File menu option. You see a dialog box with specific import options.
   
2. Click the browse button to the right of the Excel File text field to specify a path to a new Excel file. Call the new file "gINT Export". Check Selected tables and select the four tables in the screen shot, check Include field Captions, check Launch Excel after export and click OK to start the export.
3. At the end of the export process, any messages and errors are written to an export log. Click OK to close the window, and an Excel window will open.
   
   Every table in gINT is stored in a separate spreadsheet in Excel. The spreadsheets are accessible by clicking on the tabs along the bottom of the Excel screen. The first row of the spreadsheet contains the field names of the table, the second row contains the captions and units of the field, and the following rows contain the field data.

Importing Data

gINT accommodates importing data from several file formats. Common to all these import commands are two text field options, Correspondence File and Overwrite Options.
The Correspondence File field allows the program to read a gINT Correspondence File during import to map a differing file structure to the target gINT project database.
The Overwrite Option field controls how the program will deal with data that are in both the current database and the external file.
The options are:

• Never - add records who's Keys do not exist in the current database. Existing records will not be changed in any way. All options share this behaviour for new records.
• Empty fields - Writes data from the source only if the corresponding field in the target is empty.
• Named fields - Writes data from a field named in the source wherever a matching field exists in the target, overwriting any contents of the target field. Note that if a field is blank in the source it will overwrite any contents in the target field and leave it blank.
• Records - Erases each target record matched by a source record (same key) and writes the data from the source. Any records in the target that do not have corresponding records in the source will not be affected by the import.
• Data sets - Replaces entire sets of data; the resulting data set will contain only data from the source file. A "Data Set" is defined by the Keyset of the parent table. For example in a table with the PointID, Depth Keyset a Data Set is all records with a particular PointID value, while for a PointID, Depth, Reading table a Data Set is all records that share a PointID and Depth.

With the data imported to the POINT table, there is no parent table and this option acts like the Records option, that is, all the data in the POINT table will not be deleted with this option. Only the records in the target that match those in the source will be overwritten by the source data. Any records in the target that do not have corresponding records in the source will not be affected by the import.

To demonstrate the Overwrite options, modify the data in the Excel file you created previously, and import it back into the gINT database.

1. In the Excel screen, delete all other tabs except for the POINT tab. Right click on a tab to bring up a menu, and select delete to delete a tab. Press the delete button when prompted with a message box.
   
2. In the POINT tab, delete all the columns except for PointID, Elevation, North and East.
3. Enter a new record, BH104 on the next blank row. Change the values in East, North and Elevation columns for each PointID so that they are different to each other. Leave a few values blank. The Excel spreadsheet should now look like the following screenshot.
   
4. Save the Excel file, minimise Excel, and return to the gINT screen. Go to the Borehole tab and delete the North value for the borehole BH101, the East and North values for BH102 and the Surface Elevation, East and North values for BH103.
5. Click the File > Import/Export > Import from Excel File menu option to bring up the following dialog box.
   
6. Click the browse button to the right of the Excel File text field and select the Excel file that you have been working on. Select Never in the Overwrite Options text field and click OK.
   You will see that in the import log that 0 records were imported and the records were not writable. In the Borehole table, there should not have been any changes to the existing records. This is because the Never option will not write to existing records. You will also notice that BH104 was not imported because it is missing a value in the key field HoleDepth.
7. Click the File > Import/Export > Import from Excel File menu option to bring up the Excel Import dialog window again. This time, select Empty Fields in the Overwrite Options text field, and click OK.
   This time, you will see that the 3 Records have been added or updated. In the Borehole table, the empty East, North and Surface Elevation records will have been filled with the values in the Excel file. This option is useful if you have left the East, North and Elevation Value blank at the time of data entry, and you wish to enter these values at a later time. You will also notice that BH104 was not imported again because it is missing a value in the key field HoleDepth.
8. Go back to the Excel screen and enter different values for East, North and Elevation columns for all the records.
9. Go to the gINT screen, and click the File > Import/Export > Import from Excel File menu option to bring up the Excel Import dialog window. This time, select Named fields (Fields not named are ignored) in the Overwrite Options text field, and click OK.
   This time, you will see that 3 records have been imported. In the Borehole tab, you will see that the data in the gINT screen has been overwritten by the data in the Excel file. This option is useful if you wish to replace the existing East, North and Elevation values with more accurate values that were obtained at a later time. You will also notice that BH104 was not imported again.

Output Part 1 - Logs

Preview all PointIDs with IS SG BOREHOLE 1

Preview Piezometer Log 

1. Select log report from object selector: IS AU PIEZOMETER INSTALLATION 2
2. Select one PointID using the browse button
3. Select preview

Open a new data source project

Click in the Source File …, and open the file dgdt #.##.gpj.

PDF a log report for multiple PointIDs with child bookmarks

1. Click on the PointID… button, and using the Ctrl key, select the indicated 6 PointIDs.
   
2. Click the PDF icon, and name a file.
3. Check View document after export
4. Click the Bookmark path … button
5. Right click the text ROOT, and select insert child. Name item Logs
6. Click on Child Bookmarks, and click OK
7. Click Export

Utilities

In this section, we will discuss the UTILITIES application group and the purpose of each of the applications. The UTILITIES applications are primarily program maintenance applications, designed to help streamline some of the database processes in gINT.

Repair/Compact Databases

Occasionally, databases get corrupted. If that happens in gINT, you can use this application to repair the file. In addition, this utility removes deleted records. Like most databases, the records are not actually deleted in the Microsoft ACCESS files that gINT uses, they are marked as deleted and not shown.

We recommend using this utility on your library file once a month to repair and compact the file. It is a good idea to do the same for large, long-running projects. When you click the Repair/Compact Databases application tab, you see the following dialog box:

To repair/compact a database, you would enter the database name in the Files text box, or click the browse button to select the file. Instead of browsing for a file, you can select one of the following options:

• Library to repair/compact the current library.
• Current Project to repair/compact the current project database.
• Setup to repair/compact your SETUP.GSH file.

After choosing your files, you would select from one of the following options:

• Convert Access 97 files to Access 2000 (default) to convert the files to Access 2000. ACCESS 2000 handles the transition between double and single byte environments better than ACCESS '97. gINT versions 5 and 6 work equally well with ACCESS '97, 2000, or XP version files.
• Keep same database version to keep the current version of Access and not convert the files to Access 2000.
• The Remove gIDraw Pages with no entities option removes all empty gIDraw pages, regardless of the name. The Remove Pages named ">Unnamed<" option removes all library pages. Both options apply only to library files. Click the Execute when you are ready to repair/compact the database.

For further study, select the Help >  Contents > Utilities Application > Repair/Compact Databases topic.

Print Object Lists

This application allows you to batch print the entire contents of all symbol, graphic report, and drawing libraries.

To print, just move the file(s), from the Available Objects list to the Objects to Print list using the arrow buttons and then click Execute. Select your print specifications in the dialog box that displays:

Convert Projects

Convert Projects allows you to convert existing projects to a different database structure using a data template file and an optional correspondence file. The structural changes could be minor such as a changed caption, ranging to major changes such as new tables and fields.

When you click on the Convert Projects application tab, you see a dialog box similar to the following:

Specify the target Data Template file. This is the file that stores the structure you want to convert the projects to. The Correspondence File is used to map the old structures into the new and the lists of projects (Convert Files) are the files you wish to convert. Click Execute to convert the files. For each project file being translated, gINT will:

1. Create a temporary file with the structure of the specified Data Template.
2. Copy the data from the project file to the temporary file according to the mapping specified in the Correspondence File.
3. Rename the original project file to <original name>.ORG in the same folder. This creates a backup file.
4. Rename the temporary file to the name of the original project file <original name>.GPJ. For example, when you have converted "PROJECT1.GPJ", then "PROJECT1.GPJ" will be the new file and "PROJECT1.ORG" will be the original file.
5. Remove the file name from the Source Files list and add it to the Converted Files list, appending "OK" if the conversion was successful, "Failed" if there was a fatal problem (such as not being able to open the file,) or "Cancelled" if Cancel was clicked during a conversion.
6. Display a full report after all files have been converted.