Aller au contenu

Drillhole Data Import

Overview

GENESIS can import drillhole data from:

  • GeoBase / Geotic databases
  • CSV flat files (multi-file workflow)
  • Excel
  • ODBC data sources

Import Drill Hole Data Source

After import, GENESIS will display import results (What’s Loaded) and validation.

Open Import Commands

  1. Go to the Home ribbon.
  2. In Hole Data, click Import.
  3. Select the source type.

Schema Behavior During Import

Schema handling is source-dependent:

  • If project schema is empty, GENESIS can build it from imported assay variables.
  • During GeoBase/Geotic import, users can choose which detected variables to add.
  • During CSV/Excel/ODBC imports, assay columns can extend schema when needed.

Import From GeoBase / Geotic

GeoBase and Geotic are Access based loggers applications. GENESIS can import drillhole data directly from these sources.

Typical flow:

  1. Choose the .mdb / .accdb file.
  2. Review import options in the loader dialog.
  3. Select variables to import.
  4. Run import.
  5. Review loaded summary and validation log.

Import From CSV (Multi-file)

CSV import is table-based and mapping-driven.

Typical flow:

  1. Select CSV files for each drillhole table.
  2. Detect/prepare schema from assay CSV.
  3. Map CSV columns to GENESIS table fields.
  4. Run import.

Important points:

  • Header/matching configuration is required for correct mapping.
  • Schema can be updated from detected assay columns.
  • Import settings are persisted for reuse.

Import From Excel

Excel import follows a similar mapping flow:

  1. Select workbook and table/sheet mapping.
  2. Detect assay variables and update schema.
  3. Map columns to GENESIS fields.
  4. Run import.

Import From ODBC

ODBC import supports external databases (Access, SQL Server, etc.) with proper drivers.

Typical flow:

  1. Configure connection and table mapping.
  2. Detect assay variables and update schema.
  3. Map source table to GENESIS tables.
  4. Map source columns to GENESIS fields.
  5. Run import.

Reimport

GENESIS supports one-click reimport using saved settings:

  • Reimport Excel using current settings
  • Reimport Database using current settings

Reimport runs with stored mappings and import properties, then refreshes drillhole data and display validation output.

Import options

  • Overwrite only: only overwrite existing records.
  • Append only: only add new non already existing records

Note:

A record is detected to exist if the holeName already exist. So all records with the same holeName will be overwritten in overwrite mode, and all records with a new holeName will be added in append mode.

If neither overwrite or append is selected, database will be cleared before import.

Matching Import column

When importing data, you will be prompted to match your source columns to the GENESIS table fields. This is a required step to ensure that your data is correctly mapped.

Simply Drag and drop each field from the source column list to the corresponding GENESIS field in the target table.

Matching Column

Only collars are strictly mandatory for a valid drillhole dataset, but complete workflows usually include additional tables.

Collars (mandatory)

Recommended minimum fields:

  • HoleName (unique)
  • X, Y, Z
  • Azimuth, Dip
  • Depth

Recommended minimum fields:

  • HoleName
  • Depth
  • Azimuth, Dip

Recommended minimum fields:

  • HoleName
  • From, To
  • One or more assay variables

Typical missing assay value default is -1

Other Optional Tables

Depending on project needs, GENESIS can also import tables such as:

  • Lithology
  • Mineralization / Alteration
  • RQD
  • Geochemistry
  • Structures
  • any other Custom tables

Wedge Data

GENESIS supports wedge import when required wedge metadata is provided.

Required wedge metadata:

  • Wedged From: parent hole name
  • Wedge Depth: depth where wedge starts in parent hole
  • Wedge Name: wedge hole identifier

Source-specific note:

  • In GeoBase, wedge table support is expected in source structure.
  • In Geotic, wedge-related information may require adding a dedicated table/fields.

Troubleshooting Checklist

If import does not produce expected results:

  • Confirm collars contain valid mandatory fields.
  • Verify table and column mapping in matching dialogs.
  • Check assay variables are detected and schema is not empty.
  • Review option overwrite/append modes.
  • Read validation output to fix source data issues.
  • Make sure source files are accessible and not opened and locked by another software