Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Datgel
DGD Tool
DGDT-UG-002 - 4.01.4
July 2018
Disclaimer
The information in this publication is subject to change without notice and does not represent a commitment
on the part of Datgel Pty Ltd. The software described in this document is furnished under a license
agreement or nondisclosure agreement. The software must be used or copied only in accordance with the
terms of the agreement.
Every effort was made to ensure accuracy of this information. However, Datgel Pty Ltd makes no warranty as
to the correctness of this information or the supplied files.
Printed in Australia. All rights reserved worldwide. No part of this publication may be reproduced in any form
or by any means without the prior written consent of Datgel Pty Ltd. Comments are welcome and become the
property of Datgel Pty Ltd.
Email: info@datgel.com
Website: https://www.datgel.com/
Contents
About Datgel DGD Tool ...................................................................................................... vii
Key Features................................................................................................................................. vii
New in Version 4 ........................................................................................................................... vii
Editions ......................................................................................................................................... vii
About this Document .......................................................................................................... ix
System Requirements .................................................................................................................... ix
Software ....................................................................................................................................................... ix
Hardware and Operating System ................................................................................................................. ix
Required Windows Components .................................................................................................................. ix
Conventions and typography used in this guide ............................................................................ ix
Field Colours ................................................................................................................................... x
1 Installation and Basic Configuration ............................................................................ 1
1.1 Components of the gINT – DGDT System ............................................................................1
1.2 Installation .............................................................................................................................2
1.2.1 For a fresh installation of gINT and the Tool ................................................................................ 2
1.2.2 For an upgrade to an existing installation: .................................................................................... 2
1.3 Product Compatibility Upgrade ..............................................................................................2
1.3.1 Scenario 1: you do not have privileges to do the upgrade. .......................................................... 3
1.3.2 Scenario 2: you do have privileges to do the upgrade. ................................................................ 3
1.4 File Types and Locations ......................................................................................................4
1.4.1 General file locations .................................................................................................................... 4
1.4.2 *.GLB - Library ............................................................................................................................. 4
1.4.3 *.GPJ - Project Database ............................................................................................................. 4
1.4.4 *.GDT - Data Template ................................................................................................................ 4
1.4.5 *.GDW - Drawing.......................................................................................................................... 4
1.4.6 SETUP.GSH ................................................................................................................................ 5
1.4.7 *.GCI / *.GCX – Import/Export Correspondence .......................................................................... 5
1.4.8 *.GSC – Script .............................................................................................................................. 5
1.4.9 *.DTY – Coordinate File ............................................................................................................... 5
1.4.10 *.GAS – gINT AGS Schema ......................................................................................................... 5
1.5 Configure Optimal System Properties ...................................................................................5
2 Input ............................................................................................................................ 7
2.1 Make a new Microsoft Access format Project ........................................................................7
2.2 Database Structure ...............................................................................................................7
2.3 Logo ......................................................................................................................................8
2.4 Importing Pre-Existing Data from Old Project Structure ........................................................8
2.5 General Data Entry................................................................................................................8
2.6 Log output option fields .........................................................................................................9
2.6.1 Metres per page ......................................................................................................................... 10
2.6.2 Break depth and between non cored and cored logs ................................................................. 10
2.6.3 Display end of hole remark above depth to avoid overlaps ........................................................ 10
2.6.4 Optional manual override for column on right of logs ................................................................. 10
2.6.5 Rock Fracture Data representation on logs ................................................................................ 10
2.7 SPT Data.............................................................................................................................11
2.7.1 Correlations ................................................................................................................................ 12
2.7.2 Output ........................................................................................................................................ 14
2.8 Point Load Test (Is(50)) .........................................................................................................14
2.8.1 Manual Data Entry ..................................................................................................................... 14
2.8.2 Point Load Test Form Add-In ..................................................................................................... 15
2.9 Dynamic Cone Penetrometer (DCP) ...................................................................................16
2.9.1 Input ........................................................................................................................................... 16
2.9.2 Output ........................................................................................................................................ 19
2.10 Lists ................................................................................................................................19
2.11 Option Tables .................................................................................................................21
2.12 Specification ...................................................................................................................23
2.13 Site Maps .......................................................................................................................23
2.13.1 Importing DXF files ..................................................................................................................... 23
2.13.2 Referencing ECW files ............................................................................................................... 24
2.14 Alignments......................................................................................................................24
Figures
Figure 1 – INPUT with tree and tab navigation ........................................................................................ 7
Figure 2 – Graphical Data Input............................................................................................................... 9
Figure 3 – POINT table log output option fields ......................................................................................... 9
Figure 4 – SPT Test Tables ................................................................................................................... 11
Figure 5 – Point Load Test Table .......................................................................................................... 15
Figure 6 – DCP by Depth Example........................................................................................................ 17
Figure 7 – DCP by Depth Result and Refusal Example ........................................................................ 17
Figure 8 – DCP by Blow Example ......................................................................................................... 18
Figure 9 – DCP by Blow Result Example .............................................................................................. 19
Figure 10 – Lists group .......................................................................................................................... 20
Figure 11 – PROJECT_OPTIONS ............................................................................................................... 21
Figure 12 – POINT_OPTIONS.................................................................................................................... 22
Figure 13 – Specification group ............................................................................................................. 23
Figure 14 – Site Map application with referenced ECW file and imported DXF ..................................... 24
Figure 15 – Alignments table ................................................................................................................. 26
Figure 16 – Site Map application with two Alignments........................................................................... 27
Figure 17 – Fence Drape showing a seismic section ............................................................................ 28
Figure 18 – TIN Surface ........................................................................................................................ 30
Figure 19 – Lab Data Entry form ........................................................................................................... 34
Figure 20 – Lab Analysis Tables ........................................................................................................... 44
Figure 21 – Specification Tests Table ................................................................................................... 45
Figure 22 – Moisture Content Table showing the Specification Fields .................................................. 45
Figure 23 – PSD Table showing the Specification Fields ...................................................................... 46
Figure 24 – Convert Projects ................................................................................................................. 87
Figure 25 – Import from AGS File .......................................................................................................... 88
Figure 26 – Export to AGS File .............................................................................................................. 89
Figure 27 – Editing AGS Files in Excel® ............................................................................................... 90
Figure 28 – DG_COM_OFFICE .................................................................................................................. 94
Tables
Table 1 – Field Colours ............................................................................................................................x
Table 2 – SPT Supported Test Methods ............................................................................................... 11
The Datgel DGD Tool (DGDT) extends the capability of gINT for geotechnical, contaminated land and
hydrogeological site investigations and geotechnical lab result storage, and reporting, and is also the
native database for Datgel's tools.
Key Features
Longer, understandable table and field names
Support for AGS 3.1, AGS 3.1(SG), AGS 3.1 RTA 1.1, AGS 4, AGS 4 NZ
AS, ASTM, BSI and NZGS logging standards and component description; Can support all of
these using one library and data template, hence one system can be used in many countries
using different standards
Over 300 reports for in situ and lab reporting: log, fence, summary graph, histogram, table
reports, and maps
DLL Program with:
Calculations for SPT, core, soil classification, and borehole related validation
Point load test data entry and calculations
PI and LI calculations
Lab Data Entry Form - easy data entry of simple lab results
Multiple productivity tools to make your data entry task easier
DCP pre-population and calculation of correlations for CBR and bearing capacity
Show/hide tables based on usage scenario
Import tool
Excel export tool
Soil/rock mass classification
Processing and querying of 3D surfaces, alignments and tidal data
New in Version 4
AS 1726 2017 support
QLD TMR Geotechnical logging Standard lookup lists
New Reports
Specification check and examples
Design Line on parameter RL/depth graphs
SPT calculation options
Review and fixes to support SQL Server
Auto populate bottom fields from previous record’s depth
Calculate sample’s recovered length
Editions
Logs Edition - entry level product ideal for user with gINT Logs, or for field data collection using
gINT. Only log reports and program features directly related to logging are included. AGS
format support not included.
This document version was written for Datgel DGD Tool gINT Files version 3.11, Datgel DGD Tool DLL
version 3.0.10 and gINT version 8.30.04.285 or later.
Related documents
Bentley gINT User Guides, installed with gINT and stored in this folder:
C:\Program Files (x86)\Bentley\gINT V8i\docs
Datgel Fence and Map Tool User Guide
Extensive range of fence reporting option based on the DGD database structure. Dynamically
defined scale bars on both fence and map reports. Dynamically defined fence post and map
data marker legends. Pages sizes ranging from A4 to A1
Procedures for Checking AGS (SG) Data
Describes checking and review procedures for AGS Format data
Datgel Administration Tools User Guide
Tools for gINT Administrators and Power Users: Convert Tool, Export Tool, Find or Set
Properties Tool, SQL Tool, Lookup List Check Tool, Import Tool, and AGS Format Tool
Support
For technical support please email support@datgel.com, call +65 6631 9780 or +61 2 8202 8600, other
phone numbers are listed on https://www.datgel.com/contact.
System Requirements
Software
The product runs optimally using gINT Logs, gINT Professional or gINT Professional Plus,
version 8.20.800.00 (2/Jul/2010) or higher. However, with gINT Logs you may only output log
reports
Datgel DGD Tool DLL program version 4.0.0 or higher
Code sample Indicates a sample program codes inserted in user guide e.g.
public override string ToString ()
File name or path Used for formatting file name and paths e.g. abc_lib.glb or
V:\10 gINT\Datgel Install Files\
Database table name, e.g. POINT_TABLE.
Table_Name
Field Colours
Each of the fields in the project tables have been coloured to improve the data entry process as
indicated below in Table 1.
Pastel Green Calculated Field – data is written to this field by Datgel’s code
Data Entry Field – data should be entered into this field, or data
Pastel Beige
in this field influences the calculation
Legacy Data Field – historic data entered here, is typically from
Pastel Red
an old database
Pastel Blue Output Option – used to control how data displays on a report
Grey Read-only
1. gINT Professional Plus, gINT Professional or gINT LogsV8i: Application installed on client
PCs
2. SQL Server – optional if using gINT Professional Plus
a) This hosts the gINT SQL Server database(s)
b) If SQL Server is not available, gINT uses Microsoft Access database(s) that are provided
with it
3. Custom gINT Files: Customised configuration files stored on a file server and used by the
gINT application
a) Library: dgdt-<p or l> 4.## lib.glb
b) Project Files (Access format, *.gpj) – Access format files stored on file server with other
project related files
f) gINT Civil Tools Database Connectivity and Mapping: dgdt-p #.##.# gct ##.xml
g) Excel Export Tool
i. Datgel Excel Export Tool ##.xlsx
1.2 Installation
In addition to the following section this blog maybe useful: https://www.datgel.com/installation-and-
quick-start-for-gint-and-datgel-gint-add-ins
1. gINT v10 Connect Edition – see question How do I install gINT v10 Connect Edition? on
https://www.datgel.com/gint-faq.
2. Datgel DGD Tool program. To install, run the setup.exe. After installation, validate or
activate the user license as described in Chapter 2 of the Datgel Product Licensing System
User Guide.
The custom gINT Files (*.gpj, *.gdt, *.glb, *.gcx, *.gci, *.gas) should be stored on your
organisation’s file server and backed up daily.
Place the *.gdt, *.glb, *.gcx, *.gci and *.gas files in a non-project specific folder on your file
server, for example R:\gINT\
Now open gINT, and open the dgdt lib 4.##.glb Library, using command File > Change Library.
Then open the example project database dgdt 4.##.gpj.
If you are the first to use this set of gINT files in your company, you will need to apply further
configuration. Refer to section 20 Configuration.
1. gINT Professional Plus V8i package only, assuming the 3 dependencies were previously
installed.
2. Datgel DGDT program. To install, run the setup.exe.
Customise gINT user files:
1. If you only made trivial changes to the last version of the library and project, such as applying
your logo and office, it will be a simple process to merge the library objects into the new library
and apply the default value again to the Project.Office field.
2. If more in depth changes were made, please contact Datgel for specialised advice.
3. Click OK.
4. Advise your system administrator that the upgrade is needed.
Note: You might be able to continue working without the upgrade, but the products could be unreliable
1. Click Yes.
The procedure must be completed by a user that has administrative privileges for the PC.
The software makes a backup copy of the existing gINT configuration file and inserts the
changes Datgel software needs.
The following message is displayed if the process completes successfully.
Note: If you experience any difficulties in applying this procedure please contact Datgel’s support team.
Location: The Library File property in System Properties sets the location and name of the current
library. This can be viewed and changed with File > System Properties or File > Change Library
menu item in any application.
Location: The default folder is specified in the Projects property of the File > System Properties menu
item. However, you can move them.
Location: The default folder is specified in the Data Templates property of the File > System
Properties menu item. However, you can move them.
1.4.6 SETUP.GSH
This file contains the information shown in the File > System Properties dialog, and stores the user
settings along with previous current project, PointID, page from each application, and the recent file
lists.
Location: The default folder is specified in the Data Template property of the File > System Properties
menu item. However, you can move them.
Location: The default folder is specified in the Scripts property of the File > System Properties menu
item. However, they can be located anywhere.
Location: The file location is specified in the Custom Coordinate property of the File > System
Properties menu item.
1. Select INPUT | File > New Project or the (new) icon > Clone Data Template…
2. Browse to the data template dgdt 4.##.gdt, and click Open
3. Name the new project file, and click Save
See section 20.2 Configuring Logos in the Library for further details.
ags 3.1 rta 1.1 06.2 gint db to dgdt-dlst #.## ##.gci – use with database
import to import a AGS RTA project database into a DGDT project database.
gint std ags 3.1 w lab tables to dgd-dlst #.## ##.gci gci – use with
database import to import a gINT standard AGS 3.1 project database into a DGDT project
database.
gint std australia to dgd-dlst #.## ##.gci gci – use with database import to
import a standard Australia gINT project database into a DGDT project database.
You can use these with the following gINT features:
To change the report you are working on, go to File > Select Report for Input. To change PointID
when in Graphical Data Input, double-click anywhere on the log image to bring up the grid sub form,
then click Select PointID to bring up the PointID list, then select the desired PointID.
2.6.2 Break depth and between non cored and cored logs
POINT.Depth Borehole / Corehole Break: Depth at which borehole stops and core hole begins; If the borehole
contains core only then set this field to 0, if the borehole has non-core only then leave this field blank.
Applies to:
Log | IS AU BOREHOLE 1
Log | IS AU BOREHOLE 2
Log | IS AU BOREHOLE 3
Log | IS AU CORED BOREHOLE 1
Log | IS AU CORED BOREHOLE 2
Log | IS AU CORED BOREHOLE 3
Log | IS NZ BOREHOLE CONTAM 1
Log | IS NZ DRILLHOLE 1
Log | IS NZ DRILLHOLE 2
Log | IS UK BOREHOLE
Log | IS UK DRILLHOLE
If you use a test method that records three intervals, then enter the results in columns 1, 3, and
5.
Default Penetration interval values are set on the PROJECT table in fields Default SPT Pen 1 3 5
and Default SPT Pen 2 4 6. For AS/ASTM set the former to 150 and later blank, and for BS set
both to 75.
The N Value and Reported Result fields both must be empty for the basic SPT calculation to take
place. The N60 calculation will take place regardless as long at the N Value is defined or
calculated.
The calculation for N Value and Reported Result fields have options defined on Project Options:
o SPT Sample Type: Sample Type used when auto generating Sample table record for an
SPT with recovery
o SPT N Value Refusal: Blank for nothing, or set a number such as 50 or 100
o SPT Reported Result N value Refusal: select from a drop down list of syntax: N=R, N>50,
N>100, or N=##/##mm
o SPT Reported Result Length Unit: Select from a lookup list of m, cm or mm
o SPT Star Suffix for Recovery: Check to populate Reported Result with N* when Recovered
Length is > 0
Pore Pressure, Total Stress and Effective Stress are calculated based on the Depth and data
entered in the Project Options and Point Options tables.
Table 2 – SPT Supported Test Methods
Standard Description
AS 1289.6.3.1-2004 Determination of the penetration resistance of a soil - Standard penetration test (SPT)
BS1377-9:1990:3.1 Standard Penetration Test
1. Enter the Top depth of the test and select the Type of test undertaken.
2. If you enter the Recovered Sample Length, a Sample table record will be created corresponding with
the SPT test depth range.
3. For the British Standard method:
a) Enter the Self Weight Penetration, i.e. the penetration under the rod and hammer weight.
b) Enter the blow count recorded for each increment in the applicable blows field (Blows 1st,
Blows 2nd, Blows 3rd, Blows 4th, Blows 5th and Blows 6th).
c) Each increment penetration field (Pen 1st, Pen 2nd, Pen 3rd, Pen 4th, Pen 5th and Pen 6th) is
automatically populated with a default value of 75 mm and this can be overridden with the
actual increment penetration value for each respective blow count.
Note: N Value and Reported Result must be empty for the row to calculate
5. If you have entered data on the In Situ Point Options and / or In Situ Project Options tables, then the
Total Stress, Effective Stress and CN fields will be automatically calculated when you change table
or click save (Ctrl+S).
6. To calculate the N60 and (N1)60 values, see the following detailed explanation below in Section
2.7.1.
2.7.1 Correlations
The primary reference for the N60 and (N1)60 calculations was Skempton (1986). Table 3 has been
reproduced from the paper and presents the correction values used the in the N60 and (N1)60
calculations.
These correction values are each stored in the library file and; depending on the data entered into the
Hammer Type, Borehole Diameter, Sampling Method and Rod Length fields; the appropriate value from the library
table will be written to the corresponding CER, CB, CS, and CR field and used to calculate the N60 and
(N1)60 values, when you change table or click save (Ctrl+S).
𝐶𝐸𝑅 ∙ 𝐶𝐵 ∙ 𝐶𝑆 ∙ 𝐶𝑅 ∙ 𝑁
𝑁60 =
0.6
𝐼𝑓 𝑧 ≥ 𝑧w 𝑡ℎ𝑒𝑛 𝜎𝑣𝑜 = 𝑧w ∙ 𝛾 + (𝑧 − 𝑧w ) ∙ 𝛾𝑠
Where:
𝑧ω is Groundwater Depth on the In Situ Point Options table (or In Situ Project Options table if there is no
value on the In Situ Point Options table)
𝛾 is Bulk Unit Weight on the In Situ Point Options table (or In Situ Project Options table if there is no value
on the In Situ Point Options table)
𝛾𝑠 is Bulk Unit Weight Saturated on the In Situ Point Options table (or In Situ Project Options table if there is
no value on the In Situ Point Options table)
Where:
𝑧ω is Groundwater Depth on the In Situ Point Options table (or In Situ Project Options table if there is no
value on the In Situ Point Options table)
𝑔 is Gravity
The Overburden Correction Factor (CN) proposed by Liao and Whitman (1986) is defined as:
100 0.5
𝐶𝑁 = ( )
σ′vo
SAMPLE record, typically the core run which is automatically created when data is entered in the
CORE table.
SPECIMEN record. Select the correct Sample record on the top half of the screen, then on the
bottom half of the screen enter the depth of the Is(50) test(s). Later you will see that multiple
Is(50) tests may be entered for the one depth.
Lab-Rock | Point Load Test record. Enter data such as Test Method, Tested By, and Tested Date.
Now on the bottom half of the screen enter multiple tests with different Test Numbers. You may enter just
the Test Type and Is 50 value or you can enter the relevant brown fields and the green/green-brown fields
will calculate.
Standard Description
ISRM Part II:1985:6 Suggested Method for Determining Point Load Strength
To calculate the Is(50), you must first select the standard from the Test Method field on the Point Load table
that the specimen is being tested against.
Enter the test data in the data entry fields in the lower table and click Save, Ctrl+S or change table to
initiate the calculation. The values will be calculated automatically and the result will be displayed in the
calculated fields.
The field Number to Exclude from Is50 Mean on Point Load Test (upper) table defines the number of highest and
lowest values to exclude from point load strength test mean (eg. If Number to Exclude from Is50 Mean is 2,
the two highest and the two lowest values will be excluded for the mean calculation). The excluded
tests are shown in the Exclude From Mean check box.The net mean is written to the Point Load Test (upper)
table.
Moisture contents for each specimen are recorded in the Moisture Content table.
To Launch the Tool go to INPUT and select the command Add-Ins > Datgel DGD Tool > Point Load
Test Form.
The following form will then show. Select the PointID for the Point Load test results and you can view
the Point Load test results for this selected PointID. You can also add a new Point Load test result for
this PointID by entering the test result in the last row.
After entering a Specimen Depth, the code will define the relevant parent Sample based on the Sample
Top and Bottom values and Test Number.
After you have entered the new values, click the Update button in order to save the changes into the
database.
2.9.1 Input
IS-Comp Rel | DCP
Standard Description
AS 1289.6.3.2-1997 Determination of the penetration resistance of a soil - 9kg dynamic cone penetrometer
test
AS 1289.6.3.3-1997 Determination of the penetration resistance of a soil with a Perth sand penetrometer
BS 1377-9:1990:3.2 Determination of the dynamic probing resistance using the 90° cone (dynamic probing
DOP)
RTA T161 Penetration Resistance of a soil (Dynamic Cone Penetrometer - 9kg mass)
You can have many tests in one PointID, and tests can start at any depth. The test start Depth below
ground level is entered on top half of screen. The Penetration Top/Bottom are relative to the test start Depth.
Note that although we can enter many tests in one PointID, the log reports are not designed to deal with
this.
Note: The Meta data fields, such as Hammer Mass, only calculate when the given field is empty and there
are no records in the bottom half of the screen for that test.
2.9.2 Output
Logs | IS AU BOREHOLE 3
Logs | IS AU TEST PIT 3
Logs | IS AU PAVEMENTS 1
Logs | S AU PAVEMENTS 2
Logs | IS DCP
Logs | IS DCP 3 PER PAGE
Logs | IS DCP WITH TEXT AND PLOT
Logs | IS NZ SCALAR PENETROMETER
Logs | IS NZ TEST PIT HAND AUGER 1
2.10 Lists
Lists that you expect to vary between projects are stored in the Lists table group. More fixed lists are
stored in the library, as Lookup Lists, Library Data, and Symbols of various types.
Figure 11 – PROJECT_OPTIONS
The Graphic_Log fields control which graphic source will be used on log reports, the options are:
gINT only supports the import of DXF files saved in the AutoCAD Version 12 DXF file format.
To import a site map, first move to the Site Maps group, then select File > Import/Export > DXF
Import, and browse to the DXF file to import.
Assuming that the information in the original DXF file was stored on separate layers, you can use the
(Layer) button or the Modify > Layer menu item to display a list of the layer properties. From the
window that is displayed, you can choose to Hide, Lock, change the Colour of the entities on a
particular layer or Delete the entire layer; with the exception of Layer 0 which cannot be hidden or
deleted.
gINT only supports geocoded images that are in the Enhanced Compression Wave (ECW) file format.
Use the Site Maps group to reference a Geocoded Image. Select File > Import/Export > Import
Geocoded Photo, and browse to the ECW file to reference.
You can edit the properties of the image, such as the Print Order or the Layer it is stored on, by double
clicking on it to bring up the properties window. Once you have completed any required changes, click
OK to save the changes (or Cancel to undo any changes) and to return to the Site Map view.
Alternatively, a less convenient way to display images in site map is using the menu item Draw >
Graphics > In Place Bitmap Symbol….
Figure 14 – Site Map application with referenced ECW file and imported DXF
2.14 Alignments
Alignment data can be used on the Fence Reports, and to calculate chainage/offset from East/North for
PointIDs.
gINT only supports alignments that are in the LandXML, Excel or CSV file format.
To import an alignment, you should move to the Alignments table. Then select File > Import/Export >
Import Alignment, and select the xml file to import.
The Alignment (upper) table contains the general information about the alignment. After an alignment
has been imported, you can add additional attributes for it by selecting or entering values into the
Description, Initial Station, Alignment Line Type, Alignment Line Thickness, Alignment Line Colour and corresponding
“Z” fields.
The “Z” lines are optionally associated with each alignment and allow for the storage of a vertical profile
along the alignment. These line thicknesses are by default stored in millimetres, but you can override
this by checking the Line Thickness in inches field. If you do not want to display the alignment line on your
site maps, check the Do not display on Site Maps field for the relevant alignment.
The Alignment (lower) table contains the Northing and Easting values of the alignment and up to 3
optional Z values. The Station, AKA Chainage, field is read only as it is automatically populated by gINT
and it records the distance along the alignment, based on the Initial Station value in the Alignment (upper)
table.
The Z fields could hold the vertical alignment, natural ground surface, or invert of a tunnel. This data
also displays on the fence reports.
2.15 Drapes
Fence Drapes are vertical planes in 3D space, hence when viewed in plan appear as a polyline. They
are commonly used to store a geophysical interpretation or a vertical profile drawing along a linear
structure, and can be displayed as a projected onto a 2D Fence output. They are stored in the Input |
Fence Drapes group and there is no limitation on the number of drapes that can be stored in a project
file.
Before trying to import a Fence Drapes into gINT, verify that the Fence Drapes module has been
enabled. Select the Additional Modules menu and confirm there is a next to the Fence Drapes
Support item.
Fence Drapes are a gINT Drawing object (such as an imported DXF file or image) that is stored in the
project file and they are defined by a name, and the coordinates of the Drape line in plan or an
associated Alignment. To add a Fence Drape to your project file, select the Input | Fence Drapes
group and click the (new) icon, or select File > New.
You should then enter a Name for the Drape and either:
the Coordinates (as a series of East and North values) and optionally specify the Initial Station
if required; or
choose an Alignment if one already exists in your project file. This option has the advantage
that the alignment is displayed in the site map, which most users will prefer.
The Page Size and Orientation properties are only used if printing directly from with the Drapes
application.
The drapes themselves are drawn in the same way you draw any gINT Drawing object, however the
scales differ:
2.16 Surfaces
Before trying to work with Surfaces in gINT, verify that the Surfaces module has been enabled. Select
the Additional Modules menu and confirm there is a next to the Surfaces Support item.
The Surfaces group allows you to store surface definitions, such as the ground surface level, geological
unit boundaries, finial design elevation and piezometric surfaces. gINT supports both grid surfaces and
TIN or DTM surfaces.
Grid surfaces can’t be generated within gINT, however data used to generate a surface representing
the top of a geological unit can be exported. TIN surfaces can be generated by gINT using INPUT |
Additional Modules > DTM to LandXML…, and the generated XML file can be imported into
Surfaces.
Further information can be found on how to do this via the gINT Help file; Help > Index. Enter “Export
Contouring Data” in the keyword field.
If you have already created a surface grid file, you can import it into your gINT project file.
In the simplest form the grid may be imported from a delimited XYZ file. The grid needs to be
rectangular, orientated N-S/E-W, have no holes, and be perfectly regular. Grid nodes with no data
must be set to 1E10 or greater.
To add a Surface grid to your project file, use the Input | Surfaces group and click the (new) icon, or
select File > New.
1. Enter a Name for the surface grid and optionally add a Description.
2. Select the Line Type, Enter a Thickness (in inches) and select a Line Colour
The thickness of the line is in inches, and a value approximately 0.01 is appropriate.
3. Click the Import Grid File button to open a Windows Explorer window; where you should
browse to the location of the grid file
4. Click OK to import the surface file
To add a Surface grid to your project file use the Input | Surfaces group and click the (new) icon, or
select File > New.
1. Enter a Name for the surface TIN and optionally add a Description.
2. Select the Line Type, Enter a Thickness (in inches) and select a Line Colour
The thickness of the line is in inches, and a value approximately 0.01 is appropriate.
3. Click the Import TIN File button to open a Windows Explorer window; in which you should
browse to the location of the TIN file
4. Click OK to import the surface file
3.1 Activation
A license must be activated for these functions to run. Normally a network USB hardware type license
is provided. Please refer to Datgel’s fulfilment email to determine your license status.
Validation that depths do not exceed the Hole Depth on most borehole data related tables
Validation that specimens lay within a sample range
Calculation of specimen description and PSD statistics based on PSD and Atterberg data to
multiple classification standards. Occurs upon save on Specimen, Atterberg, Sieve and
Sedimentation tables.
Population of Bottom data from previous record’s Depth data on STRATA_MAIN,
STRATA_DETAILS, SAMPLE, SPECIMEN, DEPTH_REMARKS, IMAGE, CEMENTATION,
CONSISTENCY_DENSITY, MOISTURE_CONDITION, METHOD, PENETRATION_RESISTANCE,
ROTARY_FLUSH, CHISELLUNG, DRILLING_PARAMETERS, WATER_ADDED, IN_SITU_STRESS, CORE,
ROCK_STRENGTH, WEATHERING, FRACTURE, DEFECT, CORE_LOSS, RMR, GSI, ALTERATION,
ROCK_MAS_WEATHERING, DURICRUST_MASS_GRADE.
Calculation of Sample and Specimen Top and Bottom Elevations and Sample Disposal Date.
Calculate the Sample_Recovered_Length (controlled by Populate_Sample_Recovered_Length in
Project_Options table). Only works for the new fields and it does not override existing data.
Create a new Specimen for each sample if Specimen record does not exist (controlled by
Create_Specimen in Project_Options table).
Calculation of SPT data based on raw readings, including N, reported results with options
configurable on PROJECT_OPTIONS, N60 and (N1)60
SPT design line
Calculation of TCR, SCR and RQD values in Core table data based on measured data
Calculation of DCP data, and correlations of CBR and bearing capacity
Calculation of Point Load Test data
Calculation of Data Marker and colour on the POINT table
Calculation of STRATA_MAIN.3d_Cylinder_Colour based on configuration on GEOLOGY_UNIT_1
Auto pre population of CONSISTENCY_DENSITY and MOISTURE_CONDITION tables with the depth
ranges on the STRATA_MAIN table if the table is empty. Unused records will be removed on
save.
Calculation of In_Situ_Pore_Pressure, Total_Stress and Effective_Stress for SPECIMEN table records
Calculation of Liquid_Limit and Liquidity_Index on LAB_SOIL_ATTERBERG
Validation of Colour data on STRATA SOIL AS, STRATA ROCK AS, STRATA SOIL BS and AS STRATA
ROCK BS tables
Point Load Test Form: Allows you to efficiently enter Is50 results.
Pre-populate Lab Data Entry Table: Provides the user with an option to efficiently enter and
edit multiple lab results in one table interface.
Import Tool: Imports data to a project database using correspondence files.
Excel Export Tool: Allows you to export the data to a formatted excel file.
Field and Lab Description Comparison: With this Add-Ins the user obtains a comparison
between the Field material description and the Laboratory material description.
Calculate all Specification Check: using this Add-Ins, all Specification Check fields will be
calculated.
Rock UCS Average Calculations: With this Add-In, for each UCS test, an average of the test
results performed in a selected distance from the UCS test will be calculated (CaCO3, PLT and
Dry Density).
Material Mass Classification Tool: Streamlines the classification of material based on a user
defined classification system with up to three parameters.
Set Coordinate Chainage Offset: Calculates the coordinates/chainage/offset for records from
a pre-defined alignment name, chainage, offset and coordinates, or vice versa.
Set Elevation or Depth from Surface: Sets an elevation or depth field of a project table in
gINT from values in a gINT surface based on the PointID's East and North.
Set Seabed Elevation: The Seabed Elevation Tool allows the user to calculate seabed
elevation for each PointID based on water depth and tidal information.
Surface File Pre-process: Edits and corrects grid files before they are imported into gINT
Surfaces.
Fracture Spacing From Defects: copy data from Defects table to Fractures table.
Populate Bottom: Population of Bottom data from previous record’s Depth data.
Populate Hide Scenario Library Tables: User configurable INPUT interface.
Settings: This forms manages the DGD Tool software exception logging options.
Licensing: In this command you can manage the license configuration.
About: This command will display information about the DGD Tool product.
The Colours and Data Markers that are assigned are selected from two configurable gINT Library
Tables, DG_COM_USEABLE_COLOURS and DG_COM_USERABLE_DATA_MARKERS. To configure the list,
select DATA DESIGN | Library Data, the select the table name from the yellow drop down list.
When assigning new Colours/Data Markers, the Assignment calculation selects the least used
Colour/Data Marker to distribute the Colours/Data Markers as evenly as possible. If there is more than
one least used Colour/Data Marker, the first item when ordered alphabetically is selected.
To print a list of Colours and Data Markers in the current gINT Library, select UTILITIES > Print Object
Units, then select Colour and Data Marker as the Objects to Print.
It may be more appropriate to store Table Reports that are specific to certain projects in the Project
(project table XXX and YYY). For Table Reports that are used reguarly for multiple projects it may be
more appropriate create them in the Library.
Suite Parameter
Moisture Content Suite Moisture Content
Moisture Content Suite Natural Moisture Content
6.4.3 Defining what can be selected for use in the custom reports.
The columns that will appear in the report table can be either Parameter or Suites. Once both the
Parameters and Suites have been created, you will need to define the column types.
Item Key
Moisture Content Report
XML Configuration File: the file name and path to the XML configuration file which contains the
configuration information related to writing to the Excel file and extracting the data from the gINT
database. Browse to the XML file by clicking on the button on the left of this field, or by typing the full
file path in the field. The XML file ExcelExport.xml will have been provided to you. It is recommended
that you place this file on your server and that all users browse to this file, so that in the event the XML
file is updated the XML file on the server can be updated so that all users will be using the updated file.
Template Excel File: the file name and path to the Excel workbook you wish to use as the template for
the exported Excel file. The first worksheet in the template Excel workbook will be used as the template,
and will be copied into each new worksheet created in the exported Excel file. Browse to the Excel file
by clicking on the button on the left of this field, or by typing the full file path in the field. As with the XML
Configuration File, it is recommended that this file is stored on the server and all users browse to this
file.
Target Excel File: the file name and path to the Excel workbook where the data will be extracted to. If
you define an existing Excel file, the file will be overwritten. Browse to the Excel file by clicking on the
button on the left of this field, or by typing the full file path in the field.
Open Excel after export: If checked, Excel will be launched at the end of the export process and the
target Excel file will be opened. Useful if you wish to review the exported data.
Export: starts the export process. If the data exceeds the number of rows in the template worksheet,
then a new copy of the template worksheet will be added in the workbook and the data will continue to
write to this worksheet and so on. The status text and status bar will inform you of the progress.
Use the following codes in the SQL Statement in place of indicated characters.
& &
< <
> >
Library name and path ~LibFileSpec~
9.1 Tables
Note: Strata Main.Lab Description Comparison must be empty for the row to calculate
The Add-In will calculate and populate all records on the Lab Description Comparison field on the Strata Main
table for all points that have data in the fields Strata Main.Classification Symbol and in Specimen.Classification
Symbol.
The Specification (upper) table is used to define the metadata and the specific values that each lab test
can be compared against. The Data Marker and Colour fields can also be defined; however it should be
noted that these are not linked to the envelopes on the PSD graph reports.
Based on the defined specification, a P (Pass), F (Fail) or N (Not applicable) result will be displayed in
the Specification 1 and Specification 2 fields on most of the lab test tables.
To calculate all the Specification Test Results, select Add-Ins > Datgel Lab and In Situ Tool >
Calculate All Specification Tests.
10.6 Output
The results of Specification / Specification Material checks are displayed on all applicable lab test report
sheets in the Datgel Lab and In Situ Tool.
11.1 Data
To use the Add-In the offset value must be specified. Select INPUT and go to Project Options and set the
value of the offset in field Parameter Averaging Offset.
This Add-In calculates the average of the following test results: Carbonate Content, Point Load Test
and Dry Density. This results must be populated in Carbonate Content.Carbonate Content CaCO3, Point.
Load.Point Load Strength and Porosity and Density.Dry Density fields.
11.2 Usage
Run the Add-Ins > DGD Tool > Rock UCS Average Calculation.
The calculated values will be populated in table UCS & Deformability table, in fields CaCO3 Average Offset,
Point Load Index Average Offset and Dry Density Average Offset.
If your parameter is a term like rock strength, e.g. EL or VH, then the lookup must be a library or project
table, and must have an Order field. The order field would normally be an integer or double type, and
be populated for each row of the lookup table.
Once you have defined the required Parameters, you must then also define the target where the
material classification will be written to.
In the following example, the material classification is defined to be written to the Material Mass
Classification Units table.
Note: Comparisons are NOT case sensitive; stings are converted to upper case and then compared.
The Like and Not Like comparisons accept the same syntax as the gINT Software Like (function)
defined in the gINT on Line Help.
Following is an example of 1 Classification Zone that has been defined with 3 parameters:
Parameter 1 Criteria 2 Operator These have been left blank as there is only
Parameter 1 Criteria 2 Value one criteria being assessed for Parameter 1
Parameter 2 Criteria 1 Operator >= The value in the Minimum field in the Rock
Strength table must be greater than or equal to
Parameter 2 Criteria 1 Value EL EL
Parameter 2 Criteria 2 Operator <= The value in the Maximum field in the Rock
Parameter 2 Criteria 2 Value VL Strength table must be less than or equal to VL
Parameter Criteria 1 Operator >= The value in the Minimum Fracture Spacing field in
the Fractures table must be greater than or
Parameter 3 Criteria 1 Value 0 equal to 0
Parameter Criteria 2 Operator < The value in the Maximum Fracture Spacing field in
Parameter 3 Criteria 2 Value 100 the Fractures table must be less than 300
To complete the classification, each Zone that is required must be specified, as indicated in the
following example:
Note:
Any existing data in the Target table for the applicable PointIDs will be DELETED.
The first zone that satisfies the criteria will be used. Zones are ordered by Zone ID, but this is a string
hence it is ordered 1, 10, 2, 3... If this is a problem, then name Zone IDs with padded zeros, e.g. 01
Sand, 02 Sand clayey, etc.
Set Coordinate Chainage Offset Tool: Calculates the coordinates to/from chainage and
offset based on alignment data.
Set Elevation or Depth from Surface Tool: Sets the depth or elevation for a range of table
structures from 3D surfaces.
Set Seabed Elevation Tool: Calculates seabed elevation for each point based on water depth
and tidal information.
Grid File Pre-processing Tool: Pre-processes surface files to produce perfect grids, slice up
over sized grids, invert elevations and replace null values.
On this screen:
Name column: Name for each Set Coordinate Chainage Offset process. Ensure the name for each row
is entered and not duplicated. The name is used to uniquely identify each row
X Field column: A drop down list of all the fields in the POINT table, defines the field name of the X, or
East field.
Chainage Field column: A drop down list of all the fields in the POINT table, defines the field name of
the Chainage field.
Offset Field column: A drop down list of all the fields in the POINT table, defines the field name of the
Offset Field.
Alignment Field column: A drop down list of all the fields in the POINT table, defines the field name of
the Alignment field.
Direction column: A drop down list with two options to calculate Chainage/Offset or East/North for
each PointID on POINT table. Select “Ch/OS to XY” if you wish to calculate East and North values and
select “XY to Ch/OS” if you wish to calculate Chainage and Offset values.
Offset Orientation column: A drop down list with two options to define offset orientation. Select “+ve
left, -ve right” option if on the left of the chainage line is positive and select “-ve left, +ve right” option if
on the left of the chainage line is negative.
Calculate column: This is used to indicate whether to calculate Coordinate Chainage Offset or not
after “Calculate” button clicked.
Execute button: Start Set Coordinate Chainage Offset process for each PointID on the POINT table.
13.1.1 Usage
1. Enter values into Name, X Field, Y Field, Chainage Field, Offset Field, Alignment Field,
Direction, Offset Orientation and Calculate columns.
2. Click Execute button to start the Set Coordinate Chainage Offset process.
On this screen:
Surface ID column: Surface ID is used to uniquely identify each row. This field is coloured yellow, and
similar to the yellow coloured fields in gINT, this field must have a value before executing or closing the
form.
Surface Name column: The surface name used when inserting a new surface into a selected table
with PointID and ItemKey as the keyset.
Surface File Name column: External or internal surface file name. You can enter the exact surface file
name or use a wildcard in the surface file name. For example, if you have surface file named as S_01,
S_02 and S_03, in this column you can enter “S*” to include all these surface files when defining the
elevation.
Table column: A drop down list of all the PointID, PointID,Depth and PointID,ItemKey keyset tables in
current gINT Project file. Certain columns are not applicable depending on the table selection. These
fields will be automatically coloured grey and become un-editable when changing the table name
column, or become available when an applicable table is selected.
Elevation Field column: A drop down list of all the fields from the selected table to select the field that
you want to set the elevation to. This will update the elevation for all the holes on the point table that
have East and North (Destination X and Y) data. If an Elevation field is specified, then the Depth field
will be greyed out and become un-editable until the Elevation field value is cleared.
Depth Field column: Defines the field on the selected table where the Depth values will the written.
The column has a drop down list of all the fields from the selected table. The depth is relative to the
elevation of the PointID, and is calculated by subtracting the elevation of the surface file from the
elevation of the PointID, which is defined on the POINT table. This will update the depth for all the
PointIDs that have East and North (Destination X and Y) data. If a Depth Field is specified, then the
Elevation Field will be greyed out and become un-editable until the Depth field value is cleared.
Override Field column: Defines the Boolean field on the selected table that defines if the depth or
elevation has been defined manually, and hence not to be overridden by this command. A drop down
list of all the fields from the selected table. Ensure the selected override elevation field is a Boolean /
check box field. This field is optional.
Set column: Indicates whether to set the elevation or not. If “Set” is checked, depth or elevation will be
updated after Execute button clicked.
13.2.1 Usage
1. Enter values into Surface ID, Surface Name, Surface File Name, Table Name, Elevation Name
or Depth Name, Override Field, and Set columns.
2. Click Execute button to start the process. An error log will be shown in a message window at
the end of the process.
The log file displays a message for each PointID. For example, if the East and North lay outside
the surface areas, then an error message will be listed.
3. Click Save and Close on the main form to return to gINT INPUT.
13.3.1 Tables
Explanations of the tables used in this gINT Add-In are listed below.
The Tide Gauge table is in the Mon-Environmental Conditions table. The PointID is selected in the Tide Gauge
(upper) table. In the Tide Gauge (below) table the keyset for this table is PointID,DateTime. The Water
Elevation field will be used when calculating the Elevation on the POINT table.
The following fields on the POINT table are used by this tool:
Tidal Water Depth: Stores each PointID’s Tidal Water Depth information.
Tidal Date Time: Stores each PointID’s Tidal Date Time information. This field is used by the Tool
to get each PointID’s Tidal Water Elevation from the Tide Gauge table.
Tidal Calculation Tide Point Gauge: Stores each PointID’s information. This field is used by
the Tool to get each PointID’s Tidal Water Elevation from the Tide Gauge table
13.3.2 Usage
The Elevation field on the POINT table is calculated using the add-in menu command Add-Ins > Datgel
DGD Tool > Set Seabed Elevation. This will update all records on the POINT table that have Tidal Date
Time, Tidal Calc Tide Gauge PointID, Tidal Water Depth information and corresponding Tidal data on the Tide
Gauge table. The user needs to manually enter each PointID’s Tidal Water Depth and Tidal Date Time
information. Tidal Water Elevation field in POINT table will be updated from Tide Gauge table based on each
PointID’s Tidal Date Time information. Each PointID’s Elevation is calculated using the difference between
each PointID’s Tidal Water Elevation and Tidal Water Depth values.
Pre-process a grid surface file to fill in the null regions to form a perfect rectangular outline with
no holes
Divide the source grid file into several smaller rectangular grid files to cope with larger surface
files
Invert data, i.e. multiply Z by -1
On this screen:
Source file: The file path of the source XYZ grid file to be processed. Use the “Browse” button to
browse to the file.
Target file: The file path where the output XYZ grid file(s) will be generated. Use “Browse” button to
select browse to the file path.
Min (E, N, Z): Shows the minimum East, North and Elevation values from the source file.
Max (E, N, Z): This information shows the maximum East, North and Elevation values from the source
file.
East spacing: This information shows the East spacing between each row record in the source file.
Ensure the east value of the row records in the surface file are equally spaced before you start the grid
file pre-processing process.
North spacing: This information shows the North spacing between each row in the source file. Please
make sure the north value of the row records in the surface file are equally spaced before you start the
grid file pre-processing process.
Statistics Button: Use this button to display source file statistics. This is not required but it is useful to
know the file statistics in order to decide how the target files are divided. Note that the source file
statistics will be calculated and be shown in the Statistics section at the end of the pre-processing
process.
Invert elevation checkbox: Check the “Invert elevation” box to invert elevation in the target grid file,
i.e. multiple the elevation by -1. This is required only if the elevation in the source gird file has the
elevation inverted and this needs to be corrected before import into gINT.
Round E,N decimal places: Specify a value here to round all values to a number of decimal places.
Rounding can correct inconsistent grid spacing if the difference is very small. Leave this blank if you
wish to omit any rounding.
Surface file grid dimensions (E x N): Enter the East Grid dimension and North Grid dimension to cut
the grid files into equally spaced portions. You can use “File Size” information to determine the East
and North Grid dimensions. For example, if the surface file grid dimension is 2 x 2, the source surface
file will be cut into two rows and two columns, resulting into 4 files and will be named as <Target File
Name>_GridX1_GridY1.xyz, <Target File Name>_GridX1_GridY2.xyz, <Target File
Name>_GridX2_GridY1.xyz and <Target File Name>_GridX2_GridY2.xyz.
Start pre-processing at row: You can specify the starting row in the source file for the process. This is
useful if the source surface file has header information. If the actual surface record starts at row 5 in the
surface file, then enter “5” in this box.
Delimiter: The character used to separate the X, Y and Z values. The most common types can be
selected from the pick list provided, or type in the delimiter character in this field.
Grid Spacing: the spacing between one coordinate to an adjacent coordinate in the grid file. If the grid
spacing is known, enter the values in both East and North fields, and the Tool will use these values
when pre-processing. If one or both fields are left blank, then the Tool will automatically determine the
grid spacing.
13.4.1 Usage
1. Select source grid file.
2. Select target grid file.
3. Click Statistics button to display source grid file statistics.
4. Check Invert Elevation option if the source xyz file has the elevation inverted. Otherwise
uncheck it.
5. Enter a new null value to replace the default null value.
6. Enter surface file grid dimensions. You can determine the dimensions by looking at the size of
the source file.
7. Enter the pre-process starting row in the source file. If there is no header information in the
source file, then enter 1 as the starting row.
8. Select a delimiter from the pick list, or enter one in the field.
9. Enter the grid spacing for East and North, if known.
10. Click Execute button to pre-process the source file.
11. You can view the generated target files in the target file directory.
To run the Add-in with a shortcut, use the key combination: CTRL+ALT+F.
This applies to the tables: STRATA_MAIN, STRATA_DETAILS, SAMPLE, SPECIMEN, DEPTH_REMARKS, IMAGE,
CEMENTATION, CONSISTENCY_DENSITY, MOISTURE_CONDITION, METHOD, PENETRATION_RESISTANCE,
ROTARY_FLUSH, CHISELLUNG, DRILLING_PARAMETERS, WATER_ADDED, IN_SITU_STRESS, CORE,
ROCK_STRENGTH, WEATHERING, FRACTURE, DEFECT, CORE_LOSS, RMR, GSI, ALTERATION,
ROCK_MAS_WEATHERING, DURICRUST_MASS_GRADE.
To run the Add-in with a shortcut, use the key combination: CTRL+ALT+B.
The configuration can be edited by going to DATA DESIGN | Library Data and selecting the
appropriate table from the object selector (yellow drop down list at top of screen).
DG_HIDE_SCENARIO_CONFIG: Stores the project table and field name where user can select the
project type. This is set to the DGDT default table and field, and you probably don’t need to
edit this.
DG_HIDE_SCENARIO_FIELDS: Manually enter only the fields you need to control, and check the
box when the file is to be visible, uncheck to hide. Visibility of fields that are not listed will not
be effected.
DG_HIDE_SCENARIO_NAME: This is used to populate the lookup for the field defined in
DG_HIDE_SCENARIO_CONFIG.
1. Select DATA DESIGN | Library Data, and select DG_HIDE_SCENARIO_NAME, and create a new
record for the new scenario (e.g. Australia_All). The name must not have spaces or special
characters, as it will be used as a field name.
2. Select DATA DESIGN | Library Tables, and select DG_HIDE_SCENARIO_FIELDS.
3. Click on New field, enter the name (e.g. Australia_All) as entered in the
DG_HIDE_SCENARIO_NAME table, select type as Boolean, and set a default of -1.
4. Click OK
5. Repeat this step for DG_HIDE_SCENARIO_TABLE_GROUPS and DG_HIDE_SCENARIO_TABLES. You
can use Tables > Merge Fields from Current File to copy the files from the previous table.
17.2 Fences
Name Description
FENCE A3L Fence – A3 paper size – Landscape orientation with a site map
FENCE A3L NO PLAN Fence – A3 paper size – Landscape orientation without a site map
FENCE A4L Fence – A4 paper size – Landscape orientation with a site map
FENCE A4L NO PLAN Fence – A4 paper size – Landscape orientation without a site map
EOH Text Multiple options to print hole depth and elevation at bottom of fence post
Depth Scale L# / R#
17.3 Graphs
Name Description
A IS CH VS DEPTH BY PTID Horizontal coefficient of consolidation from dissipation, ch verses Depth with data
marker grouped by PointID.
A IS CH VS DEPTH BY UNIT Horizontal coefficient of consolidation from dissipation, ch versus Depth with data
marker and colour grouped by Geology Unit 1.
A IS CH VS RL BY PTID Horizontal coefficient of consolidation from dissipation, ch verses Elevation with
data marker grouped by PointID.
A IS CH VS RL BY UNIT Horizontal coefficient of consolidation from dissipation, ch versus Elevation with
data marker and colour grouped by Geology Unit 1.
A IS CPT NORMALISED SU VS Undrained Shear Strength / Effective Vertical Stress (Normalised Undrained Shear
DEPTH BY PTID Strength) verses Depth with data marker grouped by PointID.
A IS CPT NORMALISED SU VS Undrained Shear Strength / Effective Vertical Stress (Normalised Undrained Shear
DEPTH BY UNIT Strength) versus Depth with data marker and colour grouped by Geology Unit 1.
A IS CPT NORMALISED SU VS Undrained Shear Strength / Effective Vertical Stress (Normalised Undrained Shear
RL BY PTID Strength) verses Elevation with data marker grouped by PointID.
A IS CPT NORMALISED SU VS Undrained Shear Strength / Effective Vertical Stress (Normalised Undrained Shear
RL BY UNIT Strength) versus Elevation with data marker and colour grouped by Geology Unit
1.
A IS SCPT VS VS DEPTH BY Shear Wave Velocity from SCPT verses Depth with data marker grouped by
PTID PointID. Datgel Lab and In Situ Tool.
A IS SCPT VS VS DEPTH BY Shear Wave Velocity from SCPT versus Depth with data marker and colour
UNIT grouped by Geology Unit 1.
A IS SCPT VS VS RL BY PTID Shear Wave Velocity from SCPT verses Elevation with data marker grouped by
PointID.
A IS SCPT VS VS RL BY UNIT Shear Wave Velocity from SCPT versus Elevation with data marker and colour
grouped by Geology Unit 1.
A IS SPT (N1)60 VS DEPTH BY Corrected SPT (N1)60 Value verses Depth with data marker grouped by PointID.
PTID
A IS SPT (N1)60 VS DEPTH BY Corrected SPT (N1)60 Value versus Depth with data marker and colour grouped
UNIT by Geology Unit 1.
A IS SPT (N1)60 VS RL BY PTID Corrected SPT (N1)60 Value verses Elevation with data marker grouped by
PointID.
A IS SPT (N1)60 VS RL BY UNIT Corrected SPT (N1)60 Value versus Elevation with data marker and colour
grouped by Geology Unit 1.
A IS SPT N VS DEPTH BY PTID Uncorrected SPT N Value verses Depth with data marker grouped by PointID.
A IS SPT N VS DEPTH BY UNIT Uncorrected SPT N Value versus Depth with data marker and colour grouped by
Geology Unit 1.
A IS SPT N VS RL BY PTID Uncorrected SPT N Value verses Elevation with data marker grouped by PointID.
Name Notes
Title Report title
Drawn Enter person’s initials / name
Drawn Date Enter a date
Checked Enter person’s initials / name
Checked Date Enter a date
Scale Text Default text is already entered, otherwise enter text
Figure Number Enter text
Revision Enter text
Sheet Enter text
17.4 Histograms
Name Description
A IS R RQD RQD histogram
A IS S SPT N SPT N Histogram
A L CR CBR CBR histogram
A L CS PSD FINES CONTENT Fines content histogram with statistics, count and frequency axes
A L CS R BULK DENSITY Soil and Rock Bulk Density Histogram
A L R POINT LOAD INDEX Point Load Index histogram for all or selected test types
A L R UCS UCS histogram for all or selected test types
Name Notes
Scale Enter an override scale (optional)
Min E Enter an minimum easting value to override the calculate value (optional)
Min N Enter an northing value to override the calculate value (optional)
Site maps of many page sizes and orientations have been set up, and they all operate the same way.
The scale and minimum E and N are automatically calculated based on the PointIDs you chose to
output (either by filter or pick list), and can be overridden by adding data to the Scale, Min E, and Min N
user report variables.
1. Open gINT and confirm you are using the newer library file. This is important as you could lose
data if you are not.
2. Navigate to Utilities | Convert Projects.
3. For Data Template, browse to dgdt <new #.##>.gdt
4. For Correspondence File, select the file dgdt <old #.##> to dgdt <new #.##>
<##>.gci. A correspondence file is not always needed. This can be left blank if there is no
correspondence file. A correspondence file is needed when an existing field or table name
was changed, or you need to move data from one field to another during conversion.
5. In the box Convert Files, select the project files to convert. You may list several projects in this
box.
The converted project retains the original file name. The original project will be stored in the same
directory with the extension .org or or#.
gINT allows AGS import, export, checking and editing in excel and text editors. All of these functions
can be accessed from within the Input application.
AGS File Commands are located in INPUT | File > AGS Files.
Before exporting to AGS the field AGS Edition, found on the Transmission Information Export table, must be
set. Refer to Table 21 – AGS Edition Value.
If the Consolidate <CONT> lines check box is marked, continued heading, units, and data lines are
combined into one line so that there are no continuations. With AGS4 and newer <CONT> is no longer
used.
If you wish to view lines in the file where errors were pointed out in the AGS File Checker set, use the
following configuration:
With this configuration the worksheet will match the line numbers given in the AGS File Checker log.
However, the program will not recreate the AGS file from any edits you make in this mode. For edits in
Excel to be saved, the Consolidate <CONT> lines property must be marked.
If you wish to actually edit the file in Excel, you must mark the Consolidate <CONT> lines property. The
program will not recreate the AGS from the Excel spreadsheet without this property being marked. To
If you have marked the Consolidate <CONT> lines property, make changes in Excel and save the file.
gINT then recreates the original AGS file based on the new data. Quotes will be put around all data
cells and lines broken appropriately to satisfy the 240 character limit imposed by the AGS standard.
If you do select the Each dataset in a separate worksheet option, you may find some worksheet tabs
with some strange-looking names. For example, Excel does not allow the ? character, but it is a
required group prefix for tables not in the AGS specification. The program translates ? to %%d, so a
worksheet tab may read %%dABCD. If the AGS file is recreated from the spreadsheet, the program
will translate these codes back to their original characters.
Notepad++ is a freeware text editor available from http://notepad-plus-plus.org/. Its enhanced features
make it easier to view and edit AGS files.
1. Start with the latest DGDT gINT Files, or the latest relevant compiled Datgel Product gINT Files
(that incorporate many Datgel Products merged into one set of gINT Files – ask Datgel Support
for this)
2. Set file names
a) Company 1.00.gpj
b) Company 1.00 lib.glb
3. Logo: SYMBOL DESIGN | Bitmap Symbols
a) Merge Logo or Logos
b) Delete other dummy logos
c) See section 20.2 for more details
4. DATA DESIGN | Library Data | DG_COM_OFFICE
a) Set Office name
b) Set default logos for the office
c) test a log and graph, configure the offset field on DG_COM_OFFICE after testing a graph
report
d) Remove Datgel Office
5. Project table
a) Set value for PROJECT.Office
b) Set default value for PROJECT.Office
c) Set PROJECT.Data_Template_History Caption as: Company 1.00 yyyy-MM-dd
d) Set PROJECT.Data_Template_History Default Value as: Created with Company 1.00 yyyy-MM-
dd, and set the value as: Created with Company 1.00 yyyy-MM-dd
e) Coordinate System and Elevation
i. For Australian users set the value and default for Elevation Datum to AHD, and if the
user is only in one city set the default for the Coordinate System to the relevant
MGA94 Zone ##. Sydney, Melbourne and Brisbane = “MGA94 Zone 56”, Adelaide
“MGA94 Zone 54”, Perth “MGA94 Zone 50”
ii. Singapore: SVY21 and MSL
f) Set default values and values for Default SPT Pen 1 3 5 and Default SPT Pen 2 4 6. For AS/ASTM
set the former to 150 and later blank, and for BS set both to 75.
6. Set Help > User File Visioning. Fill both fields with Company 1.00 yyyy-mm-dd.
7. PROJECT_OPTIONS
a) Set Classification_Standard Value
b) Set Classification_Standard Default Value
c) Set List_Filter Value
d) Set List_Filter Default Value
e) Set SPT_N_Value_on_Plots_For_Refusal, and default value
8. Set the most relevant value and default for TRANSMISSION_INFORMATION_EXPORT.AGS_Edition.
a) AU “3.1 RTA 1.1”
b) NZ: “4.0.3 NZ”
c) SG: “3.1 (SG)”
d) MY: “4.0.3”
e) Rest of world: “4.0.3”
Figure 28 – DG_COM_OFFICE
3. Make a new record and update the Office, Engineer Logo, Figure Logo, and Figure Logo X Offset fields.
4. Return to INPUT, and on the Project table select new item in the Office field. If you prefer to use
the new office for your projects, set it as the field default, and make a new data template.
5. Move to OUTPUT, and test that log and graph reports present the logo as desired. You might
need to adjust the value for Figure Logo X Offset to present the logo cantered in the figure title
block box. Keep in mind that by default the logo will be offset by 2 mm.
20.3.1 Graphic
The symbols/hatches for the primary material graphic stored in STRATA_MAIN.Graphic, is configured in
SYMBOL DESIGN | Material. You can design more graphics here, but to comply with AGS 3.1 and
AGS 4 you must use three-number codes.
For instructions on how to design a composite symbols using gINT, refer to on-line help topic
Composite Symbols (symbols) and the Datgel gINT Training Manual.
1. Install the DGD Program, and open the DGD Tool user gINT Files, and activate the license.
If you require technical support related to gINT development you should contact your gINT support
provider, which may not be Datgel. If Datgel is not your normal gINT support provided, you can
purchase a Prepaid Technical Support Package from Datgel to enable Datgel to assist you.
Datgel licenses the DGDT, including gINT objects, on a non-transferable basis, which means you can’t
provide the library, data template, project, correspondence files, gINT Schema files, programs,
documentation etc. that were provided with the DGDT to 3rd parties.
The latest official installation package for gINT may be downloaded from
http://select.bentley.com/FulfillmentCenter. Your user account must have privileges to download
software.
There is one installation package for gINT that may be run in trial mode and licensed mode.
To install a new DLL program, simply run Setup.exe, and install over the top of the old version.
There is one installation package for DGD that may be run in trial mode and licensed mode.
Implementing a new library and project is a complex operation. The gINT developer will need to decide
what customised items should be merged from the existing working library and project into the new
library and project, so as to maintain any existing custom developed features.
1. Select INPUT | File > New Project or the (new) icon > Clone Data Template…
2. Browse to the data template dgdt 4.##.gdt, and click Open.
3. Name the new project file Tutorial.gpj, and click Save.
22.3.2 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: .
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.
Speed up selection by using lookup lists. F2 makes the list expand. If you type into fields, matching
items are selected automatically.
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 4.##.gpj. Select
File > Import/Export > Import from Database…, and configure the options as in the following screen
shot, then click OK.
Enter one description in the component description tables for soil and rock that best matches the
standard you log to.
22.3.8 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
22.3.9 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.
22.3.10 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.
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.
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.
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.
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
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.
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.
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.
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.
Then switch to the other log report by changing the yellow drop down list
22.12.3 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.
22.13 gIDraw
This is gINT’s drawing interface, and is used throughout the program by users and developers.
The Layer drop-down box in the top right of the screen displays the current layer of the drawing. If
desired, you can group your entities into layers, creating an overlay in your drawing. The colour you set
in the layer sets the colour of the entities at design time, but does not affect the colour at output time.
Click the Layer Properties icon to view the properties of the drawing layers:
For further study on layers, select the Help Contents Commands Reports Layers topic.
The outermost rectangle is the physical page boundaries and the next one in is the printable area for
the printer associated with the drawing. The innermost rectangle corresponds to the margins that you
define. By default, the margins are the “0,0” location of the X,Y coordinates, but they can be changed.
The lower right corner contains the scroll buttons to move a specified percentage of the screen height
and width. If you hover over the arrow, tooltip text displays the percentage and direction the screen will
move.
application menus. You can move the position of the toolbox using the Toolbox Position icon.
Edit
Draw
Polyline
View
Assist
Settings/Snaps
To view the command abbreviations, select the Settings Commandline Aliases menu option. You
can edit any of these command aliases and enter your own commands:
You can use a shortcut to access these commands. If you press CTRL+3, using the example above,
you would activate the Select Entities command.
If you are in the middle of a multiple-step command, the middle panel displays the command that you
executed and prompts you for the next step in the command and the panel to the right contains
additional options for the command:
The shortcut for the Erase command is the “E” key or the DELETE key on your keyboard.
When you right-click on your mouse with the General Context Menu turned on, the menu repeats
whatever command you are working on. It also contains the Navigation, Snaps, Save and Cancel
Changes options.
If context menus are turned off and there is no command in effect, when you right-click, the program
executes the last command. If you are in the middle of a command, the result is the same as pressing
the ENTER key.
Refresh drawing
Pan
Previous zoom
Zoom window
Zoom extents
Zoom page
Zoom out
Zoom in
Zoom multiply
Quick zoom
To draw a polyline, you can use the Polyline toolbox button, select the Draw Points and Lines
Polyline menu option, press CTRL+L, or type PL in the command textbox. If you recently created a
polyline you could select it from the list of prior commands.
Click the Snap to Point command and click on the lower left corner of the inside dotted frame.
Click the Snap to Perpendicular command and click the upper right corner of the frame. gINT
draws a straight line across the bottom of the frame.
Repeat this process until all four sides of the frame are drawn and then click OK. When you are
finished, your screen should look similar to the following:
To quickly erase this polyline, select the Edit Undo Last Command menu option, press CTRL+Z, or
select the entity and click the Delete key or the Erase button. There are two levels of undo; the first is
undoing the last command, and the second is the Cancel Changes button, which undoes any
changes made since the last time you saved your work.
Now we can redraw the polyline using the Snap Lock command.
Instead of clicking on a snap command several times to draw the rectangle, we can use the Snap Lock
command to repeat the same snap mode without having to re-click it each time. You can also use the
SHIFT key to display the snaps menu commands.
Another way to shorten your movements is instead of using the command buttons on the lower right
panel (such as Close, OK, and Cancel), when you are ready to complete a command, you can press
the ENTER key, or to cancel you can press ESC. You can also press the first uppercase letter of a
command to execute it. For example, if you want to close a polyline, you can type “C” on your
keyboard.
You can also use the rectangle toolbox icon and the snap options to create the same polyline we
did earlier. gINT does not have true circles, rectangles, arcs or ellipses. These shapes are created
using polylines, which gives you more flexibility when it comes to editing.
Draw a polyline at 0,0 by typing the coordinates in the command text box and pressing ENTER.
To offset a line from the current point, use the @ symbol and enter the new coordinates of the line. For
example, if you wanted the next point of a line to be 20 mm to the right and 40 mm up from the last
point, you would enter “@20,40”. You can use a negative number to move the line down.
To change the angle on a point, you use polar points. You would enter the @ symbol, the length the
less than symbol (<) and the degrees.
1. Click the line icon, and type the initial coordinates “50,50” then click the ENTER key.
2. Type “@20<45” then click the ENTER key.
To draw a circle with a set radius:
1. Click the “Circle - Centre + Radius” icon, and enter the centre coordinates “50,50” then click
the ENTER key.
2. Type the radius preceded by @, “@20”, then click the ENTER key.
To check the distance of a line, use the Assist Distance menu command or click the Distance
toolbox button. When you measure the distance of a line, you see a dialog box similar to the following:
The Grid button on the Settings toolbox allows you to place a grid on your drawing area
background. In the Grid Spacing dialog box, enter a number for spacing the grid points:
22.14.2.7 Output
Now move to OUTPUT | Fences. Configure:
1. Report: FENCE A3L
2. Use Alignment: A1
3. Baseline offset: 20
4. Drapes: check Seismic 1, set Text Scale 0-100 = 0
5. Preview
6. Configure User Report Variables
7. Click on Edit File, and provide a file name for the *.GDW gINT drawing file.
22.14.3 Graphs
1. Preview the following reports
A IS SPT N VS RL BY UNIT
A L CS ATTERBERG BY SPECIMEN
A L CS MC VS DEPTH BY PTID
A L CS PSD 10 PER PAGE SUMMARY - select about 20 specimens
A L S SU VS RL BY UNIT
2. Configure the range filter, in the Criteria row select Like from the drop down, the type
<spacebar>O*
22.17 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.
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:
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.
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:
For further study, go to Help Contents Utilities Application Print Object Lists topic.
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.
Note: If a field in a project file is not mapped to the Data Template through the Correspondence File,
the data contained in that field will be lost. Do not delete the backup files until you are sure the
converted projects are correct.
For further study, select Help Contents Utilities Application Convert Projects.
8. Preview
(Note: use CTRL + right mouse button on the Paste button to paste table name only)
The above will return a list of BH numbers, top depths and legend codes. Note column headers are
taken from the fieldname caption. This can be printed or exported to a file (e.g. XLS).
To order the data by key fields, insert the following after the existing code. Click ‘Edit’ button to amend
query.
To add a filter, insert the following after the existing code. before the order by. Click ‘Edit’ button to
amend query.
Now make this query more complex by adding group by Hole Type
The SQL expression is given a ‘Name’ and ‘Description’ for subsequent use.
For further study, go to the Help Contents Commands Input Queries topic.
Say you have Latitude and Longitude data to WGS 84, and wish to calculate East and North to a
particular coordinate system. Under this scenario you should enter data into POINT fields WGS84
Latitude and WGS84 Longitude, then define a coordinate system on the PROJECT table, and East and
North will be calculated.
Say you wish to convert the coordinate system of a set of data. First define the source coordinate
system on the PROJECT table, and the POINT fields WGS84 Latitude and WGS84 Longitude will
calculate. Then delete then clear the Coordinate System field on the PROJECT table, and clear the East
and North fields on the POINT table. Finally, assign the new coordinate system on the PROJECT table and
the new East and North will automatically calculate.
You will also need to set the Coordinate Unit field on the PROJECT table appropriately.
The Elevation Offset field on PROJECT is used to relate elevation datum between projects. Say one
project uses LAT for near shore boreholes, another project uses AHD for onshore boreholes, and you
wish to present a fence diagram using AHD using boreholes from both projects. In the near shore
project, you should set the Elevation Offset field to correct offset value for the location of work, e.g. 0.524
(for Williamstown, Victoria)
gINT Professional Plus V8i (select series 2) 8.3.3 has a new feature that facilitates user defined
coordinate systems created using Bentley Map. See https://www.datgel.com/gint-faq for the procedure.
5. Move to the Point table, and you will be asked what to calculate. Select Yes, to calculate
Lat/Long from East/North.
3. Click OK.
4. Google Earth will now launch, and zoom into the area.
gINT Civil Tools can connect to the gINT database (Access or SQL Server) to query, display in plan,
display in 3D and display in a Civil profile any borehole from the gINT database. Additionally, you can
create a MicroStation terrain model representation from a selection of or all points in your project for a
given type of lithology. A smoother surface may also be generated by using an interpolation algorithm
that generates a smoother and more attractive terrain model.
http://communities.bentley.com/products/geotechnical1/w/wiki/30868.gint-civil-tools-connect-
edition-videos-and-wiki-articles
http://learn.bentley.com/app/Public/ViewLearningPathDetails?lpId=111465
o 2017-12 (December) gINT SIG - Site Analysis using gINT Civil Tools
o 2017-07 (July) gINT SIG - gINT Civil Tools Essential for Subsurface Evaluation
If you don't heed this you will get Quarterly Term License invoices for your use of the wrong gINT Civil
Tools product level.
23.5 General
Most dialogs do not have an OK button. To make the action take place you need to click (normal left
click) in the view.
If you wat to clear data and re-query, first Ctrl+A and press Delete.
23.6 2D Map
1. Make a new drawing named 2D.dgn, use seed 2D Metric Design.dgn
2. Select the Geotechnical workflow (lookup list in top left of screen)
3. Select Site Map > Coordinate System, and set Library\Projected\Asia\Singapore\SVY21, click
OK
4. Select gINT Projects > Database Connectivity, and click on Load connectivity mapping from
xml . Select C:\Datgel Training\gINT Files\dgdt-p #.##.# gct ##.xml
5. Review each tab, and edit as your needs require
6. Select Geotechnical > gINT Projects > Query All, select rows with Name starting with ST,
and click OK
7. File > Import > Common File Types > Shape File, select C:\Datgel Training\Auxiliary
Files\MP14_PLNG_AREA_WEB_PL.shp
8. Make and Bing Maps Key, refer to:
a) https://communities.bentley.com/products/3d_imaging_and_point_cloud_software/w/wiki/2
5042.working-with-bing-maps
b) https://www.microsoft.com/maps/create-a-bing-maps-key.aspx
9. Go to File > Settings > Configuration> Configuration Variables. Create a new configuration
variable named "MS_RASTER_BINGMAP_KEY" and give it the value of your Bing Maps key.
Example, "abcdefGhiJklmnop_qrstuvwXyz".
10. Add Bing Maps:
c) Select Geotechnical > Site Map, in Raster area, click on the icon in bottom right of
ribbon section to open the Raster Manager
d) Attach Bing Maps
e) Under Bing Map Layers select Aerials with Layers. You can also change this later.
12. Label Boreholes using Geotechnical > gINT Projects > Annotate Points
7. Click OK
8. Select Geotechnical > gINT Projects > Query All, select rows with Name starting with ST
and OK. Wait a while.
9. In each view click on Fit View
3. Click somewhere in the View 1, this is like clicking OK and the Terrain is made
4. Edit layers:
a) Changed the colour of the M layer, done in the Level Manger
b) Make a new level called Ground Surface, then in the entity properties set the Ground
Surface terrain to then new layer and turned it off in the Level Display
3. Click somewhere in the View 1, this is like clicking OK and the mesh is made
4. This is on a new layer FILL_Mesh
1. Drop the surface elements using the "Drop Element" tool, make sure the option "Application
Elements" is toggled on, the result of the operation is that your terrain elements will become
meshes which are triangles stitched together
2. In the "Mesh" section, use the "Stich Into Mesh" tool and select the middle tool names "Bridge
Mesh"
3. It will prompt you to select the 1st mesh and then boundary , then the second one
4. The result is a closed mesh which will have a volume ( right click on the element, open the
"Information" tool and you will see the volume under the "geometric properties" section
24.1.1 Alignment
You have two options to create the alignment, a) draw it in site map, or b) type it on the Alignment table
PointID
Type = TRAV
East and North of the start of the Traverse
Final Depth is the length of the line
Traverse Alignment is the alignment you just created
When the data saves the East and North fields will calculate.
24.2 Output
1. Go to OUTPUT | Graphs.
2. Select report A IS R DEFECT MAP A3P from the yellow object selector list.
3. Check the box PointID list only
4. Using the Pick list, select the Line Map PointID you just made in INPUT
5. Preview, print or export the report. The report will automatically place the data in the middle of
the page and pick a proper scale like 1:500. You can override this using the User Report
Variables Min E, Min N and Scale.
Liao, S.S.C. and Whitman, R.V. (1986), Overburden Correction Factors for SPT in Sand: Journal of
Geotechnical Engineering, A.S.C.E., v. 112:3, p. 373-377