Release Notes
Oasis montaj 5.1.3
March 8, 2002
Click on the following for further information:
Wholeplot
Drillhole Plotting Upgrades
In response to suggestions from users an upgraded version of Geosoft’s Wholeplot Drillhole Plotting application is now available. This is the second phase of the Wholeplot upgrade. The following list provides an overview of some the new and upgraded features found in Oasis montaj 5.1.3.
New Oasis montaj 5.1.3 Wholeplot Features
QA/QC
- tests for collar, survey and assay data sets
- test on import and after import
- Collar data tests: Dummy East, North or RL; Duplicated locations; Reversed Easting/Northing; Dip out of range -90 to 90; Azimuth out of range -360 to 360; Dip sign discrepancy; Top of hole depth less than 0; Hole depth less than 0; Hole depth less than top of hole
- Dip-Azimuth survey tests: Dummy Depth; Depth less than hole top; Depth greater than hole bottom; Duplicated Depths; Out-of-sequence Depths; Dummy Dip or Azimuth; Dip out of range -90 to 90; Azimuth out of range -360 to 360; Dip sign discrepancy; Max curvature - degrees per meter
- From-To assay tests: Dummy From or To; From greater than To; From equals To; From or To less than hole top; From or To greater than hole bottom; Duplicated From-To intervals; Out-of-sequence intervals; Overlapping intervals; Missing intervals; Duplicated sample numbers
Masking/Selection Tools
- specify a mask channel to select individual intervals for plotting - integration with Chimera
- update selection from plan or section maps using polygon selection tool
- update selection based on rock code
- update selection based on numeric range
New! Wholeplot Strip log and Composite Tool
Strip log maps
- up to 16 data/graph type selections in each plot
- single-step plotting of single holes, selected holes, all holes, range of holes
- fixed scale plotting to one or more pages, or scale to fit to a single page
- top or side legend
Compositing tool
- works with strip log plots
- calculate and annotate composite intervals on up to five data selections at once
- multiple undo
- optional output of intervals to a text file
Upgraded Om5.1.2 Wholeplot Features
Section Plots
- pre-set vertical extent option
- improved automatic scaling, and scaling set using interactive selection from a map
- user preference for east or west-facing N-S sections
- Data Plotting to plan, section (or strip log) maps
- posting comments with text-wrap feature
- plot bars and profiles with no fill, pattern fill or corresponding rock patterns
- Logos can now be specified for the legends in plan, section or strip log maps.
"Current" X and Y channels
Prior to Oasis montaj 5.1.3, location information has always been stored in the "X" and "Y" channels. Many processes, including gridding, symbol plotting, etc., assume that "X" and "Y" channels exist, and will fail with an error message if they are not found in the current database. Whenever data was re-projected, or a warp applied, or a new set of coordinate channels was required, the original "X" and "Y" were backed up (usually to "__X" and "__Y" or similar), and then overwritten with the new values.
This system, though workable, had its drawbacks. For instance, many users would prefer "Easting" and "Northing" or "East" and "North" for the names of their locations. Also, when changing coordinates channels it could become difficult to remember where the original values resided in a database, and they might even become lost if multiple operations affecting the coordinate channels were performed. A second problem involved geochemists dealing with assay data sets. Often, these data sets involved numerous assay values for the various elements of the period table, including Yttrium, which, inconveniently, goes by the symbol "Y". To avoid overwriting locations stored in the coordinate "Y" channel, users were forced to rename the Yttrium channel to "Yt", which many, not surprisingly, objected to. Rather than attempt to get the world to accept a new version of the periodic table, we have introduced the concept of the "Current" X and Y channels into Oasis montaj 5.1.3.
Each database now remembers the two channels which are to considered as the "Current" X and Y channels. Any GX which looks for "X" or "Y" will now make use of these channels. By default the current X and Y are "X" and "Y", but the user, or a modified import function (such as now exists for Chimera and Wholeplot users in 5.1.3), can now denote other channels, such as "Easting" and "Northing" to be the current X and Y.
Now, if you select "Change X,Y coordinates..." in the "Coordinates" menu, instead of the GX creating backup copies of the existing X and Y, then copying the selected new coordinate channels into X and Y, the current X and Y channel settings for the database are simply renamed. No data is copied, no new channels are created, and no data need be backed up. From that point on, the newly specified channels will work with all existing GXs as if they were X and Y. Map-based cursor linking also works with the current X and Y channels.
To immediately identify to users which channels are currently being used as X and Y, small "x" and "y" icons have been added at the right side of the the channel title header cell in the database window. Those with existing databases will find that the "X" and "Y" channels have these indicators. If you select two other channels to be the current X and Y, the icons shift to them.
Users of Wholeplot and Chimera will find the first usage of the current X and Y channels. In Wholeplot in Om5.1.2, location information is now calculated and stored to the "DH_EAST", "DH_NORTH" and "DH_RL" channels, with the first two becoming the current X and Y channels for purposes of linking and plotting. (In fact "DH_RL" becomes the current "Z" channel and is also used in the linking). Users of Chimera will find that located data uses "East" and "North" instead of "X" and "Y".
Note: GX Developers should consult the GX Developer advances in Oasis montaj 5.1.3 for details on how to implement current X and Y channels in their GXs, and to see how it affects current GXs.
Loading and Deletion of Multiple Channels
Prior to Oasis montaj 5.1.3, in order to load a number of channels of those not currently displayed, a user had to right click on the channel header row, select "List...", select a single item from the list of available channels, then repeat this process for each additional channel. The functionality of this tool has now been upgraded to accept standard Windows-style multiple selections. "OK" and "Cancel" buttons have been added when the selection process is complete. To select a single channel, just double-click it. To select a range, click on the first and drag the cursor to the last. To add or remove a single channel in an already selected range, hold down the "Ctrl" key and click on the item.
To delete multiple channels in one step, select "Delete multiple channels..." from the same channel menu. After selecting the items, you will be prompted with a "are you sure" message before the channels are deleted from the database.
Setting projections on Import of Data
A new preference has been added to the Oasis montaj settings... If "Specify Projection on Import" is set to "Yes", then after using any one of the standard imports to a new database the projection wizard GX is run to let the user set up the projection for the data.
Colour Bars Refresh
In Oasis montaj 5.1.3, if you modify the colours for an image on a map using the colour image tool, the associated colour bar is automatically refreshed to match the new colour scheme. This is accomplished by calling the colour bar group's "Maker" to run the corresponding colour bar GX, so changes made with the map editor to the colour bar after its creation (e.g. moving, re-sizing) are lost.
New DAP Data now available
New! Kimberlite Indicator and Diamond Database (KIDD) and Kimberlite Indicator Mineral Chemistry Database (KIMC) datasets now available for download from the Geosoft DAP server for Oasis montaj 5.1.3.
top
"Current" X and Y channels
For an overview of this subject, first read the explanation under "New in Oasis montaj 5.1.3: "Current" X and Y channels.
For the vast majority of cases, all existing GXs will work seamlessly with the new "Current" X and Y channels. Here is why:
Normally, the channel symbols for the coordinate channels are obtained using commands such as the following:
XCh = FindSymb_DB(Data, "X", DB_SYMB_CHAN);
YCh = FindSymb_DB(Data,"Y", DB_SYMB_CHAN);
The FindSymb_DB function has been modified so that if it asks for "X", it will get whichever channel is defined as the current X channel. In the same way the iExistSymb_DB function has been modified, so that if it asks for "X", it will return TRUE (1) if a current X channel exists. If the requested channel is not given as "X" or "Y" the FindSymb_DB and iExistSymb_DB work exactly as before.
Setting and Getting the current X and Y channels
Several new functions have been introduced to set a specific channel to be the current X or Y channel, or to get the current X and Y channels. The following examples demonstrate their use:
SetXYZChanSymb_DB(Data, DB_CHAN_X, "Easting");
SetXYZChanSymb_DB(Data, DB_CHAN_Y, "Northing");
and
XCh = GetXYZChanSymb_DB(Data, DB_CHAN_X);
YCh = GetXYZChanSymb_DB(Data, DB_CHAN_Y);
The last two now have the same effect as
XCh = FindSymb_DB(Data, "X", DB_SYMB_CHAN);
YCh = FindSymb_DB(Data,"Y", DB_SYMB_CHAN);
For those working with 3-dimensional data, the concept extends to the current "Z" channel, accessed using the DB_CHAN_Z identifier.
The One Catch
One twist remains, however. What if a user has a "new" database with "East" and "North" as the current X and Y channels, and "Y" for Yttrium data? You can no longer use FindSymb_DB(Data, "Y", DB_SYMB_CHAN) or iExistSymb_DB(Data, "Y", DB_SYMB_CHAN) to get the Yttrium ("Y") channel, because it gets the location "North" channel. To handle this situation, two new functions have been created:
FindChan_DB works exactly like the old FindSymb_DB; you get exactly what you ask for. In addition, iExistChan_DB works exactly like the old iExistSymb_DB (only just for channels). They are used as follows:
AssayCh = FindSymb_DB(Data, "Y");
if(iExistChan_DB(Data, "Y"))
Again, unless you are writing GXs for situations where the current X and Y channels are NOT "X" and "Y", and there also exist "X" and "Y" channels separate from these which you need access to, it is not necessary to use these new functions. On the other hand, for general use, they save a few characters of typing over the original FindSymb_DB and iExistSymb_DB for access to non-coordinate channels.
New or Modified GX Functions
| GX Developer Function Additions |
Description |
| GetDataSetExtents_DAP: |
Get the full extents of a dataset. |
| RequestPointData_DAP: |
Request a random point dataset accross the DAP interface |
| hRequestConfig_DAP: |
Request the DAP Configuration Information. |
| UpdateConfig_DAP: |
Update the DAP Configuration Information. |
| SetServerStatus_DAP: |
Set the server online status |
| RequestServerStatus_DAP: |
Get the server online status |
| UpdateDataSetList_DAP: |
Update the list of datasets the server has |
| GetDataSetList_DAP: |
Get the list of datasets the server has |
| RequestAllInfo_DSEL: |
Request that all meta-data info be sent |
| MetaQuery_DSEL: |
Specify a metadata query string. |
| iExistChan_DB: |
Check if a channel exists. |
| FindChan_DB: |
Returns a Handle to the channel specified. |
| GetXYZChanSymb_DB: |
Searches for current X, Y or Z channel symbol |
| GetXYZChan_DB: |
Gets current X, Y or Z channel name |
| SetXYZChan_DB: |
Sets current X, Y or Z channel name |
| iIsAssociated_DB: |
Check to see if a channel is associated with group. |
| SetInfoMETA_DGW: |
This sets a text object to the text found in a META atrtribute. |
| GetInfoMETA_DGW: |
Copies the dialogue information to a META attribute. |
| hCollarDB_DH: |
Database for the collar table. |
| hCollarSymb_DH: |
Line/Group symbol for the collar table. |
| hDipAzSurveyDB_DH: |
Database for Dip-Azimuth survey data |
| hDipAzSurveySymb_DH: |
Line/Group symbol for a specific hole Dip-Azimuth survey. |
| hENSurveyDB_DH: |
Database for the East-North survey data |
| hENSurveySymb_DH: |
Line/Group symbol for a specific hole East-North survey. |
| iNumAssays_DH: |
Number of assay datasets. |
| hAssayDB_DH: |
Database for the assay data set. |
| hAssaySymb_DH: |
Line/Group symbol for a specific hole and assay dataset |
| ReSurveyEastNorth_DH: |
Resurvey an East-North-RL survey. |
| GetDataType_DH: |
Get the type of data in a Wholeplot database. |
| iModifyStripLogGUI_DH: |
Modify parameters for a strip log plot. |
| iCompositingToolGUI_DH: |
Annotate a strip log map using the compositing tool. |
| QACollar_DH: |
Do QA/QC on Hole Collar data. |
| QADipAzSurvey_DH: |
Do QA/QC on Dip/Az Survey data. |
| QAEastNorthSurvey_DH: |
Do QA/QC on East-North Survey data. |
| QAFromToData_DH: |
Do QA/QC on From/To data. |
| QAPointData_DH: |
Do QA/QC on Point data. |
| QADipAzCurvature_DH: |
Do QA/QC curvature checking on Dip-Azimuth Survey data. |
| QAEastNorthCurvature_DH: |
Do QA/QC curvature checking on East-North Survey data. |
| MaskPLY_DH: |
Set mask channel based on view selection polygon. |
| UnLoadDiscard_EDB: |
Unloads a database in the workspace, discards changes. |
| WriteDataViewBF_EDB: |
Write the View info from a BF into the database. |
| ReadDataViewBF_EDB: |
Retrieve view info from the database via a BF. |
| IImportChemDatabaseADO_GUI: |
Improved template creation for importing geochem database (ADO). |
| Create_HXYZ: |
Create an HXYZ object |
| iGenFileForm_GUI |
General file Open/Save Form for Multiple/Single file selections and multiple filter capability |
| iFileOpen_GUI |
Single selection file Open dialog |
| iFileSave_GUI |
Single selection file Open dialog |
| iMultiFileOpen_GUI |
Multiple selection file Open dialog |
| iMultiFileSave_GUI |
Multiple selection file Open dialog |
| Destroy_HXYZ: |
Destroys a HXYZ object. |
| GetMETA_HXYZ: |
Get the metadata of a grid. |
| SetMETA_HXYZ: |
Set the metadata of a grid. |
| hCreateSQL_HXYZ: |
Make an HXYZ from SQL Query |
| WinnowChanList2_IP: |
Same as WinnowChanList_IP, but removes current X,Y,Z. |
| Run2_KGRD |
Executes the Krigrid program directly on a database. |
| IGetObjName_META: |
Get the name of this item. |
| hGetNextItem_META: |
Count the number of items in a class |
| Meta_MVIEW: |
Store Metadata in a group |
| rArea_PLY: |
Area of a polygon |
| Thin_PLY: |
Thin polygons to a desired resolution |
| iClipPLY_PLY: |
Clip one polygon against another |
| iClipArea_PLY: |
Clip a polygon to an area |
| Run2_RGRD |
Executes the Rangrid program directly on a database. |
| Append_VA: |
Appends VAs |
| Reverse_VV: |
Reverses the order of the data in a VV |
| PolygonMask_VV: |
Mask a VV using XY data and a polygon |
| Spline2_VVU: |
Spline a Y VV onto an X VV at specified values of X. |
| OffsetCorrect2_VVU: |
Same as OffsetCorrect_VVU, but for arbitrary angle. |
top
| 10 |
Cannot load more than 2 omns using settings.gx. Internal buffer was not large enough to hold all the paths. Now it is. |
| 12 |
Unable to edit line number with colon characters. The Line number is Invalid. This occurred when a bug in an import created invalid line names. |
| 18 |
Abort importing GeoTiff |
| 19 |
Flight date information from contractor sometimes as DDMMYY or Date1 format but if the day is a single digit (1 to 9) the contractor leaves the date as DMMYY and the import fails. |
| 20 |
DEM from USGS gives error regarding DDF SDTS. This was actually not do with the grid import at all, but a rendering problem for the map! However, a problem in the error messaging itself deleted the wrong error message (one was registered because the SDTS tries twice to import the SDTS grids, using the old and new formats - it failed the first time, registering an error, but succeeded the second time. The first error should have been removed, but the rendering error was removed instead. This rendering error had to do with the 3rd party library used for displaying bitmaps in Oasis montaj. It has been corrected. |
| 31 |
Abort using basemap pdf file: maplpdf.gx |
| 35 |
The xyzstat.gx does not give all channel information when all 128 channels are filled with data. Line buffers weren't big enough to print out the information for this many channels. |
| 37 |
Map export to DXF noticeably reduces quality of vector file. Increased smooth line resolution for vector exports, which corrects an apparent loss of resolution when exporting smooth lines to DXF. |
| 46 |
Abort in Meta data when opening grid. |
| 56 |
warning message is required if a GDB or GWS is readonly. |
| 58 |
Allow ability to apply math expression or constant to new channel. Previously, you had to copy another channel to a new channel, then reset all the values at once. |
| 68 |
Abort caused by memory leak: hCreat_PROGSERVER |
| 69 |
Interactiv IP: pseudosection missing titleblock |
| 70 |
Fixed bug of drawing the grid outline with undesired 'loops' in it: gridply.gx |
| 71 |
Interactiv IP: IP pseudosection profile turned off means additional profiles are moved |
| 84 |
profile.gx: the profiles change in scale when using the log base |
| 88 |
Abort importing text file. Free_MP - impasc.gx |
| 89 |
Abort in Software Manager CDG_User::bIsChanged |
| 95 |
In the units.csv file (in 5.1.1 and 5.1.2) both ''mm'' and ''cm'' are listed as ''millimetre''. |
| 101 |
Abort using script which exports map (EXPMAP) as Mapinfo Tiff, CVU_MAP::sExportRaster |
| 118 |
Creating a comment channel only allows 60 characters width for channel display as well as posting the data on a map. |
| 130 |
Lookup1.gx: 2 table lookup format and error when using the TBL "line" type. The table now creates a 64 character string field for 'line' data and when the lookup is used the table is filtered to leave only those rows which match the current line. |
| 133 |
If you use the Edit/Edit ascii file, click on the [Editor], you will see what true editor is chosen. Users can be mislead when checking through the Edit/OASISmontaj settings which shows the editor to be notepad all the time. That is even when montaj is closed and reopened. |
| 141 |
Profile.gx: Plotting profile figure gives no decimal places in y-axis labels (gives whole numbers only). These numbers should be displayed with 1 decimal point less than the actual data. |
| 151 |
Chimera: Problems with auto converting negatives. |
| 152 |
splitline.gx: Errors when Line splitting on bad channel names, iExistSymb_DB : Invalid Line Name, Line Number is invalid |
| 153 |
Chimera: The chrose.gx, chpie.gx and chbar.gx can display all channels rather than what should be the assay channels only. |
| 156 |
Chimera: Autolink from correlation plot to scatterplot in Chimera not working |
| 161 |
Interactiv IP: IP Bug using the Interpex Zonge Inversion. If your data is in feet, then the inverted section grids still get created in meters, so they plot out of the proper section windows in the pseudo-section plot. |
| 164 |
Profile.gx: Not enough decimal places in the Y-axis labels |
| 165 |
Abort (sSetCommonMarkedAttrs_MGROUP) |
| 176 |
ASEG-GDF export produces bad dfn file. Should start with A4 before FLTLINE to allow for the 'DATA' characters in each line of data. Instead, the A4 appears before the data in the next row. |
| 177 |
Wholeplot: Wholeplot multiple horizontal slice gridded data only give single grid. All the slices get the same grid name, so it gets overwritten with each new slice. |
| 178 |
Packing map with shaded grid name greater than 18 chars. long gives bad colour |
| 180 |
GXF format error for Lambert Azimithul Equal Area, Mercator, Polyconic and Robinson projections. |
| 182 |
Chimera, Wholeplot: Error when importing MDB. "MFC could not initialize the Microsoft Jet database engine." |
| 183 |
abort with GridCopy.GX when importing a GXF (strcpy_GS) |
| 190 |
UX-Detect: Abort when using shadow-cursor-with-data-link on UXdetect grid wih digitized add targets |
| 191 |
UX-Detect Abort when clicking on a map UXO target in order to view the profile. |
| 192 |
Abort when using shadow-cursor-with-data-link on GDB. CDOC_Cell::sUpdateStat |
| 196 |
GX Developer: Both the Trend2_VVU and PolyFill2_VVU functions had errors in the wrappers which made them impossible to run. |
| 198 |
Interactiv-IP: Abort trying to do an inversion from IP data by using Zonge |
| 201 |
brkline GX: Abort breaking line in a GDB; CDOC_Cell::sUpdateStat |
| 202 |
Abort when exiting the program (Destr_SELSRV) |
| 204 |
Chimera: Grouping option for Symbols is now available in Chimera symbol options. |
| 205 |
Add POLYCONIC BRAZIL projection. |
| 213 |
Problems converting geosoft grids into landmark zmaps |
| 214 |
Error and abort linking GM-SYS models to Oasis. The error says: requested element (0) exceeds elements used (0) |
| 217 |
Abort when exiting montaj caused by simple memory bug. |
| 218 |
Abort while removing details from a duplicated grid. The Group edit tool crashed if you deleted a group and then immediately without selecting another group, clicked on any of the attributes. |
| 219 |
Abort closing Oasis montaj due to Memory Leak (hCreat_DBEXT) |
| 220 |
ArcGIS Desktop does not assume Rotation = 0:0:0.0 when ER Mapper (*.ers) file lacks Rotation line. |
| 223 |
If map is minimized and one uses GX that requires digitizing, map does not open for the process. |
| 225 |
Applications that create group names (like DXF import) should create a group name of the right size from the file name. |
| 230 |
Chimera: Assay import gives ASSAYS setting to all but the sample channel. |
| 233 |
UX-Detect: Cannot dynamically link to the Symbol group of Targets in UX-Detect after adding additional targets. |
| 237 |
Fixed to allow the parallel=0 when using the 'New Method' oprion in ipjset GX. |
| 238 |
Interactiv IP: Abort trying to create an Interpex Zonge Model. |
| 239 |
Error trying to import a dxf. Getting error "cannot set a font size to be <=0.0" because DXF file contains text with size 0 |
| 243 |
Wholeplot: abort creating section with old database |
| 247 |
Grid boolean operation miscalculation problem with SHORT grids. |
| 248 |
trenddb GX: Abort in Find Trends regarding "Window for Max-Min Search" length |
| 249 |
ASCII import: There was a limit of 4096 characters for line lengths and longer lines resulted in an abort. We have increased the maximum line length to 16384 characters and resolved the abort with an error. |
| 254 |
Wholeplot: when producing a section plot, the default thickness does not change from 0. |
| 255 |
ERMapper header file is being rewritten when opened in OM, resulting in the coord information being lost on displaying the grid. Corrected problem reading GEODETIC projection in an ERS file and then updating the ERS header. |
| 260 |
Interactiv IP: Abort while exporting IP data using ipxy.gx |
| 261 |
Interactiv IP: Order of Stacked section plots is wrong in an "Equal" section spacing |
| 267 |
Interactiv IP: The default installed psstak.con file has a bad line 17 |
| 268 |
Wholeplot: Using the tutorial data, if a section is created with the data channel "weathering" plotted as comments in orange text and Lith2 as posted text in black, then the Legend has some orange text and black text mixed togther. |
| 273 |
Abort trying to import a cg3 dataset through the Gravity menu. |
| 293 |
Grid header is not accepted by Geosoft. Cannot import grid. Error (the data for attribute "Axis rotation" of type "R8" contained a value of "Minimum" that violated the "" of "". ) |
| 315 |
Wholeplot: Import of assay.csv file resulting in error "Cannot use the sWriteDataAt_DB function on a compressed database." Writes the hole lines to gdb but no data. Occurred with compressed databases. Rewrote code to use different method. |
| 316 |
Wholeplot: Import of assay data to 5.1.2 Wholeplot results in data being not imported or deleted. |
| 322 |
Chimera: Elements not assigned as Assay class: chimplab.gx |
| 325 |
Wholeplot: Wholeplot legend The Assay box has mis-matched colours. |
| 328 |
Abort while opening a map because of an undefined 'edges' VV in the PLY object |
| 329 |
Interactiv IP: UXO shift correction problem and default oasis montaj opening folder. We had encountered problems with the offset algorithm when working with the USACE offset GX. |
| 331 |
Wholeplot: Section views are not in logical direction. It is standardized to always face north (positive) (west to the left - east to the right) and face east (positive) (north to the left - south to the right). Added user preference. |
| 353 |
Chimera: Standards report GX has debugging dialog: STR_TRIMBOTH - removed. |
| 359 |
Chimera:: When you import the survey.csv file for the Chimera tutorial, the ASCII wizard wants to start the import on line 33, instead of line 2. |
| 367 |
Chimera: When using CHCORREL.gx (ChemAnalyse - Correlations), to draw a correlation plot, the right column is squished (No matter how many channels are displayed) - A bug in the GX meant that data was not plotting with the log option set for the last column of plots. |
| 392 |
Airborne QC: QCPLAN gx. Get ' hGetResource_GXP(22622) GX using deleted or invalid handle. Fixed a bug due to using database handle after UnLock_EDB(). |
< back |