Import Interval Data

Two of the four import modes are for interval data — rows of depth-from / depth-to data that go into a data table. They differ only in whether the file covers one drillhole or many.

For the wizard’s general behaviour, see Import Overview. For collar/header imports, see Import Drillholes.

Prepare the file

A typical interval file has:

The depth columns are auto-detected by alias. The wizard recognises From, To, Depth_From, Depth_To, from_m, to_m, etc.

Things to check before import

• Hole ID matches existing names exactly (Bulk Domain only). DDH-001 ≠ DDH001 ≠ ddh-001. If they don’t match, the row is rejected. For new holes, run a Collar import first.
• Sort by depth. Rows display in creation/import order. A pre-sorted file gives you a tidy spreadsheet that matches geological order.
• Units. g/t, ppm, ppb — make sure the values match what your column expects. Numeric types don’t carry units; the only place units live is in your column name (e.g., au_g_t).
• Dropdown values match. If a column has dropdown options (e.g., rock_type with Granite, Basalt, …), source values must match exactly — including capitalisation. granite is rejected; Granite is fine.

Single Domain — one hole, one table

Use when you’re importing a single hole’s data into a single table.

1. Step 1 — Upload File. Drop the .csv or .xlsx.
2. Step 2 — Import Type. Choose Single Domain.
3. Step 3 — Pick Target. Select the drillhole and the data table. Both must already exist (use the Templates editor or Create a Drillhole to set them up first). Optionally create a new table on the fly here.
4. Step 4 — Map Columns. Drag or click to map source columns onto the table’s columns. The wizard pre-fills detected matches. Add new columns to the table if needed.
5. Step 5 — Import. Click Import. The summary shows imported, skipped, and error rows.

Bulk Domain — many holes, one table

Use when one file contains rows for many drillholes, distinguished by a Hole ID column.

1. Step 1 — Upload File. Drop the .csv or .xlsx.
2. Step 2 — Import Type. Choose Bulk Domain.
3. Step 3 — Pick Target. Select the data table. Confirm or change the auto-detected Hole ID column.
4. Step 4 — Map Columns. Map source columns to table columns. The Hole ID column is mapped automatically (you confirmed it in step 3).
5. Step 5 — Import. Click Import. Each row is routed to the drillhole whose name matches its Hole ID value.

What happens if a Hole ID doesn’t match

Rows whose Hole ID doesn’t correspond to any existing drillhole are rejected and listed in the errors panel of the import summary. They are not auto-created — for that, run Import Drillholes first.

After the import

Open one of the affected drillholes and confirm the rows appear in the target table — see Enter Interval Data. Run validation by clicking the error counter; if rules are tight, expect some warnings on imported data and clean them up — see Fix Validation Errors.

Imported data syncs to the cloud on the next sync cycle.

Duplicates

Re-importing a file creates duplicate rows — Blue Butterfly does not detect existing rows. To avoid duplicates, delete the existing data first, or trim the source file to only new rows. See Import Overview.

Common issues

“Hole ID column not detected.” The wizard looks for common aliases (HoleID, hole_id, DHID, DrillholeID). For unusual names, set the column manually in step 3.

“Many rows rejected for missing Hole ID match.” The Hole ID values in your file don’t match any existing drillhole names. Common causes: hole names with different formatting in your file vs the project, missing leading zeros (DDH-1 vs DDH-001), or holes you haven’t created yet. Run a Collar import first if needed.

Dropdown columns import as blank. Source values don’t match the dropdown options exactly. Open the column in Templates and confirm the option list, then standardise the source file.

Validation errors after import. Common — strict rules will reject some real-world data. Resolve as you would for typed-in data; see Fix Validation Errors.