GDM - UserGuideV13

GDM 5.
0
The geologist's
everyday tool
User's Guide
Version 1.3
An application from the BRGM software range

The BRGM Group is internationally renowned as France's leading soil and subsoil
specialist. Present on every continent, its teams have acquired invaluable experience and
developed the tools required to successfully carry through their projects. The BRGM
range of software applications, sold in more than 50 countries, is designed and developed
in this spirit.
Welcome
Flexible and easy to use, GDM ( Geological Database Management ) is a reliable and powerful
software application which you can use to:
Manage your data:
Whatever the type: drill holes, profiles, geological and topographical contours, point
samples
Whatever the form: sample description texts, analysis results, logs, geological or structural
codes, coordinates, deviation measurements, scanned or vectorial images
Whatever the volume
Produce high-quality graphics that you can incorporate in your MS Office documents, or print
on your printer or plotter:
Maps and sections (multi-layer documents)
Drill hole logs (multi-column documents)
Interpolate and model your data in 3 dimensions:
On maps and sections
With faults and other geological boundaries
Automatically (interpolation) or manually (digitization with the mouse)
GDM works directly on your data without duplicating it, whether it be Excel, Access, Text, dBase,
Oracle, SQL-Server data, or proprietary-format data from previous GDM versions.
Once you have modified your database, when you open a GDM Project, all the modifications
appear on your graphics.
You can even modify your database while GDM is running, whereby the "Refresh" function takes
account of your modifications.
GDM is used for:

exploring and exploiting mineral resources
designing tunnels, dams, ground storage sites
urban planning
soil pollution assessments
managing resources such as water, etc.
The GDM software tool can be integrated in your company's computer environment. In the field,
GDM can be used to acquire and represent data with a laptop. In the office, you can use it to
communicate with the corporate database and other company software.
GDM 5 documentation
The User's Guide is split into three sections:

GDM 5 installation
This section gives information on the GDM installation folders and the software's protection.
You will find out how to perform single station or network installations, how to upgrade an
existing version, how to move GDM from one computer to another, etc. A list of error
messages related to the protection is given at the end of this section.
Introduction to GDM 5
This section describes the user interface and the data used by GDM, the definition of the
terminology used to manage the data and various advice.
Getting started with GDM 5
This section represents a veritable course book of some 200 pages using data sets installed in
the GDM Tutor folder.
Here you will find an overview of the main GDM functions, from accessing Excel or Access
data to modeling.
If you take the time to complete all of the proposed exercises in order, you will subsequently
be able to make the most of your own data.
If you are not immediately concerned with all the GDM functions, you can skip certain
chapters, according to the schema given on page 77.
In addition to the
hard copy of the
Users Guide,
available on the
GDM installation
CD,
you can also use
the GDM online
help which serves
as a Reference
Manual. .
The online help

describes all GDM
functions in detail.
Table of contents
GDMINSTALLATION 1
HowGDMwillbeinstalled3
GDMfoldersandfiles....................................................................................................3
GDMworkingfolder......................................................................................................4
32bitODBC..................................................................................................................4
Softwareprotection........................................................................................................5
TheProductCode..................................................................................................................5
Installingtheprotection.........................................................................................................5
Precautionsafteractivatingtheprotection.............................................................................6
InstallingGDM7
Standardinstallation.......................................................................................................7
Copyingthesoftwaretoyourharddisk.................................................................................7
Installingtheprotection.......................................................................................................10
Activatingtheprotection.....................................................................................................13
UsingGDMonanetwork............................................................................................14
InstallingGDMonaclientstation......................................................................................15
GDMupgrades.............................................................................................................18
UpgradingGDMversion3..................................................................................................19
RemovingGDM...........................................................................................................20
MovingGDM21
InstallGDMoncomputerB.........................................................................................21
InstalltheprotectiononcomputerB............................................................................21
UninstallGDMoncomputerA....................................................................................22
ActivatetheprotectiononcomputerB.........................................................................24
ReactivatingGDMoncomputerA..............................................................................26
Protectionerrormessages27
ErrormessageswhenGDMisstarted..........................................................................27
II Table of contents
Protectionprogramerrormessages..............................................................................29
INTRODUCTIONTOGDM5 31
Folders,files,userinterface33
GDMProject................................................................................................................33
Projectfile...........................................................................................................................33
Projectfolder.......................................................................................................................33
Temporaryfiles(workingfolder).................................................................................34
Files,databasesanddatasources.................................................................................34
Theuserinterface.........................................................................................................36
TheProjecttree...................................................................................................................37
TheDesktoptree.................................................................................................................38
TransferringelementsbetweentheProjectandtheDesktop...............................................38
AddingaProjectelementtotheDesktop.........................................................................38
PlacingaDesktopelementintheProject.........................................................................39
Menubar.............................................................................................................................39
ProjectProperties..........................................................................................................39
Projectdata......................................................................................................................40
New GDM database.....................................................................................................................40
New palette..................................................................................................................................40
Establish link with database ("connect").....................................................................................41
Establish link with palette ("connect").........................................................................................41
Copy GDM database in project....................................................................................................42
Copy palette in project.................................................................................................................42
Copy log document 4.2 in project................................................................................................42
Copy graphic document 4.2 in project.........................................................................................42
Load Windows metafile...............................................................................................................43
Setup................................................................................................................................43
Basicfeatures(appliedtoProjectelements)........................................................................43
Displayingpopupmenusbyrightclicking......................................................................43
Toolbarsofwindowsintheviewingarea........................................................................44
Doubleclickshortcuts.....................................................................................................44
Keyboardshortcuts..........................................................................................................44
Data45
TypesofdatainGDM5...............................................................................................45
NewGDMdatabase............................................................................................................46
Establishlinkwithdatabase,orCopyGDMdatabaseinproject.........................................46
GDMdatabases............................................................................................................47
Databasetypesandnames...................................................................................................47
Namesoffields...................................................................................................................47
StandardandExtendedGDMdatabases(thenewCodefields)..........................................48
StandardGDMdatabases.................................................................................................48
ExtendedGDMdatabases................................................................................................49
GDM 5.0 User's Guide 356244635.doc V1.3

Table of contents III
RecognizinganExtended/StandardGDMdatabase.........................................................49
"External"databases.....................................................................................................51
Databasetypesandnames...................................................................................................51
Establishlinkwithdatabase................................................................................................52
Automaticchecksandcalculationswhenconnecting..........................................................54
GDMfielduses...................................................................................................................54
"Drillhole"datamodelsrecognizedbyGDM.....................................................................56
Palettes..........................................................................................................................56
Standardpalettes.................................................................................................................57
Extendedpalettes................................................................................................................57
Mixedpalettes.....................................................................................................................57
Sharingfiles..................................................................................................................58
Sharingdatabasesorpalettes...............................................................................................58
Sharingimages(WMFmetafiles)........................................................................................58
Sharingdatabasesorpalettesthatcontainimages...............................................................59
Someimportantfunctions61
Placeinproject,Remove,Delete.................................................................................61
Placeinproject....................................................................................................................61
Remove...............................................................................................................................61
Delete..................................................................................................................................61
DeleteGDMdatabase......................................................................................................62
Deletepalette...................................................................................................................62
Deletelogdocument,graphicdocumentorparameters...................................................62
Rename,Save,Export..................................................................................................62
Renaming(aTreeelement).................................................................................................62
Renamingfiles....................................................................................................................62
Renamingdatabaseandpalettefiles................................................................................63
ExportLogorGraphicdocumentas4.2..........................................................................63
Save.....................................................................................................................................63
Saving(anelementdisplayedinredintheTree).............................................................63
Cancelmodifications.......................................................................................................64
Saveas.........................................................................................................................64
Saveas4.2...................................................................................................................64
Export..................................................................................................................................64
Export(Datasource)........................................................................................................64
ExportWMF(Document)................................................................................................64
NeworenhancedfunctionsinGDM5.........................................................................65
ListmodeforCurveandDrillholedata..............................................................................65
Improvementsonthegraphicdocuments............................................................................65
Generalizationoftheinterviewssystem.............................................................................65
Acceptanceofcoordinateunits...........................................................................................67
Filtersonthedatasources...................................................................................................67
Concatenatingdatasources.................................................................................................68
UG5.doc V1.3 GDM User's Guide 5.0

IV Table of contents
Someadvice/hints/restrictions69
RetrievingtemporaryCurvesdatabases.......................................................................69
Isolines................................................................................................................................69
Gridprofilecurves..............................................................................................................69
Usingexternaldatabases..............................................................................................70
Miscellaneousinformation..................................................................................................70
Variousconnectionproblems..............................................................................................71
Variousexportproblems.....................................................................................................72
GDMrestrictions..........................................................................................................72
Performanceandvariousadvice...................................................................................74
Tips...............................................................................................................................74
GETTINGSTARTEDWITHGDM5 77
Wheredoyoustart?......................................................................................................77
FoldersandfilesintheTutorfolder.............................................................................78
Processingverticaldrillholedata79
GDMcharacteristicsofdrillholedata.........................................................................80
ConnectingtoExceldata..............................................................................................81
DataformatinExcel...........................................................................................................81
Connection..........................................................................................................................81
Geologicaldata................................................................................................................82
Mineralogicaldata...........................................................................................................85
Analyticaldata.................................................................................................................88
Loggingdata....................................................................................................................89
ConnectingtoAccessdata...........................................................................................90
DataformatinAccess.........................................................................................................90
Connection..........................................................................................................................91
Geologicaldata................................................................................................................91
Mineralogicaldata...........................................................................................................95
Analyticaldata.................................................................................................................97
Loggingdata....................................................................................................................98
Graphicdocuments101
Preview.......................................................................................................................101
Drillholepresentation(1/3).......................................................................................102
Coordinatesystem......................................................................................................104
Newgraphicdocument...............................................................................................105
Addlayer....................................................................................................................107

Table of contents V
Currentlayer...............................................................................................................109
Movethecurrentlayerback(orforward)..........................................................................109
Consultingthedatafromthegraphic.................................................................................109
Findingdataonthegraphics..............................................................................................109
Defineview................................................................................................................111
Graphicdocumentscale.............................................................................................112
Verticalsections.........................................................................................................114
Sectionsparalleltotheaxes..............................................................................................114
Sections.............................................................................................................................115
Creatingapatternpalette............................................................................................122
Representationofthetopographicsurface.................................................................125
Modelingthetopographicsurface.....................................................................................125
Representingthetopographyonasection(Gridprofilelayer).........................................128
Representingthetopographyonamap(Isolinelayer).....................................................129
Drawingillustrations..................................................................................................133
IllustrationusingtheGDMImagesdatabase.............................................................135
Convertinggraphicformats:WmfConv............................................................................136
CreatinganImagesdatabase.............................................................................................136
EnteringvaluesintheImagesdatabase.............................................................................137
Imageslayer......................................................................................................................137
Printingthedrawing...................................................................................................138
Exportingthedrawing................................................................................................139
ImportingthedrawingtoWord/Excel/PowerPoint....................................................139
Modelinggeologicalformations/bodies141
Modelingageologicalformation...............................................................................141
Determineformationorcomposite....................................................................................141
Graphicverificationbeforeinterpolating..........................................................................144
Interpolatingtheformation'shangingwall........................................................................148
Representingtheformation'shangingwallonamap........................................................150
Filteringadatasource.......................................................................................................150
Interpolatingtheformation'sfootwall...............................................................................152
Representingtheformationonsections.............................................................................152
Addinginterpretationdatatothemodel............................................................................154
Finalmodel:creatingthegrid............................................................................................156
Finalmodel:addingvalues................................................................................................158
Finalmodel:checkingvalues............................................................................................161
Finalmodel:representationonsections.............................................................................163
Finalmodel:representationonmaps.................................................................................165

VI Table of contents
Brokenlinesections...................................................................................................167
Digitizingprofiles.............................................................................................................168
Creatingbrokenlinesections............................................................................................172
Calculatingthevolumeofaformation.......................................................................176
Calculationonthewholegrid............................................................................................176
Adjustingabasemap........................................................................................................178
Digitizingapolygon..........................................................................................................182
Interpolationlimitedbypolygons......................................................................................185
Calculatingthevolumelimitedbyapolygon....................................................................188
Modelingonsectionsusingthemouse.......................................................................188
Drillholelogs195
NewLogdocument....................................................................................................195
Modifyingalog..........................................................................................................197
Creating/modifyingcolumns.............................................................................................197
Creating/modifyingheadings............................................................................................197
Othermodifications...........................................................................................................197
Scale/Depthportion.......................................................................................................197
Selectinganotherdrillhole............................................................................................198
Depthgraduation...........................................................................................................198
Columnheadingheight..................................................................................................198
Defaultformatofcolumnheadings...................................................................................198
Exampleofalog.........................................................................................................199
Columndepthgraduation..................................................................................................199
Depthcolumn....................................................................................................................200
Patternscolumn.................................................................................................................202
Values(oftext)column....................................................................................................202
Changingscales.................................................................................................................204
Changingdrillholes..........................................................................................................204
Movingacolumn..............................................................................................................204
Variablegraphcolumn......................................................................................................206
Depthcolumn....................................................................................................................208
Variablegraphcolumn......................................................................................................208
Values(ofVariables)columns..........................................................................................209
Overlappingcolumns........................................................................................................211
Cumulativegraphcolumn.................................................................................................212
Graph+values(ellipse)column........................................................................................212
Modifyingthestandardheading........................................................................................214
Printingthelog...........................................................................................................215
Exportingthedrawing................................................................................................216
ImportingthedrawingtoWord/Excel/PowerPoint....................................................217
Repeatlog...................................................................................................................217

Table of contents VII
Othercolumntypes....................................................................................................219
Processingdeviateddrillholedata221
ConnectingtoExceldata............................................................................................222
DataformatinExcel.........................................................................................................222
Connection........................................................................................................................222
Deviationdata................................................................................................................222
Drillholerundata..........................................................................................................224
ConnectingtoAccessdata.........................................................................................225
DataformatinAccess.......................................................................................................225
Connection........................................................................................................................225
Deviationdata................................................................................................................226
Drillholerundata..........................................................................................................227
Graphicdocuments,logs............................................................................................229
Intersectionofdrillholesandsections..............................................................................231
Modelingfromdeviateddrillholedata......................................................................231
Modelingthetopography..................................................................................................232
Determiningthemineralizedvein.....................................................................................233
Automaticverification.......................................................................................................233
Interpolatingthevein'shangingwall.................................................................................236
Interpolatingthefootwallandtheveingrades...................................................................239
Buildingamodel...............................................................................................................242
Additionalfunctions251
Interpolationwithfaults.............................................................................................251
Thedata.............................................................................................................................251
Interpolatingwithoutthefaults..........................................................................................253
Interpolatingwiththefaults...............................................................................................257
CorrectingFaultdatasources............................................................................................259
Checkingtheautomaticcorrection.................................................................................259
Helpwiththemanualcorrection....................................................................................260
UsingaGridlayerwithcoloredblocks.............................................................................260
UsingDXFfiles..........................................................................................................262
Dataprovidedfortheexercise...........................................................................................262
Connectingto/ImportingtheDXFfile..............................................................................264
Otherexample:DXFmodeloftunnels..............................................................................267
3Dviewsofdataandmodels.....................................................................................270
VRMLviewers..................................................................................................................270
GDM>VRMLconversionprograms..............................................................................270
Files...................................................................................................................................271
ConvertingaGDMsurface:programGRD2VRML.........................................................272
Convertingdrillholes/curves:programHED2VRML.......................................................274
Convertingpoints:programB2D2VRML.........................................................................276

VIII Table of contents
Managingcolors................................................................................................................277
Optionalparameterscommontoallthe.PARfiles............................................................279
GDM>VRML2conversionexercise..............................................................................279
APPENDICES 287
GDM5popupmenus289
Onthenamesofdatasources............................................................................................289
OnthenamesofLogdocuments.......................................................................................290
OnthenamesofGraphicdocuments.................................................................................290
OnthenamesofPalettes...................................................................................................291
OnthenamesofParameters..............................................................................................292
IntheListmodeeditzone.................................................................................................292
OntheLogdocuments......................................................................................................292
OntheGraphicdocuments................................................................................................292
Toolbarsintheviewingarea293
Listmodetoolbar..............................................................................................................293
Logdocumenttoolbar.......................................................................................................293
Graphicdocumenttoolbars................................................................................................294
Generaltoolbar..............................................................................................................294
Digitizationtoolbar........................................................................................................294
Basemapadjustmenttoolbar.............................................................................................295
PaletteofstandardGDMpatterns296
GDMsetupfile298
GDMLicenseAgreement301
FreewareLicenseAgreement302
SOFTWARE PRODUCT LICENSE302
LIMITED WARRANTY302
Technicalsupportaddress303

GDM Installation
To install GDM, you will need:

a PC running Windows 95/98/Millenium/NT4/2000
preferably a graphics card with a definition of 1024 x 768 or higher
Microsoft 32-bit ODBC installed on your computer
The complete installation of GDM requires 50 MB of disk space, 40 of which is for the exercises
in the Getting started with GDM 5 tutor folder.
If you wish to immediately proceed with the standard GDM installation,

go directly to "Installing GDM", page 7.
How GDM will be installed
GDM folders and files

The installation procedure will create (or use if already created) the GDM installation folder
on C:\GDM. It will contain most GDM components.
If you wish, you can choose another disk and another folder name for the GDM installation
folder. Caution: you must not install GDM in a folder whose complete name (including the
path) contains spaces.
The GDM installation folder will contain the following subfolders:
Program (6 MB) for the GDM programs and the protection
Grphflt (4 MB) for the WMFConv utility and the graphic filters
Models (100 KB) for the GDM database models
Temp (empty) for the GDM working files
Tutor (40 MB) for the files used for Getting started with GDM
Protect (22 KB) for the protection installation files
Wmf (100 KB) for the GDM shared metafiles
The installation procedure will also create the GDM50.INI file in the Windows folder
(C:\WINDOWS or C:\WINNT). If you decide to keep the default name proposed by the
installation procedure for the GDM installation folder, the paths of the folders used by GDM
will be defined as follows in the first lines of GDM50.INI:
GDMDisk=C: program disk (GDM.EXE and .DLL files)
GDMDirectory=\GDM\Program program folder
GDMDemoDisk=C: \GDM\Tutor disk
GDMWorkDisk=C: GDM working folder disk
GDMWorkDirectory=\GDM\Temp GDM working folder (temporary files)
GDMProtect=\GDM\Protect protection installation file folder
Model=C:\GDM\Models models database disk and folder
WMF=C:\GDM\Wmf shared metafiles disk and folder
Lastly, the installation procedure creates the GDM 5.0 Program Group containing an icon to
run GDM and other icons for the additional programs:
GDM 5.0: GDM program
Protection: GDM protection management program

4 GDM Installation
WMFConv: File converter for converting graphic files to WMF

format, and vice versa
DXFtoCSV: File converter for converting DXF files to CSV

format ready for the connection to GDM
GDM working folder

While in use, GDM creates temporary files in the working folder (by default: C:\GDM\Temp)
defined by the GDMWorkDisk and GDMWorkDirectory parameters in the GDM50.INI file.
The amount of disk space required to create these files depends on the size of the databases
being used by GDM. If necessary, you can define this working folder on another disk by
editing GDM50.INI and manually creating the new working folder.
Comment: when you exit GDM, it deletes all its working files. If you exit GDM incorrectly, or
if your computer crashes, some files may remain in the GDM working folder.
When GDM is not in use, you can delete all the files contained in this folder.
If any files remain in the working folder when you start GDM, you will get the following
message:
In most cases, you should answer "Yes". However, if you are in the process of opening a
second GDM session, you must answer "No" to avoid deleting the first session's
temporary files.
Note: although not recommended, opening a second GDM session on the same computer is
possible when you have a multi-user license.
32-bit ODBC
GDM 5.0 uses MS ODBC 32-bit drivers for connecting to and exporting CSV, XLS, DBF,
MDB data. If these drivers are not installed on your computer, error messages will be
displayed when you start GDM.
You must install these drivers from your Office 97/2000 CD.
You can also install them from the GDM distribution support's ODBC32 folder: read the
ODBC.TXT file contained in this folder.

How GDM will be installed 5
Software protection
GDM is protected against copying by software protection.
Your copy of GDM is identified by a Product Code placed on the support by BRGM. Each
time you install the software on a hard drive, you must subsequently implement the protection,
which generates a random serial number. To be able to use GDM, you must ask BRGM for an
activation code. This code will only be valid for your Product Code and the Serial Number
which has just been generated.
GDM is thus installed in three steps:
the software is copied to your hard disk by the Install program,
the protection files are installed by the Protection program,
the protection activation code is input by the Protection program.
The Product Code

To retrieve the Product Code for your copy of GDM:
On the distribution support, the product code is the name of the .CCC file in the
Installation folder.
After copying GDM onto your hard drive via the Install program, you will see the
product_code.CCC file in the GDM\PROTECT folder.
After installing the protection files (first step of the Protection program), you will
notice a hidden folder called product_code.690 in GDM\PROGRAM. This is the
protection folder.
You can only install a new copy of the software in the same installation folder (for example
to upgrade GDM) if the distribution support Product Code is the same as that of the
protection already installed.
If the Product Codes are different, to install GDM in the same installation folder, you must
first delete the installed protection's GDM\PROGRAM\product_code.690 folder in the
Windows Explorer.
Installing the protection

The protection is installed by the Protection program.
It cannot be installed if there is already a protection corresponding to another Product Code
in GDM\PROGRAM (see "The Product Code" above).
The installation of the protection generates a random Serial Number.
You must then ask BRGM for the activation code corresponding to both your Product
Code AND your Serial Number.
Comments:
Some disk cache utilities may prevent the protection's implementation. In this case,
you must disable them temporarily to implement and modify the protection.
If you have selected the maximum protection options offered by certain anti-virus
programs, they may alert you to the presence of a virus in the

6 GDM Installation
GDM\PROGRAM\product_code.690 folder when you install the protection, when you

activate this protection or when you run a "scan" on your hard disk. These warning
messages mean the anti-virus program has confused the installation or modification of
the protection with a virus attack.
If you select the Repair file automatically or Delete file automatically anti-virus
options, the protection will be destroyed without you being able to intervene.
If your anti-virus program prompts you to choose between "Repair file", "Delete file"
and "Cancel", select "Cancel".
Precautions after activating the protection

Once the protection has been activated, you must not subsequently move the GDM
installation folder.
The protection is located in a hidden folder called product_code.690 in GDM\PROGRAM.
Do not delete or move this hidden folder.
The GDM user must have Read-Write-Create rights on this folder.
Do not perform any backup/restore operations with the "include system/hidden folders"
option.
If you compress your disk, uninstall GDM before starting the compression. You can only
uninstall GDM by installing the GDM programs on another machine (see "Moving GDM",
page 21).
If you defragment your disk, there is not risk for the protection.

Installing GDM
Standard installation
Copying the software to your hard disk

Insert the CD-ROM in your CD drive. In the Windows Explorer, search for the Install
program in the Installation folder, and double-click on it to open it. The following dialog
box is displayed:
Click on "Next" to display the license agreement:

8 GDM Installation
If you accept the terms of this agreement, click "Yes" to display the next dialog box,
otherwise click "No" to abort the installation.
If you accept the license agreement, the following dialog box is displayed:
COMMENTS:
1) You can change the default installation folder (C:\GDM) if you choose, however you
must take account of this when subsequently interpreting instructions, explanations or
examples in the GDM documentation.
2) Do not install GDM in a folder whose name includes spaces, such as "Program files", or
"My documents".

Installing GDM 9
3) If you install GDM in an existing folder, files with the same name already present will
be overwritten. The other files will remain unchanged.
Click on "Next" once you have chosen the installation folder:
Select "Complete (standard) GDM station", then click on "Next":
Click on "Next".
If protection corresponding to another Product Code already exists in \GDM\Program (see
The Product Code, page 5), installation is not possible, and the following message is
displayed:

10 GDM Installation
Using the Windows Explorer, remove the existing protection's \GDM\Program\

product_code.690 folder, then restart the Install program.
If no protection is found (new installation), or if protection corresponding to the same
Product Code already exists (upgrade), the files are copied to your hard disk. The
following dialog box is then displayed:
You must now run the protection management program.
Installing the protection

CAUTION! BEFORE PROCEEDING, CHECK THE DATE ON YOUR COMPUTER: an
incorrect date may prevent GDM from operating once the installation is finished, or may
prevent it from operating if you correct the date after installation (see Errors -25 and
-64 in Error messages when GDM is started, page 27).
Click on the Protection icon in the GDM 5.0 Program Group, or run SETPROT.EXE in
\GDM\Program.
For a new GDM installation, the following dialog box is displayed:

Installing GDM 11
No Product code is displayed. This means you must install the protection:
If the "Product code" is already displayed and the "Next update number" is 1, click on
"Request" (see next page).
If the "Product code" is already displayed and the "Next update number" is greater than
1, click on "Exit". GDM should now be ready to run.
If the "Product code" is missing, click on "Install". The following dialog box will be
displayed:
Click OK.

12 GDM Installation
The "Next update number" is 1. This means that the protection has not yet been activated.
Click on "Request".
Fill in the fields in the
"Activation request" dialog box,
then click on OK.
If you have an Internet

connection, instead of clicking
on OK, you can click on "Send"
to directly send your Activation
Code request.
The following message is displayed:
Click on OK, then on "Exit" in the following dialog box.
Send file GDMWPROT.TXT to:

Installing GDM 13
Mr. Jacques BOBILLIER - BRGM - Orleans - France

Tel.: +33 (0)2 38 64 30 14 - Fax: +33 (0)2 38 64 39 70
E-mail: gdm@brgm.fr
Activating the protection

Once you have your Activation Code:
\GDM\Program.
The following dialog box is displayed:
Click on "Modify".
Enter your Activation Code (upper or lowercase):

14 GDM Installation
Click on OK. The following message should then be displayed:
Comment: the confirmation code is not used.

Click on OK to display the protection status ("Next update number" = 2):
Click on "Exit".
In the event of any problem, refer to the list of errors on page 29.
Using GDM on a network

You can install GDM on a program server and use it on different client computers. To do this,
install GDM on the server with the Complete (standard) GDM station option. The number of
client station GDM installations is unlimited, however the number of simultaneous users will
be limited by the number of licenses you have purchased for the server station. This number is
one of the protection's parameters.
On the server, assign the GDM user group Read-Write-Create rights for the protection folder,
i.e., the product_code.690 hidden folder in GDM\Program.
Assign the group Read-Execute rights on the server's other \GDM folders.
The protection will not be installed on the client stations.

Installing GDM 15
In order to run GDM on a client station, the connection with the GDM server disk must be
open continuously. This connection must always be made with the same letter of the network
drive.
Installing GDM on a client station

Before starting the installation, you must use the "Map Network Drive" function to map
the network drive to the server's GDM folder. The letter associated with this network drive
must subsequently be the same each time you use GDM.
Insert the CD-ROM in your CD drive. In the Windows Explorer, search for the Install
program in the Installation folder, and double-click on it to open it.
Once you have read the GDM license agreement, the following dialog box will be
displayed:
Specify the name of the installation folder on the client station:

COMMENTS:
1) You can change the default installation folder (C:\GDM) if you choose, however you
must take account of this when subsequently interpreting instructions, explanations or
examples in the GDM documentation.
2) Do not install GDM in a folder whose name includes spaces, such as "Program files", or
"My documents".
3) If you install GDM in an existing folder, files with the same name already present will
be overwritten. The other files will remain unchanged.
Click on "Next" once you have chosen the installation folder.


16 GDM Installation
Select "Client GDM station", then click on "Next":
Click on "Browse" and locate the GDM folder on the server:

Installing GDM 17
Click on OK.
Make sure you have defined the GDM server's full path (disk and folder) before clicking
on "Next".

18 GDM Installation
Click on "Next".
Once the installation program has copied the files, the "client" installation is complete.
You do not install any protection on a client station.
In order to run GDM on a client station, the connection with the GDM server disk must be
open continuously. This connection must always be made with the same letter of the
network drive.
GDM upgrades
To find out the version number of an installed GDM version that is running, choose "Help -
About".
If the installed version is no longer running, you can find its version number via the following
indications:
GDM version 3 is installed by default in C:\GDMW,
uses folder C:\GDMDEMO for Getting started with GDM,
and creates file GDM30.INI in C:\WINDOWS (or C:\WINNT).
GDM version 4 is installed by default in C:\GDM,
and creates subfolders PROGRAM, GRPHFLT, TEMP and TUTOR in this folder.
Versions 4.0 and 4.1 use file GDM40.INI in C:\WINDOWS (or C:\WINNT).
Version 4.2 uses file GDM42.INI in C:\WINDOWS (or C:\WINNT).

Installing GDM 19
Upgrading GDM version 3

If the installation procedure installed GDM version 3 in the default folders, to remove this
version you must delete the following:
folder C:\GDMW
folder C:\GDMDEMO
file GDM30.INI in C:\WINDOWS (or C:\WINNT)
the GDM Program Group
your personal shortcuts to the GDM programs
Before or after these deletions, you will run a complete installation of GDM 5.0.

Proceed as follows to uninstall GDM version 4:
Start Settings Control Panel Add/Remove Programs: indicate that you want to
uninstall GDM
You will also have to delete the following manually:
the C:\GDM\Program folder (if GDM 4 was installed in the default folders)
your personal shortcuts to the GDM programs
Before or after removing GDM 4, you must run a complete installation of GDM 5.0.
Caution: if you install GDM 5 before removing GDM 4, you must choose a folder other
than the one that contains GDM 4 for the installation.

If the new version does not have the same Product Code as the one already installed, you
will have to partially delete the installed version of GDM 5 before running a complete
installation of the new version:
If GDM 5 was installed in the default folders proposed by the installation procedure,
you must delete the C:\GDM\Program folder.
(To find out the Product Code of each version, see The Product Code, page 5).
If the new version has the same Product Code as the version already installed, you will run
a standard GDM installation in the same folder as the installed version (C:\GDM by
default). If you subsequently use client stations, you will run the client GDM installations
on these machines.
Files with the same name will be overwritten without you being prompted to confirm.
You will not need to modify the protection since the Product Codes of the two versions
are the same.

20 GDM Installation
Removing GDM
If you wish to permanently move GDM from one computer to another, only use this deletion
procedure once you have transferred the GDM protection (see "Moving GDM", page 21).
To completely delete GDM on a computer, use the standard Windows uninstall program:
Control Panel - Add/Remove Programs. Select GDM in the list of programs and click on
Add/Remove.
Note that this program does not remove components added after the end of the GDM Install
program:
the \GDM\Program\product_code.690 that contains the protection,
folders you may have created in the GDM folder.
COMMENTS:
1) If GDM protection is active on this computer when you uninstall GDM, you can re-install
GDM in the same folder without requesting a new Activation Code, since the protection is still
present.
2) If using GDM for DOS, do not delete the GDM folder if it contains the EXE and FMT
GDM 2.6 subfolders.

Moving GDM
To move GDM from computer A to computer B: you install GDM on computer B first
(distribution support Install program) and install the protection on this computer (Protection
program) to generate a new Serial Number (see Software protection, page 5).
You will then use this Serial Number, created on computer B, to uninstall the GDM protection
installed on computer A. This operation will create the Activation Code for the protection installed
on computer B.
To prevent the loss of the protection, you must follow the next four steps in the order specified.
Install GDM on computer B

Follow the instructions in chapter "Copying the software to your hard disk", page 7.
Install the protection on computer B

CAUTION! BEFORE PROCEEDING, CHECK THE DATE ON YOUR COMPUTER: an
incorrect date may prevent GDM from operating once the installation is finished, or may
prevent it from operating if you correct the date after installation (see Errors -25 and -64 in
Error messages when GDM is started, page 27).
Click on the Protection icon in the GDM 5.0 Program Group, or run SETPROT.EXE located in
\GDM\Program:
Click on "Install".
22 GDM Installation
Then, when you click OK:
The "Next update number" is 1. This means that the protection has not yet been activated.
Note the Serial number.
Click on "Exit".
Uninstall GDM on computer A

Click on the Protection icon in the GDM 5.0 Program Group, or run SETPROT.EXE located in
\GDM\Program.

Moving GDM 23
Click on "Move".
If you have completed step "Install the protection on computer B" on page 21 and noted the
serial number, you can click on "Yes" to display the following dialog box:
Enter the serial number you noted in the previous step:

CAUTION! If you do not know the Serial Number for the new installation, click on
"Exit", not on "Create". You will be unable to use an Activation Code created for an
invalid Serial Number, and you will be unable to reinstall the protection that has just
been removed.
Otherwise, click on "Create". The following message is displayed:

24 GDM Installation
The GDMWCODE.TXT file has been created in \GDM\Program. It contains the new
installation's Activation Code.
The protection folder has been deleted from the \GDM\Program folder.
Activate the protection on computer B

Copy the GDMWCODE.TXT file created in the previous step to \GDM\Program on computer
B (overwriting a file with the same name if it already exists), or to a diskette.
\GDM\Program.
Click on "Modify". The following dialog box is displayed:

Moving GDM 25
Click on "Read code...".
Select file GDMWCODE.TXT, then click on "Open".
Comment: if the procedure is performed correctly, the code displayed should resemble the one
in the above capture: it consists of a series of numbers and letters (the letters can only be A, B,
C, D, E, or F).
Click on OK.

26 GDM Installation
Comment: the confirmation code is not used.

Click on OK.
You will notice that the "Serial number" has been replaced by that of computer A, while the
"Next update number" has been incremented to 3.
Click on "Exit".
Reactivating GDM on computer A

On page 21, you saw how to move GDM from computer A to computer B. In reality, you have
merely removed the protection from computer A: the GDM programs are still present. To
reactivate GDM on computer A, you simply "retrieve" the protection installed on computer B
(thereafter GDM will no longer run on computer B).
For this purpose, simply repeat steps 2, 3 and 4 in Chapter 7, inverting the names A and B of the
two computers in the instructions.

Protection error messages
Error messages when GDM is started

The following list contains the most common protection error messages that may occur when
starting GDM.
If you get any other message, contact technical support (at the address given on page 301).
-25 You have reached the GDM expiry date. If the date on your computer is correct,
contact technical support. Otherwise, enter the correct date and try to restart GDM.
-28 Protection not found.
Reminder: the protection is in a hidden folder called product_code.690, located in the
same folder as the GDM.EXE program (by default, the installation procedure installs
GDM in C:\GDM\Program).
Error -28 may occur in one of the following cases:
1. GDM is searching for the protection in the wrong folder: Edit file GDM50.INI in
C :\WINDOWS (or C:\WINNT) and check that the lines:
[Installation]
GDMDisk=C:
GDMDirectory=\GDM\Program
indicate the path to the folder containing GDM.EXE
2. The Protection program (installation of the protection) should have been run after
the Install program (installation of the GDM files). You may have forgotten to
install the protection, the protection may have been installed in a folder other than
C:\GDM\Program, or it may have been moved.
Use the Windows Explorer to find the hidden folders with the extension 690
(search files *.690) on your hard drive.
2.1. If you are unable to find the product_code.690 folder, run the Protection program
to install the protection.
2.2. If you find the product_code.690 folder elsewhere than in \GDM\Program, do not
move it, as this will simply disable the protection. You must delete this hidden
folder, then run the Protection program to install a new protection.
If you find the product_code.690 folder in \GDM\Program, error -28 indicates
that files are mixed: your GDM.EXE file is designed to run with another
Product Code.
- If the Product Code in \GDM\Program is valid, you must reinstall the GDM
files (Install program) from the installation support corresponding to this
Product Code.
- If the Product Code in \GDM\Program is invalid, you must delete the
product_code.690 folder in \GDM\Program, then reinstall a new protection
(Setprot program in \GDM\Program).
28 GDM Installation
-64 The date or time on your PC has regressed. Enter a date or time later than that of the
last time GDM was used, or wait until this date or time has been reached to use GDM
again.
In some cases, you will have to contact GDM technical support to re-establish GDM
while keeping the correct date on the computer.
-67 You have reached the maximum number of users.
Error -67 may occur in one of the following cases:
1. You are not using GDM on a network. You purchased a "standard" license, in
other words for a single user. You are trying to start a new GDM session whereas
GDM is already in use.
2. GDM is used on a network. An attempt has been made to start GDM after
reaching the maximum number of simultaneous users (which depends on the
number of licenses purchased).
Other possible cause: the user does not have Read-Write-Create rights on the server's
GDM protection folder.
-71 CCADD forgotten
Contact technical support.
-117 Write error in the protection folder. Reboot your computer and try again. Also try
after disconnecting your computer from the network.
-121 Is your disk full?
-155 Subsequent to an access rights problem, the protection folder may contain two
subfolders, NFS and NFT. In this case, delete the one that is empty, reboot your
computer and try again.
-185 Increase the FILES value in CONFIG.SYS
-213 The protection is installed but not activated. If you have already requested and
entered a code for the first protection modification, this code probably did not contain
the protection's activation order. Contact technical support.
-215 Unable to check the number of simultaneous network users on this network. Some
networks have a LOCK option which must be activated in a .INI file (PCTCP.INI,
section nDrive, where n = drive letter).
Networks compatible with the protection system:
Novell (Netware versions 2.0 to 5.0) Amstrad Network
Novell Lite PCSA
Windows for Workgroups PC-NFS
Windows 95, 98 AS400 avec PC Support
Windows NT Laplink
PC LAN Manager Brooklyn Bridge
MSNET Fastlynx
Interlink HP95 DOS Connect
PC Network PCTCP
Banyan Vines Etc.
LANtastic
-1005 Error creating or opening a file. Check the user's access rights to the Windows
temporary files folder.

Error messages 29
Protection program error messages

The following list contains the most common error messages that may occur when installing
GDM protection, or when modifying the protection parameters.
If you get any other message, contact technical support (at the address given on page 301).
-38 Code invalid. You may have made a typing error when entering the protection
modification code. Alternatively, the code does not correspond to your Product
Code/Serial Number/protection program version.
-43 Protection not found. The protection modification code does not correspond to your
Product Code.
-44 This update number has already been run.
-45 You cannot move a protection that has not yet been activated.
-92 Error creating a file in the Windows temporary files folder. Probably due to an NT
security level that is too strict.

Introduction to GDM 5
If you have never used GDM:

You are advised to begin with the exercises in the Getting Started with GDM section
(page 77), at least up to page 138 (end of the "Graphic Documents" chapter).
You can then come back to this Introduction to GDM 5 section and consolidate the knowledge
you will have acquired.
If you have been using GDM 4:

In this introduction to GDM 5, you will find the main concepts that will be useful in the early
stages of this new version. Then, if you have the time, you can discover the GDM functions
you have never used before by completing the exercises in the Getting Started section.
If you absolutely must get started without reading this manual, at least read the following
pieces of advice:
Do not work with GDM 5 in a folder containing a project created using GDM 4.
Create a new folder which will contain all the data in your GDM 5 project. Warning:
GDM does not support spaces in Database names/Palettes/Documents, so make sure you
do not include any spaces in this folder's name, or create it in "My Documents", for
example.
If you wish to start with GDM data created using GDM 4, do not copy the data to this
folder before opening GDM. You must use the main menu's "Copy in project"
functions, and especially the "Copy document in project" functions, which will copy
the GDM databases and the palettes at the same time.
If you wish to start with existing Excel or Access data, first copy this data to the Project
Folder (unless this data is to be shared between a number of applications/users). In GDM,
use the main menu's "Establish link with database" function.
Do not go directly to the "New GDM database" function as in GDM 4.2: in GDM 5, it
is only used to create a GDM database in which you will enter new data with the keyboard.
Look at the examples of GDM projects provided in the Tutor folder: in each end-of-
level Tutor folder, open the Project (Project Open .GDM file).
Folders, files, user interface
GDM Project
The GDM Project consists of a set of data sources, log documents, graphic documents,
palettes, images and parameter files used for a project.
There are no limits concerning the number of elements that make up a Project.
GDM can only open one Project at a time.
If you have a multi-user license, you can open two GDM sessions on the same computer.
However, this involves certain risks:
especially if you open the same Project in two simultaneous GDM sessions,
or if you open different Projects that share the same data,
even if the projects have no points in common, because the GDM working files for both
projects are created in the same folder.
Consequently, you should avoid opening two GDM sessions on the same computer, or
opening the same Project on two computers.
Project file
This is a text file, much like Windows parameter files, with the .GDM extension. Clicking
on a .GDM file in the Windows Explorer opens the GDM application and the project saved
in this file.
Project folder
GDM does not allow you to create more than one Project per folder (i.e., one .GDM file
per folder).
All the files corresponding to the elements created in a Project are created in the Project
folder. GDM creates temporary files in the GDM working folder (See Temporary files
(working folder), page 34).
Generally speaking, users do not need to know the names of the files corresponding to the
elements created by the Project, unless they need to use them for another Project (see
Renaming files, page 62). The names of the files created by GDM often have nothing in
common with the names of the Project's elements visible via the GDM user interface. You
must therefore make sure you don't delete files whose name seems to have little meaning
in the Project folder.
You are strongly advised to place all Project components in the Project folder. By
doing so, should you subsequently copy the Project's complete folder to another
computer, this computer will have a Project that can be used directly, without you
having to re-establish the link to databases or other Project elements.
Exceptions to this rule:
34 Introduction to GDM 5
When you use a database or a palette shared by a number of users, for example a
centralized company database, or a palette common to various projects.
When you wish to share images, legends, headings, or extended patterns (WMF files)
between a number of Projects. In this case, you place them in GDM's "folder of shared
WMF files", defined by the WMF parameter in GDM50.INI (the GDM setup file,
located in \WINDOWS or \WINNT).
See GDM palette of standard patterns, page 294.
As with any other software application, you are advised to make regular backups of
your data. For this purpose, you must save all the files contained in the Project folder,
as well as files used by the Project that are shared by several GDM projects, and
therefore not located in this folder.
Temporary files (working folder)

When you open a Project, GDM creates temporary files in the working folder defined in the
GDM50.INI setup file by the WorkDisk and WorkDirectory parameters (C:\GDM\Temp by
default).
You must never delete files in the working folder while a Project is open in GDM.
When you exit GDM, it deletes all its working files. If you exit GDM incorrectly, or if your
computer crashes, some files may remain in the GDM working folder. An accumulation of
unnecessary files in this folder can slow GDM down considerably.
For this reason, when you start GDM, if any files remain in the working folder, you get the
following message:
In most cases, you should answer "Yes".

Note: although not recommended, opening a second GDM session on the same computer is
possible when you have a multi-user license. However, if you are inadvertently in the
process of opening a second GDM session, you must answer "No" to avoid deleting the
first session's temporary files.
Files, databases and data sources

In the GDM user interface, a "database" represents a file, or the group of files that make up a
database, whereas a "data source" represents the "view of a set of data in GDM" (displayable
in List mode in one or two tables, depending on the type of data).
Examples:
For GDM, an Access database is a database. GDM will see each table or query in the
Access database as a data source.

Folders, files, user interface 35
For GDM, an Excel workbook is a database. GDM will see each worksheet in this
workbook as a data source.
A GDM drill hole or curve database (made up of 3 files of the same name with the
extensions .HED, .BSD, and .IND) will be seen by GDM as a data source.
A filtered instance of this same GDM database will be seen as another data source (on the
disk, this will correspond to a file containing the filter's "query").
For external drill hole databases (Access/Oracle/SQL-Server/Excel/Text/dBase), the data
source (seen in GDM) may contain fields (such as To Depth) and records (empty intercalated
runs) that do not exist in the external database. Conversely, fields in the external database may
not be seen in the data source (because they were not included on connection).
With the exception of filters, a GDM database can only include one data source in a GDM
Project. Moreover, all the fields and records in a GDM database are visible in the data source.
For these reasons, when actually dealing with a GDM data source, you may encounter in this
manual or in the GDM interface the term "database" (or, for example, Drill hole database,
Points database) in certain contexts where what is really meant is "data source" (GDM), or
GDM drill hole data source.
Lastly, note that a GDM Palette is saved as a GDM database (made up of 3 files of the same
name with the extensions .HED, .BSD, and .IND).
The various data forms are described in chapter "Data", page 45.

The user interface
The screen is split into two areas:

On the left, the Project tree (light blue background) or the Desktop tree (yellow
background). To switch from one to the other, you click on the corresponding tab at the
bottom.
On the right, the Viewing Area containing the data editing windows and the Log or
Graphic document display windows.

The button is used to hide/show the left-hand area.
Note: clicking on the button automatically saves ALL the elements being modified
(except for the Graphic document and the Data source being digitized).
Project tree Desktop tree
The Project tree

The Project tree (blue background) displays the list (unlimited) of all the Project elements,
split into 5 categories: Data sources, Log documents, Graphic documents, Palettes and
Parameters.
In each category, the elements are arranged in their Project creation order, or their Project
insertion order. The elements are therefore always displayed in the same order.
An element is displayed in red once it has been modified or when not yet saved. You will
therefore not see any elements in red when you open a Project.
An element displayed in yellow indicates an anomaly when opening the Project: this
element has not been found (file moved or renamed since the Project was last closed), or it
cannot be opened (incomplete files or invalid format). To correct this anomaly:
Right-click on the element and choose "Properties" to find out the name of the file
searched for:
for Data sources and Palettes, underneath "Type of database",
for Documents and Parameters, opposite "File name".

You then either use the "Re-establish link with" function on this element (if it has been
deliberately moved or renamed), or, using the Windows Explorer, rename or find on
a backup copy the corresponding file(s) if renamed, deleted or moved inadvertently.
The Desktop tree

The Desktop tree (yellow background) displays the list of Data sources, Documents and
Palettes which you are currently working on, i.e., those that are "loaded". In GDM, they
are said to be "added to the desktop".
The Desktop is thus a subset of the Project.
You will notice that the Parameters are never displayed on the Desktop.
In each category, the elements are arranged in the order in which they were added to the
Desktop. Since you can "place" Desktop elements in the project, and later "add" them to
the Desktop, you will not therefore see the elements in the same order.
The Desktop cannot contain more than 100 Data sources + Palettes, more than 10 Log
documents or 10 Graphic documents, or 15 Log documents + Graphics.
Furthermore, it cannot contain more than 4 filtered/unfiltered instances of the same GDM
data source (see Filters on the data sources, page 67).
Concept of "Current data source" and "Current palette": this is the Data source or Palette
that is highlighted in gray or blue in the Desktop Tree, or if none are highlighted, the last
Data source or Palette clicked on in this Tree. Whenever possible, this "current" element is
proposed by default in dialog boxes such as New graphic document, Add layer, New log,
New Log column, Adjust base map, etc.
Transferring elements between the Project and the Desktop
Adding a Project element to the Desktop
Right-click on the element and choose "Add to desktop".

Double-clicking on an element in the Project tree represents a threefold action:
it opens this element in display mode,
it adds it to the Desktop (unless this element was already on the Desktop),
it displays the Desktop tree in place of the Project tree (unless this element was
already on the Desktop).
Adding a Log document or a Graphic Document to the Desktop concurrently adds the
Data source and Palettes it uses.
To find out the list of Data sources and Palettes used by a Document, right-click on the
Document name "Sources".
When you add an External data source to the Desktop , GDM "refreshes" the
data source (re-establishes the connection).

Placing a Desktop element in the Project
Right-click on the element and choose "Place in project".

This element must not be in view mode (in the Viewing Area). You must close it first in
the corresponding window.
If the element is a Data source or a Palette, it must not be used in one of the Desktop's
Log or Graphic Documents.
On a Data source or a Palette, right-clicking on "Dependencies" displays the list of
Documents using this Data source or Palette.
Placing a Log Document or a Graphic Document in the Project does not concurrently
place the Data sources and Palettes its uses on the project.
Menu bar
The menu bar contains the functions for creating and modifying the Project, adding data to
the Project and configuring the Project. Only those menu elements for which explanations
are required are dealt with below.
Project Properties
Opens the "Project properties" dialog box:
"Name": this is not the name of the .GDM file (if the latter needs to be changed, use
the "Project Rename" function). The Project name in the "Project properties" dialog
box is for documentary purposes only (used to give a detailed name).
"Authors": on the left, the person(s) who created the Project. On the right, the person(s)
who have modified the Project.
"Geographic zone": if you enter a value other than zero, when you establish a link with
a Database, or when you copy a GDM Database to the Project, if the points in the new
Data source are outside this zone, you will get a warning message. CAUTION: this
geographic zone is defined without units. If you have Data sources in different units

(m, km, feet, miles), you may get a warning message whereas the new data is indeed
inside the zone.
"Keywords": not used by GDM. They can participate in a search by the Windows
Explorer on all the hard drive's .GDM files.
Project data
All the functions in this menu, except for the last one, add elements to the Desktop
(and thus in the Project Tree also).
New GDM database
The GDM database created will be a "standard GDM database" (see Standard and
Extended GDM databases (the new Code fields), page 48).
This function must only be used to create a new GDM database in which you will
enter data in List mode or in Form mode, or to which you will concatenate the
records of one of the Desktop's Data sources (see Concatenating data sources, page
68).
It must not be used prior to a data import, since the "Import data" function does not
exist in GDM 5 (see Establish link with database ("connect"), page 41).
New palette
Used to create a new palette. Opens the "New palette" dialog box:
For Code-type palette tables (left-hand column in the "Palette tables" frame), you
will use the "List of code values" button to add the codes of a data source in the
"Table" frame.
Don't forget to select the "Add one line for each code in the table" option before
clicking on OK:

Now fill in for all the records the Num and CLOR fields (double-click in the
cells).
Establish link with database ("connect")
You will use an existing database:

If it is a GDM database, the fields will automatically be recognized. If the database
is not in Read only mode, you will be able to modify it (structure, values) in GDM.
If it is an External database, you must define the GDM Uses and Units of certain
fields in order for GDM to be able to use it. You will not be able to modify this
database in GDM. If you wish to import this data in GDM, you will only be able to
do so once you have established the link. For this purpose, you will use the "Save
as" function (Desktop popup menu on the Data source name).
If it is not a Shared database, you are advised to keep it in the Project folder
(see Project folder, page 33).
For an External database, you must first copy it to the Project folder. Indeed, if
you move the database to the Project folder after establishing the links, these
links will be broken, and you will have to re-establish them (see The Project
tree, page 37).
For a GDM database, you can subsequently save it in the Project folder (Save
as). However, it is easier to use "Copy GDM database in project", rather than
"Establish link" then "Save as " (see Copy GDM database in project, page
42).
Establishing a link with an Images, Base map or Log images database does not
automatically copy the corresponding metafiles to the Project folder. To copy these
metafiles automatically, see Copy GDM database in project, page 42.
You cannot establish more than one link on the same GDM database, or on the
same Table/Query of an external database.
Establish link with palette ("connect")
You will use an existing palette.

If it is not a Shared palette (see Sharing databases or palettes, page 58), you are
advised to keep it in the Project Folder (see Project folder, page 33).
In this case, if the palette is not in the Project folder, you can subsequently save it
in this folder ("Save as"). However, it is easier to use "Copy palette in project",
rather than "Establish link" then "Save as" (see Copy palette in project,
page 42).

Establishing a link with a palette containing "Extended patterns" does not

automatically copy the corresponding metafiles to the Project folder. To copy these
metafiles automatically, see Copy palette in project, page 42).
You cannot establish more than one link on the same palette.
Copy GDM database in project
For GDM databases only. This function copies a GDM database in the Project
folder and creates the corresponding data source.
Copying an Images, Base map or Log images database automatically copies the
corresponding metafiles in the Project folder, unless they are located in GDM's
"folder of shared WMF files" (see Project folder, page 33). When the metafiles are
copied in the Project folder, the Images or Base map databases are updated so that
they only refer to the short names of the files (see Sharing images (WMF
metafiles), page 58).
Copy palette in project
Copies a Palette in the Project folder and creates a new Palette element in the
Desktop Tree.
Copying a Palette that contains "extended patterns" automatically copies the
corresponding metafiles in the Project folder, unless they are located in GDM's
"folder of shared WMF files" (see Project folder, page 33). When the metafiles are
copied in the Project folder, the Palettes are updated so that they only refer to the
short names of the files (see Sharing images (WMF metafiles), page 58).
Copy log document 4.2 in project
Copies a Log document in GDM 4 format (.DLG file), and all the elements it uses
(Databases, Images, Palettes, Free heading) in the Project Folder (unless the
elements are already present, or already in the folder of shared WMF files), and
creates a new Log document element in the Desktop tree.
To copy a Log document in GDM 5 format from Project A to Project B, you must
first open Project A and export this document using the Desktop "Export the Log
document in GDM 4.2 format" function (see Export Log or Graphic document as
4.2, page 63).
This function, which is only available for Log documents that do not use external
databases, creates a GDM 4-type .DLG file (with the full names of the Database
and Palette files it uses). Note: you do not see the exported Log document in the
Desktop and Project trees.
Copy graphic document 4.2 in project
Copies a Graphic document in GDM 4 format (.DCG file), and all the elements it
uses (Databases, Images, Palettes, Legend, Heading) in the Project folder (unless
the elements are already present, or already in the folder of shared WMF files), and
creates a new Graphic document element in the Desktop Tree.
To copy a Graphic document in GDM 5 format from Project A to Project B, you
must first open Project A and export this document using the Desktop "Export the
Graphic document in GDM 4.2 format" function (see Export Log or Graphic
document as 4.2, page 63).

This function, which is only available for Graphic documents that do not use
external databases, creates a GDM 4-type .DCG file (with the full names of the
Database and Palette files it uses). Note: you do not see the exported Graphic
document in the Desktop and Project trees.
Load Windows metafile
Displays the metafile in a graphic window:

either to view it only (i.e., to preview the image),
or to do a Base map adjustment.
This function does not add any elements to either the Desktop or Project trees.
The metafile stays in the folder you accessed to find it. If you want to use this
metafile as a base map, you are advised to have copied it in the Project folder
beforehand (see Project folder, page 33).
Note: in GDM, whenever an Image is mentioned, it concerns a metafile.
Setup
This menu's functions apply to all Project documents. They are not saved in the Project
file (.GDM). When you open another Project, the configurations defined for the
previous Project are replaced with default Windows configurations.
Basic features (applied to Project elements)

These are functions for viewing and modifying Project elements. Some of these functions
may add data (by calculation) or parameter files to the Project.
Displaying popup menus by right-clicking
On an element in the Project tree or an element in the Desktop tree.

IMPORTANT: the popup menus on the same element are different in the Project tree
(all the Project's available elements) and on the Desktop tree ("loaded" elements).
On the name of a Graphic document layer, on a Log column, on a Log heading: menu
specific to this sub-element.
Elsewhere in the viewing area of a Graphic or Log document: menu specific to this
document.
In the edit zone of a GDM data source in List mode.
A complete list of the popup menus is given in the Appendix (page 287).
Toolbars of windows in the viewing area
Note: you can move all toolbars.

Certain buttons correspond to functions that you will also find in a popup menu (Print,
Scale, etc.).
Other buttons correspond to functions not present in menus (Data source List mode
buttons, Graphic document Add layer, digitization toolbar buttons, inter-views system
buttons, etc.).
A description of the toolbars in the viewing area's windows is given in the Appendix
(page 291).
Double-click shortcuts
Examples:
On a Project tree element (see Adding a Project element to the Desktop, page 38).
On the name of a Graphic document layer, on a Log column, on a Log heading: opens
the Presentation mode.
Keyboard shortcuts
In addition to the shortcuts indicated by an underlined letter in the menu options:

F4 on the View window (List mode, Graphic view, Log view) saves the
corresponding data.
Move from window to window: Ctrl-F6
In List mode for GDM data sources or palettes:
Maj-F6: selects the Table of Collars or the Table of Runs/Segments (toggle).
Note: simply clicking in one of the two tables selects it.
Add line: Ctrl-A
Insert line: Ctrl-I
Delete line: Ctrl-S
Copy-Paste lines: Ctrl-Shift-C and Ctrl-Shift-V
On Log or Graphic documents: Refresh the drawing: F8
On Graphic documents: Stop digitization: Esc

Data
Types of data in GDM 5

The following can be distinguished:
Data sources that can be displayed in a single table:
Points data sources, for which no fields with a specific use are required. However, you
are advised to at least have coordinates if you want to be able to use them in the Graphic
documents.
Images data sources which are special points data sources, characterized by a list of fields
defined by GDM.
Base map data sources which are special points data sources, characterized by a list of
fields defined by GDM.
Grid data sources which are data sources created by GDM exclusively (you cannot
connect to a Grid contained in an external database).
Data sources that can be displayed in two tables:
Curves data sources, consisting of one table of Collars and one table of Curve Segments.
They are characterized by the presence of Collar and Segment coordinates, and in general
by the absence of End of run depth variable ("TO" variable).
Drill holes data sources, consisting of one table of Collars and one table of Drill hole
runs. They are characterized by the presence of a "TO" variable in the table of Drill hole
runs (this variable may not be present in the external database on which you are
establishing a link. In this case, it is calculated by GDM and visible in the table of runs).
Log images data sources = special drill hole data sources characterized by an 80-character
Full ID in the table of Runs containing names of Image files.
A different icon is associated with each of these 7 types in the Project Trees and the Desktop:
Points Images Base map Grid Curves Drill holes Log images
GDM assigns one of these 7 types when inserting the Data source in the Project (using one of
the "New GDM database", "Establish link with database", "Copy GDM database in project",
"Copy document in project" functions, or when GDM creates the database automatically by
a menu function).
Thereafter, you will be unable to use, for example, a Drill holes data source in a Graphic
document Curves layer, or a Curves data source in a Log document.
However for some applications, you can add a "TO" variable to a Curves data source; the
source's "Curves" type will not be modified, but you will be able to use it in a Log document
(see Tips, page 74), or calculate the distance along the curve (=To Depth).
New GDM database

This "Project data" menu function includes three types: Points, Base map, Drill
holes/Curves.
If you choose the Points data type, depending on the model subsequently chosen, you
will obtain:
No model, or a POINTS model: a Points database
IMAGES model: an Images database
BASEMAP model: a Base map database
Note: You are not allowed to delete or rename the fields in the Images and Base
map databases.
If you choose the Base map data type, you directly obtain a Base map database.
If you choose the Drill holes Curves data type, depending on the model subsequently
chosen, you will obtain:
No model:
if you do not define any run coordinates, a Drill holes database
if you define run coordinates and a TO variable, a Drill holes database
in all other cases, a Curves database
CURVES model: a Curves database
DEVIA model: a Drill holes database for deviation measurements
HOLEVERT model: a Drill holes database for vertical (or deviated) holes
HOLEINCL model: a Drill holes database for inclined holes
HOLEDEVI model: a Drill holes database for deviated (or vertical) holes
LOGIMAG model: a Log images-type Drill holes database
Establish link with database, or Copy GDM database in project

These "Project data" menu functions offer the following types:
Points
Drill holes
Curves
Grids
Images
Base map
For a link to be established, or for a copy to be made, the database to connect to or to copy
must present the characteristics expected by GDM for the type chosen (described in "Types
of data in GDM 5", page 45).
GDM recognizes the Log images type by finding the name of at least one Windows
metafile in the 80-character Full ID of the table of runs in a Drill holes database.

Data 47
GDM databases
Database types and names

Right-click on the name of a Data source and choose "Properties" to display the "Data
source properties" dialog box. For GDM databases, the "Type of database" field contains
"GDM". If the "Type of database" field contains anything other than "GDM", this means it
is an External database.
"Name": the name you see in the Tree. You can change this name whenever you like.
Underneath the "Type of database" field is the name of the database file on the disk. It
cannot be modified in the "Properties" dialog box. If you modify this file's name or
location outside GDM, the Data source name will be displayed in yellow the next time you
open the Project. To rename a GDM database "properly", use the "Rename GDM database"
Desktop function.
The "Read only" checkbox enables you to protect the database against possible
modifications made in this Project. Another Project may "see" this database without
protection.
Names of fields
In all the dialog boxes, and in List mode, the "Full name" of the fields (up to 20 characters)
is displayed.
However, the 4-character short name is the one used "in the background" by GDM. Thus,
the names of fields saved in Parameter files (Export, Formations calculation, Calculations,
Interpolation, etc.) and in Log (.DLG) or Graphic (.DCG) document files are always short
names.
Consequently: you can change any field's Full name in a GDM database without
"harming" the Documents or Parameter files. Conversely, you must not modify field
short names.
You can see the short names of GDM databases by choosing "Display Summary".
Note: the short names of External databases (names created by GDM) and the Descriptions
are not visible in the "Summary" dialog box.
Example: "Display Summary" on the "VERTL drill holes" data source of project
Vertical.GDM in Tutor\Vertical_Holes\GDM.

To modify full names, you use the popup menu on the name of the Data source in the
Desktop tree: "Structure Field attributes".
NOTE: When using a GDM 4 database (by "Establish link", or "Copy"), you may have
fields with the same name (if you gave the same Full name to various fields in GDM 4). A
quick way of knowing whether this is true is to select "Structure Field attributes", then
click on OK: GDM positions the cursor on the duplicate Full name and asks whether you
wish to modify it.
Standard and Extended GDM databases

(the new Code fields)
With GDM 5, you can create/use "Standard GDM databases" and "Extended GDM
databases" in the same Project.
Standard GDM databases
In a Standard GDM database, in each table of a data source, you can have up to 50
Codes using 4 characters, and a single Text using up to 996 characters.
A Standard GDM database is synonymous with a "GDM 4 database".
This type of database created by GDM 5 can be used with earlier GDM Windows
versions, or with GDM DOS.
When you create a GDM database by selecting "Project data New GDM database",
you can only create a Standard GDM database.

Data 49
Extended GDM databases
With GDM 5, you can create/use in certain conditions databases in which each
table can contain up to 50 Texts/Codes/Dates (so called "long codes") with a total
length of up to 5000 characters.
An Extended GDM database is a GDM database that contains "long codes".
CAUTION:
A "long code" can be defined with a length of 1 character.
A GDM database that only contains codes using 4 characters can be an Extended
GDM database, if it was created from an External database.
Any database said to be External (for example, Access database or Excel workbook
data) is seen (using the "Establish link with database" function) as an Extended GDM
data source if it contains at least one Text/Code/Date, even if this code is 4 characters
long.
By selecting "Save as" on such a data source, you automatically create an Extended
GDM database.
If the Extended database does not contain any Text/Codes/Dates, by selecting "Save
as" on such a data source, you create a Standard GDM database.
An Extended GDM database can therefore only be created from an External database
containing Texts/Codes/Dates using the "Establish link with database" function
followed by "Save as".
In an Extended GDM database, you cannot add Texts/Codes/Dates, nor can you modify
the length of existing Texts/Codes/Dates.
NOTE: Using "Save as 4.2" on an External data source containing Texts/Codes/Dates,
or on an Extended GDM data source, creates a Standard GDM database by truncating
all the values of Texts/Codes/Dates to 4 characters.
Recognizing an Extended/Standard GDM database
If the "Save as 4.2" function is available, it must either be an External database or an

Extended GDM database. If the "Structure" function is also available, then it is an
Extended GDM database.
By looking at the definition of the "character" fields in Summary mode:
For Standard GDM databases, the Description column contains a description text
(by default, the field's short or full name, depending on the way in which the
database was created).
For Extended GDM databases, the Description column contains the length of the
character fields.
For External data sources, the Long column contains the length of the character
fields.
Example: "Display Summary" on three External data sources of project
Vertical.GDM in Tutor\Vertical_holes\Excel\End:

"Copy 4.2 Geological data" is a Standard GDM database.
"Copy 5.0 Geological data" is a Extended GDM database.

Data 51
"Geological data" is a data source on an External database.
"External" databases
Database types and names

Right-click on the name of a Data source and choose "Properties" to display the "Data
source properties" dialog box. If the "Type of database" field contains anything other than
"GDM" (for example Excel 97, or ACCESS), it is an External Database.
"Name": the name you see in the Tree. You can change this name whenever you like.
Underneath the Type of database field are the names of:
either the Excel worksheet and workbook,
or the Table/Query of the Access/Oracle/SQL-Server database,
or the Text (CSV) or dBase (DBF) file.

If you modify the name or location of this file outside GDM, the data source name will be
displayed in yellow the next time you open the Project.
Note that the "Read only" checkbox is non-modifiable: GDM cannot modify an External
database. Similarly, GDM cannot rename an External database.
If you modify values in an External database to which GDM is connected, you must use
the Desktop's "Refresh" function in order for the modifications to be accepted by GDM. If
the data source is open in List mode, the List mode tables are then updated automatically.
If the data source is used by Log or Graphic documents displayed in the Viewing area, the
modifications will only be displayed once you click on the "Refresh" button for each
document.
Establish link with database

External databases are exclusively connected to GDM using the "Establish link with
database" function in the "Project data source" Project menu.
You must enter the following in this dialog box:

"Name of the data source in the project": enter a name that explicitly designates this
data in the Project (using up to 200 characters). This is the name that will be entered in
the Project and Desktop Trees. Otherwise GDM will choose a default name that you
can subsequently change using the "Rename data source" function.
"Type of data" (Drill holes, Curves, etc.; see Types of data in GDM 5, page 45).
"Type of database": choose Access/Oracle/SQL-Server/Excel/dBase/Text (CSV).
Click on the "Connect" button. You then use the Windows "Open file" dialog box to
choose the external database to open (except with an Oracle or SQL-Server database).
Reminder: if this database is not shared by several projects, you are advised to copy it to
the Project folder beforehand. This enables you to move the Project to another folder more
easily if necessary.
After opening the External database, the "External database GDM correspondence"
dialog box is displayed:

Data 53
At the top:
Choice of Table/Query, if the external database is an Access, Oracle, or SQL-Server type
database. If it is an Excel-type database, you must choose the workbook's sheet.
For Drill holes or Curves databases, you must also choose the key: when this field's value
changes in the database, it informs GDM of the switch from one drill hole (or a curve) to
another.
Correspondence table between the fields of the External database and those you wish to
see in GDM :
To make fields correspond: double-click in the column under the arrow . For drill
holes (or curves), choose the "GDM-Collar fields" or "GDM-Run fields" column (or
"GDM-Segment"), or possibly both for certain fields.
You can change the names of the GDM fields if appropriate.
You must define the GDM use of each field (double-click and choose from the list).
See GDM field uses, page 54.
If necessary, correct or complete the units (double-click and choose from the list).
Buttons along the bottom:
"Coordinate system": definition of the database coordinate system. To be used if the
database coordinates are local (see the Geological data in Excel connection examples,
page 82, or Geological data in Access, page 91).
"Data control": to find out whether the definition of the field uses is compatible with
a GDM Data source structure (see "Drill hole" data models recognized by GDM,
page 56).
"Define vertical/straight/deviated drill holes": by default, the drill holes will be
considered as vertical. In order for them to considered as straight (= inclined), in the
GDM Collar fields, you must have one field with the Azimuth use and one with the
Inclination use. In order for the "Deviated drill holes" option to be available, a
deviation measures data source must already be present on the Desktop (see
"Processing deviated drill holes", page 219).
"Use table": the parameters chosen in the "External database GDM
correspondence" dialog box are automatically saved to a "links file" in the Project
folder. By clicking on this button, you can reuse an existing table, saved from a
previous connection (before modifying it if necessary).

When you click on OK, for a connection to an Excel or Text file, GDM asks you which
length you wish to keep for each Text/Code/Date field.
For a connection to a database (dBase, Access, Oracle, or SQL-Server), the length of these
fields in GDM will be that of the same fields in the external database. Consequently, you
must have defined the length of the fields in the External database: for example, the Text
fields in Access have a default length of 255 characters. GDM will refuse such a field as a
Full ID (which is limited to 80 characters). Similarly, if, for example, you wish to use 6-
character codes, you are advised to define the length of the field in Access accordingly.
For Access "Memo" fields, the question of length still applies.
Other types of Access field:
GDM does not recognize "OLE object" and "Hypertext link" Access fields.
Date/Time fields are recognized as Text/Code/Date values.
Yes/No fields are recognized as numeric fields with a value of 0 or 1.
Automatic checks and calculations when connecting

If the coordinates are large numbers, GDM prompts you to define a local coordinate
system. The calculations GDM subsequently performs will thus be more accurate (in
particular drill hole run coordinate calculations). The user can accept, modify or refuse the
translation proposed.
Control of the increase in depth of drill hole data, and of the non-overlapping of runs when
you define a From Depth and a To Depth.
Addition of intermediate runs to ensure a continuous description (contiguous runs) when
you define a From Depth and a To Depth.
Calculation of drill hole run coordinates.
GDM field uses

The uses are entered in full format (for example, X coordinate) in the "External database
GDM correspondence" table, and displayed in short format for certain fields in "Display
Summary".
In the following list, the short-format uses are written between parentheses (for example
XXXX, or ( ) when the short format does not exist).
Short ID ( ): text field, length 4 characters. 0 or 1 per table. Used to store a short name of a
sample, drill hole, curve, etc.
Full Id ( ): text field, length defined by the user (up to 80 characters). 0 or 1 per table.
Used to store a long name of a sample, drill hole, curve, etc.
Sample number ( ): long integer-type numeric field. 0 or 1 per table. Used to store the
number of a sample, drill hole, curve etc.
Text/Code/date ( ): text field, length defined by the user. 0 to 50 per table. Total length
authorized for all the Text/Code/Date fields in a table: 5000 characters.
Note 1: to be able to use one of these fields as a Code in a Palette, it must not exceed 20
characters.

Data 55
Note 2: in a Standard GDM database (see Standard and Extended GDM databases (the
new Code fields), page 48), you can have 0 to 50 codes using 4 characters, and 0 or 1 text
using 996 characters.
X Y or Z coordinate (XXXX, or YYYY, or ZZZZ): single-decimal numeric field (7 or 8
significant digits). 0, or 2, or 3 per table. When you establish a link on an External database
containing only the X and Y coordinates, GDM automatically assigns the value 0 to the Z
coordinate. Possible units: Kilometers, Meters, Centimeters, Miles, Feet, Inches.
Azimuth (AZIM): single-decimal numeric field. 0 or 1 per table. Used for drill hole
angles. Possible units: degrees, grades, radians.
Inclination (INCL): single-decimal numeric field. 0 or 1 per table. Used for drill hole
angles. Possible units: degrees, grades, radians.
Direction (DIR): single-decimal numeric field. 0 or 1 per table. Used for structure angles
or section planes in which you digitize. Possible units: degrees, grades, radians.
Dip (DIP): single-decimal numeric field. 0 or 1 per table. Used for structure angles or
section planes in which you digitize. Possible units: degrees, grades, radians.
To Depth (TO) : single-decimal numeric field. 0 or 1 per table of drill hole runs (and if
necessary, use added to the "distance" variable of the table of curve segments). The unit
must be the same as that of the Z coordinate.
From Depth (FROM): single-decimal numeric field. 0 or 1 per table of drill hole runs.
The unit must be the same as that of the Z coordinate.
Thickness (THIC): single-decimal numeric field. 0 or 1 per table of drill hole runs. The
unit must be the same as that of the Z coordinate.
Total Depth (TTD): single-decimal numeric field. 0 or 1 per table of drill hole collars. The
unit must be the same as that of the Z coordinate.
Altitude (ALTI): single-decimal numeric field. The unit must be the same as that of the Z
coordinate.
Topography (TOPO): single-decimal numeric field. 0 or 1 per table. The unit must be the
same as that of the Z coordinate.
Area (AREA): single-decimal numeric field. 0 or 1 per table of curve collars. Possible
units: Kilometers2, Meters2, Miles2, Feet2, Inches2, Hectares, Acres.
Density (DENS): single-decimal numeric field. 0 or 1 per table. Any unit (since a density
has no unit, it will not be considered).
Curve points order (ORDP): single-decimal numeric field. 0 or 1 per table of curve
segments. Any unit. Required for a connection to an Access, Oracle, or SQL-Server
database.
Variable ( ): single-decimal numeric field. 0 to 200 per table. Any unit (not considered in
the calculations. It is up to the user to apply the necessary coefficients in the calculations).

"Drill hole" data models recognized by GDM

For most data processing operations and graphics, GDM uses the drill hole To Depth
exclusively. The drill holes must therefore be described continuously in GDM: the From
Depth of each run is always equal to the To Depth of the previous run.
However, GDM can establish a link with an External database containing another drill hole
data model. On connecting, GDM calculates the drill hole run To Depths if they do not
exist in the original model and, if necessary, will intercalate empty runs if the original
model is not continuous.
For certain data models, the information may be redundant, for example in the To Depth +
Thickness model. This represents a possible source of error. GDM thus refuses to establish
the connection and prompts you to modify the uses. In this example, you must either delete
the thickness use, or replace the To Depth use with that of the From Depth (if you
inadvertently specified the wrong use for the depth field).
GDM recognizes the following drill hole data models in an External database:
To Depth: the drill holes are described continuously in the External database.
To Depth + From Depth: GDM will add empty intercalated runs if necessary. The To
Depth of each drill hole will be that of the last run.
To Depth + From Depth + Total Depth: GDM will add empty intercalated runs if
necessary. The To Depth of each drill hole will be the Total Depth.
To Depth + Total Depth: GDM will add an empty run if the last run To Depth is less
than the Total Depth.
From Depth + Total Depth: the drill holes are described continuously in the External
Database.
From Depth + Total Depth + Thickness: GDM will add empty intercalated runs if
necessary. The To Depth of each drill hole will be the Total Depth.
From Depth + Thickness: GDM will add empty intercalated runs if necessary. The To
Depth of each drill hole will be the From Depth of the last run + the last thickness.
Palettes
GDM 5 can use two types of Code Palettes, corresponding either to:
Standard GDM databases (4-character codes),
External Databases, or Extended GDM databases (long codes). See Standard and Extended
GDM databases (the new Code fields), page 48.
We thus talk of "Standard Palettes" and "Extended Palettes".
Do not confuse Extended Palette (applied to long codes) with Palette of extended patterns
(using patterns in the form of WMF files). Standard palettes and Extended palettes can both
contain extended patterns.

Data 57
Standard palettes
A Standard palette is a palette created with GDM 4, or with GDM 5 for Standard GDM
database codes.
The first column, with the heading "Code", shows the values of the codes (using 4
characters). The last column, with the heading "Text", shows the description and/or the
names of the extended patterns (WMF files).
Extended palettes
An Extended palette is a palette created with GDM 5 for "long codes", i.e., Extended GDM
database codes, or External database codes.
The values of the codes (using up to 20 characters) are placed in the right-hand column
with the heading "Code". They may be preceded by the names of extended patterns (WMF
files) provided the 40 character limit for the Code value + Name of the pattern file is not
exceeded.
Mixed palettes
A Standard palette can, if necessary, be reused with an Extended GDM database or an
External database by entering the long code values in the "Text" column.
This "mixed" palette can be used by a Standard GDM database, which will use the
standard code values in the left-hand "Code" column, or by an Extended GDM database or
an External database, which will use the long code values in the right-hand "Text" column.

Sharing files
A user may want to share databases, palettes or images (extended patterns, base maps, etc.)
between different projects.
You may also want to share these elements between different users.
Sharing databases or palettes

You will preferably place the databases and palettes to share in a separate folder, and avoid
creating a GDM Project in this folder.
If necessary, you can use Windows Read only protection on this folder and/or on some of
the files it contains.
You can also use GDM Read only protection in each Project that uses these elements
("Properties" function in the Project and Desktop).
Each Project will be connected to these shared elements via an "Establish link with"
function, not via a "Copy" function, which would produce a copy in the Project Folder.
None of the users of an External database can modify the data via GDM. The data can only
be modified in its corresponding application (Excel, Access, etc.).
For a GDM database or a palette, it is best to avoid several users from being authorized to
modify data, since GDM does not save the modifications instantly in the database or
palette; it only saves them when you use the Desktop's "Save" function.
When you move a Project that uses shared databases or palettes, you may be required to re-
establish certain links when you open the moved project (see The Project tree, page 37), in
particular if you moved the Project to another computer. Indeed, the path to the
databases/palettes connected via the "Establish link" function is stored in its entirety in the
Project File (.GDM) for the databases/palettes located outside the Project Folder.
Sharing images (WMF metafiles)

GDM uses images (Windows metafiles = .WMF files) in the following cases:
Images of a Base map database, or an Images database (Points databases), or a Log
images database (Drill holes database). The names of the image files are stored in a
data source's "Full ID" field (80 characters).
Free heading of a Drill hole log, Heading or Legend of a Graphic document.
Extended patterns of a palette used in the Log documents.
If the filename was entered without the path, GDM will look for it as follows:
First in the Project folder,
then in the folder of GDM's shared WMF files, defined in GDM50.INI by the WMF
parameter (by default, WMF=C:\GDM\Wmf),
if the file is not found in either of these folders, the image cannot be displayed.
Similarly, if you add a WMF filename in GDM via the Browse function:
If the selected file is in the Project folder or in the folder of shared GDM WMF files,
GDM will save the filename without its path.

Data 59
If the selected file is in another folder, GDM will save the filename with the complete
path.
Sharing databases or palettes that contain images

To share databases or palettes with images between a user's various projects, the images
must all simply be placed in the user's folder of shared WMF files.
To share these databases or palettes between a number of users, you must:
either store the complete path of the images, provided this path is the same for all the
users,
or define the same folder in the WMF parameter in the GDM50.INI files of the various
users.

Some important functions
Place in project, Remove, Delete
Place in project
Desktop function, on a Data source, on a Palette, or on a Log or Graphic document.
This function means remove from the Desktop to place in the Project. It is the opposite
of "Add to desktop".
There is only one requirement for placing an element in the project: if the Project's "Add to
desktop" function, or the "New Log/Graphic document" function is no longer available
because you have reached the maximum number of elements on the Desktop (see The
Desktop tree, page 38), you must place several elements in the project to be able to add
others to the desktop.
The Place in project function is not available if the element is displayed in the Viewing
area. You must first close the viewing window.
The function is not available for a Data source or a Palette which is used by one of the
Desktop's Documents. On the Data source or Palette, right-click and choose
"Dependencies" to display the list of Documents that use this data source or palette. All the
Documents in this list must have been placed in the Project before you can place the data
source or palette in the project.
If the Data source or the Document is displayed in red (being modified), when you click on
"Place in project", GDM asks you whether you want to Save or Cancel your modifications.
Remove
Project function, on a Data source or on a Palette.
Means break the link with an element, without deleting it from the disk. It is the opposite
of "Establish link". You can always establish the link later.
You must first "Place in project" the Data source or the Palette to remove.
The function is not available if the Data source or the Palette is used by a Document or a
Parameter file of the Project.
If you know beforehand that you will not need to reuse this data source or palette, it is
better to use "Delete" rather than "Remove" in order to free up the disk space
corresponding to this element.
There is no "Remove" function for Graphic/Log documents or Parameter files.
Delete
This function deletes from the disk a Database, Palette or a Log/Graphic document.
Note: if you apply this function to an element displayed in yellow on the Tree (see The
Project tree, page 37), it corresponds instead to "Remove": you don't actually delete
anything from the disk since the file searched for cannot be found. You simply remove the
name from the Project and Desktop Trees.
Delete GDM database
Desktop function.
This only concerns a GDM database (function not available on an external data
source). The database may be undergoing modification, or displayed in List mode.
The function is not available if the Database is used in a Log or Graphic document of
the Project. Right-click and choose "Dependencies" to display the list of Documents
that use this Data source.
Delete palette
Desktop function.
This function is not available if the Palette is used in a Log or Graphic document of the
Project. Right-click and choose "Dependencies" to display the list of Documents that
use this Palette.
Delete log document, graphic document or parameters
Project functions.
For a Log or Graphic document, the function is not available if the Document is on the
Desktop.
Rename, Save, Export
Renaming (a Tree element)

The "Rename data source" (for data sources), or "Rename" (for all other elements)
functions are accessible from both the Project Tree and the Desktop Tree. They are used to
change the names displayed in these trees.
These functions are always available.
Renaming files
You will not usually need to know the names of the files corresponding to the Project
elements, unless you have to use them for another Project.
If this is the case, you must find these elements in the new Project using the "Establish link
with" function (to share these elements between the two projects) or the "Copy in
project" function. To use these functions, you need to know the names of the files.
To find out the names of the files (in the Project that already uses them), right-click on the
name of an element and choose "Properties" to display the name of the file(s)
corresponding to a Data source, a Palette, a Document or a Parameter file.

Some important functions 63
Renaming database and palette files
You may be required to rename databases or palettes before copying them in a Project
that already contains databases or palettes with the same name.
External databases: renaming is not possible since GDM cannot modify external
databases.
GDM databases: Desktop "Rename GDM database" function on the name of the
data source.
Palettes: Desktop "Rename GDM database" function on the name of the palette.
Export Log or Graphic document as 4.2
The "Rename document" functions do not exist. Instead, you will use the Desktop
"Export Log document as 4.2" or "Export Graphic document as 4.2" functions which
create a new .DLG (Log) file or a new .DCG (Graphic) file in the Project folder. No
new elements appear in the Project or Desktop Trees. The files are created in the
Project folder only to be subsequently copied by another Project. Unlike the Project
folder's other files, you can delete these files in the Windows Explorer without the risk
of any problems when you subsequently open the Project.
Explanations:
The only way to insert an existing document in a Project is to choose "Project data
Copy document in project". This function copies the document and all the
elements it uses to the Project folder (except for the elements that are already
present).
In order for GDM to be able to find these elements, they must first be named in
hard coded format, in other words with the full filenames (disk unit + folder name
+ filename) written in the document file (.DLG or .DCG), as with GDM 4.2
documents.
The files of documents "exported" by GDM thus contain full names for all the files
used (Database, Palette, Image).
Note: the "Export Log document as 4.2" and "Export Graphic document as 4.2"
functions are not available when these documents use an external data source.
Save
Saving (an element displayed in red in the Tree)
These Desktop tree functions are used to save all the changes made on a GDM data
source or on a Log/Graphic document.
A keyboard shortcut (F4 key) can be used to save the corresponding element in the
viewing area's active window.
Reminder: the Project menu "Project Save all" options, or the button on the
Project's menu bar automatically save all the Desktop elements currently being
modified (except the graphic document and the data source being digitized).

When you close the Project, or when you exit, GDM asks you whether or not you want
to save each element displayed in red on the tree (modified element).
Cancel modifications
The "Cancel modifications" Desktop tree function cancels all the modifications made
on a GDM data source since it was last saved.
To cancel the modifications on a log or graphic document, close the corresponding
window, then place the document in the project. GDM then prompts you to either save
or cancel your modifications.
Save as
These Desktop tree functions are used to create a copy of a data source, palette, log or
graphic document. They create a new element in the Project and Desktop Trees, and a
new GDM database or a new file in the Project folder.
The Project tree "Copy parameters" function creates a copy of a parameter file under a
new name.
On an external data source, the "Save as" function creates a copy in the form of a
GDM database: an Extended GDM database if the external source contains one or
more Code or Text fields (long codes), otherwise a Standard GDM database.
Save as 4.2
This Desktop tree function is only available on the name of an External data source
containing at least one long code, and on the name of an Extended GDM data source. It
creates a Standard GDM database (GDM 4.2 database) in which all the long codes are
truncated to 4 characters.
The "Save as 4.2" function creates a new data source element in the Project and
Desktop Trees.
Export
Export (Data source)
This Desktop tree function is used to export a GDM data source as a file or external
database (Text, Excel, Access, etc.). It is not available on External data sources. No
elements are created in the Project or Desktop Trees.
Export WMF (Document)
This Desktop tree function is used to export the graphic of a Log or Graphic document
as a Windows metafile (.WMF). No elements are created in the Project or Desktop
trees.
Not to be confused with the "Export Log document as 4.2" and "Export Graphic
document as 4.2" functions (see Export Log or Graphic document as 4.2, page 63).

New or enhanced functions in GDM 5
List mode for Curve and Drill hole data

Two synchronized tables: at the top a table for the Collars, at the bottom a table for the
Segments (Curves data source) or Runs (Drill holes data source).
A word on the concept of "Current table": before using the buttons on the toolbar or the
edit shortcut keys, you need to know which of the two tables will be affected. The current
table is the one you clicked on last.
If the "Segments of" or "Runs of" bar is in blue, the bottom table is the current one. If
it is in gray, the table of collars is the current table.
Improvements on the graphic documents
Moving the selected layer

Up and down arrows on the toolbar (see Graphic document toolbars, page 292).
Hide layers
The layers' invisibility is saved in the graphic documents.
Digitization
All the digitization functions are grouped together in a specific toolbar (see
Digitization toolbar, page 292).
Generalization of the inter-views system
In the data source List mode toolbar

Simply clicking on one of the following buttons activates the search for the
data item selected at that moment in the List mode.
To Logs: this button is only available for Drill hole data sources. At least one log
document using this data source must currently be displayed in the viewing area.
Otherwise, GDM displays a warning message. For all the log documents being viewed,
GDM calculates and displays the log of the corresponding drill hole without changing
the current zoom factor, and plots a horizontal red line at the end of run depth of the
data. When the zoom factor cannot display the entire log, the red line is automatically
centered in the window.
To Graphics: at least one graphic document using this data source must be
displayed in the viewing area. Otherwise, GDM displays a warning message. For all
the graphic documents being viewed, if the data is within the document's X,Y,Z limits,
GDM displays a red cross on the data, without changing the current zoom factor. When
the zoom factor cannot display the entire document, the red cross is automatically

centered in the window. For each document whose X,Y,Z limits do not allow the data
to be shown, a warning message is displayed.
In the Log Document toolbar

Clicking on one of the following buttons changes the form of the cursor. By
then clicking in a Log column, you trigger the search for the data selected (end of run
depth closest to the point clicked on).
To Table: according to the column in which you clicked, GDM opens the data
source used by this column in List mode (if not already in List mode) and selects in
each table the line corresponding to the data.
To Graphics: at least one graphic document using the data source used by the
column in which you clicked must be displayed in the viewing area. Otherwise, GDM
displays a warning message. For all the graphic documents being viewed, if the data is
within the document's X,Y,Z limits, GDM displays a red cross on the data, without
changing the current zoom factor. When the zoom factor cannot display the entire
document, the red cross is automatically centered in the window. For each document
whose X,Y,Z limits do not allow the data to be shown, a warning message is displayed.
In the Graphic Document toolbar

In order for the buttons to be available, in the document, you must have
selected a Layer other than the Frame layer, and which additionally is neither an Isoline
layer, a Grid profile layer, nor a Base map layer.
Clicking on either of these buttons changes the form of the cursor. By then clicking on
the Graphic document (inside the frame), you trigger the search for the data selected
(closest to the point clicked on).
To Logs: this button is only available for Layers related to Drill hole data sources.
At least one log document using the data source used by the chosen Layer must
currently be displayed in the viewing area. Otherwise, GDM displays a warning
message. For all the log documents being viewed, GDM calculates and displays the log
of the corresponding drill hole without changing the current zoom factor, and plots a
horizontal red line at the depth (end of run) of the data. When the zoom factor cannot
display the entire log, the red line is automatically centered in the window.
To Table: GDM opens the data source used by the chosen Layer in List mode (if
not already in List mode) and, according to the data source type, selects in the table
or in each table the line corresponding to the data.

Acceptance of coordinate units

In GDM 4, the X, Y and Z coordinate units were only used to calculate the scales and to be
displayed in the log headings.
In GDM 5, the coordinate units are taken into account to position the data. For example,
you can superimpose data in Km, Km, m, and data in m, m, m on a graphic document.
The scale displayed is calculated from the coordinate units of the data source used for the
graphic document's Frame Layer.
Consequently, if you copy certain graphic documents created in GDM 4 to a GDM
Project, certain Layers may not be displayed, quite simply because the data source units
they use are not correct. To correct these anomalies, simply modify these units using the
"Structure" function.
For Grid, Isoline and Grid profile graphic layer types, if the data is not displayed on the
copied document, you must recalculate the Grid with GDM 5. Indeed, in GDM 4, the X, Y
coordinate units were not stored in the Grids.
Consequently, a Grid calculated in GDM 4 may be unusable in a new graphic document
layer. If so, you must recreate it in GDM 5.
Note: for a Grid calculated using GDM 4, choosing "Display Summary Parameters"
displays units. However, these are default GDM configuration units (the DefaultXYUnit
and DefaultZUnit parameters in GDM50.INI), not units stored in the Grid (since GDM
could not do this until version 5).
Filters on the data sources

You can only create filters on GDM data sources (and not on External data sources).
For this purpose, you use the "Filter" menu in the Desktop tree.
Using the data source "Properties" function, you can know whether it is an "Unfiltered"
GDM data source, or a "Filtered" instance of a GDM data source:
You cannot have more than four instances of the same GDM data source on the Desktop
(the complete database + 3 filtered instances) at any time. In this case, to create a new
filter, or to "Copy" a filter, you must first use the "Place in project" function on one of the
filtered instances.
Note that you can work on more than one filtered instance of the same GDM data source
and, if necessary, on the source itself in the following conditions:

You can only modify the database structure on the unfiltered instance of the database.
Here, you cannot delete fields, insert Variables or Codes, or change the short name of
the fields. The only thing you can do is add new fields.
Using the "Save" function on the unfiltered data source or on one of the filtered
sources saves the modifications in the unfiltered data source and recreates the
Desktop's data source filters using this source. You can be certain that there will be no
recreation problems because you will have been unable to delete or rename the fields
used by the filters.
Note: once you have saved such a data source, the filtered data sources will no longer
necessarily contain the same number of data records since the filter will have been
recreated and reapplied.
The "Save" function also updates the List modes of each instance open in List mode
when used.
When a Project is loaded, if GDM detects - on a Desktop data source - a consistency
problem between the filter and the associated data source (the data source has been
modified after creating the filter), it automatically recreates the filter, which may take a
while (hourglass icon displayed) if the data source contains a lot of records.
When adding a filtered data source of the Project to the Desktop, if GDM detects a
consistency problem between the filter and the data source, it automatically recreates the
filter.
If you have removed fields used by certain criteria, the filters are recreated automatically
by removing the criteria on these fields.
If the recreated filter poses consistency problems (all the fields used by the criteria have
been removed), GDM displays the "Filter to redo" message and automatically places the
user in the "New filter" dialog box.
You cannot use "Save as" on a filtered data source's data. You must use the "Extract"
function, which creates a new GDM database.
You cannot extract the data from a filtered data source that is being modified: you must
save it first.
Concatenating data sources

The Desktop "Concatenate data source" function adds all the records of a same-type data
source present on the Desktop (Points, Drill holes, Curves, etc., except Grid) to a GDM
data source.
The concatenation is performed on all the fields with the same use and the same name
(full) in both sources. If the sources' Coordinate Systems are different, GDM take account
of this and recalculates the concatenated coordinates.
Note: the concatenation of curves or drill holes only enables you to add new curves or new
drill holes. You cannot add curve segments or drill hole runs.

Some advice/hints/restrictions
Retrieving temporary Curves databases
Isolines
The display of isolines by a graphic document creates a temporary GDM Curves database
called ISO% (consisting of three files: ISO%.HED, ISO%.BSD, and ISO%.IND) in the
GDM working folder, defined in GDM50.INI by the GDMWorkDisk and
GDMWorkDirectory parameters (C:\GDM\Temp by default). The % number of ISO%
depends on the number of graphic documents viewed and the number of isoline layers in
the graphic document
This Curves database is not displayed in the Desktop tree.
Some users may want to keep this database, for example to import it in another software
application.
For this purpose:
As soon as you have displayed the graphic document containing isolines, use the
Windows Explorer to identify the name of the most recent ISO%.HED file in the GDM
working folder (if the graphic document only contains one isoline layer).
Copy this file to another folder in the Windows Explorer.
Grid profile curves

The display of grid profiles by a graphic document creates a temporary GDM Curves
database called PRF% (consisting of three files: PRF%.HED, PRF%.BSD, and PRF
%.IND) in the GDM working folder, defined in GDM50.INI by the GDMWorkDisk and
GDMWorkDirectory parameters (C:\GDM\Temp by default). The % number of PRF%
depends on the number of graphic documents viewed and the number of grid profile layers
in the graphic document
This Curves database is not displayed in the Desktop tree.
Some users may want to keep this database, for example to import it in another software
application.
For this purpose:
As soon as you have displayed the graphic document containing grid profiles, use the
Windows Explorer to identify the name of the most recent PRF%.HED file (if the
graphic document only contains one grid profile layer).
Copy this file to another folder in the Windows Explorer.
For a graphic document built with a broken line coordinate system, this manual operation
isn't necessary: you can retrieve this file using the "Repeat profiles" function (in the Grid
profile layer popup menu).
Using external databases

"External databases" represent:
Text, Excel, or dBase files
Access, Oracle, or SQL-Server databases
i.e., the data GDM can access using MS (or Oracle) ODBC 32-bit drivers, or the data GDM
can export.
This chapter does not concern GDM exports of the type DXF, MIF, DMN and BGN which are
carried out entirely by GDM.
GDM can access external databases via the "Establish link with database" function, or write
in/create External databases via the "Export" function.
Note: GDM does not export data to Oracle and SQL-Server databases.
Various problems may arise, due to the fact that:
the rules for the names of files/sheets/tables/views/queries/fields differ from one external
database format to another,
the types of fields are defined in the databases, but not in the Text or Excel tables,
the possible field formats differ in the various external databases,
there are lots of versions of ODBC drivers supplied by Microsoft. They are all bugged (i.e.,
behave differently from their specifications). GDM can only get around some of these
bugs.
As a general rule, you will encounter less connection problems using Access/Oracle/SQL-
Server/dBase which are Databases, than with Excel/Text files in which the fields are not
typed.
Miscellaneous information
Oracle connection: GDM uses the Oracle ODBC driver, or that of Microsoft.
Oracle or SQL-Server connection: GDM asks the user to choose the data source from
among those defined in the GDM setup. GDM considers this data source name as the
name of the Oracle/SQL-Server database.
You cannot retrieve the sort criteria of an Access/Oracle/SQL-Server query (ODBC
restriction). For this reason, the Establish link with an Access, Oracle, or SQL-
Server database function requires a field with a "Curve points order field" use.
You are allowed to add fields in an external database table/query between two separate
sessions using this database by GDM. However, you are not allowed to delete or
insert fields.
If you modify the length of the fields in an Access, Oracle, or SQL-Server database,
GDM will automatically take this into account when you use the Refresh function, or
when you reopen the Project.
By way of precaution, GDM transforms all special characters (\ / . : ) to _ in the
names proposed by default for an export.
When exporting, if a Text (long code) field is longer than the maximum authorized
length in the text fields of the file or of the exported database, GDM breaks the field

Some advice/hints/restrictions 71
down into several substrings and thus exports more than one field, except with Access
databases where GDM creates a Memo field.
Connection to Excel 97 files: there are no limits concerning the maximum length of the
Text/Code/Date fields, since they can contain up to 32,768 characters in Excel 97 (255
in Excel 5/7). However, make sure you do not exceed the limits accepted by GDM
(5000 characters for all "long code" fields).
The "dot" character is forbidden in the names of GDM fields, because this character
causes problems when exporting. For databases created in GDM 4.2, GDM transforms
dots into spaces.
Connection to a Text file: the filename's extension must be .CSV and the field
separator must be the semi-colon.
Various connection problems

You are advised to avoid using special characters other than " _ " in the names of
files, tables, sheets or fields.
Do not use the " _ " character in the names of Text files (.CSV) to connect,
otherwise you will see a table displayed with the column names A,B,C instead of the
field correspondence table.
Do not mix "Text" and "Numeric" types in the same column of a Text or Excel file
which GDM must connect to. Note: in Excel, the TEXT function can be used to
convert a number into text, and the VALUE function to convert text into a number.
Connection to a numeric field: if, in the header of the Text or Excel file to import,
more than 16 records have not been assigned values for a numeric field, it will be
considered as a text field. Change the order of the lines in the file to connect.
Connection to a text field in a Text or Excel file: if this text field contains numeric
values, their format cannot be controlled. You should therefore put them in "Text"
format in the file to connect.
Under Windows 2000, some ODBC versions may randomly close GDM while
connecting to external data sources. In this case you need to download a newer ODBC
version, like MDAC 2.6 SP1 + Jet 4.0 SP5, from the MicroSoft website.
With some ODBC versions, certain Excel worksheet names are not accepted. In
some cases, the name of the sheet does not appear in the list of tables/views. For
example, sondDEV (2) is not always recognized, in particular with version
4.04202.00 of the Excel driver. In other cases, (numeric sheet name, e.g. "2000", or
sheet name with spaces) no fields are displayed in the correspondence tables.
Post codes in Excel: in reality, these are numeric fields. Transform them to Text format
first.
Time fields in Excel: considered as Dates by certain ODBC versions. Transform them
to Text format first.
There are problems with some ODBC versions for the connection of Text files whose
field names contain spaces. This produces a table of links with no field names. In this
case, you must replace the spaces in the field names with " _ ". You can also put the
names of fields between " " using a text editor or Word (this cannot be done in Excel).

Connection to Text files: in some configurations (first lines with rounded numeric
values with no decimals and no decimal point), you may lose the decimals in numeric
fields.
Connection to DBASE IV files: the filenames must respect rule 8.3, i.e., the name of
the .DBF file must contain no more than 8 characters.
Access query: if you run a query whose result contains fields with the same name
from different tables, Access creates fields named Table1.field and Table 2.field in the
query. These fields names (with a dot) cause the connection to fail. In the Access query,
you must rename these fields (putting "New name:" in front of at least one of the two
field names.
Hint: change formats when you encounter difficulties with a given format: like GDM,
other software applications often allow you to read or export in a number of formats,
and do not react in the same way with these different formats.
Various export problems

CSV exports are very slow if the GDM data source contains a lot of records. Choose
an Excel or Access export instead. Excel or Access will quickly be able to generate
the CSV files.
XLS export: if the first record of the GDM data source contains numeric fields with
no values, the corresponding columns in Excel will be in Text format. Before
exporting, put 9999 in the numeric fields with no values of the first GDM record, then
remove these values in Excel.
GDM does not detect that a table with the same name has already been created in an
Excel file if the name of the GDM data source only contains digits.
Export in Excel 97: you cannot export Text fields or Text/Code/Date fields with
more than 255 characters to a single EXCEL 97 text field, even though you can
import EXCEL 97 Text fields with more than 255 characters in GDM. This is actually
one of the restrictions with ODBC. In this case, GDM creates as many fields (with up
to 255 characters) as necessary.
Export in dBase IV: the names of the fields are truncated after the 10th character.
Consequently, you risk getting errors when exporting since you may have the same
truncated field name more than once. Furthermore, the name of the exported file must
respect rule 8.3 (i.e., a maximum 8 characters for the name of the .DBF file).
Hint: change formats when you encounter difficulties with a given format: like GDM,
other software applications often allow you to read or export in a number of formats,
and do not react in the same way with these different formats.
GDM restrictions
The following list does not contain quantified GDM limits (such as: "Maximum number
of"). A list of these limits is available in the online help (search for "Limitations" in the
index).
Spaces are forbidden in the names of GDM databases, the names of Palettes, and
consequently in the name of the Project folder. For this reason, you are not allowed to

install GDM in "Program Files", otherwise the databases or palettes located in

\MODELS, \TUTOR, and \TEMP will be inaccessible.
Using data sources with different coordinate units in the same Project: here, you are
advised to leave the parameters of the geographic zone covered by the project at 0
("Project properties" dialog box) to avoid getting a warning when you establish a link with
a database or when you copy a database in the Project.
You can have long code fields of up to 5000 characters. GDM allows you to enter
character strings up to this length in List mode. However, when you view these fields in
the edit zone, not all the characters are shown. You must use the arrows to go from one
line to the next and to see the end of the long code text.
GDM 5.0 cannot update long codes.
The zoom function is not always centered. Sometimes it is only centered in terms of
height or width, depending on the drawing's proportions.
If you use very small fonts, when you export or print a Log document, Windows may
replace this font with a larger system font (if the size of the exported or printed font is less
than 1).
Using the dot as a thousands separator in the Windows configuration causes display
errors in List mode: the values end up being multiplied by 100, 1000 etc. To use GDM
correctly, you must not use the dot as the thousands separator in the Windows
configuration.
List mode: the order of the columns only concerns the column display. It does not modify
the order of the columns in the data source. The presentation in List mode (order of
columns, width of columns) is not kept when you close the List mode window, or when
you close the Project, or when you exit GDM.
The names of GDM fields are right-justified in the drop-down lists. Consequently,
when the name of a field is almost 20 characters in length, you will not see the start of the
field's name in certain drop-down lists. Similarly, when the name is very short, you may
see only spaces in certain drop-down lists. In both these cases, you must use the horizontal
scroll function to see the field name's first characters.
Copy-Paste:
In List mode, one cell at a time (Ctrl-C and Ctrl-V), or several complete lines at a time
(Ctrl-Shift-C and Ctrl-Shift-V).
In Form mode: you can copy the selection in the table of Texts/Codes/Dates, or in the
table of Variables (including the column headings) in Excel using Ctrl-C and Ctrl-V.
Palettes: you can copy the selection of several lines (without the column headings) in
Excel using Ctrl-C and Ctrl-V.
Summary of data sources: you can copy the selection of the entire table (including the
column headings) in Excel using Ctrl-C and Ctrl-V.
In Excel, Ctrl-C in the edit zone, then Ctrl-V in a GDM cell.
For information: there may be a difference between the dates given in Summary mode
and those given via Properties. For a GDM database with which you establish a link, the
summary mode indicates the GDM database creation and update dates, whereas the dates
given via Properties are those of the data source's integration in the Project.
For information: the names of Palettes appear hard coded in .DCG and .DLG files, version
5.0, since the files are created by the same function which exports them in 4.2 and 5.0

format. In 5.0, these names are not used; the IDs of the database are used. In 4.2, hard
coded Palette names are used.
Performance and various advice

The processing of external databases with palettes porting to long codes is optimized.
However, the optimization is inoperative if, in a Drill hole layer, you use the same
Palette for the patterns and the line styles with correspondence by codes. In this case,
it is better to do 2 different layers.
You are strongly advised to sort the Palettes porting to short codes. The sort has a
considerable effect in terms of performance when you are required to handle a large
number of code values for a large number of points, runs or curves.
When a Palette is used by more than one Project, this Palette's WMF legends must be
stored in a directory that is accessible from all the Projects. Moreover, this directory must
be defined as the directory of Windows Metafiles common to all these Projects. The
projects will therefore all produce drawings with the same associated legends.
Tips
Undefined value: To "Repeat" undefined values in List mode ( ), or use a filter
criterion "Equal to" undefined value, enter a backspace character.
In a Project in which you wish to connect an External database which has already been
connected to another Project, you can reuse the old Project's links file.
To find out the link parameters between GDM and an external database table, simply
establish a link between the database table and GDM, and use the table of links. This
enables you to see all the link parameters and the drill hole run coordinate calculation
parameters in the table. If you click on OK inadvertently, GDM establishes the link and
finishes by displaying an error forbidding the operation because the table is already used in
the Project.
External data source: when the links file has disappeared, GDM displays the element
in yellow in the Project tree. By re-establishing the link, if you choose the same database
and the same table/query, you subsequently get a message telling you that you cannot
connect to the same table/query twice. In this case, simply close the Project then reopen it,
and the connection is established.
To take into account fields added in an Access table, you must close the GDM project
using this database, rename this database in the Windows Explorer, then reopen the Project
in GDM Windows. All the data elements that use the database are then displayed in yellow.
On the data element corresponding to the modified table, re-establish the link by choosing
the new Access database name, then the table, then the links file. Then define a link on the
new fields. Exit the GDM Project. Give the initial name to the Access database again, then
re-establish the links once more.
The previous operation does not take account of inserted fields not accepted on the first
connection. In this case, you must move the new fields in the Access table and place them
after the fields already connected.
To take into account modifications to the length of fields in a Text or Excel file, you
must modify using an editor the number of characters to connect in the links file. When

you come to use the Refresh function, or when you reopen the Project, the new lengths
will be accepted.
Creating long codes in a GDM database. You can only do this on a GDM database that
does not already use codes and a text. Define a text whose length corresponds to the total
length of the long codes, define as many short codes as there will be long codes and define
the full names of these fields. Quit the "Structure" dialog box and save the modifications.
Return to the "Structure" dialog box, put "Extended" in the description of the text and, for
each long code, enter its length in the description. Quit the "Structure" dialog box and save.
You can add the TO use to a field in a GDM Curves database and thus create logs on a
Curves data source. When you create this kind of database, you must first define
everything except the TO use, then return to the Structure to define the TO use.
For an external database, you can define a To Depth variable, in which case there is no
need to define a field with a "Curve points order" use.

Getting started with GDM 5
Where do you start?

You are advised to do the exercises in the order of the pages that follow.
However, the following variants are possible:
Processing vertical drill hole data
GDM characteristics of drill hole data
Connecting to Excel data
Connecting to Access data
Graphic documents
Modeling geological formations/bodies
Drill hole logs
Processing deviated drill hole data
Additional functions
Note: depending on whether you do the exercises with Excel or Access data, you will not
necessarily see the drill holes in the same order in GDM, because when the connection to
Access data is established, GDM sorts the drill holes in alphabetical order of the drill hole
keys.
Folders and files in the Tutor folder

Vertical_holes
Excel
Start
End
Access
Start
End
Examples
GDM
Deviated_holes
Excel
Start
End
Access
Start
End
Fault_models
Start
End
Examples
Geochem
Start
End
Metro
Examples
VRML
VRML
Programs
GLView
Start
End
Only the last-level folders contain files.

The first-level folders contain compressed WinZip files of the last-level files. You can thus
restore the contents of the folders used for the exercises in Getting started with GDM 5 if
necessary.

Processing vertical drill hole data
This example is taken from a vertical drilling campaign for the exploration of a clay deposit.
However, the data used has been altered for confidentiality reasons (changed drill hole names,
changed names and values of certain fields, data incorporated from another site). Do not therefore
pay attention to geological, geochemical or geophysical inconsistencies between certain types of
data.
The Tutor\Vertical_holes folder (in the GDM installation folder) contains two Access and Excel
subfolders used to complete the exercise as you choose on data in an Access 97 database or in an
Excel 97 workbook.
Each Access and Excel subfolder contains two Start and End subfolders:
Start is the folder in which you will do the exercise: it contains only the data required to start
the exercise.
End is the folder that contains the same exercise, but completed. You can thus use it to see the
results of the exercise (logs, maps, sections) before starting, or during the exercise.
Files
\Tutor\Vertical_holes\Excel_Start.ZIP
\Tutor\Vertical_holes\Excel_End.ZIP
\Tutor\Vertical_holes\Access_Start.ZIP
\Tutor\Vertical_holes\Access_End.ZIP
can be used to restore the contents of the Start and End subfolders if necessary.
Note that the processing of data contained in an Oracle or SQL-Server database is similar to the
processing in Access, while the processing of data contained in Text (CSV), or dBase IV (DBF)
files is similar to processing in Excel.
The Access, Oracle, or SQL-Server database can be open while you work in GDM.
With most Windows versions and configurations, you must close the Excel, Text, or dBase file to
be able to connect GDM to the data.
In the Excel\Start subfolder, .CSV files with the same data are available to show the format of
CSV data compatible with GDM:
The extension of the Text files must be .CSV (and not .TXT). The field separator must be the
semi-colon.
The Text files provided use the dot as the decimal separator. If your Windows configuration
defines the comma as the decimal separator, you will be unable to use these .CSV files. To
change the numbers display definition in Windows, select Start Settings Control panel
Regional Settings Numbers.
80 Getting started with GDM 5
GDM characteristics of drill hole data

GDM displays the drill hole data in two tables:
The table of Drill hole collars, containing one line (= a record) per drill hole. It must have
at least the name of the drill hole and its three coordinates. You can add any data
pertaining to the drill hole, such as the creation date, the total length, the drill hole type,
etc.
GDM finds drill holes by name. You can choose a short name (= Short ID, maximum 4
characters), or a long name (= Full ID, user-defined length using a maximum 80
characters), or both.
Each drill hole must have its three X, Y and Z coordinates (unless you only intend using
GDM to draw drill hole logs)
The table of Drill hole runs, containing one line (= a record) per drill hole run. It must
have at least the "Drill hole run To Depth". You can add any data describing a drill hole
run: code, text, measurement, image name, etc.
GDM locates the drill hole runs by their "To Depth". For each drill hole, the records are
arranged in increasing order of depth. Each run is the portion of the drill hole between the
previous To Depth (or the zero depth for the first run) and its own To Depth. If your data
includes a run From Depth and a To Depth, GDM will check that the runs do not overlap,
and will intercalate empty runs when the hole portions are not given. See "Drill hole" data
models recognized by GDM, page 56.
Point observations/measurements along a drill hole are identified by a single depth. For
GDM, this is the "To Depth". The distinction between a point observation and one between
two depths does not appear in the GDM data structure. It is made by the user when the data
is processed.
If you want to describe the following data for drill holes, you must arrange it in 3 different
tables. Each table corresponds to a description of the same drill holes according to a section at
different depths.
Lithology Samples Logs

Processing vertical drill hole data 81

If you prefer to complete the exercise with Access data, proceed to page 90 (Connecting to
Access data).
Data format in Excel

The Vertical_holes.xls workbook (in Tutor\Vertical_holes\Excel\Start) contains all the drill
hole data on four worksheets (note that this data could also be in different Excel
workbooks):
"Geology" for geological data (lithological code and description)
"Minerals" for clay mineral semi-quantitative data
"Assays" for chemical analysis and physical parameter data
"Logging" for log data
You will notice that:
This data describing the same drill holes is placed in different sheets, since it
corresponds to different sections according to the depth.
Each sheet contains essential fields: drill hole name, X, Y and Z coordinates and To
Depth.
The drill hole order is irrelevant: in the Logging sheet, the order of the drill holes is
different from that of the other sheets.
For each drill hole, the runs are arranged in increasing order of depth. The depths are
therefore all defined.
The names of fields common to all four sheets (drill hole name, coordinates, depth) are
not necessarily the same in all the sheets.
The drill hole name is present on every line: a change of name indicates to GDM the
switch to a new hole.
The values of the other "collar" fields (coordinates, date) must be present on the first
line of each drill hole (Geology and Minerals sheets), but nothing stops you from
repeating them on the other lines (Assays and Logging sheets).
The coordinates in the Assays sheets are different from those in the other sheets. These
are so-called "geographic" coordinates in Km, whereas in the other sheets, they are
coordinates in meters in a local coordinate system (see "Local coordinate system" in
the online help index). GDM will automatically superimpose this data in the same
place as that in the other sheets on the Graphic Documents if you have defined the
coordinate system of each data source.
Connection
In most Windows versions, you will have to close the Excel worksheet before being able to
connect with GDM. This is not the case when working with Access (or Oracle, or SQL-
Server) data.
Start GDM, and create a New project ( , or menu "Project New") in

Tutor\Vertical_holes\Excel\Start) giving it, for example, the name "Vertical".

Geological data
Menu "Project data Establish link with database". Fill in as follows:
Click on "Connect" and choose Vertical_holes.xls

The "External database GDM correspondence" dialog box is used to define how
GDM will interpret the data contained in the Excel sheet "to connect":
Which fields will be seen as "collar" fields, and which will be seen as "run" fields,
What the use of each field in GDM will be,
What the units of certain numeric fields (coordinates, angles, etc.) are,
What the coordinate system is.
The dialog box shows the fields in the Assay sheet (the first in alphabetical order):
By default, GDM assigns the Drill hole key (field present on every line and whose
change of value indicates to GDM that you have switched to another hole) to the first
field in the Excel worksheet.
The names of the fields in the Excel worksheet are displayed in gray in the left-hand
column. By double-clicking in one of the two columns with the heading on the
line of each field, you can link each field to either a "GDM-Collar field" or to a
"GDM-Run field" (or possibly to both).
GDM automatically recognizes the name of certain fields. This is the case for Z which
has been recognized as a "collar field", with the "Z coordinate" use. The unit assigned
(meters) is the Z unit defined by default in GDM50.INI (see GDM setup file, page
296).

As soon as a Collar or Run field has been defined, GDM assigns it a "Use" by default
(usually "Text/Code/Date" for a text field, and "Variable" for a numeric field). You can
change its "Use" by double-clicking on the assigned use.
Once you have chosen the use of a numeric field, you can modify the "unit" by double-
clicking on the unit displayed.
In "Table/Query: Drill holes", choose the Geology worksheet, and fill in the
correspondence table as follows:
The Short ID, X, Y, Z coordinate and To Depth uses are essential in order for GDM to
recognize the drill hole data.
Notes:
You can rename the fields (this has indeed been done for Xlocal, Ylocal and Z
coordinate).
Short ID can be replaced by Full ID when the names of drill holes use between 4
and 80 characters.
You can omit the three coordinates. You will only subsequently be able to produce
Log documents (no maps/sections/formation calculations, etc.).
You can use the From Depth in place of the To Depth, but you will need an
additional Collar "Total Depth" field, or a Run "Thickness" field (see "Drill hole"
data models recognized by GDM, page 56).
Since the Geology sheet's coordinates are local coordinates, you must assign the
characteristics of the local coordinate system used. We will see that for the Assays
sheet, this step is unnecessary since this sheet's data consists of geographical
coordinates.
Click on the "Coordinate system" button, and change the values of Xo, Yo (X and Y
coordinates of the local coordinate system's origin in the geographic system) and Theta
(angle of the local coordinate system axis with the North = Y of the geographic
coordinate system):

Click OK, then on OK in the main dialog box.

For each Text\Code\Date field, GDM asks you to specify the number of characters to
accept. Enter 4 for Litho, and 100 for Description.
Once you click OK, you see the "Geological data" data source in both the Project
tree and the Desktop tree (see The Project tree page 37, and The Desktop tree). This
is a Drill hole-type data source ( ).
Note: a VERTICAL_HOLES-Geology._LH text file has been created in the Project
folder. It contains all the connection parameters. It will be used automatically the next
time you open the Project, or when you Refresh the data source after modifying the
data in the Excel worksheet. You can also reuse this file to re-establish the links that
would have been broken with the Excel file by clicking on the "Use table" button in the
"External database GDM correspondence" dialog box.
By double-clicking on the data source name (or via the popup menu on the data
source name in the Desktop tree "Display List"), you display the data source of
drill holes in GDM. The data is distributed in two synchronized tables: the Collars on
top, the Runs of the hole selected in the Collars below (see List mode for Curve and
Drill hole data, page 65).

Since this data is external to GDM, you cannot modify it in GDM. Modifications must
be made in the corresponding Excel worksheet, and you must then save the Excel
workbook before clicking on "Refresh" in GDM (popup menu on the name of the data
source in the Desktop tree).
Notes:
For the Date fields, GDM uses the short date format defined in your Windows
configuration (Start Settings Control Panel Regional Settings Date). This
explains why, on connection, GDM didn't ask for the length of the Date field, and
why the date format displayed in GDM is different from that in Excel.
The drill hole run coordinates were calculated on connection.
Mineralogical data

In "Table/Query: Drill holes", choose the Minerals worksheet, and fill in the

Click on the "Coordinate system" button and change the values of Xo, Yo and Theta
as with the Geology sheet.
Click on OK, then on OK in the main dialog box.
Open the CONNECT.ERR file using the Windows Notepad:

2 errors were found.
Drill hole M112 run number 5: To Depth undefined or
decreasing or greater than the total drill hole depth.
Undefined hole/curve : line(s) without any hole/curve
name.
Correct both errors in Excel:
Row 13, depth 15.00 instead of 12.00
The second error is typical of data input in Excel: the rows following the end of the
data (as of row 150) appear empty, but actually contain invisible "residues". To
correct this error, you must select the 10 or 100 rows following the data and
"Delete" (not "Clear") them.
Save the Excel workbook.
In GDM, redo "Establish link" as above. After selecting Minerals in "Table/Query:
Drill holes", click on the "Use table" button and choose the VERTICAL_HOLES-
Minerals._LH links file which was saved on the first connection attempt. This restores
the connection parameters, including the definition of the Coordinate system. Now
click on OK.


Undefined hole/curve : line(s) without any hole/curve
name.
Drill hole M123: Collar coordinates undefined.
In Excel, correct the error that causes the two messages:
Row 44, add the name of the missing drill hole (M123).
Save the Excel workbook.
In GDM, redo "Establish link" as above. After selecting Minerals in "Table/Query:
Minerals1._LH links file which was saved on the second connection attempt. This
restores the connection parameters, including the definition of the Coordinate system.
Now click OK.
Once you click OK, you will see the "Minerals data" data source in both the
Project tree and the Desktop tree. This is a Drill hole-type data source ( ).

Analytical data

In "Table/Query: Drill holes", choose the Assays sheet, and fill in the
When you define the Uses, you will notice an anomaly on row RC: GDM considers
this field as a text field, whereas the data contained in the Excel RC column is numeric.
This is because:
1. You cannot define a field type for a column in Excel, which is a spreadsheet
program, not a database engine.
2. The MS ODBC drivers used for the connection read the first 16 rows in the Excel
sheet to deduce each column's type. Since the first value of RC is on row 23,
ODBC considers that the data in the column is of text type.
Note 1: you would be faced with the same problem by importing this Excel sheet in
Access.
Note 2: you would be faced with the same problem by connecting GDM to a text file
(.CSV).
To correct this problem, you must go back to Excel and put drill hole M121 at the top
of the file (Cut rows 21 to 30, and Insert them in front of row 2).
Once you have done this and closed Excel, you can establish the connection by filling
in the correspondence table as follows:

The coordinates of the Assays sheet are in Km and in the "geographic coordinate
system". Consequently,
You must remember to define the X and Y units as KM
You do not use the "Coordinate system" button
Click on OK.
Once you click OK, you will see the "Analytical data" data source in both the
Project tree and the Desktop tree.
Logging data

In "Table/Query: Drill holes", choose the Logging sheet, and fill in the

Check that the unit of the X and Y coordinates is indeed M.

as for the Geology sheet.
Once you click OK, you will see the "Logging data" data source in both the Project
tree and the Desktop tree.
Now proceed to page 101 (Graphic documents).

If you prefer to do the exercise with data in Excel, go back to page 81 (Connecting to Excel).
Data format in Access

The Vertical_holes.mdb database (in Tutor\Vertical_holes\Access\Start) contains all the
drill hole data, distributed in 5 tables:
T_Holes for drill hole collar data
T_Geology for geological data (lithological code and description)
T_Minerals for clay mineral semi-quantitative data
T_Assays for chemical analysis and physical parameter data
T_Logging for logging data
You will notice that:
This data describing the same drill holes is placed in different sheets, since it
corresponds to different sections according to the depth.
Each "drill hole run" data table contains essential fields: Drill hole name and To Depth.

The drill hole order is irrelevant: in the T_Logging table, the order of the drill holes is
different from that of the other sheets.
For each drill hole, the runs are arranged in increasing order of depth. The depths are
therefore all defined.
The names of fields common to all four tables (drill hole name and depth) are not
necessarily the same in all the tables.
The drill hole name is present on every line: a change of name indicates to GDM the
switch to a new hole.
Only table T_Assays can be connected to GDM, because it contains the Drill hole
name and To Depth fields, and the three coordinates. To connect the other data to
GDM, three Queries have been prepared, joining the fields in each table of drill hole
runs to the T_Holes table.
The coordinates in the T_Assays table are different from those in the T_Holes table.
These are so-called "geographic" coordinates in Km, whereas in the T_Holes table,
they are coordinates in meters in a local coordinate system (see "Local coordinate
system" in the online help index). GDM will automatically superimpose this data in the
same place on the Graphic documents if you have defined the coordinate system of
each data source.
Connection

Tutor\Vertical_holes\Access\Start) giving it the name "Vertical", for example.
Geological data
By selecting the "Save password" option, you can avoid Access requesting the
password each time you open the Project.
Click on "Connect" and choose Vertical_holes.mbd:
Click OK.

The "External database GDM correspondence" dialog box is used to define how
GDM will interpret the data contained in the Access Table or Query "to connect":
Which fields will be seen as "collar" fields, and which will be seen as "run" fields
What the use of each field in GDM will be
What the units of certain numeric fields (coordinates, angles, etc.) are
What the coordinate system is
The dialog box shows the fields in the Q_Geology query (the first Table/Query in
alphabetical order):
By default, GDM assigns the Drill hole key (field present on every line and whose
change of value indicates to GDM that you have switched to another hole) to the first
key field in the Access Query.
The names of the fields in the Access Query are displayed in gray in the left-hand
column. By double-clicking in one of the two columns with the heading on the
line of each field, you can link each field to either a "GDM-Collar field" or to a
"GDM-Run field" (or possibly to both).
GDM automatically recognizes the name of certain fields. This is the case for Z which
has been recognized as a "collar field", with the "Z coordinate" use. The unit assigned
(meters) is the Z unit, defined by default in GDM50.INI (see GDM setup file, page
296).
As soon as a Collar or Run field has been defined, GDM assigns it a "Use" by default
(usually "Text/Code/Date" for a text field, and "Variable" for a numeric field). You can
change its "Use" by double-clicking on the assigned use.
Once you have chosen the use of a numeric field, you can modify the "unit" by double-
clicking on the unit displayed.
Fill in the correspondence table as follows:

The Short ID, X, Y, Z coordinate and To Depth uses are essential in order for GDM to
recognize the drill hole data.
Notes :
You can rename the fields (this has indeed been done for Xlocal, Ylocal and Z
coordinate).
Short ID can be replaced by Full ID when the names of drill holes use between 4
and 80 characters.
You can omit the three coordinates. You will only subsequently be able to produce
Log documents (no maps/sections/formation calculations, etc.).
You can use the From Depth in place of the To Depth, but you will need an
additional Collar "Total Depth" field, or a Run "Thickness" field (see "Drill hole"
data models recognized by GDM, page 56)
Since the Geology sheet's coordinates are local coordinates, you must assign the
characteristics of the local coordinate system used. We will see that for the Assays
sheet, this step is unnecessary since this sheet's data consists of geographical
coordinates.
Click on the "Coordinate system" button, and change the values of Xo, Yo (X and Y
coordinates of the local coordinate system's origin in the geographic system), and
Theta (angle of the local coordinate system axis with the North = Y of the geographic
coordinate system):


Once you click OK, you see the "Geological data" data source in both the Project
tree and the Desktop tree (see The Project tree page 37, and The Desktop tree). This
is a Drill hole-type data source ( ).
Note: a VERTICAL_HOLES-Q_Geology._LH text file has been created in the Project
folder. It contains all the connection parameters. It will be used automatically the next
time you open the Project, or when you Refresh the data source after modifying the
data in the Access database. You can also reuse this file to re-establish the links that
would have been broken with the Q_Geology query by clicking on the "Use table"
button in the "External database GDM correspondence" dialog box.
By double-clicking on the data source name (or via the popup menu on the data
source name in the Desktop tree "Display List"), you display the data source of
drill holes in GDM. The data is distributed in two synchronized tables: the Collars on
top, the Runs of the hole selected in the Collars below (see List mode for Curve and
Drill hole data, page 65).
Since this data is external to GDM, you cannot modify it in GDM. Modifications must
be made in the corresponding Access database, then you must click on "Refresh" in
GDM (popup menu on the name of the data source in the Desktop tree).
Notes:
For the Date fields, GDM uses the short date format defined in your Windows
configuration (Start Settings Control Panel Regional Settings Date).
The drill hole run coordinates were calculated on connection.

Mineralogical data
Click on "Connect" and choose Vertical_holes.mdb
Click on OK.
In "Table/Query: Drill holes", choose the Q_Minerals query, and fill in the
as with the Geology sheet.


Drill hole M112 run number 5: To Depth undefined or
decreasing or greater than the total drill hole depth.
In Access, find drill hole M112 in the T_Minerals table. You will notice that two
successive runs have the same 12-meter depth.
Replace the second value (record whose Palygorskite field value is 1) with 15.00
In GDM, redo "Establish link" as above. After selecting Q_Minerals in "Table/Query:
Q_Minerals._LH links file which was saved on the first connection attempt. This
restores the connection parameters, including the definition of the Coordinate system.
Now click on OK.
Once you click OK, you will see the "Minerals data" data source in both the
Project tree and the Desktop tree. This is a Drill hole-type data source ( ).

Analytical data
Click on OK.
In "Table/Query: Drill holes", choose the T_Assays table, and fill in the
The coordinates of the T_Assays table are in Km and in the "geographic coordinate
system". Consequently,
You must remember to define the X and Y units as KM
You do not use the "Coordinate system" button
Click on OK.

Once you click OK, you will see the "Analytical data" data source in both the
Project tree and the Desktop tree.
Logging data
Click on OK.
In "Table/Query: Drill holes", choose the Q_Logging query, and fill in the
Check that the unit of the X and Y coordinates is indeed M.

as for the Q_Geology query.

Once you click OK, you will see the "Logging data" data source in both the Project

Graphic documents
Preview
The "Preview" function (via the popup menu on the name of a data source in the Desktop tree)
automatically displays a view as a horizontal projection of this data.
Use this function on the "Analytical data" source:
The Preview function has created a Graphic document containing two layers:
The Frame layer ( ) which is always the first layer in a Graphic document, with a
default representation.
A Drill holes layer ( ), with a default representation. The name of each drill hole is
displayed twice, because the default presentation mode posts the name of the drill hole to
the start and end of the hole.
The Graphic document appears in the Desktop tree under the name "Preview Analytical data".
The popup menu on the document name contains among others a "Rename document"
item. Proceed by renaming the document to "Location map (geog.)".
102 Getting started with GDM 5 Processing vertical drill hole data
Drill hole presentation (1/3)

To modify the presentation of a graphic layer, use the "Presentation mode" popup menu on the
name of the layer, or double-click on this name. Modify the Drill hole layer's presentation as
follows:
Click on the "ID" button and, in the "ID posted" frame, deselect the "At end
of hole" option.
Click on OK, then on OK in the "Drill hole presentation" dialog box.

To view the modification made to the Graphic document, click on the "Refresh drawing"
( ) button:

Graphic documents 103
The name of the Graphic document is displayed in red in the Desktop tree, because it has been
modified.
The popup menu on the name of the document contains, among others, a "Save" item used to
save the modifications if you wish. Once you save, the name of the document is once again
displayed in black. See Save page 63.

Coordinate system
Now use the "Preview" function on the "Logging data" source:
Use the "Illustration" ( ) button on the new Graphic document, and select the "North
arrow" and "Scale bar" options.
( ) button:

The result shows you that the "Preview" function uses the local coordinate system when it
has been defined: the coordinates of the axes are local coordinates, and the map's orientation
is different from that of "Location map (geog.)".
The North arrow shows the orientation of the local coordinate system (-11 degrees).
The Graphic document appears in the Desktop tree under the name "Preview Logging data".
Rename the document "Location map (local)", and save it.
New graphic document

To create a Graphic document in the geographic coordinate system (like "Location map
(geog.)") from the "Logging data" source, the coordinates of which are local, you must not use
the Preview function; instead, you use the GDM main menu "Project data New graphic
document":

Once you have selected the "Logging data" source, click on "Coord. system":
Select "the geographic coordinate system", then click on OK, then on OK in the "New graphic
document" dialog box.
The Graphic document appears in the Desktop tree under the name "New graphic". Double-
click on the name of the document (or choose "Display" from the popup menu) to display it:
The new graphic document contains a Frame layer ( ) in the geographic coordinates system.
To view data, you will have to add one or more graphic layers to this Document.

In summary, the "Preview" function (page 101) amounts to the following two-function
sequence:
"New graphic document" from the selected data source,
"Add layer" of data from this same source.
Remember that the "Preview" function cannot be used to choose the Document's coordinate
system when the coordinates of the data source are local coordinates. The coordinate system
chosen is always the local system.
Add layer
Go back to the "Location map (geog.)" Graphic document viewing window, and click on the
"Add layer" ( ) button:
Select the "Drill holes" layer type and the "Logging data" data source.
Double-click on the name of the new layer to display the "Drill hole presentation" dialog box.
Modify the presentation as follows:

Click on the "ID" button and, in the "ID posted" frame, deselect the "At top of
hole" option. Click OK.
Click on the "Axis" button and, in the "Plot drill hole axis with" frame, choose
the color red for the Line style. Click OK.
Click on OK in the "Drill hole presentation" dialog box.
( ) button:
The result shows that the data of the "Logging data" source (local coordinates and in
meters) is indeed superimposed automatically by GDM on the data of the "Analytical data"
source ("geographic" coordinates in Km).
Note that a GDM 5.0 Graphic document can contain up to 20 graphic layers.

Current layer
The current layer is the one highlighted in blue in the list of layers.
Move the current layer back (or forward)

The "Logging data" layer is superimposed on the "Analytical data" layer (the square
symbols representing the drill holes are in red).
To modify the order of these layers, with the "Logging data" layer selected, click on the
"Move the current layer back" ( ) button, then on the "Refresh drawing" ( ) button.
The square symbols representing the drill holes are now displayed in black, as defined in
the "Analytical data" drill hole layer presentation.
Conversely, the "Move the current layer forward" ( ) button moves the layer up to the
Graphic document foreground.
Consulting the data from the graphic
With the "Logging data" layer selected, click on the " -->table " ( ) button.
The cursor then takes the form of a table.
Click on drill hole M132. This opens the List mode of the "Logging data" data source, with
the List mode cursor positioned on the first run of drill hole M132.
Finding data on the graphics

Select drill hole M113 in the "Logging data" List mode:
Click on the " -->graphic " ( ) button.

GDM searches for drill hole M113 on all the open Graphic documents, and superimposes a
red cross at the location of the data:
Note that GDM searches for the data in all the open Graphic documents using the
"Logging data" data source, whatever the current layer on each of these Documents.
For more details, see Generalization of the inter-views system, page 65.

Define view
The "Define view" function (via the popup menu on the "Location map (geog.)" name in the
Desktop tree, or the button on the Graphic document toolbar) is used to modify the
document's limits (minimum and maximum coordinates) and the projection type (view point
on the data):
The "Volume of data" frame displays the minimum and maximum coordinates of all the data
sources used by the Graphic document.
The "New volume" frame displays the minimum and maximum coordinates of the Graphic
document. When GDM creates the Document ("Preview" function page 101, or "New graphic
document" function, page 105), it calculates these coordinates to cover all the data source's
data used to create the Document. This data source is used to create the Document's "Frame
layer" ( ), the first non-removable layer of all Graphic documents.
If you clear X0 and XM, and/or Y0 and YM, and/or Z0 and ZM, GDM will recalculate these
coordinates from the minimum and maximum coordinates of the Frame layer data source.
If you modify these coordinates, GDM will modify the Graphic document's limits:

Enter the following coordinates

then click on OK,
then Refresh drawing ( ).
You will notice that the Document's limits have been increased (there is more space between
the frame and the data).
The "Projection type" frame indicates that the Graphic document currently represents a
"Horizontal projection" of the drill holes (since the drill holes are vertical, you could be led to
believe that you are looking at a location map of the drill hole collars).
Select "West-East" (view from South)", then click on OK, then on :
You now see all the data included in the "New volume" projected on a vertical West-East
plane. This is therefore a "view from South" of all the drill holes.
Graphic document scale

By default, GDM calculates the Graphic document's scale so that the drawing fits onto an A4
page in portrait format.
Thus, if you click on "Define scale" ( ):
You will notice that the horizontal and vertical scales are 1/1857 and are non-modifiable.
Click on Cancel, then on "Define view" ( ), and choose the "South-North (view from
East)" Projection type, then click on OK, then on :

This "view from East" of all the drill holes is on a scale of 1/1643, i.e., different to that of the
"view from South".
For as long as you are in a "data exploration phase", you can let GDM calculate the scale of
each view according to a paper format. Consequently, if you select "A4 Landscape", the views
from the South and East become more readable.
To produce printed documents, you need to be able to control the scale of your Graphic
documents.
For this purpose, click on "Define scale" ( ) and, from the "Scale for paper format" drop-
down list, choose "Personalized" (the first in the list, above "A4 Portrait"):
You can now modify the scales. Enter 1/1200 for the horizontal scale and 1/600 for the vertical
scale. Note that when you enter a scale value, the "Frame size" is calculated simultaneously,
which lets you see whether you can print the Document on your printer or plotter.
Click on OK, then on to display the "view from East" with this new scale:
From now on, all the sections you define from this Document will be calculated with these two
scales, and the horizontal projections will be at a scale of 1/1200.

Vertical sections
Viewing a projection of all the drill holes on a vertical plane is not particularly beneficial. You
will usually want to be able to define sections that are "less thick".
Sections parallel to the axes

Proceed as follows to view a West-East section covering drill holes M112, M122,,
M152:
Click on
Select
Reduce the section's thickness by entering
Click on OK
Refresh the drawing ( ):
On a section parallel to the axes, the horizontal coordinates are absolute coordinates (here,
the X coordinates).
Sections
A section is defined with the mouse using either the "Define section" ( ) or the "Define
adjusted section" ( ) functions on a horizontal projection view.
To go back to the horizontal projection of all the drill holes on "Location map (geog.)":
Click on
Select
Clear the values Y0 and YM, or enter
Click on OK
Refresh the drawing ( )
Using "Define section" ( ), you will define a section by clicking successively in any
two places on the horizontal-projection Graphic document.

The function is disabled (button grayed) if the Graphic document has been modified
without being redrawn. In this case, click on .
Using "Define adjusted section" ( ), you will define a section by clicking successively
near to two points of data on the horizontal-projection Graphic document, having selected
the graphic layer that uses the data on which you wish to "adjust" the section.
The function is disabled (button grayed) in the following cases:
The layer selected is the Frame layer ( ), or a Base map layer ( ), or a Grid
profile layer ( ). Select another layer.
The Graphic document has been modified without being redrawn. In this case, click on
.
On "Location map (geog.)", we will define a section adjusted on drill holes M113 and
M151:
Select one of the drill hole layers, for example
Click on . The cursor takes the following form: (digitization cursor)
Click near to drill hole M113, then keeping the button pressed, drag the cursor near to
drill hole M151 and release.
This effectively draws the extension of the section on the Graphic document:

All the data contained in the rectangle will be represented on the section.
The arrow indicates the "view point" on the section. The section will be seen from the
South-East. The view point is defined by the order in which you digitized the two points:
the first point defines the left side of the section.
GDM extends the section on both sides of the points clicked by a length equal to 5% of the
distance between the two points. These are the "right and left extensions".
The width (thickness) of the section is equal to 20% of the distance between the two
points.
GDM displays the "View parameters" dialog box:
To keep the section as it is at present, you would simply click on OK

It is difficult to know whether drill holes M122, M123, M141 and M142, which are at the
edge of the section's rectangle, will be visible on the section. To eliminate them once and
for all, you need to reduce the width of the section, by entering 0.03 KM, for example.
Conversely, to ensure their presence on the section, you will increase the width by entering
0.05. The OK button is subsequently disabled. Click on the "Display" button to see the
section's new limits.
To display this section, click on OK, then on :
On an ordinary section, the horizontal coordinates are relative coordinates, to the left of the
section.

If you want to modify the section's

parameters, click on , and enter your
modifications in the "Section parameters"
frame
To draw a new section, click on , select , refresh the drawing ( ),

and use or .

In the list of "Location map (geog.)" layers, double-click on the drill hole
layer to modify its presentation.
Click on the "Diagram to the right of the drill hole" button:
In the "Variable to post" frame:

Select "Variable".
Choose Log3 in the drop-down list. This variable's Min and Max values in the data source
are then displayed (3.1370 81.5670).
"Interval to process": enter 0 and 100.
In the "Graph type" frame, select "Linear graph" (since the data in the "Logging data" source
describes point measurements, not drill hole run measurements.

In the "Graph color/width" frame:

No. units per cm: enter 200 (note that the graph's maximum width is instantly calculated),
Curve color: choose Red in the drop-down list.
Click on OK, then on OK in the "Drill hole presentation" dialog box, then click on the
"Refresh drawing" ( ) button:
To see the drawing in more detail, use the "Zoom in" function:
Now double-click on the drillholeslayertomodifyitspresentation.
Click on the "Diagram to the right of the drill hole" button:

In the "Variable to post" frame:

Select "Variable".
Choose RVB in the drop-down list. This variable's Min and Max values in the data source
are then displayed (390 998).
"Interval to process": enter 400 and 1000.
In the "Graph type" frame, select "Bar graph" (because the data in the "Analytical data" source
describes drill hole runs (samples between two depths) and not point measurements.
In the "Graph color/width" frame:
No. units per cm: enter 1200 (note that the graph's maximum width is instantly calculated),
Curve color: choose Blue in the drop-down list.
Click on OK.
Click on the "Values to the right of the drill hole" button:

In the "Field type" frame, select "Variables".

In the "Field to post" frame:
Choose RVB in the drop-down list,
Choose the font: Arial 8
In the frames at the bottom:
Select "Values at middle of run"
"Distance Axis values": 0.7 cm
Select the "Ticks at end of run" option
"Length": 0.1 cm
Click on OK, then on OK in the "Drill hole presentation" dialog box, then click on the
"Refresh drawing" ( ) button:

Creating a pattern palette

To view the data in the "Geological data" source on the Graphic document, you must create a
Palette which will associate a pattern with each geological code (for the palettes, a Code is a
Text/Code/Date field with a length of up to 20 characters).
Use the GDM main menu: "Project data New palette":
Select "Patterns for a code", then click on the "List of code values" button:
Choose "Geological data" from the "Data source" drop-down list.

Select "Run codes", then "Litho" from the drop-down list. In the Values field, GDM then
displays the list of all the "Litho" code values used in the "Geological data" source in
alphabetical order.
Select the "Add one line for each code in the table" option.
Click on OK.
GDM fills in the "Patterns for a Code" table:

You must now complete this table by choosing:

Patterns (double-click in the "Num" column).
Colors for the patterns (double-click in the "CLOR" column), if you want to replace the
default color (CLOR = 1 corresponds to Black).
Scales in terms of X and Y for the patterns (by entering values in the "Xsca" and "Ysca"
columns), if you want to replace the default scales.
Note that you can also directly enter the pattern and color numbers:
By consulting the Standard GDM patterns palette, page 294,
By consulting the GDM 48-color palette after printing file
Tutor\VRML\Programs\PalRVB.doc on your printer or plotter (the rendering of the colors
varies according to the printer used).
Complete the patterns table as follows:

Num CLOR Xsca Ysca Code
8 27 1 0.5 A Clay
23 46 0.6 0.6 AC Calcareous clay
177 6 0.7 0.7 AS Silty clay
26 4 0.8 0.8 CA Limestone
6 5 0.6 0.6 GLAU Glauconite
102 2 0.6 0.6 LA Laterite
4 23 0.6 0.6 SA Sand
31 1 0.6 0.6 SOL Soil
Given by way of information, the right-hand column specifies the meaning of the codes.
Once you click OK, you see the "New palette" in the Desktop tree. Rename it "Palette 1" (via
the popup menu on "New palette").

Click on the "Add layer" ( ) button of the "Location map (geog.)" Graphic document, and
add a layer of drill holes using the "Geological data" source.
We will use the palette we have just created.

In the list of "Location map (geog.)" layers, double-click on the drillholes

layertomodifyitspresentation.
Select
then click on the "Lithology" button":
Select "Litho" from the drop-down list.

In the "Lithology column" frame:
Select "Left of axis"
Enter 0.5 cm for the "Column width"
Click on OK, then on OK in the "Drill hole presentation" dialog box, then on the "Refresh
drawing" ( ) button:
By clicking on the " -->table " ( ) button, you can access any run of the drill holes visible
on the section. According to the Drill hole-type layer selected, you will access one of the three
data sources used by the Graphic document.
Conversely, in the List mode of each of the tree data sources, you can find the position of a
drill hole run on the Graphic document by clicking on the " -->graphic " ( ) button.

Representation of the topographic surface

To see the plotting of the topographic surface on the section, you must first model the
topographic surface on the entire area covered by the drill holes (i.e., create a 2D grid of the
topography). By then adding a Grid profile-type layer to our Document, the topography will be
visible on any section plotted from this Document.
Modeling the topographic surface

We will estimate the topographic surface at all points of the area covered by the drill holes
using the Z coordinates of the 18 drill hole collars. Note that if we had a greater number of
points, such as those on a topographic survey, we would obtain a more precise topographic
model (less smooth).
Use the "Calculations Estimate 2D Grid" popup menu on one of the data sources, e.g.,
"Geological data":
Select "Interpolation on the collars", then click on OK:
Simply clicking on the button selects Z as the unique variable to interpolate, before
clicking OK in order for GDM to calculate a model of the topography using all the default
options:
The grid will be a grid of points.
The grid origin and dimensions are proposed to cover the entire area covered by the
drill holes.

The interpolation method will be "Kriging for linear variogram without drift", and a
selection by octants of the "neighborhood" will be done.
The calculation will not use faults or limits (beyond those imposed by the
neighborhood).
We will not detail all the possible GDM interpolation options. You will find more
information in the GDM online help by pressing F1 when the "Create 2D grid" dialog box
is displayed.
We will modify some of the interpolation options before starting the grid's calculation:
Remember to first select the Variable to interpolate ( ).
Click on the "Options..." button in the "Grid definition" frame:
We will choose a grid of blocks rather than a grid of points, because the grid of blocks
layer presentation mode is more "readable".
Select "Block grid", choose "The coordinates specified for the grid origin are those: the
center of the first block". Enter 1 as the Number of discretization points in a block along X
and along Y. Click on OK.
Enter 5 m along X and along Y for the "Block size":
You will notice that GDM immediately recalculates the Number of blocks, so as to cover
the area to estimate.
Click on the "Neighborhood" button in the "Interpolation method" frame:

Select the "Select by octants" option. Do not change the number of points proposed by
GDM. For more details, press F1 ("Neighborhood" online help).
Click on the "Save parameters" button, enter the name "Topography", then click on
"Save". This name will be displayed in the Project tree's list of "Interpolation"
parameters. You can thus reuse these parameters, with or without subsequent
modifications, for another interpolation.
Click on OK in the "Create 2D Grid" dialog box.
GDM calculates the grid, and displays:
This file contains the statistics of the interpolation that you can consult using the Windows
Notepad.
Once you click on OK, you see the "2D Grid on Geological data: Collars" data source in
the Desktop tree.
This is a Grid-type data source ( ).
Rename it "Topography":

Representing the topography on a section

(Grid profile layer)
On "Location map (geog.)", click on the "Add layer" ( ) button.

In the "Data" frame, choose "Grid profile", and in "Data source": "Topography". Click on
"Refresh drawing" ( ):
The topography represented is the intersection of the model ("Topography" grid-type data
source), with the median plane of the section (passing through drill holes M113, M132 and
M151). The other drill holes are not in the section's median plane, and do not therefore all
appear as starting on the topography.
To modify the presentation, double-click on the "Grid profile" layer:
To fill in above the topography, click in the first rectangle below "Filling". In the color
palette, click on gray-light green (color no. 32), then on the "Add" button:

To fill in below the topography, click in the following rectangle. In the color palette, click
on light yellow (color no. 15), then on the "Add" button.
Click on OK in the "Profile presentation" dialog box, then on "Refresh drawing" ( ):
the filling in of the "Grid profile" layer hides the "drill hole" layers. You must "Move the
current layer back" to place it just after the "frame" layer. To do so, click four times on
"Move the current layer back" ( ).
Click on "Refresh drawing" ( ):
Representing the topography on a map

(Isoline layer)
To go back to the horizontal projection of all the drill holes, click on , select
, then click on OK and on Refresh the drawing ( ).
The "Grid profile" layer ( ) is not represented on the graphic, since this type of layer is
only represented on sections.
To represent the topography on a horizontal projection, you can choose between two types
of layer:
A "Grid" layer ( ). For a grid of blocks, the default layer presentation is a grid of
"rainbow" colored blocks from blue (minimum grid value) to red (maximum value).
This presentation has the advantage of providing an instant preview of the interpolation
result, and enables you to spot any anomalies in the grid calculation just done, for
example, the presence of non-colored blocks indicating a neighborhood that is too
restrictive.

An "Isoline" layer ( ).This is the type of layer we will use to represent the
topography on our map:
Note: "Grid" ( ) and "Isoline" ( ) layers are only represented on horizontal
projections (maps).
On "Location map (geog.)", click on the "Add layer" ( ) button.
In the "Data" frame, choose "Isolines", and in "Data source": "Topography". Click on
"Refresh drawing" ( ).
We now have a view of the topographic surface, according to the default "Isoline" layer
presentation: interval between curves calculated by GDM, unsmoothed curves, no isoline
labels and no coloring between the curves:
To modify the presentation of the isolines, double-click on the isolines

layer:

In the "Isoline definition" frame, enter an interval of 1 meter (instead of 2) for the "Normal
isolines". GDM instantly recalculates the value of the last isoline (53 m instead of 52).
Enter an interval of 5 meters, and a thickness of 0.06 cm for the "Master isolines".
In the "Isoline labels" frame, select "Isoline labels", and deselect the "Label at start of
isoline" option.
In the frame on the right, choose "Spline" for the "Isoline smoothing", then click on the
"Filling" button:

Select the "Filling with colors" option.

Click on the "Export legend" button to save the legend which we will use in chapter
"Drawing illustrations", page 132:
In the "File name" field, enter "Legend_Iso". The extension will be WMF.
Click on "Save", then on "OK" in the "Filling by intervals" box, then on OK in the "Isoline
presentation" box.

The filling of the "isolines" layer hides the "drill holes" layer. You must move this current
layer back to place it just after the "Grid profile" layer. To do so, click four times on "Move
the current layer back" ( ), then click on "Refresh drawing" ( ).
Note: the grid is inclined because it has been calculated from the "Geological data" source
whose coordinates are in a local coordinate system at an angle of 11 degrees with the North
(defined on connection to the data). If you had estimated the topography from the
"Analytical data" source, the grid would have been calculated in the geographic coordinate
system, and would be parallel to the axes of the Graphic document.
Drawing illustrations
Title
Click anywhere on the Graphic document to display the Scale
popup menu: View
Illustration
Frame and Mesh
"Title" (equivalent to ) is used to insert a title at the top of the Graphic document.
"Scale" (equivalent to ) is used to define the scale of the map, or the two section scales.
"View" (equivalent to ) is used to define the projection type (the angle of view) and the
maximum coordinates of the volume represented.
"Illustration" (equivalent to ) is used to insert the following in the Graphic document:

the North arrow

a scale bar (two bars for the sections)
a heading and/or legend
"Frame and mesh" (equivalent to a double-click on the Document frame layer ) is used to
define the axis graduations and to add a mesh.
For a quick illustration of your drawing, select the "Illustration" menu item:
.
Select "North arrow", "Scale bar" and "Heading (WMF)", then click on "Open":
Select the file containing the legend you saved in the previous chapter (Representing the
topography on a map (Isoline layer), page 128), then click on "Open".
Click on OK in the "Drawing illustrations" dialog box, then on the "Refresh drawing"
( ) button:

The "Heading" and "Legend" functions in the "Illustration" function are used to quickly add a
legend to the Graphic document, whatever the projection type (map or section):
The "Heading" is always positioned at the bottom right between the two Graphic document
frames.
If we had chosen "Legend" instead of "Heading", the legend would have been positioned at
the bottom right of the Document, inside the inner frame.
These functions cannot be used to modify the legend's size, or to position it other elsewhere
than in the locations corresponding to these two functions.
Illustration using the GDM Images database

The role of the Images database is to store:
the names of images in Windows metafile format (WMF) that can be generated by GDM
or by another software application,
the coordinates of the images,
image position, dimension and visibility parameters.
Images databases are used in the Graphic documents via the Images ( ) layer. This type of
layer has no Presentation mode.
The images can be photos of samples or landscapes, sample test graphics, or any other image
of which you know the whereabouts.

Here we will use the properties of the Images databases to position the legend and a logo on
our Graphic document, while controlling their size.
Converting graphic formats: WmfConv

The legend is in the Project folder under the name Legend_Iso.wmf. It is already a
Windows metafile since it was created by GDM.
The logo is in the Project folder under the name BRGM.BMP. In order for GDM to be able
to use it, it must first be converted to WMF format:
Click on Start Programs GDM 5.0 WmfConv
Load the logo: File Open, BRGM.BMP
Save it as a WMF file: File Save, BRGM.WMF
Close WmfConv.
Note that WmfConv can convert a wide variety of graphic formats to WMF, and that you
can also use it to convert WMF files created by GDM into a wide variety of other formats.
Creating an Images database

GDM main menu: "Project data New GDM database":
In the "Type of data" frame, select "Points".

Choose "IMAGES.B2D" as the "Model, then click on OK:

Answer No (you do not need to modify the structure of this database).

You then see the "New database Images" data source in the Project and Desktop trees. It is
an Images database-type data source ( ).
Rename it "Legend" (popup menu "Rename data source").
Entering values in the Images database

Double-click on the name of the Images database to open it in List mode.
Click twice on "Add lines" ( ) to add two empty lines.
To know what the various fields are used for, look up "Images database" in the GDM's
online help index.
Fill in the first two lines as follows (the columns of unused fields are not displayed):
Notes:
- The logo's anchor point is the top left corner
of the image (ULFT).
You place this point at coordinates X0,YM of
the Graphic document volume.
- The legend's anchor point is the bottom left
corner of the image (LLFT).
You place this point at coordinates X0,Y0 of
the Graphic document volume.
Be careful with rounded values: if you use the Y0 coordinate displayed in the "New
volume" frame of "Define view" (Y0 = 124.587) for the "Leg" legend, this legend is
not displayed on the Graphic document (the image is considered to be outside the
volume). Simply add 1 meter (124.588 Km) for the image to appear.
A X translation of 5 meters has been added to "Leg" to avoid the legend being stuck to
the frame.
Images layer
To display the Logo and Legend referenced in the Images database on "Location map
(geog.), simply add an "Images" layer ( ) on the "Legend" data source. This type of
layer has no Presentation mode.

You can now delete the heading (legend's display to the right of the frame): click on
"Illustration" ( ) and remove the "Heading (WMF)" check mark.
Click on "Refresh drawing" ( ).
Printing the drawing

Before printing a Graphic document, click on "Define scale" ( ) to see the minimum paper
size to be used (in "Frame size").
Click on , or use the "Print" popup menu on the name of the Graphic document in the
Desktop tree.
Choose the paper size and orientation according to the "Frame size". If you choose a format
that is too small, the drawing will be clipped on the right-hand side and/or at the bottom.
Note: you can also use the GDM main menu: "Configuration Printer setup for graphic
documents" to define the printer settings for all the Project's graphic documents.

Exporting the drawing

Use the "Export WMF" popup menu on the name of the Graphic document in the Desktop
tree to save the graphic as a Windows Metafile (.WMF extension).
Importing the drawing to Word/Excel/PowerPoint

In these applications, you use the "Insert Image From file" function. You can then keep
these drawings as they are, or modify them as appropriate.
Tip: in PowerPoint, when possible, avoid using the "Ungroup" function which thickens the
lines. Instead, superimpose your modifications on the original drawing.

Modeling geological formations/bodies
Modeling a geological formation

Modeling a geological formation consists in modeling the surfaces of its "hanging wall" and its
"footwall" (creating a 2D grid of the hanging wall and a 2D grid of the footwall) in the same
way as we modeled the topographic surface (see Modeling the topographic surface, page 124),
then in applying, if necessary, calculation formulas to correct these surfaces if they intersect at
certain points on the model.
The data to interpolate will be the points of the hanging wall (/ footwall) whose three X, Y, and
Z coordinates you know. This data can come from:
Drill holes: the "Determine formation or composite" function is used to extract this data
from a drill holes data source.
Surface data: the boundary of the formation observed in the field.
Data digitized on sections: the geologist's interpretation on sections displaying drill hole
data, or sections provided by a geophysical survey.
We will be able to display the interpolated surfaces just as we displayed the topographic
surface, by inserting "Isoline" layers in our Graphic documents for the views on a horizontal
projection (maps), and "Grid profile" layers for the sections.
Determine formation or composite

This GDM function offers four different ways of defining a formation:
Using the values of a Code (Text/Code/Date field): the formation is defined by one or
more values of this code. The formation's hanging wall in each drill hole will be the
start of the first drill hole run containing one of the list values. The footwall will be the
end of the last run containing one of the list values.
Using the values of a Variable (numeric field): the formation is defined by the drill hole
runs for which the value of this variable is greater (or less) than a given value
(threshold). The formation's hanging wall in each drill hole will be the start of the last
drill hole run for which the value of this variable is greater than the threshold. The
footwall will be the end of the last run for which the value of this variable is greater
than the threshold.
Between two depths: this way of defining a formation is used (exclusively with vertical
drill holes) to define slices of terrain parallel to the topographic surface.
Between two Z: used to define horizontal slices of terrain.
Whatever the method used to define the formation, you can ask GDM to calculate for
each drill hole the average value of any variable or list of variables inside the formation.
For more details on this GDM function, look up "Formation" in the online help index, or
press the F1 key when the function is selected or its dialog box displayed.
Using the "Geological data" drill hole data source, we will use the first method to define
the "carbonate" formation from the values of codes "CA" and "AC" ("Limestone" and
"Calcareous clay").
On the Desktop tree's "Geological data" data source, choose "Calculations Determine
formation or composite" from the popup menu:
In the "Determine formation or composite" frame:

Select "from code",
Select "Litho" from the drop-down list of codes,
Use the arrow to select values "AC" and "CA" of the "Litho" code.
In the "Values calculated for the formation or the composite" frame, select the "Values
stored in a new GDM database" option.
Click on the "Save parameters" button, then enter the name "Carbonate", and click on
"Save". This name will then be displayed in the Project tree in the list of "Formations"
parameters. You can thus reuse these parameters, with or without modifications, to
determine a new formation.
Click on OK in the "Determine formation or composite" dialog box.
A new "Formations on Geological data" source is displayed in the Desktop tree. This is a
Points-type data source ( ).
Rename it "Carbonate":

Modeling geological formations/bodies 141
Double-click on this data source to open the List mode:
This Points data source contains one line for each drill hole.
The different fields describe the intersection of the formation with the drill hole. The
complete description of these fields is given in the online help ("Elements calculated for
the formation").
We will focus on the following fields in particular:
Z1: altitude of the drill hole's intersection with the formation's apparent hanging wall,
Z2: altitude of the drill hole's intersection with the formation's apparent footwall,
THCK: apparent thickness of the formation,
FORM: code indicating the position of the drill hole in relation to the formation.
Z1
Z1
Z2
Z1
Z2
Z1
Z2
Z2
Values of FORM: CROS END BGIN IN NO

CROS: the drill hole crosses the formation
END: the drill hole ends in the formation
BGIN: the drill hole begins in the formation
IN: the drill hole is entirely in the formation
NO: the drill hole is outside the formation
This diagram shows us that:
Z1 is the true altitude of the formation's hanging wall when FORM = CROS or END,
Z2 is the true altitude of the formation's footwall when FORM = CROS or BGIN,
THCK is the true thickness of the formation when FORM = CROS.
When the points data source resulting from "Determine formation or composite" shows the
CROS value for the FORM code for all the drill holes, you can simultaneously interpolate
Z1, Z2 and THCK (by choosing the 3 variables in "Estimate 2D grid"), from all the records
of this data source.

The same applies if you only find values CROS and NO, since Z1, Z2 and THCK are not
defined when FORM = NO.
In all other cases, you must calculate Z1, Z2 and THCK separately on sets of different drill
holes.
Note: in all cases, instead of interpolating THCK, you can alternatively calculate the
thickness after interpolating Z1 and Z2, from the difference between the two surfaces.
Graphic verification before interpolating

A quick way of checking both the drill hole data (values of the "Litho" code) and the
method for defining the formation chosen is to plot a map showing the distribution of the
FORM code's values.
For this purpose, we will use a palette supplied ("FORMPAL" in the Project folder),
containing the definition of "Symbols for a code":
Main GDM menu: "Project data Establish link with palette":
Name this palette "Formations", then click on "Connect":

Select "FORMPAL.HED", then click on "Open".

A new "Formations" palette is displayed in the Desktop tree.
Double-click on this palette and view the contents of the "Symbols for a code" table:
This is a palette for "standard" GDM codes (see Palettes, page 56).
Click on the "Legend" button:

Click on the "Export" button.

Enter the filename "Legend_FORM", then click on "Save".
You can view it in GDM using the GDM main menu: "Project data Load Windows
metafile", then selecting file "Legend_FORM.WMF":
Rename the "New Graphic" graphic document "Carbonate (maps)". At the moment, it has
only one Frame layer. We will add a Points layer on this document using the "Carbonate"
data source.
On "Carbonate (maps)", click on the "Add layer" ( ) button.
In the "Data" frame, choose "Points/End of run", and in "Data source": "Carbonate". Click
on "Refresh drawing" ( ).
To modify the Points presentation, double-click on the Points layer:

Select "Formations" in the list of palettes, then click on the button representing the
position of the point's graphic symbol:
Select the "Symbol according to field value:" option, then select the "FORM" field in the
drop-down list before clicking on OK.
Click on OK in the "Point presentation" dialog box , then click on "Refresh drawing"
( ):

At first sight, you will not notice any inconsistencies in the results of the determining of
the formation:
Drill holes M111, M112 and M113 which are outside the (FORM = NO) are grouped
together in the West.
Drill holes M141, M142 and M153 which have not crossed the formation's footwall
(FORM = END) are mostly in the East.
However, you must check the consistency of the model with the data because holes
M151 and M152, located further away, have crossed the formation's footwall.
Interpolating the formation's hanging wall

Earlier, we saw that Z1 is only the true altitude of the formation's hanging wall when
FORM = CROS or END. Since the values of FORM in the "Carbonate" data source are
CROS, END and NO, we can interpolate Z1 on all the records.
On the "Carbonate" Points data source, choose "Calculations Estimate 2D grid" from the
popup menu.
Click on the button to select Z1 as the only variable to interpolate:

IMPORTANT: for the construction of the final model which will have three surfaces
(hanging wall and footwall of the "Carbonate" formation, and topography), we must merge
the three interpolations (i.e., the 3 grids) in a single grid to perform additional calculations
between the three estimated variables.
However, Grid data sources can only be merged if their geometric characteristics ("Grid
definition" frame) are strictly the same: same grid type, same origin and same dimensions.
To create a grid with geometric characteristics identical to an existing grid, click on the
"Use model" button which copies a grid's characteristics. We can use the "Topography"
grid as a model to define the geometry of our "Carbonate hanging wall" grid.
Since you may want to copy the characteristics of a grid located in any GDM Project, the
"Use model" function uses the name of the grid file, not the name of the data source. To
find out what this name is, click on "Cancel" in the "Create 2D grid" dialog box, and
choose "Properties" from the popup menu on the "Topography" Grid data source:
The file's name is given on the right under the "Type of database" field. The "Topography"
data source file is thus called GRID1.GRD, and is located in the Project folder since it is
not preceded by a path.
Use the "Calculations Estimate 2D grid" popup menu again on the "Carbonate" Points
data source, then click on the button to select Z1 as the only variable to interpolate.
Click on the "Use model" button and select the file corresponding to the "Topography"
data source. When you subsequently click on "Open", you will see that the "Grid
definition" has changed.
Click on the "Save parameters" button, enter the name "Carbonate hanging wall" then click
on "Save".
Click on OK in the "Create 2D grid" dialog box.
The "2D Grid on Carbonate" data source is now visible in the Desktop tree.
Rename it "Carbonate hanging wall".
Representing the formation's hanging wall on a map
On "Carbonate (maps)", click on the "Add layer" ( ) button.

In the "Data" frame, choose "Grid", and in "Data source": "Carbonate hanging wall". Click
on OK.
A Grid layer has been added to the list of "Carbonate (maps)
layers".

Click on "Move the current layer back" ( ) so that the new layer does not hide the
Points layer, then click on "Refresh drawing" ( ):
We can now see the surface of the "Carbonate" formation's hanging wall, according to the
default Presentation mode for "Grid (of blocks) layers.
This type of layer has the advantage of providing an instant preview of the interpolation
result, and enables you to spot any anomalies in the grid calculation just done, for example,
the presence of non-colored blocks indicating a neighborhood that is too restrictive.
Filtering a data source

Earlier, we saw that Z2 is only the true altitude of the formation's hanging wall when
FORM = CROS or BGIN.
Since the values of FORM in the "Carbonate" data source are CROS, END and NO, we
will filter this data source to show only those records whose FORM = CROS.
On the "Carbonate" Points data source, choose "Filter Filter" from the popup menu:

Click on "New":
Select the "FORM" field in the drop-down list.

To display this field's values in the data source, click on "List of values".
Now click on "New value ->", and enter .
Click on to enter the formula in the list of criteria.

Click on OK, then on OK in the "New filter" dialog box.
A new Points data source called "Filter on Carbonate" is displayed in the Desktop tree.
Double-click on it to open the List mode: you only see the 12 drill holes for which FORM
= CROS.
This data source is a filtered view of the "Carbonate" Points data source (the data has not
been copied). If you make any modifications in either of these two sources, they will be
visible in the other one.

Interpolating the formation's footwall

On the "Filter on Carbonate" Points data source, choose "Calculations Estimate 2D grid"
from the popup menu.
When we interpolated the formation's hanging wall, we saw how the geometric
characteristics of an existing grid could be copied via the "Use model" button.
This time we will click on the "Use parameters" button:
Select "Carbonate hanging wall", then click on "Open".

Click "Yes" for the warning message.
All the parameters used to estimate the formation's hanging wall are thus copied: grid
definition as with "Use model", but also all the other parameters (names of variables to
estimate, interpolation method, neighborhood, faults and limits if any were defined).
Click on to delete Z1 from the list of variables to interpolate, then on to add Z2

and THCK to this list. We can interpolate THCK along with Z2 since the true thickness
corresponds to FORM = CROS:
Click on the "Save parameters" button, enter the name "Carbonate footwall", then click on
"Save".
The "2D grid on Filter on Carbonate" data source is now displayed in the Desktop tree.
Rename it "Carbonate footwall".
Representing the formation on sections

We will now make a copy of "Location map (geog.)" which is currently on a horizontal
projection (map), under the name "Sections" and which we will use to view sections:
Right-click on "Location map (geog.)" in the Desktop tree, and choose "Save as" in the
popup menu. Enter "Sections" and click on OK.
Double-click in the Desktop tree to view the Document.

Remove the layer using the "Delete layer" popup menu item on the name of
the layer, or the button. Indeed, this legend is not adapted to the sections.
Define an adjusted section ( ) from drill hole M151 to hole M153.
We will now add two "Grid profile" layers to view the "Carbonate" formation's hanging
wall and footwall:
Click on "Add layer" ( ). In the "Data" frame, choose "Grid profile", and in "Data
source": "Carbonate hanging wall", then click on OK.
Click on "Add layer" ( ) again. In the "Data" frame, choose "Grid profile", and in
"Data source": "Carbonate footwall", then click on OK.
Double-click on the layer to modify its presentation:

Choose Red as the
"Profile color":
Click on OK, then on "Refresh drawing" ( ):

You will notice that the formation's footwall calculated by interpolation crosses drill hole
M153, whereas it should pass below the drill hole, since the hole ends in the formation.
You will notice the same situation for drill holes M141 and M142 on the section between
drill hole M141 and hole M144.
Adding interpretation data to the model

In order for the model to comply with the observations made on drill holes M153, M141
and M142, you must take account of the information provided by these drill holes: the
footwall of the "Carbonate" formation is lower than the end of these holes:
Z2 < 22.4 m for M153
Z2 < 28.2 m for M141
Z2 < 28.8 m for M142
Since the interpolation algorithm cannot use inequalities, it is up to the geologist to
estimate the values of Z2 on the position of these three drill holes, and to add them to the
data used for the first estimate of the formation's footwall, before recalculating the model.

Note 1: similarly, the geologist can add "interpretation data" at any place in the area to be
estimated in order to "impose" greater geological credibility on the model.
Note 2: you will not add "interpretation data" in the "Carbonate" Points data source which
contains the "basic data", but in a copy of this data source. You can thus subsequently
modify the interpretation data, but not the basic data, which you must keep as a reference.
Right-click on the "Carbonate" Points data source in the Desktop tree and choose "Save
as". Enter the name "Carbonate (interpreted)", then click on OK.
Double-click on this new data source to open it in List mode, and enter new values for Z2:
For M141: 25 m (instead of 28.2)
The name of the "Carbonate (interpreted)" Points data source in the Desktop tree is
displayed in red since it has been modified. Use the "Save" popup menu item.
We will recalculate the formation's footwall from the "Carbonate (interpreted)" data
source.
Right-click and choose "Calculations Estimate 2D grid".
Click on the "User parameters" button:
Select "Carbonate footwall", then click on "Open".
Answer "Yes" to the warning message.
Click on to delete THCK from the list of variables to interpolate, since we have not
"corrected" this variable in the data source.
Click on the "Save parameters" button, enter the name "Carbonate (interpreted) footwall",
then click on "Save".
The Desktop tree now displays the "2D grid on Carbonate (interpreted)" data source.
Rename it "Carbonate (interpreted) footwall".
Go back to "Sections".
source": "Carbonate (interpreted) footwall", then click on OK.
Choose Blue as the
"Profile color":

The blue curve shows a credible estimate of the carbonate formation's footwall.
Final model: creating the grid

We will merge the three surface models (topography, carbonate formation hanging wall
and footwall) on the same grid, thus making it possible to perform calculations between the
surfaces.
Reminder: the three models can only be merged because we were careful to calculate them
all with the same grid definition (geometric) (see Interpolating the formation's hanging
wall, page 146).
Right-click on the name of the "Topography" data source, and choose "Save as":
Enter "Model" for the "Name of data source in the project", then click on OK.
Right-click on the new "Model" data source and choose "Structure":

Click on the "Modify" button to modify the list of Fields:
In the list of "Variables", replace "ZEST" (Z estimated) with "Topo", and enter the
following new variable names: HW, FW, Cov (overburden thickness), and Thck (for
thickness of the carbonate formation).
These are short names, limited to 4 characters.
Click on OK, then on the "Field attributes" button in the "Structure of the GDM
database" dialog box:
In the "Full name" column, enter explicit names for the 5 variables (these names are
limited to 20 characters).
Double-click in the "Usage" column and choose ALTI as the usage for variables Topo,
Carb Hanging wall and Carb Footwall.
Double-click in the "Unit" column and choose M for all the variables.
Click on OK, then on OK in the "Structure of the GDM database" dialog box.
Right-click on the name of the "Model" data source and choose "Save" from the popup
menu.
Open this data source in List mode (double-click on the name of the data source):

Final model: adding values

We will "Update" the "Carb Hanging wall" field from the "Carbonate hanging wall" data
source.
Right-click on the "Model" data source, and choose "Update GDM fields":
Select "Carbonate hanging wall" in the "Input data source" drop-down list, then click on
OK:

Double-click in the "GDM Fields" column and select "Carb Hanging wall" in the list of
"Model" data source fields to be updated from "Read" variable Z1, then click on OK.
Once you have saved the "Model" data source, repeat the "Update" operation on this
source for the "Carbonate footwall" field using the "Carbonate (interpreted) footwall" data
source:
We will now calculate the thickness of the overburden (Topography Formation hanging
wall), and the thickness of the formation (Formation hanging wall Formation footwall).
Save the "Model" data source, then choose "Calculations Assign value to numeric
fields" from the popup menu.
Click on the "Add" button in the "Calculations" dialog box:
Choose the first formula type, use the four drop-down lists to define it, then click on OK.
Click on "Add" again in the "Calculations" dialog box, and define the second formula as
follows:
Click on OK:

Click on the "Save as" button and enter "Thickness on Model" as the name for these
parameters. Click on OK, then on the "Apply" button in the "Calculations" dialog box.
You will now see all the fields with values in the "Model" data source list mode:
Final model: checking values

Once you have saved the "Model" data source, choose "Display Summary" from the
popup menu.
By reducing the size of the "Name" and "Description" columns until they are completely
hidden, or by using the horizontal scroll bar to see the columns on the right, you can see
the following statistics, which were automatically calculated when you saved the data
source:

You will notice a negative minimum value for the thickness of the carbonate formation: the
two estimated surfaces of the hanging wall and the footwall intersect.
This occurs to the West of the area, where the thickness of the formation decreases, and
where there is no data in drill holes M111, M112, and M113. This can be seen on a section
between M111 and M144:
To correct this anomaly in the model, we will add a new calculation formula that forbids
the formation's footwall to pass above the hanging wall (we could also "fix the footwall"
and forbid the hanging wall from passing beneath. When you construct a multi-layer
model, you will fix the best-known surfaces).
Right-click on the "Model" data source and choose "Calculations Assign value to
numeric fields" from the popup menu.
Click on the "Open" button, select "Thicknesses on model" in the list of parameters, then
click OK :

With the table's first formula selected, click on the "Insert" button, and define a formula
as follows:
Click on OK:
Click on the "Save" button to update the saved parameters, then on the "Apply" button.
Note 1: we have inserted the new formula before the thickness calculations because the
formulas are run in order. By applying these calculation parameters, the formation's
footwall is forced to not intersect the hanging wall, then the thicknesses are calculated.
Note 2: if the carbonate formation's hanging wall had intersected the topography, we would
have inserted a "Carb Hanging wall = min (Topography, Carb hanging wall)" formula
before the "Carb Footwall" = " formula.

Final model: representation on sections

Go back to "Sections" and display the section between M111 and M144.
We will replace the four "Grid profile" ( ) layers with a single "Grid profile" layer,
using the "Model" data source:
Select the layerandclickon"Deletelayer"( ).
Dothesameforlayers , ,and
.
source": "Model", then click on OK.
Click three times on "Move the current layer back" ( ).
To fill in with color above the topography, click in the first rectangle under "Filling". In the
color palette, click on color no. 21, then on "Add":
Click in the next rectangle (filling between Topo and Carb Hanging wall), and click on
color no. 15 in the color palette, then on "Add".
For the filling between the Carb Hanging Wall and the Carb Footwall, use color no. 19.
Below the Carb Footwall, use color no. 9.

From the horizontal projection (which you come back to by clicking on Projection
typeHorizontalplane,then on ), you can define any section and view it according to
this style.

Final model: representation on maps

Go back to "Carbonate (maps)".
We will hide the "Grid"layer:selectthislayeranduncheckthe
checkbox.Clickon toseetheresult.
We will now add two "Isoline" layers:

Click on "Add layer" ( ). In the "Data" frame, choose "Isolines", and in "Data source":
"Model", then click on OK.
Right-click on the name of the "Model" graphic layer and rename it "Carb Hanging wall".
Double-click on the layer to modify its presentation as follows (or
click on the "Filling" button and choose "Filling with colors"):
Click on "Add layer" ( ). In the "Data" frame, choose "Isolines", and in "Data source",
choose "Model", then click on OK.
Right-click on the name of the "Model" graphic layer and rename it "Carbonate thickness".
Double-click on the layer to modify its presentation as follows: (also
click on the "Filling" button and choose "Filling with colors"; click on the "Font" button
and choose Arial 8 for the isoline labels):

Before displaying, put the layer back to the foreground: select it, then
double-click on "Move the current layer forward" ( ).

This map represents the isolines of the carbonate formation's thickness.
To view the map of altitude isolines of the carbonate formation's hanging wall, uncheck
the checkbox to hide this layer and display the one beneath it.
You could add three other "Isoline" layers to this document using the "Model" data source,
and define their presentation modes to create maps of: the topography; the altitudes of the
carbonate formation's footwall; the thickness of the overburden.
To illustrate these maps, each with its own specific title and legend, you are advised to
create one Document per map. For this purpose, simply copy "Carbonate (maps)" as other
names using the "Save as..." popup menu item.
Broken line sections

The sections we have seen up until now have all been straight. With GDM, you can also plot
non-straight sections, referred to as "broken line" sections, either to link precise points (drill
holes, for example), or to follow a defined plot (such as a road or tunnel).
For this purpose, you will create Graphic documents in GDM which are in neither a
"geographic coordinate system" nor in a "local coordinate system", but in a "broken line
coordinate system".
A broken line section is a vertical section that follows a "broken line profile" contained in a
Curves data source. This data source can be an external database (Access/Excel/etc.), a GDM
database in which you enter the coordinates of the curve's points, or a GDM database created
by digitization on a horizontal projection (map). We will use the latter method.

Digitizing profiles
On "Location map (local)", we will digitize profiles that will serve as a "support" for
broken line sections. Since this Document is in a local coordinate system, the GDM Curves
database that we will create will be in this same coordinate system. You could just as well
use a Curves database in a geographic coordinate system or in another local system to
define broken line sections.
We will use the Document's digitization toolbar (see Digitization toolbar, page 292).
In the "Location map (local)" toolbar, click on "Create curve overlay" ( ).
This initiates:
the appearance of a "Curves" data source ( ) called "Digitized curves" in the
Desktop tree,
the addition of a "Curves" layer to our Document,
the transformation of the mouse's cursor to the ( ) digitization cursor.
The first click on the mouse creates a curve "head", the next clicks create other "points" on
this same curve. A double-click enters the last point on a curve. Another way of "declaring"
the end of a curve is to press the "Escape" key after entering the last point. This is the
method we will use.
If you want certain digitized points to be "adjusted" on data points displayed on the graph,
you must (1) select the Graphic document layer using the data source on which you wish to
adjust, (2) keep the "Ctrl" key pressed while clicking near the data point whose coordinates
you want to copy. You can change adjustment layers at any time while digitizing.
Select the drill holes layer. Keeping the "Ctrl" key pressed, click on the
following drill holes successively: M111, M121, M122, M132, M133, M143, M144.
Click on "Digitization options" ( ):
Select the "Enter field values after entering each point or curve" option, then click on OK.
Note: the value of the 3rd coordinate is the value of Z which will be used for those points
not adjusted on data points.
Press the "Escape" key to finish this first digitized curve:

Enter "BR01" as the ID (curve identifier), then click on "Close".
Now digitize a second curve:

Select the curves layer, then click on "Add new point/curve"
( ).
Select the drill holes layer. Keeping the "Ctrl" key pressed, click on
drill holes M113 and M153 successively.
Press "Escape" to finish the curve.
Enter "S01" for the curve's ID, then click on the "Close" button.
Proceed in the same way to digitize the third curve "S02" from M124 to M151.
Lastly, digitize a curve "BR02" "freehand", i.e., without using the "Ctrl" key, from M131
to M152:
Click on "Stop digitization" ( ).

Right-click on the "Digitized curves" data source and choose "Save".
Double-click on "Digitized curves" to open it in List mode:

Use the popup menu on the "Digitized curves" data source to rename it "Profiles". Note
that this does not change the name of the layer that uses this data source in the Graphic
document.
Click on the "ID" button:

In the "ID" frame:

Select the "ID" field
Select the Arial 12 Bold font
In the "ID posted" frame:
Select the "Top of curve" and "End of curve" options and enter a distance of 0.1 cm
In the "ID orientation" frame:
Select "Aligned with the curve"
Click on OK, then on OK in the "Curve presentation" dialog box.
Change the Document's scale by clicking on : choose "A4 landscape".

This Document is a location map of our future "broken line" sections.
Creating broken line sections

From the GDM main menu, choose "Project data New graphic document":
After selecting the "Profiles" data source, click on the "Coord. System..." button:

Select "the coordinate system of the broken line" option, select broken line "BR02, then
click on OK, then on OK in the "New graphic document" dialog box.
The Graphic document is displayed in the Desktop tree under the name "New Graphic".
Rename the Document "Broken line sections", then double-click on the name of the
Document (or choose "Display" from the popup menu) to display it.
We must now add graphic layers:

Click on the "Add layer" button ( ) of the "Broken line sections" Graphic
document, and add a Drill holes layer using the "Geological data" data source.
Double-click on the drillholelayertomodifythislayer's
presentation.
Select
Then click on the "Lithology" button.
Select the Litho "Code for lithology" in the drop-down list.

In the "Lithology column" frame, choose "Left of axis", and enter 0.5 cm for "Column
width".
The extension along Z of the Document, based on the "Frame" layer, is insufficient.
Click on "Define view" ( ).

Using the information in the "Volume of

data" frame:
Enter the following in the "New volume"

frame:
for Z0: 20 m
for ZM: 55 m
Now change the Document's scale ( ):
Note: the section's X axis, graduated in meters from the profile's origin, displays the
curvilinear distance along the length of the digitized profile.
source", choose "Model", then click on OK.
Double-click on the layer to modify its presentation.

Use the same Presentation mode as in "Final model: representation on sections", page 161.
Click on "Move the current layer back" ( ).
Proceed as follows to display another broken line section:

Click on "Define view" ( )
Select section "S02" in the drop-down list:
Click on OK, then on ( ):
Sections "S01" and "S02", defined by two points only, could also have been produced
using either the or buttons.
Broken line Graphic documents can be used to "manage" the straight sections (i.e., name
them, keep their position), as well as to quickly go from a section to another.
Proceed as follows to change "the volume" of the broken lines sections:

Click on ( ).
In the "Projection" frame, you see that the section is considered as a
section.

Thus in the "New volume" frame:

X is the distance along the profile,
Y is the coordinate perpendicular to the
section.
The section's thickness is therefore the sum of the absolute values of Y0 and YM; if
you enter different absolute values for these two parameters, the plane on which the
"Grid profile" layers are displayed will not be the section's median plane. This property
is used to include - in a section - a selection of data other than that obtained with an
"ordinary" section (i.e., defined using or ) whose plane in which the "Grid
profile" layers are displayed is always the section's median plane.
To extend S02 "to the left and right", enter 15 m for X0 and 220 m for XM. Click on
OK, then on ( ):
Calculating the volume of a formation
Calculation on the whole grid

Right-click on the name of the "Model" data source and choose "Display Summary":
By reducing the size of the "Name" and "Description" columns until they are completely
hidden, or by using the horizontal scroll bar to see the columns on the right, you can see
the following statistics, which were automatically calculated when you saved the data
source:

On the "Thickness Carb" line, note:

Def. value = 1271: the number of grid blocks with defined values
Mean = 6.6978: average carbonate thickness in a block
Click on the "Parameters" button:
The surface of the mesh is deduced from its size (DMX, DMY): 5 x 5 = 25 m 2.
By multiplying this surface by the number of defined values and the average thickness, you
obtain the volume of the carbonate formation on the whole grid:
25 m2 x 1271 x 6.6978 m = 212 823 m3

Adjusting a base map

We have a scanned map of parcels of land on which there are drill holes, and we want to
calculate the volume of carbonate in parcel no. 255:
We will use this image as a "Base map" in GDM to digitize the contour of the parcel we
are interested in.
We will proceed as follows:
Create a GDM "Base map" database
Convert the scanned image to WMF (Windows Metafile) format
"Adjust the base map", i.e., reference it geographically in the "Base map" database
Add a "Base map" layer to a Graphic document
Digitize a closed curve along the boundaries of parcel no. 255 displayed in the Base
map
Use this curve as the boundary for interpolating the model of the carbonate formation
Calculate the volume of carbonate in this model
To create a "Base map" GDM database:

Use the GDM main menu: "Project data New GDM database":

Choose "Base map", then click on OK.

The new data source is displayed in the Desktop tree.
To convert the image (BMP file) to Windows Metafile (WMF) format, proceed in the same
way as on page 135:
The scanned image is located in the Project folder under the name Prop.BMP
Click on Start Programs GDM 5.0 WmfConv
Load the image: File Open, Prop.BMP
Save it as WMF: File Save as, Prop.WMF
Close WmfConv
To georeference (adjust) the image:

Use the GDM main menu: "Project data Load Windows metafile":

Select "PROP.WMF" and click on "Open":
To adjust this image, we must provide the coordinates of two points. For this purpose,
we will use the crosses, the coordinates of which are known.
Note 1: the two points must not be chosen on the same West-East or North-South
line.

Note 2: the further the points are from one another, the better the adjustment's
precision.
Note 3: given that GDM only uses two points to reference the image, the
adjustment will only be accurate if the image was scanned in parallel to the
coordinate axes.
We need to enlarge the image to digitize the position of the crosses as precisely as
possible:
Maximize the window using the "Maximize" ( ) button
Enlarge the image using the "Fit to window" ( ) button
Click on "Setting point 1" ( ):
The cursor changes to the digitization cursor ( )
Click exactly on the cross situated in parcel no. 272:
Enter the coordinates of the cross as above, then click on OK.

Click on "Setting point 2" ( ):
Click exactly on the cross situated at the North-East edge of the map:
Enter the coordinates of the cross as above, then click on OK.

Note that we have entered 30 as the Z coordinate for both adjustment points
because the altitude 30 is inside the "volume" of our Graphic documents.
If you enter a Z coordinate outside the volume defined using "Define view" ( )
in the "New volume" frame, the Base map will not be displayed on the Graphic
document.
You must enter the same value for Z1 and Z2. GDM thus knows that you are
"adjusting" an image on a horizontal plane.
You can adjust Base maps on West-East sections by entering the same values for
Y1 and Y2, and on North-South sections by entering the same values for X1 and
X2.

Click on "Calculate metafile coordinates" ( ):
This dialog box displays the image's minimum and maximum coordinates (the South-
West and North-East corners), which will be stored with the image name in the Base
map database chosen in the drop-down list.
Click on OK.
Save the "New Base map database" source that has just been modified.
Digitizing a polygon
We will add a "Base map" type layer to a Graphic document to digitize the contour of the
parcel we are interested in:
Make a copy of "Carbonate (maps)" in "Parcel 255": Right-click on the "Carbonate
(maps)" name in the Desktop tree and choose "Save as":
Display "Parcel 255", then use the "Delete layer" ( )

button to delete the three layers:

Click on "Add layer" ( ). In the "Data" frame, choose "Base map", and in "Data
source", choose "New Base map", then click on OK.
Since the map of parcels is a scanned map, it is opaque and hides the
layer. Select this points layer, and click on "Move the current layer forward" ( ),
then on ( ).
To digitize the contour of parcel no. 255:

We need to enlarge the image to digitize as precisely as possible:
Maximize the window using the "Maximize" ( ) button
Enlarge the image using the "Fit to window" ( ) button
In the "Parcel 255" toolbar, click on "Create curve overlay" ( ). This initiates:
Desktop tree
the addition of a "Curves" layer to our Document
the transformation of the cursor to the digitization cursor ( )
Select the "Close curves" option, then click on OK.

Digitize the contour of parcel no. 255 by clicking on points 1 to 9:

Once you have entered point 9, press the "Escape" key. GDM then closes the curve by
creating a tenth point with the same coordinates as point 1.
Right-click on the name of the "Digitized curves" data source and choose "Save" from
the popup menu.
Double-click on "Digitized curves" to open it in List mode:
Right-click on the name of the "Digitized curves" data source, and choose
"Calculations Calculation on curves Area". GDM subsequently calculates the
surface area of the curve and assigns a value to the "AREA" field:

Note: to calculate the area of the curve, GDM uses the "STRI" (Strike - direction of the
digitization plane) and "DIP" (Dip of the plane) variables. The area calculated is that of
the curve projected on the plane defined by "STRI" and "DIP", which is justified when
the points on the curve are not all in the digitization plane.
Right-click on the name of the "Digitized curves" data source, and choose "Save" from
the popup menu, then choose "Rename data source" to rename it "Parcel 255".
Right-click on the layer of "Parcel 255" and choose "Rename
layer". Rename it "Parcel 255".
Click on the "Line" button:
Modify the line's thickness and color as above, then click on OK.
Click on OK in the "Curve presentation" dialog box, then refresh the drawing ( ) to
make sure the digitized contour effectively corresponds to the plot of parcel 255.
Interpolation limited by polygons

Right-click on the name of the "Carbonate (interpreted)" Points data source, and chose
"Calculations Estimate 2D grid".
Click on the "Use parameters" button:

Choose "Carbonate (interpreted) footwall", and click on "Open".
Add THCK to Z2 in the list of Variables to interpolate.

Click on the "Limits" button:
Choose "Polygons" and select the "Parcel 255" data source, then click on OK.
Click on "Save parameters", enter the name "Parcel 255", and click on "Save".
The "2D grid on Carbonate (interpreted)" data source is now displayed in the Desktop tree.
Rename it "Model parcel 255".
To quickly view the result on "Parcel 255", use the "Add layer" button ( ).
In the "Data" frame, choose "Grid", and in "Data source", choose "Model parcel 255".
Click on OK.
A Grid layer has been added to the list of "Parcel 255" layers.
Click twice on "Move the current layer back" ( ), then on "Refresh drawing" ( ):

This view represents the altitude of the carbonate formation's footwall (first variable in the
"Model parcel 255" grid).
Double-click on the name of the layer to open the "Grid of blocks presentation" dialog
box:
Click on the "Filling" button:
Choose THCK (thickness of the carbonate formation) as the "Variable to represent" instead
of Z2 (altitude of this formation's footwall), then click on OK.
Click on OK in the "Grid of blocks presentation" dialog box, then on "Refresh drawing"
( ):

Calculating the volume limited by a polygon

Right-click on the name of the "Model parcel 255" data source, choose "Display
Summary" from the popup menu, and calculate the volume in the same way as for the
Calculation on the whole grid, page 174):
For the THCK variable:
Def. value = 451: the number of grid blocks with defined values
Mean = 4.43395: average carbonate thickness in a block
Mesh area = 25 m2.
The area of the parcel calculated from the model is thus:

451 x 25 m2 = 11 275 m2
Note: the area of the digitized polygon is 11 251 m 2,i.e.,adifferenceof0.2%.
By multiplying this area by the average thickness, you obtain the volume of the carbonate
formation on parcel no. 255 :
11 275 m2 x 4.43395 m = 49 993 m3
Modeling on sections using the mouse

When the shape of the geological body to model means you are unable to define its hanging
wall and footwall as two distinct areas, the geologist digitizes the shape of this body on
parallel sections. GDM will calculate the area of the digitized polygons on each section, and
the volume will be obtained by multiplying this area by a thickness assigned to each section in
order to cover the entire zone on which you wish to calculate the volume of the geological
body.
We will use this method to estimate the volume of Glauconite. This discontinuous "formation"
takes the appearance of lenses situated sometimes above, sometimes below the carbonate
formation. In the drill holes, it is characterized by the "GLAU" value of the "Litho" code.
To represent the position of the Glauconite on sections, we will represent it on its own in the
"Lithology" column of the presentation of a drill hole graphic layer. For this purpose, we will

use the "Patterns for a code" table in the "Formations" palette, in which the only code value to
have been inserted is "GLAU".
Make a copy of "Sections" in "Modeling on sections": Right-click on the "Sections" name in
the Desktop tree, and choose "Save as":
Display "Modeling on sections", click on "Define view" ( ), and choose the "Horizontal
plane" projection type, then click on OK, then on .
Proceed as follows to define a section adjusted on drill holes M113 and M153:
Select one of the drill hole layers, e.g.,
Click on . The mouse cursor takes the following form: (digitization cursor)
Click near drill hole M113, then keeping the button pressed, drag the cursor near to drill
hole M153 and release.
To keep the section as it is, click on OK in the "View parameters" dialog box. To display this
section, click on :
Uncheck the checkbox to hide the two layers:

Click on "Add layer" ( ). In the "Data" frame, choose "Drill holes", and in "Data source",
choose "Geological data", then click on OK.
Double-click on the last drill hole layer whichhasjustbeenadded,then
modifythislayer'spresentation.
Select
Then click on the "Lithology" button.
Select the Litho "Lithology code" in the drop-down list.

In the "Lithology column" frame, choose "Right of axis", and enter 0.3cm for the "Column
width".
The pink pattern is used to clearly situate the Glauconite runs on drill holes M123, M133 and
M143.
To digitize the contour of the Glauconite:

We need to enlarge the image to digitize as precisely as possible:
Maximize the window using the "Maximize" ( ) button,
Enlarge the image using the "Fit to window" ( ) button, then using "Zoom in" on
drill hole M123.
In the "Modeling on sections" toolbar, click on "Create curve overlay" ( ). This
initiates:
Desktop tree
the addition of a "Curves" layer to our Document
the transformation of the mouse's cursor to the ( ) digitization cursor

Select the "Close curves" option, then click on OK.

Digitize the contour of the first lens:
Double-click to enter the sixth point. GDM then closes the curve by creating a seventh
point with the same coordinates as the first point.
Use the cursor at the bottom of the Document window to center the image on drill holes
M133 and M143, and digitize the estimated contour of the other two lenses:


Right-click on the name of the "Digitized curves" data source, and choose "Save".
Double-click on "Digitized curves" to open it in List mode.
Right-click on the name of the "Digitized curves" data source, and choose "Calculations
Calculation on curves Area". GDM subsequently calculates the surface area of the
three curves and assigns a value to the "AREA" field.
Choose "Save" from the popup menu on the name of the "Digitized curves" data source,
then choose "Rename data source" to rename it "Glauconite section 3". Double-click on
the data source to open it in List mode:

Note: Since the Graphic document's X and Y coordinates are expressed in Km, the areas
are expressed in Km2. Reminder: you can see the Data source's Variable Units in Summary
mode.
Right-click on the "Modeling on sections" layer, choose "Rename
layer" and rename it "Glauconite section 3".
You can estimate the volume of each lens by multiplying the area of each curve by a section
thickness of 50 meters, for example (where 50 m is the distance between two sections).

Drill hole logs
Log documents are created exclusively from Drill hole sources, characterized by a "To Depth" use
variable in the run data.
A Log document is the juxtaposition of columns whose width you define in cm (or in inches,
depending on the option chosen in the GDM main menu "Setup Draw units"). The Log's
different columns can come from different data sources, but they all belong to the same drill hole.
When you define a log's scale, it is applied to the drawing's "Y dimension", which is a depth
(distance in relation to the origin of the drill hole), not an altitude.
You create a Log document on a given drill hole, but it is actually a model that applies to all the
drill holes being studied.
New Log document

Use the GDM main menu: "Project data New log document":
Select the "Geological data" drill hole data source.

GDM will search for the drill holes in the different sources by their "Short ID" field (which is
the only available identifier in "Geological data").
The Log document will be created on drill hole "M111". GDM will calculate a default log
scale for the log's first display on the basis of this hole's length.
Click on OK:
The "Log format" dialog box shows a diagrammatic representation of the log: the first
"Graduation" column ( ) has been created, with a Heading "Depth (M)", and a width of
2 cm. Click on OK
Double-click on the name of the "New log" document in the Desktop tree to see the drawing of
the log in the log's display window:
By default, this new Log

consists of a
"Standard log heading"
and a "Graduation"
column"
To go back to the "Log format" dialog box, use the "Modify log" ( ) button.

Drill hole logs 195
Modifying a log
Creating/modifying columns
Using the buttons on the right-hand side of the "Log format" dialog box, you can perform
all the operations possible on the columns: Add, Insert, Delete, Modify, Move.
"Move column" ( and ) is only available here.
"Add column", "Insert column" and "Delete column" are also available in the log display
window by right-clicking on a log column.
You will also find "Add column" in the display window's toolbar: .
You can access the "Modify column" function by double-clicking on either of the
following:
a column in the "Log format" dialog box
a column in the log display window
Creating/modifying headings
The "standard log heading" is the one placed by default at the top of our log. It displays
information specific to each drill hole in the data source, together with other information as
free text.
A "free heading" (or specific log heading) is a Windows Metafile (.WMF) which is
placed either above the standard heading or in its place.
Using the buttons at the bottom of the "Log format" dialog box, you can access the
"Standard heading" and "Specific log heading" dialog boxes.
You can also access these two dialog boxes via the "Presentation" popup menu on the
name of the Log document on the Desktop.
Alternatively, you can access these boxes by double-clicking on these headings in the log
display window.
Other modifications
Scale/Depth portion
You can modify the scale and/or the depth portion:

using the "Scale/Depth portion" button in the Log format dialog box
by right-clicking on the name of the Log document on the Desktop, then choosing
"Depth portion/Scale"
using the "Define scale" button ( ) in the log display window

Selecting another drill hole
Whenever necessary, you can display another drill hole in the Log document by
selecting it in a drop-down list of drill hole names,
either using the "Drill hole" button in the "Log format" dialog box
or via the "Drill hole" option in the Log document's popup menu on the Desktop
tree
Depth graduation
You can request a depth graduation on all the columns via the "Presentation" pop-up
menu on the name of the Log document in the Desktop tree.
In each column's parameters, you must select the "Column depth graduation" option to
make the graduation visible on this column.
Column heading height
You define the height of all column headings via the "Presentation" popup menu on the
name of the Log document in the Desktop tree.
Default format of column headings

There are 12 different types of column in GDM. Consequently, there are 12 dialog boxes in
which you can define the column parameters. Each dialog box contains a "Heading" button
which calls the "Column heading" dialog box:
By default, "Heading" is the name of the field represented in the column, followed by the
unit in parentheses if one has been defined. You can enter another heading if you wish.

Drill hole logs 197
When you superimpose a column on the previous column, you can either keep the
headings of the two columns, or completely delete the heading of one of the two columns,
leaving you with a single heading at the top of the column.
When you add or insert a column, by default, the "Text orientation" and "Font" are those of
the previous column (the column to the left of the new column).
Example of a log
We will add some columns to our first log and see how to superimpose and move columns. We
will not detail the 12 column types, nor will we examine all the presentation parameters of
each column. These details are all available in the GDM online help (search for "List of
available columns for a log" in the index).
Note that a Log document in GDM 5.0 can contain a maximum 50 columns.
You will use the "Refresh drawing" ( ) function each time you want to view your most
recent additions or modifications.
Column depth graduation

Right-click on the name of the Log document in the Desktop tree, and choose
"Presentation Depth graduation". Define the parameters of these graduations as
follows:
On our "New log" document, double-click on the "Depth (M)" column, then click on the
"Heading" button and modify the parameters as follows:

Note: choose the Arial 9

Bold font
Click on OK, then modify the other parameters of the "Graduation" column as follows:
Note: choose the Arial 10

Bold font
Click on OK.
Depth column
Click on "Add column" ( ) and choose a "Depth" column on the "Geological data" data
source:

Drill hole logs 199
Click on OK, then modify the parameters of this "Depth value column" as follows:
Click on the "Heading"

button and change the
column's heading to
"Depth".
Click on OK.

Patterns column
This column requires a Patterns palette. If you skipped chapter "Graphic documents" and
went directly on to chapter "Drill hole logs", refer to page 121 (Creating a pattern palette)
before continuing.
Click on "Add column" ( ) and choose a "Pattern" column on the "Geological data"
source.
Click on OK, then modify the parameters of this "Pattern" column as follows:
Click on OK.
Values (of text ) column
Click on "Add column" ( ) and choose a "Values" column on the "Geological data"
source.
Click on OK, then modify the parameters of this "Values" columns as follows:

Drill hole logs 201
Click on OK.
You will notice that the height reserved for the Column headings is insufficient.
Right-click on "New log" in the Desktop tree, and choose "Presentation Column heading
height":

Enter 3 cm, click on OK, then on .
We will change scale and drill hole:
Changing scales
Click on : and enter 100 instead of 50:
The log height has gone from 46.2 cm to 26.1 cm.
Changing drill holes
Right-click on the name of the Log

document in the Desktop tree and choose
"Drill hole" from the popup menu.
Choose drill hole M143,
then click on OK.
Moving a column
We will move the second column with the heading "Depth" and place it between the
"Litho" and "Description" columns. Click on "Modify log" ( ):

Drill hole logs 203
Select the second column, then click on the "Move to the right" button ( ):

Variable graph column
Click on "Add column" ( ) and choose a "Graph" column on the "Analytical data" drill
hole data source.
Click on OK, then modify the parameters of this "Variable graph" column as follows:

Drill hole logs 205
Click on the "Heading" button and change the title "MgO" to "MgO (%)".
Select the "Graduation for the column" option and modify the parameters as follows:
Click on OK.

Depth column
Click on "Add column" ( ) and choose a "Depth" column on the "Analytical data" drill
holes data source.
Click on OK, then modify this column's parameters as follows:
Click on the
"Heading" button
and change the column
heading to "Depth".
Click on OK.
Variable graph column
Click on "Add column" ( ) and choose a "Graph" column on the "Analytical data" drill
holes data source.

Drill hole logs 207
Click on the "Heading" button, then change the column's heading to "RVB (mm)".
Click on OK.
Values (of Variables) columns
Click on "Add column" ( ) and choose a "Values" column on the "Analytical data" drill
hole data source.

Click on the "Heading" button, and delete this column's heading.
Overlapping columns
We will now overlap the last column (values of field RVB) on the penultimate column
(graph of field RVB). Click on "Modify log" ( ):

Drill hole logs 209
Select the last column, then click on the "Overlap column" button ( ). The color of this
button becomes a lighter gray (and is pressed in).
Cumulative graph column
Click on "Add column" ( ) and choose a "Cumulative graph" column on the "Logging
data" drill holes data source.

When "Log1" is selected in "Fields to total", choose the color Red in the "Graph filling"
frame.
When "Log2 is selected in "Fields to total", choose the color "Yellow" in the "Graph
filling" frame.
When "Log3" is selected in "Fields to total", choose the color "Light green" in the "Graph
filling" frame.
Click on the "Heading" button, then change the column's heading to "Log 1+2+3", then
click on OK.
Graph + values (ellipse) column
Click on "Add column" ( ) and choose a "Graph + values (ellipse)" column on the
"Analytical data" drill holes data source.

Drill hole logs 211
Choose font Arial 8 Bold.

Click on the "Heading" button, then change the column's heading to "Weakness (Kg)",
then click on OK.

Modifying the standard heading

Right-click on the name of the Log document in the Desktop tree, and choose "Page
setup":
You will notice that the width of the Standard heading is 15 cm, whereas the total column
width is 16.5 cm. Click on OK to close the "Page setup" dialog box.
Double-click on the Standard heading, and modify the parameters as follows:
Choose font Arial Bold Italics 14. Click on OK, then on :

Drill hole logs 213
Printing the log

Before printing a Log document, click on "Define scale" ( ):
To obtain the size of the paper for printing, you

must add the margins defined in GDM (in Page
setup) to Log width and Log height.
The Log width guides your choice in terms of the
paper's width. If you choose a paper width that is
too small, the Log will be clipped on the right.
If the Log height is greater than that of the paper,
GDM will automatically print the log on more
than one page.
Right-click on the name of the Log document in the Desktop tree, and choose "Page setup":

You can define the Top, Bottom and Left margins.
When you know beforehand that the log will be printed on more than one page:
you can choose to Repeat the standard heading on every page, or to only print it on the first
page
you can print a Page number (bottom right)
and each page's Depth portion (bottom right).
Use the "Font" button to define the fonts for the page numbers and Depth portions.
Click on to print, or choose "Print" from the popup menu on the Desktop tree's Log
document.
Choose the paper size and orientation according to the Log size and the Page setup you have
defined.
Note: you can also use the GDM main menu: "Setup Printer setup for Log documents" to
define the printer settings for all the Project's log documents.
Exporting the drawing

Right-click on the name of the Log document in the Desktop tree, and choose "Export
WMF" to export the graphic as a Windows Metafile (.WMF extension).

Drill hole logs 215
Importing the drawing to Word/Excel/PowerPoint

In these applications, you use the "Insert Image From file" function. You can then keep
these drawings as they are, or modify them as appropriate.
Tip: in PowerPoint, when possible, avoid using the "Ungroup" function which thickens the
lines. Instead, superimpose your modifications on the original drawing.
Repeat log
Right-click on the name of the Log document in the Desktop tree, then choose "Repeat log"
to print or export a series of Logs in Windows Metafile format:
From the list of all the drill holes available in the various data sources used by the Log
document (left-hand column), use the arrows to create the right-hand list of "Drill holes to
plot".
Click on "Print" to print this series of logs on your printer.
Click on "Export" to export this series of logs. In the example above, the following files will
be created in the Project folder: M132.WMF, M143.WMF and M151.WMF. If files with these
names already exist, GDM will create files M1321.WMF, M1431.WMF, and M1511.WMF.
Click on "Export to Images database" to export this series of logs and to create a GDM
Images database ("Images on New log" in the Desktop tree) containing the names of the
exported files and the parameters required to position these images on Graphic documents
(maps or sections):

For more details on the "Export to Images database" function, see "Repeat log" in the online
help index.
You will find an example of a Graphic

document using Log images by opening
project Vertical.GDM in
Tutor\Vertical_holes\Examples:
The "Repeat log" function has been used on

the "Log for sections" document to generate
the "Images on Log for sections" database.
The second column was chosen as the
reference column, with "Drill hole axis
position" to the left of the reference column,
in order to center columns 1 and 2 on the
drill hole axis on the sections.
The "Sections" Graphic document (see

below) uses this Images database.
By going back to a Horizontal projection,
you can define any other section using .

Drill hole logs 217
Note: in the Images database, the only modification made has been the use of the Repeat
( ) function to assign a value of 0.25 instead of 1 to the "X drawing coef " field.
Other column types

In the Vertical.GDM project, located in Tutor\Vertical_holes\Examples, the "Log example"
Log document includes other types of columns:
1 2 3 4 5 6 7
Column 1 and column 7 are examples of "Graph + Patterns" columns: the shape of the
graph depends on the values of a Variable, its filling depends on the values of a Code, for

whose values you have defined a Palette (you could also use a Variable and a Patterns
palette for a Variable).
In the case of column 1, two columns of the same graph have been overlapped using two
different Palettes: the first defines flat colors (pattern no. 182), the second defines patterns
which are all black.
In the case of column 7, an extended Patterns palette (see Palettes, page 56, or open the
"Extended patterns Litho" palette).
Column 2 is an example of a Symbols column:
A Palette must be defined for the values of a field (Code or Variable) to define the
symbols.
Up to three other Variables can optionally be used to define:
the position of the symbol in the column's width
the orientation of the symbol (the orientation defined in the palette is not used in this
case)
the size of the symbol (the size defined in the palette is not used in this case)
Columns 3 and 4 are examples of Images columns with different parameters:
in column 3, the images are said to be "Joined"
In column 4, they are said to be "Middle of run"
Column 5 is an example of a Structural Symbols column:
Two Dip and Direction-use variables (DIP and STRI) are used to position the structural
symbols ("tadpoles") according to a trigonometric horizontal scale.
You can vary the "tadpole heads" according to a field associated with a symbols palette.
Column 6 is an example of a Patterns column using a palette of extended patterns.

Processing deviated drill hole data
You must have read chapter "Processing vertical drill hole data" before reading this chapter (pages
77 to 101).
This example is taken from a drilling and trenching campaign for the exploration of a metal mine.
However, the data used has been altered for confidentiality reasons (changed drill hole names,
names and values of certain fields). Do not therefore pay attention to any geological or
geochemical inconsistencies.
The Tutor\Deviated_holes folder (in the GDM installation folder) contains two Access and Excel
subfolders used to optionally complete the exercise on data in an Access 97 database or in an
Excel 97 workbook.
Each Access and Excel subfolder contains two Start and End subfolders:
Start is the folder in which you will do the exercise: it contains only the data required to start
the exercise.
End is the folder that contains the same exercise, but completed. You can thus use it to see the
results of the exercise (logs, maps, sections) before starting, or during the exercise.
Files
\Tutor\Deviated_holes\Excel_Start.ZIP
\Tutor\Deviated_holes\Excel_End.ZIP
\Tutor\Deviated_holes\Access_Start.ZIP
\Tutor\Deviated_holes\Access_End.ZIP
can be used to restore the contents of the Start and End subfolders if necessary.
GDM uses a specific type of data source, called "Deviation database", containing the deviation
measurements of all the drill holes.
This data source must be connected to first, since it will be used to calculate the coordinates of the
runs of other Drill hole data sources (Geology, Analyses, Logging, etc.) when they are connected.
From GDM's point of view, a Deviation database must contain the following fields:
"Drill hole collar" fields:
Drill hole name
X, Y and Z coordinates of the drill hole's start point (otherwise, these fields must be
present in the other data sources: Geology, Analyses, Logging, etc.)
An "Azimuth"-use variable which will contain the drill hole's initial direction
An "Inclination"-use variable which will contain the drill hole's initial inclination
"Drill hole run" fields:
A "To Depth"-use variable which will contain the depth of the deviation measurement
An "Azimuth"-use variable which will contain the direction measured at this depth
220 Getting started with GDM 5 Processing deviated drill hole data
An "Inclination"-use variable which will contain the measured inclination

If you prefer to complete the exercise with Access data, proceed to page 223 (Connecting to
Access data).
Data format in Excel

The Boreholes.xls workbook (in Tutor\Deviated_holes\Excel\Start) contains two
worksheets:
"Data" for the geological and analytical data
"Survey" for the deviation data
We could have other worksheets which, like the "Data" sheet, would contain the Drill hole
Name and Depth fields, followed by fields specific to each sheet's data type.
Note that this data could also be in different Excel workbooks.
Connection
In most Windows versions, you will have to close the Excel worksheet before being able to
connect with GDM. This is not the case when working with Access (or Oracle, or SQL-
Server) data.

Tutor\Deviated_holes\Excel\Start giving it, for example, the name "Mine".
Deviation data
Click on "Connect" and choose Boreholes.xls
In "Table/Query: Drill holes", choose the Survey worksheet, and fill in the

Processing deviated drill hole data 221
All the uses must be redefined.

Notes:
Short ID can be replaced by Full ID when the drill hole names use between 4 and
80 characters.
You can omit the three coordinates, but only if they exist in all the other
worksheets describing the drill holes.
Click on OK. The following message is displayed:
At this stage, GDM does not know that it is a Deviations database. Since variables with
the "Azimuth" and "Inclination" uses are present in the "Collar" fields, this data source
could be an Inclined holes data source (straight, non-vertical). The calculation of the
coordinates of the deviation measurements will not subsequently be used. You can thus
click on Yes.
Once you click on OK, you see the "Deviations" data source in both the Project
Tree and the Desktop Tree. This is a Drill hole-type data source ( ).
Drill hole run data

Menu: "Project data Establish link with database". Fill in as follows:
Click on "Connect..." and choose Boreholes.xls

In "Table/Query: Drill holes", choose the Data worksheet, and fill in the
Click on the "Define vertical/straight/deviated drill holes" button:
Select the "Deviated holes" option in the "Calculate drill hole run coordinates" frame.
The drill hole "collar" coordinates will be taken in the "Deviations" data source.

For greater precision when calculating run coordinates, GDM will generate intercalated
runs every 10 cm (these runs will not be kept in the "Data" data source).
For each Text\Code\Date field, GDM prompts you to specify the number of characters
to be taken into account. Enter 4 for Geological Code, and 5 for Mine Code.
Once you click on OK, you see the "Data" data source in both the Project Tree and
the Desktop Tree.
Now move on to page 226 (Graphic documents, logs).

If you prefer to do the exercise with data in Excel, go back to page 220 (Connecting to Excel
data).
Data format in Access

The Boreholes.mdb database (in Tutor\Deviated_holes\Excel\Start) contains two tables:
"Data" for the geological and analytical data
"Survey" for the deviation data
We could have other tables which, like the "Data" table, would contain the Drill hole Name
and Depth fields, followed by fields specific to the data type of each table.
Connection

Tutor\Deviated_holes\Excel\Start giving it, for example, the name "Mine".
Deviation data

By selecting the "Save password" option, you can avoid Access requesting the
password each time you open the Project.
Click on "Connect" and choose Boreholes.mbd:
Click on OK.
In "Table/Query: Drill holes", choose the Survey table, and fill in the
All the uses must be redefined.

Notes:
Short ID can be replaced by Full ID when the drill hole names use between 4 and
80 characters.
You can omit the three coordinates, but only if they exist in all the other tables
describing the drill holes.
Click on OK. The following message is displayed:

At this stage, GDM does not know that it is a Deviations database. Since variables with
the "Azimuth" and "Inclination" uses are present in the "Collar" fields, this data source
could be an Inclined holes data source (straight, non-vertical). The calculation of the
coordinates of the deviation measurements will not subsequently be used. You can thus
click on Yes.
Once you click on OK, you see the "Deviations" data source in both the Project
Tree and the Desktop Tree. This is a Drill hole-type data source ( ).
Drill hole run data
Click on "Connect" and choose Boreholes.mbd:
Click on OK.
In "Table/Query: Drill holes", choose the Data table, and fill in the correspondence
table as follows:

Click on the "Define vertical/straight/deviated drill holes" button:
Select the "Deviated holes" option in the "Calculate drill hole run coordinates" frame.
The drill hole "collar" coordinates will be taken in the "Deviations" data source.
For greater precision when calculating run coordinates, GDM will generate intercalated
runs every 10 cm (these runs will not be kept in the "Data" data source).
Once you click on OK, you see the "Data" data source in both the Project Tree and
the Desktop Tree.
Graphic documents, logs

Use the "Preview" function in the popup menu on the "Data" source:

The "Preview" function displays a view on a horizontal projection of all the trenches and drill
holes in the "Data" data source.
Click on "Define view" ( ), and in the "Projection type" frame, select "West-East (view
from South)", click on OK, then on .
You now see all the data projected in on a vertical West-East plane. This is therefore a "view
from South" of all the drill holes:

All the operations we have done on the vertical drill holes in chapters "Graphic documents"
(page 101), "Modeling geological formations/bodies" (page 139), and "Drill hole logs" (page
193) can be done on the "Data" data source.
If you close the current project, and open the "Mine" project
in folder Tutor\Deviated_holes\Excel\End (exercise with Excel data),
or in folder Tutor\Deviated_holes\Access\End (exercise with Access data),
you will be able to see Log and Graphic documents created from this data.
Copies of the "Boreholes" and "Model" Graphic documents have been made using the "Save
as" function to freeze different views of the data. The two original documents are seen on a
horizontal projection. The copies show sections.
Proceed as follows to create the "Log" and "Boreholes" documents:
Print the "Log" document and the "Boreholes" and "Copy of Boreholes" documents.
Note the list of layers in the "Boreholes" document and their main presentation parameters.
Close the "Mine Project in subfolder \End, and load the one you have created in
subfolder \Start.
Use the "Copy palette in project" function to use the three palettes provided in
subfolder \End.
Recreate the "Log" and "Boreholes" documents based on observations made in the printed
documents and in your notes.

Intersection of drill holes and sections

When you look closely at the "Copy of Boreholes" document, which is simply a given
section created from the "Boreholes" document, you can see how GDM represents the
intersection of the drill holes with the section's limits:
The collar of drill hole SD14 is represented by a symbol

which indicates that the drill hole collar is inside the section.
The end of drill hole SD14 is represented by a symbol

which indicates that the end of the drill hole is inside the section.
The collar of drill hole SD05 is represented by a symbol

which indicates that the drill hole collar is outside the section.
The symbol represents the drill hole's entry point in the section, at an
altitude of 880.898 m.
The end of drill hole SD05 is represented by a symbol which

indicates that the end of the drill hole is outside the section.
The symbol represents the exit point of the drill hole from the
section, at an altitude of 802.614 m.
Modeling from deviated drill hole data

The mineralized vein has been modeled from the "Filon" values of the "Mine" Code, just as we
modeled the "Carbonate" formation in the exercise on the vertical drill holes.
However, with deviated drill holes (or inclined holes), the X and Y coordinates of a drill hole's
intersections with the formation to model are not the same for the formation's hanging wall and
the footwall.
In this chapter, we will see how to model the three surfaces of the topography, the hanging
wall and the footwall. We will not go into great detail on this subject, which you should now
be familiar with having read:
Representation of the topographic surface, page 124,
Modeling geological formations/bodies, page 139.

Modeling the topography

Right-click on "Data" (Collars data) and choose "Calculations Estimate 2D grid", with
the following parameters:
Click on the "Options" button in the "Grid definition" frame:
Click on the "Neighborhood" button in the "Interpolation method" frame, and choose
"Select by octants".
Click on "Save parameters": enter "Topo".
Rename "2D grid on Data: Collars" as "Topo".
Right-click on the name of the "Boreholes" Graphic document and choose "Save as":
name the new document "Modeling".
If you did not redo the "Boreholes" document, you can continue the exercise by saving
"Preview Data" as "Modeling".
Add a Grid layer to the "Modeling" document from the "Topo" data source.

Determining the mineralized vein

Choose "Calculations Determine formation or composite" on "Data", with the
following parameters:
Click on "Save parameters": enter "Vein".

Rename "Formations on Data" as "Vein".
View the "Vein" source in List mode.
Coordinates X1, Y1, Z1 are those of the intersection of the drill holes with the vein's
hanging wall.
CoordinatesX2,Y2,Z2arethoseoftheintersectionofthedrillholeswiththevein'sfootwall.
Coordinates X, Y, Z are those of the middle of segment X1,Y1,Z1 X2,Y2, Z2. They will
be used, for example, to post grades in a "Points" Graphic document layer on a section,
either with a palette of "Symbols for a variable" to represent value classes, or using
symbols proportionate to the value of a variable (Symbol size according to a field).
Automatic verification
If you consult GDM's online help (Index: search for "Formation"), you will read the
following:
INVZ code indicating the swapping of Z1 and Z2 for "up-going" drill holes:
Whenadrillholeisgoingupwards(drilledfromaminegalleryforexample),theZ1
valueofthedrillholeentrypointintheformationissmallerthantheZ2valueofthe
drillholeexitpoint.Inthiscase,GDMswapsthetwoseriesofvaluesX1,Y1,Z1,and
X2,Y2,Z2,asifthedrillholeweredrilleddownwards.GDMassignsthe"INV"value
totheINVZcodetoindicatethisswapping.Thiscodeisnotassignedanyvalueforthe
"downgoing"drillholes.

Generally X1, Y1, Z1 are the coordinates of a formation's "hanging wall" point, and
X2, Y2, Z2 are the coordinates of a formation's "footwall" point. However, this rule is
less certain when the drill hole inclination gets closer to the horizontal, and/or when the
formation's dip gets further from the horizontal. Therefore, when the drill holes are not
vertical or sub-vertical, the user (according to his or her own interpretation of the
geological sequencing) will have to verify for each drill hole that Z1 corresponds to the
formation's "hanging wall", and Z2 corresponds to the "footwall". For some drill holes,
the user may have to manually swap the two sets of coordinates.
We can already see that the "INVZ" field is empty in "Vein". However, since the slope of
the vein to model is steep, and given that we have horizontal trenches, it is wise to proceed
with a graphic verification:
On the "Preview on Data" document, choose "Save as" from the popup menu and save it
as "Check vein".
Change the presentation mode of the Drill hole layer:
Choose the "Vein" palette in the drop-down list,
Click on the "Lithology " button and define the Lithology column as follows:
Refresh the drawing, then define the following section "in the middle" of the vein and in
the direction of the slope, (using ):
Change the width of the section to 250 m:

Refresh the drawing:
You will see all the drill hole and

trench intersections with the vein.
You can thus check that the drill holes

and trenches all "enter the vein from
the same side".
The fact that the drill hole (or trench)

distance from top and end symbols are
always respectively a square and a
circle means, in particular for
trenches, that you can know "in which
direction a drill hole (or trench) has
been done".
If the data pertaining to the trenches
(horizontal) had been entered in the
other direction, you would have had
to swap X1,Y1,Z1 and X2,Y2,Z2 in
the "Vein" data source before
interpolating the hanging wall and the
footwall.

Interpolating the vein's hanging wall

Create the following filter on the "Vein" data source:
The new "Filter on Vein" data source contains 31 drill holes and trenches (as opposed to 33
for "Vein").
On the "Filter on Vein" data source, choose "Extract":
The "Extract" function creates a new database from a filtered data source. This database
has the same structure and only contains the data kept by the filter. You thus make a
physical copy of the data (as would the "Save as" function on a non-filtered data source).
We have created the "Vein Hanging wall" data source to subsequently modify its
coordinates. If we performed the coordinate modification on "Filter on Vein", we would
modify the "Vein" data source at the same time.
We will copy the X1 and Y1 coordinates in place of the X and Z coordinates by choosing
"Calculations Assign value to numeric fields":

Click on "Save as": enter "Hanging wall coordinates", then click on "Apply".
Save the "Vein Hanging wall" data source.
Now that the X and Y coordinates of the points on the vein's hanging wall have been
updated, we can calculate a grid using these points (model the vein hanging wall).
Choose "Calculations Estimate 2D grid" on "Vein Hanging wall":
Choose "Z1" as the variable to interpolate.
Click on "Use model" to take the grid in the "Topo" data source as the model: in
principle, GRID1.GRD if you have not created any other grids.
Click on "Limits" and select "Convex limits" with a boundary of 10 m to limit the
interpolation to the area containing data:

Click on "Save parameters": enter "Vein Hanging wall".

Rename the new "2D grid on Vein Hanging wall" grid as "Vein Hanging wall grid".
Add a Grid-type layer to the "Modeling" document from the "Vein hanging wall grid" data
source.
Note that the model's range is confined to the limits of the vein's data.

Interpolating the footwall and the vein grades

We could apply a filter on the "CROS" values of the "FORM" code in the "Vein" data
source, then "Extract" the data source obtained, as we did for the vein hanging wall.
We can also proceed "manually" when there are a small number of drill holes, as is the
case in the following example:
On the "Vein" data source, choose "Save as" and enter "Vein Footwall":
Open "Vein Footwall" in List mode, and click on "Column order" ( ):
"Remove" the FORM field, then "Insert" it in front of field P1:
Click on OK.
Select (one by one) the lines on which the FORM code does not have the "CROS" value,
and delete these lines using the "Delete line" ( ) button. You thus delete the lines of
trenches SDTB and SDTD, and of drill holes SD01 and SD09:

"Save" the "Vein footwall" data source. It contains 29 drill holes and trenches.
Note: if you inadvertently remove a line, you can use "Cancel modification" to return to
the starting point.
Use "Calculations Assign value to numeric

fields" to copy the X2 and Y2 coordinates in
place of the X and Z coordinates:
Click on "Save as": enter "Footwall coordinates", then click on "Apply".
Save the "Vein footwall" data source.
Now that the X and Y coordinates of the points on the vein's footwall have been updated,
we can calculate a grid using these points (model the vein's footwall).
Choose "Calculations Estimate 2D grid" on "Vein footwall":

Click on "Use parameters" and choose "Vein hanging wall" in the list:
Answer Yes.
Remove "Z1" from the list of Variables to interpolate, and add Z2, Au and Ag. Note
that we will not interpolate THCK (thickness) which is meaningless when the drill
holes are not vertical. We will calculate the thickness in the final model from the
difference between the hanging wall and the footwall values.

Click on "Save parameters": enter " Vein Footwall Grades".

Rename the new "2D grid on Vein footwall" as "Vein Footwall & Grades".
Add a Grid-type layer to the "Modeling" document from the "Vein Footwall & Grades"
data source.
Note that the model's range is not exactly the same as that of the vein's hanging wall. This
is hardly surprising given that the "Vein hanging wall" and "Vein footwall" data sources do
not have the same number of points, and that the points corresponding to the same drill
holes in both sources do not have the same coordinates.

Building a model
We will merge the three surface models (topography, vein hanging wall and footwall) in
the same grid.
Choose "Save as" on the "Topo" data source:
Enter "Model", then click on OK.
Choose "Structure" on the new "Model" data source.

Click on the "Modify" button to modify the list of fields:
In the list of "Variables", replace "ZEST" (Z estimated) with "Topo", and enter the new
names of the following variables: HW (hanging wall), FW (footwall), Thck (vein
thickness), Au and Ag.
Click on OK, then on the "Field attributes" button in the "Structure of the
GDM database" dialog box:

In the "Full name" column, enter the full names of the variables.
By double-clicking in the "Usage" column, choose ALTI as the usage for variables Topo,
Hanging wall and Footwall.
Click on OK, then on OK in the "Structure of the GDM database" dialog box.
"Save" the "Model" data source.
We will now "Update" the "Vein hanging wall" and "Vein footwall" fields from the "Vein
hanging wall Grid" and "Vein Footwall & Grades" data sources.
Choose "Update GDM fields" on the "Model" data source:
Select "Vein Hanging wall Grid", then click on OK:

In the "GDM Fields" column, select "Hanging wall" then click on OK.
Once you have saved the "Model" data source, repeat the "Update" operation on the "Vein
Footwall & Grades" data source:
Choose "Save Update Format":
When you have saved the "Model" data source, view it in Summary mode:

You will notice that out of 594 grid blocks, 158 have values for the vein hanging wall, and
147 for the other parameters.
By viewing "Model" in List mode:
you can see that, as with the "Modeling" document, some blocks - near the vein's boundary
- have not been assigned values either for the hanging wall or the footwall.
The last step for building the model consists in ensuring that the three surfaces do not
overlap. At the same time we will calculate the "Thickness". For this purpose, apply the
following calculation formulas to "Model" (by choosing "Calculations Assign value to
numeric fields"):

Click on "Save as": enter "Model adjustment", then click on "Apply".

Save the "Model" data source.
Proceed as follows to represent the model on Graphic documents:

Choose "Save as" on the "Boreholes" document (or the "Preview on Data" document
if you did not create the "Boreholes" document) and enter "Model".
On the "Model" document, add an Isoline-type layer from the "Model" data source.
Choose "Move the current layer back" on this layer to place it just after the Frame
layer.
Define the presentation of this new layer as follows, and request "Filling with colors":
Refresh the drawing:

"Save" the "Model" document.

Add a "Grid profile" layer from the "Model" data source.
Choose "Move the current layer back" on this layer to place it just after the Frame
layer.
Define the presentation of this new layer as follows:
From top to bottom, the following colors are

used:
32
15
20
15

Define a SW-NE section

at the center of the model
(near drill hole SD27),
using button :
Click on :
You can ignore this message given that the vein's hanging wall and footwall are in
close proximity in the upper third of the section. There is no "overlapping of block
values". However, although invisible at this scale, the hanging wall and footwall curves
overlap. Click on OK:

If you want to see a horizontal projection

view and a section view of the model
simultaneously, you can save the "Model"
document as "Copy Model".
Note: we could improve the model by adding "interpretation data" to take account of drill
hole data for which the FORM code has values different from the CROS code, as we did
when processing vertical drill hole data (page 152).

Additional functions
Interpolation with faults

Before reading this chapter, you must have read chapter "Processing vertical drill hole data"
(pages 77 to 101), which showed you how to connect data, and chapter "Graphic documents"
(pages 101 to 138), which showed you how to create Graphic documents and model a surface.
The example used is taken from a drilling campaign for the exploration of an oil-field. We will
model the reservoir's hanging wall from data taken from 182 drill holes, and from a digitized
fault system.
In folder Tutor\Fault_models in the GDM installation folder, you will find the Start and
End subfolders:
Start is the folder in which you will do the exercise: it contains only the data required to
start the exercise.
End is the folder that contains the same exercise, but completed. You can thus use it to see
the results of the exercise before starting, or during the exercise.
The Start.ZIP and End.ZIP files contained in folder Tutor\Fault_models can be used to restore
the contents of the Start and End subfolders if necessary.
The data
Open project Oil_Field.GDM in Tutor\Fault_models\Start.
You will find the data is the two worksheets in the Oil_Wells.XLS Excel workbook. Note
that we could have done the exercise in exactly the same way with two Access tables.
The points of intersection of the drill holes with the reservoir's hanging wall are in the
"Wells" Points data source, connected to the "Wells" worksheet. The following
correspondence table has been used:
250 Getting started with GDM 5 Additional functions
You will notice that the coordinates are in feet (Unit = FT).
The "Subsea" field contains the altitude of the surface to be modeled (point of intersection
of each drill hole with the reservoir's hanging wall).
Note: the assignment of the "Altitude" Use to this field is not compulsory (we could keep
the "Variable" use). When this choice is made:
GDM proposes to represent the variables with an "Altitude" use on Grid profile-type
graphic layers by default.
GDM only shows the Isoline layers if values Z0 and ZM in the Graphic document's
"New volume" frame cover the altitudes of the contours.
The digitized faults are in the "Faults" Curves data source, connected to the "Faults"
worksheet. The following correspondence table has been used:
Note the variable with the "Curve points order" Use, which is not compulsory with Excel
or Text files, but which is compulsory with Access/Oracle/SQL-Server databases.
The "Nb" field contains the ID of the faults. It could have been assigned a "Short ID" or a
"Full ID" Use.

Additional functions 251
The "Location map" graphic document shows the position of the points (with the altitude
value), and the plotting of the fault system:
Interpolating without the faults

Choose "Calculations Estimate 2D grid" on the "Wells" data source:
Select the Variables to interpolate ( ).

Click on the "Options" button in the "Grid definition" frame:

Enter 500 FT along X and Y for the "Block size".

Click on the "Neighborhood" button in the "Interpolation method" frame, and choose
"Select by octants".
Click on the "Limits" button and choose "Convex limits":
Click on "Save parameters", enter the name "Without faults, and click on "Save":

GDM creates a "2D Grid on Wells" data source in the Desktop tree.
Rename it "Without faults".
Use the "Save as" function to make a copy of the "Location map" document under the
name "Without faults".
On the "Without faults" graphic document, add an "Isolines" layer from the "Without
faults" data source, use the "Move the current layer back" to place it in second place (just
after the Frame layer), then modify its presentation as follows:

Request a filling with colors.

Rename the Isolines layer "Topography".
This is a map of the topography.

Now add an Isolines layer from the "Without faults" data source, use the "Move the current
layer back" function to place it in third place (just after the "Topography" layer), then
modify its presentation as follows:

Request a filling with colors.

Refresh the drawing ( ): the new layer is not displayed.
Click on "Define view" ( ), and compare the values included in the "Volume of data"
and the "New volume" frames:
To make the isolines layer (layer of altitudes between 350 FT and 600 FT) visible, you
must enter 400 for Z0.
This is a map of the reservoir's hanging wall calculated without taking into account the
faults. You will notice steep altitude gradients, especially along the long East-West fault.

Interpolating with the faults

Right-click on the "Wells" data source and choose "Calculations Estimate 2D grid".
Click on "Use parameters" and open "Without faults":
Remove "Z coordinate" from the list of variables to interpolate.

Choose "Faults" in the "Faults source" drop-down list:
Click on "Save parameters" and enter the name "With faults".

Click on OK to start the grid's calculation.
Rename the new "2D grid on Wells" data source as "With faults".
Use the "Save as" function to make a copy of the "Location map" document under the
name "With faults".
Proceed as follows on the "With faults" graphic document:
Click on "Define view" ( ), and enter 400 for Z0 in the "New volume" frame.
Add an "Isolines" layer from the "With faults" data source.

A warning message reminds you that the grid was calculated taking into account the faults,
and that you must remember to include this Faults data source in the layer's presentation.
Use the "Move the current layer back" function to place this layer in second place (just
after the "Frame" layer). Modify its presentation as below, remembering to choose "Faults"
in the "Faults data source" frame, and to request a filling with colors:
Refresh the drawing ( ). You get the following message:
and two new data sources appear in the

Desktop tree:
GDM does not calculate isolines when two or more points of a fault are in the same cell on
the grid. In this case, GDM creates a "New fault definition" data source in which segments
have been removed.
You must now modify the presentation of the Isolines layer by

replacing, in the "Faults data source" frame, the "Faults" data
source by the "New fault definition" source.

You get the map of the reservoir's hanging wall taking into account the faults.
Correcting Fault data sources

We have seen that GDM can automatically correct Fault data sources by removing
segments.
However:
The automatic correction can, in certain rare situations (since the removed segments
are very short) provoke a change in the plotting of the faults which may not suit the
user.
GDM cannot correct all the fault plotting errors (in the online help index, see "Isolines
Presentation of isolines on a drawing"), and the user will have to manually insert,
move or remove points.
Checking the automatic correction
When GDM proposes a "New fault definition" data source, the easiest way to check
that the new faults plot is not excessively different from the original plot is to
superimpose the set of faults on a graphic document.
As an example, refer to the "Check New Faults" document in the "Oil_Field.GDM"
project in Tutor\Fault_models\End: three layers of Curves are superimposed:
The removed segments in a thick green line
The original set of faults in a medium black line
The set of faults proposed by GDM in a thin red line

Help with the manual correction
Proceed as follows to correct an existing set of faults:

Use "Save as" on the faults data source, if it is an external data source, to create a
GDM database that can be modified directly by digitization (Edit database
function: ).
Use the digitization adjustment function (see Digitizing profiles, page 166) when
two faults meet, so that they have a common point.
Use a graphic document that shows all the faults, fault points and the mesh of the
grid to calculate.
See, for example, the

"Check Original Faults"
graphic document in the
"Oil_Field.GDM" project in
Tutor\Fault_models\End:
The following layers are superimposed:

A grid of blocks layer showing a grid identical to the one that will be calculated
with the faults. In its presentation, choose: "No filling" and "Grid mesh".
A Curves layer showing the faults to be corrected.
A Points/Ends of run layer showing the points of the faults.
Using a Grid layer with colored blocks

In some cases, GDM will be unable to calculate the isolines: it will take a long time to
calculate the isolines, and will produce a map on which one or more isolines are missing,
informing you that one or more isolines exceed the maximum number of points for an
isoline (49997 points). In this case, you must abandon the isoline calculation, and choose a
Grid layer with colored blocks instead.
An example is provided in Tutor\Fault_models\Examples, with Project "Paola.GDM":
The "Maps" and "Copy of Maps" graphic documents represent the models of the footwall
of two geological formations in the form of a grid of colored blocks:

In the Paola project, you can use the "Sections" document to define sections using the
button.
The "Copy of Sections" document is an example of a section obtained in this way:

Using DXF files

Before reading this chapter, you must have read chapter "Processing vertical drill hole data"
(pages 77 to 101), which showed you how to connect data, and chapter "Graphic documents"
(pages 101 to 138), which showed you how to create Graphic documents.
The example used here is taken from a stream-sediment geochemistry survey.
In the Tutor\Geochem folder in the GDM installation folder, you will find the Start and
End subfolders:
Start is the folder in which you will do the exercise: it contains only the data required to
start the exercise.
End is the folder that contains the same exercise, but completed. You can thus use it to see
the results of the exercise before starting, or during the exercise.
The Start.ZIP and End.ZIP files contained in the Tutor\Geochem folder can be used to restore
the contents of the Start and End subfolders if necessary.
Data provided for the exercise

We have:
Geochemical data (sample points identified by a sample number, and described by their
X,Y coordinates in Km, the results of multi-element chemical analyses and a
classification code).
A digitized drainage pattern (X,Y coordinates in meters).
Contours of the geology digitized in AutoCAD (X,Y coordinates in Km, Z in m).
Open the Geochem.GDM project in Tutor\Geochem\Start.

The data is contained in three files:
Geochemistry.XLS for the samples
Rivers.XLS for the drainage pattern
Geol.DXF for the contours of the geology
The geochemical samples are in the "Geochemistry" Points data source, connected to the
"Geochem" worksheet in Geochemistry.XLS. The following correspondence table has been
used:

You must define the units

(KM) of the coordinates.
The units of the variables are
optional.
On connection, a length of 1
character was entered for the
Classes field.
If you open the

"Geochemistry" data source,
you will notice that GDM
has added a Z coordinate
(field ZZZZ) with a value of
0 meters.
The drainage pattern is in the "Rivers" Curves data source, connected to the "Rivers"
worksheet in Rivers.XLS. The following correspondence table has been used:
Note that if this data was in an Access table, you would have to add a variable with the
"Curve points order" use.
In the absence of any curve IDs, the Collar "XX" coordinate is used as the curve key,
provided two successive curves do not start at the same X coordinate.
The X and Y units have been defined in meters.
If you open the "Rivers" data source, you will notice that GDM has added a Z coordinate
(field ZZZZ) with a value of 0 meters in the Collars and in the Segments of the curves.
"Palette 1" is provided.
The "Map" graphic document shows the position of the points and the drainage pattern:

Connecting to/Importing the DXF file

The Geol.DXF file contains the schematic contours of the geological formations in the
form of 3D curves (AutoCAD 3D polylines).
We will convert this DXF file to a text file (CSV) which GDM can connect to:
Start Programs GDM 5.0 DXFtoCSV
File Import
Open the Geol.DXF file in Tutor\Geochem\Start
File Save Lines
The program prompts you to confirm the creation of a Geol.Csv file. Click on OK.
13 lines have been converted.

They can be Lines (segments) or
Polylines (curves).
Here, the 13 lines are polylines.
Click on "Close" to close DXFtoCSV.

We will now establish a link on file Geol.CSV:

"Project data Establish link with database". Fill in as follows:
Click on "Connect" and choose GEOL.CSV

Fill in the correspondence table as follows:
Note that the COUL code will be connected twice:

- In the curve collars you can use this code to fill in closed curves, after defining a
Patterns palette for a Code.
- In the curve segments you can use this code to plot the curve segments according
to a Line style, after defining a Line style palette for a Code.
Click on "Connect":
Answer "Yes" to both warnings.
Once you click on OK, you see the "Geology" Curves data source in both the Project

Add a "Curves" layer to the "Map" graphic document from the "Geology" data source.
Use the "Move the current layer back" function to place this layer in second place (just
after the "Frame" layer). Modify its presentation as below:
Choose "Palette 1".
Then click on the "Filling"

button.
Choose the filling according to

the COUL field.

Note: if you use the "Save as 4.2" Desktop function on the name of the "Geology" data
source, you import the file of DXF curves to the GDM database, which offers the
advantage of being able to modify the curves by digitization.
Comment: use the "Save as 4.2" function rather than "Save as" when the length of the
original codes is less than or equal to 4 characters. This will subsequently enable you to
add other codes if necessary.
Other example: DXF model of tunnels

The "EOLE.GDM" project in Tutor\Metro\Examples was created by Italian company
GEODATA, for the Parisian EOLE subway project.
The drill hole databases are GDM databases.
The geological model was calculated with GDM using drill hole data.
The tunnels model was created using AutoCAD and imported in GDM just as we imported
the "Geology" curves in the previous chapter.
The "Map/Sections" graphic document, which shows the drill hole data, the geological
model and the tunnels project at the same time, is used to see in which layers the tunnels
are to be dug:

The contours represent the

altitude of the "Sables de
Beauchamp" (Beauchamp
sand) footwall.
You can calculate and display

any section from this
horizontal projection view
using .
Sections 1 and 2 below are
examples:
Section 1
"Sables"
footwall

Section 2
"Sables"
footwall
In order to know how to dig the tunnel, it is extremely important that we know the shape of
the "Sables de Beauchamp" footwall, a formation less solid than the lower formation.
The following image is a 3D view of the drill holes, the geological model, and the tunnels
model produced according to the method explained in the next chapter. The corresponding
"VRML model" (EOLE.wrl) is in folder Tutor\Metro\VRML.

3D views of data and models
All the data used by GDM (samples, drill holes, curves), or created by GDM (models) is 3D
data (i.e., with X, Y and Z coordinates). However, at present, GDM can only display this data
in 2D: projection on a horizontal plane, on a vertical plane, or on a broken line vertical profile
(Note: by modifying the coordinate system's definition, you can also display data projected on
a sloping plane).
Programs developed in DOS can be used to convert the GDM data to VRML2 format (Virtual
Reality Modeling Language - version 2).
This data can then be displayed using any viewer that supports the VRML2 or VRML97
standard.
VRML viewers
You can find many types of VRML viewer. Among them are the following which can be
downloaded for free:
GLVIEW, application that can be downloaded from www.snafu.de/hg
Cosmo Player, plugin that can be downloaded from www.cai.com/cosmo
Blaxxun Contact, plugin that can be downloaded from www.blaxxun.com
Cortona VRML Client, plugin that can be downloaded from www.parallelgraphics.com
Version 4.4 of GLVIEW (the one currently available for downloading) uses the coordinates
(0,0,0) as its center of rotation for objects; this makes its use difficult with GDM data
which is usually not centered on these coordinates.
For this reason, we have chosen to provide version 3 of GLView which uses the center of
the screen as the center of rotation. It is installed in Tutor\VRML\GLView. To use it,
simply add a shortcut to GLView.EXE on your Windows Desktop.
GDM -> VRML conversion programs

The following programs are available:
Three GDM data conversion programs:
GRD2VRML.EXE conversion of a surface (GDM file with the extension .GRD)
HED2VRML.EXE conversion of drill holes/curves (3 GDM files with the
extensions .HED, .BSD and .IND)
B2D2VRML.EXE conversion of points (GDM file with the extension .B2D
(points),
or .HED (drill hole collars/curves),
or .BSD (drill hole runs/curve points).
Two additional programs, for the conversion of GDM palettes (colors associated with a
Code):
GDM2RGB.EXE conversion of a standard GDM palette
GDM2RGB5.EXE conversion of an extended GDM palette

(see the definition of both types of Palette on page 56).

To make these five programs accessible from any folder, you can copy them in
\WINDOWS (or \WINNT), or add C:\GDM\Tutor\VRML\Programs to your system's
PATH.
CAUTION: the names of fields and files must not exceed 8 characters with these
programs.
Before using these programs, make sure you read the freeware license agreement, on page
300.
Files
Conversion program input files
Each GDM data conversion program reads:

a .CSV file exported from GDM containing the data to convert,
a .PAR file, created in a text editor, containing parameters to run the conversion
program,
optionally for the drill holes/curves and points, a .COL file (color palette).
Conversion program output files
Each GDM data conversion program creates 3 files:

a .WRL file
This file will be opened by GLVIEW (or another VRML viewer).
It does not contain data to display, it "calls" files containing the objects to display.
a .BOX file
This file contains a parallelepiped to locate the data in space using a trihedron
X,Y,Z, with coordinates written at the corners of the parallelepiped, and with a
North arrow.
This parallelepiped, or "boundary box", can be defined by the user (in the .PAR
file), or calculated automatically from the minimum and maximum values of the
coordinates of data contained in the .CSV file.
a .SCN file
This file contains GDM data converted to VRML format, which can be:
a surface (.SCN file created by GRD2VRML)
drill holes/curves (.SCN file created by HED2VRML)
points (.SCN file created by B2D2VRML)
Each .SCN file thus contains a single type of data: a Surface, or a set of drill
holes/curves, or a set of Points.

Choice of files to view
GLVIEW opens a .WRL file

The list of data to display by the viewer is located at the end of the .WRL file. You can
modify this list using a text editor by adding a line for each type of data to display.
Generally speaking, you will display one .BOX file and one or more .SCN files.
Example: at the end of file HWFWHOL.WRL in folder \Tutor\VRML\End:
Inline { url "HW.BOX"} parallelepiped
Inline { url "HW.SCN"} vein hanging wall (surface)
Inline { url "FW.SCN"} vein footwall (surface)
Inline { url "Holes.SCN"} drill holes
Note: to avoid displaying the .BOX file or one of the .SCN files, instead of removing
the corresponding line, you can also insert the # character at the start of the line.
Converting a GDM surface: program GRD2VRML
In GDM, preparation of file grid.CSV:
The grid must be exported with the coordinates of each node/block. These coordinates
must be "field" coordinates, and not "grid" coordinates in relation to the grid origin.
Proceed as follows from the Grid data source:
Display Summary Parameters
Note the number of columns (NX) and the number of lines (NY) that you must
specify in the grid.PAR file, then close the dialog box.
Save as Type of data: points (to obtain a points file with coordinates)
Calculations Change coordinate system Reset all the parameters to zero (to
obtain field coordinates)
Export Save as: Text with separator (*.CSV)
List of fields to export:
"Altitude"-type variable: one minimum
Variable(s) to manage the color(s): optional
X and Y: mandatory
Note 1: if you export several "altitude" variables, you will be able to create several
surfaces (.SCN files) to display from the same .CSV file.
Note 2: place X, Y at the end to make sure you always have a defined variable in the
.CSV file's last column (otherwise GRD2VRML will be unable to interpret the file).
Note 3: if the file to export is large, you will gain time by exporting in Excel format,
then asking Excel to create the .CSV file.

With a text editor, preparation of file grid.PAR:
Each line must have the following format: keyword # value.

The next 5 lines are mandatory:
NCOL # number of columns in the grid (see NX earlier)
NLIG # number of lines in the grid (see NY earlier)
IX # position in the .CSV file of the field containing the X coordinate
IY # position in the .CSV file of the field containing the Y coordinate
IZ # position in the .CSV file of the field containing the altitude variable
The values to be entered on these lines are all integers.
With only these 5 lines, the VRML surface generated will be red (default color).
The surface can be colored in different ways:
Other plain color: add a line COLOR # (see "Managing colors", page 275).
Variable color (varying from blue to red):
If you add a line ICOL # position in the .CSV file of a field containing a
variable to manage the color, the minimum and maximum values of this
variable will be used to define the limits of the color gradation scale. Note: if
you wish, the position specified can be that of the field containing the altitude
variable (same value for IZ and ICOL).
If in addition to ICOL you add lines VMIN # min. value and VMAX # max.
value these values will be used to define the limits of the color gradation scale.
Other parameters that can be used: see "Optional parameters common to all the
.PAR files", page 277.
Running program GRD2VRML:
In a DOS window, access the folder containing files grid.CSV and grid.PAR (they
must have the same name), and enter the following command:
GRD2VRML grid
The following files are subsequently generated:
grid.WRL
grid.BOX
varZ.SCN (varZ is the name of the altitude field in the .CSV file)
Note: if files with the same names already exist, they will be replaced without prior
warning.
If the program crashes, you can delete the following temporary files if they are present
in the current folder:
grid.PTS, grid.TES, grid.TRI
PT.TMP, NORM.TMP, COLOR.TMP, IND.TMP

Converting drill holes/curves: program HED2VRML
In GDM, preparation of file hed.CSV:
The data source to convert must be a GDM database. If it is an external database, use
the "Save as" function to create a GDM database.
From the GDM drill holes database:
A drill hole/curve identifier: mandatory.
The XX,YY,ZZ coordinates of the drill hole collars/curves: mandatory.
One (or more) code(s) to manage the color: optional.
The X,Y,Z coordinates of the drill hole end of runs/curve end of segments:
mandatory.
Note 1: if there is no curve identifier, you can use the XX or YY coordinate of the
curve head.
Note 2: place X,Y,Z at the end to make sure you always have a defined variable in
the .CSV file's last column (otherwise HED2VRML will be unable to interpret the file).
With a text editor, preparation of file hed.PAR:

The following 7 lines are mandatory:
INOM # position in the .CSV file of the field containing the drill hole identifier
IX0 # position in the .CSV file of the field containing the X coordinate of the
collars
IY0 # position in the .CSV file of the field containing the Y coordinate of the
collars
IZ0 # position in the .CSV file of the field containing the Z coordinate of the
collars
IX # position in the .CSV file of the field containing the X coordinate of the
runs/segments
IY # position in the .CSV file of the field containing the Y coordinate of the
runs/segments
IZ # position in the .CSV file of the field containing the Z coordinate of the
runs/segments
With only these 7 lines, the style of the VRML curves generated will be fine and red
(default color).

The curves can be colored in different ways:

Variable color (according to a "Color code" in file hed.CSV):
Add a line ICOL # position in the .CSV file of the field containing the Color
code.
A "palette" file named colorCode.COL must be provided if the "Color code"
field contained in file hed.CSV is called "colorCode" (see "Managing colors",
page 275).
The curves can be represented by cylinders:
By adding a line LINE # C. The diameters of the cylinders will be equal to 1/200
of the boundary box's diagonal.
By adding a line SIZE # diameter, you can control the diameter of the cylinders.
The diameter's value must be given in the same unit as the coordinates.
Preparation of file colorCode.COL:
This file is only required if you are using a Color code in file hed.CSV.
To create this file, see "Managing colors", page 275.
Running program HED2VRML:
In a DOS window, access the folder containing files hed.CSV and hed.PAR (they must
have the same name), and file colorCode.COL if you want variable colors on the drill
holes/curves, then enter the following command:
HED2VRML hed
hed.WRL
hed.BOX
hed.SCN
warning.
If the program crashes, you can delete the following temporary files if they are present
in the current folder:
hed.PTS, hed.TMP, hed.SEG
PTINDEX.TMP, USECOL.TMP, COLOR.TMP, CLRINDEX.TMP

Converting points: program B2D2VRML
In GDM, preparation of file b2d.CSV:
The data source to convert must be a GDM database. If it is an external database, use
the "Save as" function to create a GDM database.
From the GDM Points data source (or from collars or runs/segments of a drill
holes/curves database):
One (or more) point identifiers (ID/Code/Variable): optional.
One (or more) codes to manage the color: optional.
The X,Y,Z coordinates of the points: mandatory.
Note 1: place X,Y,Z at the end to make sure you always have a defined variable in
the .CSV file's last column (otherwise B2D2VRML will be unable to interpret the file).
With a text editor, preparation of file b2d.PAR:

The following 3 lines are mandatory:
IX # position in the .CSV file of the field containing the X coordinate of the
points
IY # position in the .CSV file of the field containing the Y coordinate of the
points
IZ # position in the .CSV file of the field containing the Z coordinate of the
points
With only these 3 lines, the VRML points generated will be red spheres (default color).
The diameters of the spheres will be 1/200 of the boundary box's diagonal.
The spheres can be colored in different ways:

Variable color (according to a "Color code" in file b2d.CSV):
Add a line ICOL # position in the .CSV file of the field containing the Color
code.
A "palette" file named colorCode.COL must be provided if the "Color code"
field contained in file b2d.CSV is called "colorCode" (see "Managing colors",
page 275).

The spheres can be replaced by cubes:

Add a line POINT # C
To check the diameter of the spheres (or the width of the edge of the cubes):
Add a line SIZE # diameter. The value of the diameter must be given in the same unit
as the coordinates.
An identifier can be written above each point:
Add a line INOM # position in the .CSV file of the field containing the identifier.
Note: the color and the height of the identifier are those of the spheres (or cubes).
Preparation of file colorCode.COL:
This file is only required if you are using a Color code in file b2d.CSV.
To create this file, see "Managing colors", page 275.
Running program B2D2VRML:
In a DOS window, access the folder containing files b2d.CSV and b2d.PAR (they must
have the same name), and file colorCode.COL if you want variable colors on the
spheres/cubes, then enter the following command:
B2D2VRML b2d
b2d.WRL
b2d.BOX
b2d.SCN
b2d.NOM: VRML identifiers file (if you used the INOM parameter)
warning.
If the program crashes, you can delete the following temporary file if present in the
current folder:
b2d.PTS
Managing colors
RGB colors
The colors used are RGB primaries (made up of a combination of the three primary
colors Red, Green, Blue). The component colors have values between 0. and 1.
Example : Red = 1. 0. 0.

Blue = 0. 0. 1.
Purple = 1. 0. 1.
Black = 0. 0. 0.
Etc.
To obtain the RGB translation of the 48 colors in the GDM palette, you can display or
print file Tutor\VRML\Programs\PalRGB.Doc
Structure of .COL files
To color drill holes/curves or points according to a code in the GDM database exported
to the .CSV file along with the coordinates, a file called colorCode.COL must be
present in the current folder when you run the data conversion program.
The filename ("colorCode") must be that of the field in the .CSV file which is
referenced by the ICOL # parameter in the .PAR file.
Example of a colorCode.COL file:
# 1 1 1
ARGI # 0 1 0
BREC # 0 0 1
CARS # 0 1 1
FESA # 1 1 0
GLSA #.5 .5 .5
A line's general structure is: "color code value" # "RGB value"
This file can be generated with either
a text editor,
the GDM2RGB utility from the export file of a standard GDM palette (standard
GDM codes),
the GDM2RGB5 utility from the export file of an extended GDM palette (long
codes).
Use of GDM2RGB or GDM2RGB5
These utilities create a colorCode.COL file from the export file of a GDM palette. The
colors of the GDM palette are translated by their RGB equivalent.
In GDM, open the palette containing the "Patterns for a Code" or the "Symbols for
a Code" defined for the code exported in the .CSV file.
"Export table": a default name and a .TXT extension are proposed. Note the name
under which you export (palette.TXT).
If the GDM palette contains standard codes, the .TXT file will resemble the one
below (names of the codes in the first column):
50 4 0.30 0.30
ARGI 182 3 0.50 0.50
BREC 182 19 0.50 0.50
CARS 182 2 0.50 0.50
If the GDM palette contains long codes, the .TXT file will resemble the one
below (names of the codes in the last column):
182 32 1.00 1.00
182 3 1.00 1.00 Argi
182 19 1.00 1.00 Brec

182 2 1.00 1.00 CarS

In a DOS window, access the folder containing palette.TXT and enter the
following command:
GDM2RGB palette.TXT colorCode.COL (for standard codes)
GDM2RGB5 palette.TXT colorCode.COL (for long codes)
Optional parameters common to all the .PAR files
Keyword Type Description

NAME Char. field for optional comments
BACKGROUND RGB RGB color of the viewer's background (default: black)
COEFXY Real multiplication coefficient for X,Y coordinates
COEFZ Real multiplication coefficient for the Altitude variable
UNITXY Char. character string indicating the unit of the X,Y coordinates
UNITZ Char. character string indicating the unit of the Altitude variable
XMIN Real parameters to predefine the boundary box
XMAX Real parameters to predefine the boundary box
YMIN Real parameters to predefine the boundary box
YMAX Real parameters to predefine the boundary box
ZMIN Real parameters to predefine the boundary box
ZMAX Real parameters to predefine the boundary box
GDM -> VRML2 conversion exercise

We will create 3D views of deviated drill hole data which we used to process deviated drill
hole data (page 219), and models of the vein's hanging wall and footwall which we
calculated.
In folder Tutor\VRML in the GDM installation folder, you will find the Start and
End subfolders:
Start is the folder in which you will do the exercise: it contains only the data required
to start the exercise.
End is the folder that contains the same exercise, but completed. You can thus use it to
see the results of the exercise before starting, or during the exercise.
The Start.ZIP and End.ZIP files contained in folder Tutor\VRML can be used to restore the
contents of the Start and End subfolders if necessary.
If you want to view the results (3D views) before starting the exercise, you can start
GLVIEW and open files HWFWHOL.WRL and HWPTS.WRL in Tutor\VRML\End.
You can also view the drill hole and model data in 2D (plane and sections) by displaying
the "Model and "Copy of Model" graphic documents in the Mine.GDM project in
Tutor\VRML\Start.

Vein hanging wall and footwall surfaces
Exporting the data:
On the "Model" data source, choose "Display Summary Parameters" to find out
the parameters of the grid: 27 columns and 22 lines.
On this data source, choose "Save as", enter the "Points Model" name and
choose the "Points" type of data.
If you open the "Points Model" data source in List mode, you will notice that the
coordinates are in the grid's local coordinate system.
On "Points Model", choose "Calculations Change coordinate system", reset X0,
Y0, Z0 to zero, then save the data source. The coordinates are now so-called
"geographic" coordinates.
On "Points Model", choose "Export data source", choose the "Excel Files 97"
type, and click on "Save":
Select fields Vein hanging wall, Vein footwall, Thickness, Au, X and Y.
Click on OK.
Open Points_Model.XLS in Excel, rename the fields Vein_Hanging_wall,

Vein_Footwall and Thickness to HW, FW and THCK respectively (GRD2VRML
uses field names with a maximum 8 characters).
Save the modifications, and save this file in CSV format (semi-colon separator) as
HW.CSV, then as FW.CSV.
Note 1: you export in Excel because the ODBC export in CSV is very slow.
Note 2: you export X or Y last for the last exported field to always be defined.
Creating VRML models:
Vein hanging wall:

The HW.PAR file has been prepared in an editor:
The size of the boundary box has been defined,
The ICOL parameter specifies that the 4th field will be used to define a surface
color varying between the minimum and maximum values of "Au".

In a DOS window, run the following

command: GRD2VRML HW
Files HW.WRL, HW.BOX, and HW.SCN

have been created.
You can view HW.WRL using GLVIEW:
Vein footwall:
File FW.PAR has been prepared in an editor:

the COLOR parameter defines the color of the
surface.
In a DOS window, run the following

command: GRD2VRML FW
Files FW.WRL, FW.BOX, and FW.SCN have

been created.
You can view FW.WRL using GLVIEW:
Simultaneous display of the hanging wall and the footwall:
Copy HW.WRL as HWFW.WRL
Edit HWFW.WRL and add the following line at

the end of the file:
Inline { url "FW.SCN"}
You can view HWFW.WRL using GLVIEW:
Drill holes

Exporting the data:
On the "Data" data source, choose "Save as...", enter the name "Data GDM", and
choose the "Drill holes" type of data.
On "Data GDM", choose "Export data source", choose the "Excel Files 97" type
and click on "Save":
Select fields Borehole, X, Y, Z, Geological code, XXXX, YYYY, ZZZZ,
Click on OK.
Open Data_GDM.XLS in Excel, rename the "Geological_Code" field as
"GeolCode" and save your changes.
Also save this file in CSV format as Holes.CSV.
Still in GDM, open the "Geol. Colors" palette, click on the "Export Table"
button, and enter the name "GeolCol.txt". Note that the codes of the "Patterns for a
Code" table are "long codes".
Preparing the palette:
In a DOS window, run the following command:

GDM2RGB5 GeolCol.TXT GeolCode.COL
The GeolCode.COL file contains the definition of the RGB colors corresponding to
the colors defined in the palette.
Creating the VRML model:
The HOLES.PAR file has been prepared in an editor.

HED2VRML HOLES
Files HOLES.WRL, HOLES.BOX, and HOLES.SCN have been created.
You can view HOLES.WRL using GLVIEW:

Simultaneous display of the drill holes and the vein's surfaces:

Copy HWFW.WRL as HWFWHOL.WRL
Edit HWFWHOL.WRL and add the following line at the end of the file:
Inline { url "Holes.SCN"}
You can view HWFWHOL.WRL using GLVIEW:

Impact of the drill holes on the vein's hanging wall
Exporting the data:
On the "Vein" data source, choose "Export data source", choose the "Excel Files
97" type, then click on "Save":
Select fields SHID, FORM, X1, Y1, Z1,
Click on OK.
Open Vein.XLS in Excel, delete row "SD09" for which there are no coordinates,
then Save. Also save this file in CSV format as Points.CSV.
Still in GDM, open the "Vein" palette, choose "Symbols for a Code", click on the
"Export Table" button and enter the name VeinCol.txt. Note that the codes in this
palette table are standard codes.
Preparing the palette:

GDM2RGB SeamCol.TXT FORM.COL
The FORM.COL file contains the definition of the RGB colors corresponding to
the colors defined in the palette.
Creating the VRML model:
The POINTS.PAR file has been prepared in an editor.

In a DOS window, run the following command: B2D2VRML POINTS
Files POINTS.WRL, POINTS.BOX, POINTS.NOM, and POINTS.SCN have been
created.
You can view POINTS.WRL using GLVIEW:

Simultaneous display of the vein's hanging wall and the points of impact:
Copy HW.WRL as HWPTS.WRL
Edit HWPTS.WRL and add the following lines at the end of the file:
Inline { url "Points.SCN"}
Inline { url "Points.NOM"}
You can view HWPTS.WRL using GLVIEW:
You will notice that the drill holes causing anomalies in the form of the surface are
holes SD01, SD10 (hollow) and SD24 (boss).

Appendices
GDM 5 popup menus
On the names of data sources

In the Project tree
Add to desktop
Redo data source filter
Re-establish data source link
Rename data source
Remove data source
Display
Dependencies
Other sources
Preview
Properties
In the Desktop Tree
Place data source in project

Rename data source
Rename GDM database
Delete GDM database
Cancel modifications
Save
Save as
Save as 4.2
Refresh
Summary
Concatenate data source
List
Export data source
Form
Display
Dependencies Filter
Preview Modify
Filter Copy
Structure
Drill hole run coordinates
Calculations
Assign value to character fields Thickness
Extract From depth
Assign value to numeric fields
Update GDM fields To depth
Change coordinate system
Properties Calculation on drill hole runs Contiguous runs
Determine formation or composite
Area...
Calculation on curves
Estimate 2D Grid
288 Getting started with GDM 5 - Appendices
On the names of Log documents

In the Project tree
Add to desktop
Re-establish document link
Rename document
Delete document
Display
Sources
Properties
In the Desktop Tree
Place document in project

Rename document
Save
Save as
Export log document as 4.2
Export WMF
Print
Page setup
Display
Sources
Repeat log Modify
Depth portion/scale Standard heading
Drill hole Specific heading
Presentation Depth graduation
Properties Column heading height
On the names of Graphic documents

In the Project tree
Add to desktop
Re-establish document link
Rename document
Delete document
Display
Sources
Properties

Appendices 289
In the Desktop Tree
Place document in project

Rename document
Save
Save as
Export graphic document as 4.2
Export WMF
Print
Display
Sources
Define view
Scale
Properties
On the names of Palettes

In the Project tree
Add to desktop
Re-establish palette link
Rename palette
Delete palette
Display
Dependencies
Properties
In the Desktop Tree
Place palette in project

Rename palette
Rename GDM database
Delete palette
Save
Save as
Display
Dependencies
Properties

On the names of Parameters
Re-establish parameter link

Rename parameters
Delete parameters
Copy parameters
Sources
Properties
In the List mode edit zone
Undo
Cut
Copy
Paste
Delete
Select all
On the Log documents
Parameters
Properties
Add column
Insert column
Delete column
On the Graphic documents

On the document On the name of a layer
Title Rename layer

Scale Presentation mode
View Delete layer
Illustration Properties
Frame and mesh Repeat grid profiles

Appendices 291
Toolbars in the viewing area
List mode toolbar

Left-hand side: "column" buttons
Undo fix columns(s)

Fix columns(s)
Column order
Restore column(s)
Undo Hide column(s)
Hide column(s)
Right-hand side: "line" buttons and search
To documents
Repeat
Replace
Search
Insert lines
Paste lines
Copy lines
Cut lines
Delete lines
Add lines
Erase lines
Log document toolbar
To graphic
To table
Define scale
Fit to window
Zoom out
Zoom in
Add column
Refresh drawing
Modify log
Print

Graphic document toolbars
General toolbar
Left-hand side:
Define title
Move the current layer forward
Move the current layer back
Delete layer
Add layer
Refresh drawing
Print
Right-hand side:
To table
To log
Define illustration
Define adjusted section
Define section
Define view
Define scale
Fit to window
Zoom out
Zoom in
Digitization toolbar
Digitization
options
Cancel
Delete curve
Delete point
Information on point/curve
Add new point/curve
Stop digitization
Edit current layers source
Create curve overlay
Create point overlay

Appendices 293
Base map adjustment toolbar
Calculate metafile coordinates

Setting point 2
Setting point 1
Fit to window
Zoom out
Zoom in

Palette of standard GDM patterns
1 2 3 4 5 6 7 8
16 17 18 19 20 21 22 23
31 32 33 34 35 36 37 38
46 47 48 49 50 51 52 53
61 62 63 64 65 66 67 68
76 77 78 79 80 81 82 83
91 92 93 94 95 96 97 98
106 107 108 109 110 111 112 113
121 122 123 124 125 126 127 128
136 137 138 139 140 141 142 143
151 152 153 154 155 156 157 158
166 167 168 169 170 171 172 173
181 182 183 184 185 186 187 188
196 197 198 199 200 201 202 203
211 212 213 214 215
The scales in X and Y used for these patterns are the default scales (Xsca and Ysca = 1).
By varying the scales, you create a wide variety of patterns.
To consult GDM's palette of 48 colors which you can assign to your patterns, print file
Tutor\VRML\Programs\PalRGB.doc on your printer or plotter (the rendering of the colors varies
depending on the printer used).

Appendices 295
8 9 10 11 12 13 14 15
23 24 25 26 27 28 29 30
38 39 40 41 42 43 44 45
53 54 55 56 57 58 59 60
68 69 70 71 72 73 74 75
83 84 85 86 87 88 89 90
98 99 100 101 102 103 104 105
113 114 115 116 117 118 119 120
128 129 130 131 132 133 134 135
143 144 145 146 147 148 149 150
158 159 160 161 162 163 164 165
173 174 175 176 177 178 179 180
188 189 190 191 192 193 194 195
203 204 205 206 207 208 209 210
Example of changes of scale on pattern no. 26:

Xsca * Ysca 1*1 1 * 0.5 0.5 * 1 1*2 2*1 2*2

GDM setup file

This file is located in the Windows folder ( C:\WINDOWS, or C:\WINNT).
The contents of the GDM50.INI file displayed below correspond to that resulting from a standard
installation of GDM.
Comments added are in italics.
[Localisation]
CharSet=0 Russian version: CharSet=204
[Installation]
GDMDisk=C: Do not modify after installing the Protection
GDMDirectory=\GDM\Program Do not modify after installing the Protection
GDMDemoDisk=C: Modifiable. Location of GDM\Tutor
GDMWorkDisk=C: Modifiable. Location of temporary files
GDMWorkDirectory=\GDM\Temp Modifiable. Location of temporary files
GDMProtect=\GDM\Protect Do not modify
[Data]
Model=C:\GDM\Models Modifiable. Location of Model databases
Type=1
DefaultXYUnit=M Default coordinate units for "New database"
DefaultZUnit=M Default coordinate units for "New database"
HoleType=1
DrawingUnit=cm Default drawing units
WMF=C:\GDM\Wmf Modifiable. Location of shared WMFs
[UnitsList] Do not remove units from this list

Number of Units=54 Units can be added
; Millimeters
1=MM
; Centimeters
2=CM
; Meters
3=M
. . .
. . .
. . .
; Parts per million
52=PPM
; Parts per billion
53=PPB
; pH
54=PH
[WindowFrame] Location and size of the GDM window

Xcoord=207
Ycoord=17
Width=911
Height=612
Visible=1
[Palette]
Make=no
MakeColor=no

Appendices 297
TreeViewStudy] Project tree colors

Background_Red=210
Background_Green=255
Background_Blue=255
Folder_Red=0
Folder_Green=0
Folder_Blue=0
ItemNormal_Red=0
ItemNormal_Green=0
ItemNormal_Blue=0
ItemModify_Red=255
ItemModify_Green=0
ItemModify_Blue=0
ItemAbsent_Red=190
ItemAbsent_Green=170
ItemAbsent_Blue=0
[TreeViewWork] Desktop tree colors

Background_Red=255
Background_Green=255
Background_Blue=200
Folder_Red=0
Folder_Green=0
Folder_Blue=0
ItemNormal_Red=0
ItemNormal_Green=0
ItemNormal_Blue=0
ItemModify_Red=255
ItemModify_Green=0
ItemModify_Blue=0
ItemAbsent_Red=190
ItemAbsent_Green=170
ItemAbsent_Blue=0
[DSN] ODBC configuration

Nb=5
Driver_1=Microsoft Text Driver (*.txt; *.csv)
Driver_2=Microsoft dBase Driver (*.dbf)
Driver_3=Microsoft Access Driver (*.mdb)
Driver_4=Microsoft Excel Driver (*.xls)
Driver_5=Microsoft Excel Driver (*.xls)
[DSN_1]
DSN=GDM_CSV
Description=Interface GDM / Text
DriverId=27
SafeTransactions=0
UID=
Extensions=asc,csv,tab,txt
ImplicitCommitSync=Yes
Threads=3
UserCommitSync=Yes
[DSN_2]

DSN=GDM_DBF
Description=Interface GDM / DBase IV
DriverId=277
FIL="dBase III;"
SafeTransactions=0
UID=
CollatingSequence=ASCII
Deleted=1
PageTimeout=600
Statistics=0
Threads=3
UserCommitSync=Yes
[DSN_3]
DSN=GDM_MDB
Description=Interface GDM / ACCESS
DriverId=25
FIL="MS Access;"
PWD=
SafeTransactions=0
UID=admin
MaxBufferSize=512
PageTimeout=5
Threads=3
UserCommitSync=Yes
[DSN_4]
DSN=GDM_XL5
Description=Interface GDM / Excel 5/7
DriverId=22
FIL="excel 5.0;"
ReadOnly=0
SafeTransactions=0
UID=
MaxScanRows=16
Threads=3
UserCommitSync=Yes
FirstRowHasNames=1
[DSN_5]
DSN=GDM_XL97
Description=Interface GDM / Excel 97
DriverId=790
FIL="excel 5.0;"
ReadOnly=0
SafeTransactions=0
UID=
MaxScanRows=16
Threads=3
UserCommitSync=Yes
FirstRowHasNames=1

Appendices 299
GDM License Agreement

WARNING: If the Product Code used in the protection of this GDM copy begins with EDU, the software
shall be used only for teaching or research activities. Any commercial use is forbidden.
This document is a legal agreement between you (a natural person or body corporate, referred to as "the User")
and BRGM (the owner of the GDM software). By installing the software, you formally bind yourself to the
following provisions:
If you do not agree with the provisions of this agreement, you should immediately return the complete software
package (disks, printed documentation and all other items) to the sales point from which you purchased it, in
order to obtain a full refund.
1 - Purpose. BRGM hereby grants you the right to use its GDM software (including the stored program and its
documentation) subject to the provisions described below. These provisions supersede any other operating
terms and conditions for the GDM software which you may have received previously. These provisions shall
apply for the term of the demonstration period granted (if you have obtained a demonstration copy) and shall
continue to apply thereafter provided you have paid the entire license price and received the final software.
2 License description Operating conditions. a) The software may be used on one machine only at a time.
If you have obtained several licenses for the software, you may concurrently use as many copies as you have
licenses. b) The software may be copied or duplicated, either in printed or machine readable form, for back-up
purposes only (however, certain diskettes may contain devices which limit or prevent duplication). c) It is
strictly forbidden to decompile or disassemble the software.
3 Ownership right - Protection. The software shall remain the exclusive property of BRGM. Consequently,
it shall not, under any circumstances, be transferred, sub-licensed, lent or made available, either free of charge
or for consideration. The software and its documentation are covered by BRGM copyright. You shall,
therefore, take all necessary steps to protect such software and documentation. In particular, you hereby agree
not to change or alter the software without BRGM's prior approval. Any modification to the software shall
remain BRGM's property. If the software (stored program and/or documentation) is stolen, you shall
immediately inform BRGM accordingly so that appropriate action may be taken.
4 Software Special Guarantee - Upgrades - Support. BRGM guarantees the software for a three month
period from the date of delivery against any error detected and located by the User, and agrees to replace the
defective copy. Revisions or updates may be proposed. The license agreement does not cover after-sale user
support which shall be provided for in a separate agreement, as necessary.
5 Limited guarantee - Liability. BRGM hereby guarantees that the software performs the functions described
in the documentation. This guarantee shall not, under any circumstances, be construed as a guarantee that the
results obtained from the software shall correspond to the User's needs. You hereby acknowledge that you
accept sole liability for the choice of the software to meet your objectives and that you shall use the software
according to your own instructions, under your own control and subject to your own liability. If BRGM is
held liable for any reason whatsoever, the corresponding compensation shall not, under any circumstances,
exceed the price of the license.
6 - Termination. The license shall remain valid until canceled. BRGM may terminate the license without notice
if you fail to observe the agreed conditions of utilization. In the event of cancellation, the software must be
destroyed along with its documentation.
7 Applicable Law - Disputes. The license is governed by French Law. If the Parties fail to reach an amicable
settlement, any dispute shall be submitted to the competent court in Paris (France).
BRGM Software Products

Avenue Claude Guillemin - BP 6009 - 45060 Orlans Cedex 2, France

Freeware License Agreement

END-USER LICENSE AGREEMENT FOR SOFTWARE DELIVERED FREE OF CHARGE
BY BRGM TO THE GDM USERS
This Agreement is a legal agreement between you (either an individual or a single entity) and BRGM for the
utility or complementary software delivered free of charge to the GDM users.
This Software Product may include computer software and associated media, printed documents, and "online"
or electronic documentation. By exercising your rights to make and use copies of the Software Product, you
agree to be bound by the terms of this agreement. If you do not agree to the terms of this agreement, you may not
use the Software Product.
SOFTWARE PRODUCT LICENSE

The Software Product is protected by copyright laws and international copyright treaties, as well as other
intellectual property laws and treaties. The Software Product is licensed, not sold.
1. Licensing
This agreement grants you the following rights:
- Installation and Use: You may install and use an unlimited number of copies of the Software Product.
- Reproduction and Distribution: You may not reproduce, or distribute copies of the Software Product.
2. Description of other rights and limitations
- You may not transfer, reverse engineer, decompile, or disassemble the Software Product.
- Termination: Without prejudice to any other rights, BRGM may terminate this agreement if you fail to
comply with the terms and conditions of this agreement. In such event, you must destroy all copies of the
Software Product and all of its component parts.
3. Copyright
All title and copyrights in and to the Software Product are owned by BRGM or its suppliers. The Software
Product is protected by copyright laws and international treaty provisions. Therefore, you must treat the
Software Product like any other copyrighted material.
LIMITED WARRANTY
1. No warranties
BRGM expressly disclaims any warranty for the Software Product. The Software Product is provided "as
is" without warranty of any kind, either express or implied, including, without limitation, the implied
warranties or merchantability, fitness for a particular purpose, or non-infringement. The entire risk arising
out of use or performance of the Software Product remains with you.
2. No liability for consequential damages
In no event shall BRGM be liable for any damages whatsoever (including, without limitation, damages for
loss of business profits, business interruption, loss of business information, or any other pecuniary loss)
arising out of the use of or inability to use this Software Product, even if BRGM has been advised of the
possibility of such damages.
BRGM Software Products

Avenue Claude Guillemin - BP 6009 - 45060 Orlans Cedex 2, France

Appendices 301
Technical support address

Feel free to send any questions or suggestions you may have to:
Mr. Jacques BOBILLIER GDM Sales and Technical Support

BRGM
Service CDG
BP 6009 - 45060 ORLEANS CEDEX 2
FRANCE
E-mail: gdm@brgm.fr
Tel.: +33 (0)2 38 64 30 14
Fax: +33 (0)2 38 64 39 70

The information contained in this document may be modified without prior notice.
GDM is a registered trademark of BRGM.
All trademarks mentioned herein are registered by their respective companies.
BRGM Copyright 1987-2002
Printed January 24, 2002.

GDM - UserGuideV13

Uploaded by

Copyright:

Available Formats

GDM - UserGuideV13

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GDM - UserGuideV13

Uploaded by

Copyright:

Available Formats

GDM 5.

An application from the BRGM software range

GDM is used for:

The User's Guide is split into three sections:

The online help

GDM 5.0 User's Guide 356244635.doc V1.3

UG5.doc V1.3 GDM User's Guide 5.0

GDM 5.0 User's Guide 356244635.doc V1.3

UG5.doc V1.3 GDM User's Guide 5.0

GDM 5.0 User's Guide 356244635.doc V1.3

UG5.doc V1.3 GDM User's Guide 5.0

SOFTWARE PRODUCT LICENSE302

GDM 5.0 User's Guide 356244635.doc V1.3

To install GDM, you will need:

If you wish to immediately proceed with the standard GDM installation,

GDM folders and files

GDM 5.0: GDM program

Protection: GDM protection management program

WMFConv: File converter for converting graphic files to WMF

DXFtoCSV: File converter for converting DXF files to CSV

GDM working folder

GDM 5.0 User's Guide 356244635.doc V1.3

The Product Code

Installing the protection

UG5.doc V1.3 GDM User's Guide 5.0

GDM\PROGRAM\product_code.690 folder when you install the protection, when you

Precautions after activating the protection

GDM 5.0 User's Guide 356244635.doc V1.3

Copying the software to your hard disk

Click on "Next" to display the license agreement:

GDM 5.0 User's Guide 356244635.doc V1.3

Click on "Next" once you have chosen the installation folder:

Select "Complete (standard) GDM station", then click on "Next":

UG5.doc V1.3 GDM User's Guide 5.0

Using the Windows Explorer, remove the existing protection's \GDM\Program\

You must now run the protection management program.

Installing the protection

GDM 5.0 User's Guide 356244635.doc V1.3

UG5.doc V1.3 GDM User's Guide 5.0

If you have an Internet

The following message is displayed:

Click on OK, then on "Exit" in the following dialog box.

Send file GDMWPROT.TXT to:

GDM 5.0 User's Guide 356244635.doc V1.3

Mr. Jacques BOBILLIER - BRGM - Orleans - France

Activating the protection

Enter your Activation Code (upper or lowercase):

UG5.doc V1.3 GDM User's Guide 5.0

Click on OK. The following message should then be displayed:

Comment: the confirmation code is not used.

Using GDM on a network

GDM 5.0 User's Guide 356244635.doc V1.3

Installing GDM on a client station

Specify the name of the installation folder on the client station:

Click on "Next" once you have chosen the installation folder.

UG5.doc V1.3 GDM User's Guide 5.0

Select "Client GDM station", then click on "Next":

Click on "Browse" and locate the GDM folder on the server:

GDM 5.0 User's Guide 356244635.doc V1.3

UG5.doc V1.3 GDM User's Guide 5.0