Datamine Discover KB - Project Manager

Are drillhole HoleIDs case sensistive?

kbadmin — Wed, 05 Nov 2025 03:46:28 GMT

Yes Discover Drillhole tools was compare HoleID primary keys with case sensitive.

There is a validation option to check for Collar name mismatch, this will return any HoleID values which are not found in the Collar table, including case differences only.

It is recommonded to convert all HoleID field values to upper case to avoid issues.

When I go to setup or open a drillhole project, there is no Next or OK buttons at bottom of dialog

kbadmin — Sun, 02 Jun 2019 23:17:30 GMT

Occurrence

In Discover 2019, when I open to upgrade of Modify a drillhole project, there is no Next or OK bottom at bottom of the dialog. It is truncated.

Solution

This issue can occur on low resolution screens such as 1366x768.

This issue is resolved in the Discover 2019 Update. Note you will not be able to install this version if your screen is lower than 1366x768.

Error: Projection system is not supported

kbadmin — Mon, 22 Jan 2018 23:57:28 GMT

Occurrence

In Discover 2017, when I am opening or creating a drillhole projection, there is an error on the Collar table I selected, the tooltip says "Projection system is not supported".

Solution

This issue is will be resolved in Discover 2017 Update (MapInfo 17.0) and later.

Starting from Discover 2016, the Drillhole systems converts your original tab files into geopackage format, this is also available if you got o MapInfo HOME>Save Copy As and change the file type to geopackage.

This limitation of this format, mean it does not support -

1. Affine coordinate systems (the first number value is 100x or 300x)

2. Custom datums or 7 parameter datums (the second number value is >=999)

3. In addition, Latitude/Longitude projections are not supported in the drillhole module

Explicit bounded coordinate systems (the first number value is 200x or 300x) are also not supported, however these are not blocked as the bounds are simply dropped, which will result in some loss of precision.

To workaround, the drillhole collar table will need to be reprojected into a coordinate systems that does use these features.

How do I highlight different drillhole types on a section, such as Planned holes, or RAB vs RC vs DDH?

Josh Knight — Mon, 24 Mar 2014 01:51:27 GMT

Solution

A couple of tips that may assist you with the current version of Discover (v2013).

1/. To highlight 'Planned' holes.

In addition to adding the planned hole/s' collar (and survey entries if needed) information, add a single lithology entry for each planned hole to the lithology table, spanning it's entire depth (e.g. From 0 To 300). Assign an attribute such a 'Planned' to the appropriate lithology field. We'll be leveraging this via a lithology trace shade. When the updates are done, Save the changes, and 'Recache the Drillhole Project'.

In the projects 'lithology' legend (in the Legend Editor), add a new row, called 'Planned' and set a colour/pattern that stands out for planned holes (my example below is orange vertical stripes).

Then apply this to one or more sections. Example output as below:

2/. To separate drillholes by type

a. Add a 'Type' character field to your project's collar table, and attribute as necessary (such as 'RAB', 'RC' and 'Planned'). Save, and Recache the project.

b. Create 3 queries (I used Discover's Data Utilites>Select by Group) from this collar tab ...

Drillhole validation issues and how to resolve them

Josh Knight — Thu, 15 Dec 2011 04:52:43 GMT

Discover's new drillhole project Validation Tool (in version 2011) is a powerful and comprehensive error-checking facility, essential for problem-free section/plan generation and annotation.

This tool will consecutively check the project's collar, survey and downhole data tables as assigned during Project Setup. For each of these drillhole data types, the Validation tool will present both Compulsory (ticked and greyed out) and Optional (can be enabled by user) error checks. See Discover's interactive Help system for detailed use of this functionality.

Below are the Errors that may be listed by this tool, and their common causes and resolutions. The content of this article is also available as a PDF attachment for offline reference.

NOTES:

1. If using a database or shared dataset (e.g. read-only files on a server), it is strongly recommended to resolve all issues in the source dataset, not just on the user's local native MI Pro table copies.

2. All data changes should be first checked and verified against field logs/records.

3. Failure to resolve compulsory errors will cause or erroneous/misleading section displays.

Collar Validation report

Mismatched Collar Object (compulsory)

Cause - The spatial position of a collar (in the map window) does not match the values in the assigned collar easting/northing fields. The collar object may have been either:

Physically moved/edited, or

Occurrence

Often down-hole data is collected as point data located with a single depth field. Examples include structural measurements such as foliation and bedding observations, geophysical readings (e.g. magnetic susceptability), or water table depth.

Solution

This is resolved in new feature in Discover 2017 or later.

In older versions -
Discover's Drillhole module requires all downhole data tables to have both individual From and To depth columns. In order the handle point data correctly, simply duplicate the single Depth field into two identical data columns, both populated with the same values.

To accomplish this easily:

1/. Use Table>Maintenance>Table Structure to rename the Depth field to, for example, 'From'. Then also create a new float field called 'To'

2/. Use the Table>Update Column tool to populate the new 'To' field with the contents of the 'From' field.

I cannot select my Collar table

kbadmin — Fri, 06 Nov 2009 05:48:23 GMT
Occurrence

I have opened my Collar table file, and I am trying to create a new Drillhole Project, but I cannot select my collar table.

Solution

Simply use Table>Create Points, to create a map for the collar table firstly, and you will then be able to select it.

How can I make visible the X and Y fields for a mapped ODBC/DBMS table?

kbadmin — Wed, 23 Apr 2008 02:21:41 GMT

Occurrence

After making a ODBC/DBMS linked table mappable, the fields used to map the X and Y Coordinate are missing
or invisible from the browser window. This is blocking me from using it as a Collar table in a Drillhole project.

Solution

Alternatively, you can view the X and Y fields from the mapped table, by creating a duplicate field in the database and subsequently link via DBMS.

The best way to achieve this would be to make -
1) Query/virtual fields in the datbase, that are simply "=X" and "=Y".
2) A query of the table, and place two entries for the X and Y fields in the query. Subsequently, link the query table in MapInfo via DBMS.
When mapped, the extra X and Y fields will be visible in the browser window.