Import Formats (Wells)

In Insight, well data is read from the project database. Well data are loaded from Log ASCII Standard (LAS) (see Import a LAS file), checkshots, deviation and marker files into the database. You can load the wells into a session from the project database (see Loading Wells).

Prior to Insight 3.0, well data is saved in the .duwell file. Every well file in this format is linked to the components of LAS, checkshots, deviation and marker files. You can import the .duwell files into a session (see Importing a Legacy Well).

LAS file format

Each well should have a LAS file that stores the curve and log data of the well. Insight supports the LAS 2.0 (1992) file specification as defined by the Canadian Well Logging Society (CWLS). Read the full details of the LAS 2.0 specification. In addition, Insight also supports basic LAS 3.0 files, see the LAS 3.0 specification for more details.  To import, see Import a LAS file.

An example of a LAS file:

 VERS.                 2.0	: CWLS LOG ASCII STANDARD -VERSION 2.0
 WRAP.                 NO 	: ONE LINE PER DEPTH STEP
#MNEM.UNIT              DATA                   DESCRIPTION
#----- -----            ----------          ---------------------
STRT    .M              1670.0000            :START DEPTH
STOP    .M              1660.0000            :STOP DEPTH
STEP    .M              -0.1250              :STEP 
NULL    .               -999.25              :NULL VALUE
WELL    .       ANY ET AL 12-34-12-34        :WELL
FLD     .       WILDCAT                      :FIELD
LOC     .       12-34-12-34W5M               :LOCATION
PROV    .       ALBERTA                      :PROVINCE 
DATE    .       13-DEC-86                    :LOG DATE
UWI     .       100123401234W500             :UNIQUE WELL ID
#MNEM.UNIT            	API CODES               CURVE DESCRIPTION
#--------------       	-----------------     --------------------------------
 DEPT  .M                                  :  1  DEPTH
 DT    .US/M           60 520 32 00        :  2  SONIC TRANSIT TIME
 RHOB  .K/M3           45 350 01 00        :  3  BULK DENSITY
 NPHI  .V/V            42 890 00 00        :  4  NEUTRON POROSITY
 SFLU  .OHMM           07 220 04 00        :  5  SHALLOW RESISTIVITY
 SFLA  .OHMM           07 222 01 00        :  6  SHALLOW RESISTIVITY
 ILM   .OHMM           07 120 44 00        :  7  MEDIUM RESISTIVITY
 ILD   .OHMM           07 120 46 00        :  8  DEEP RESISTIVITY
#MNEM.UNIT              VALUE             DESCRIPTION
#--------------     ----------------      ------------------------
 MUD    .              GEL CHEM        :  MUD TYPE
 BHT    .DEGC          35.5000         :  BOTTOM HOLE TEMPERATURE
 BS     .MM            200.0000        :  BIT SIZE
 FD     .K/M3          1000.0000       :  FLUID DENSITY
 MATR   .              SAND            :  NEUTRON MATRIX
 MDEN   .              2710.0000       :  LOGGING MATRIX DENSITY
 RMF    .OHMM          0.2160          :  MUD FILTRATE RESISTIVITY
 DFD    .K/M3          1525.0000       :  DRILL FLUID DENSITY
Note: The logging tools became stuck at 625 metres causing the data between 
625 metres and 615 metres to be invalid.
~A  DEPTH    DT    RHOB      NPHI    SFLU    SFLA    ILM      ILD
1670.000  123.450 2550.000  0.450  123.450 123.450 110.200  105.600
1669.875  123.450 2550.000  0.450  123.450 123.450 110.200  105.600
1669.750  123.450 2550.000  0.450  123.450 123.450 110.200  105.600


For a checkshot file, each file must contain at least two columns with time-depth tie points along the well path. The typical columns in a checkshot file are:

  • TWT - Two-Way Time
  • OWT - One-Way Time
  • MDSS - Measured Depth Sub Sea
  • MDKB - Measured Depth using Kelly Bushing datum
  • MD - Measured Depth (assumed to be MDKB)

Tip: For a graphical representation of each column label, see Height datums and abbreviations in the FAQ section.

An example of a checkshot file:

Time-depth survey for Well-1
1210.00   1170.07
1710.00   1500.07
2210.00   1800.04
2700.00   2150.06
3200.00   2520.03
3730.00   2810.07
4000.00   2960.74

Note: Insight also supports checkshots in TWT-TVD pairs.

Deviation survey

Insight uses deviation surveys to display the deviated wells accurately. Each file must contain at least four columns to tie the measured depth, true vertical depth, X and Y locations.

Expected measured depth column labels are:

  • MDKB - Measured Depth using Kelly Bushing datum
  • MDSS - Measured Depth Sub Sea
  • MD - Measured Depth (assumed to be MDKB)

Expected true vertical depth column labels are:

  • TVDKB - True Vertical Depth from Kelly Bushing
  • TVDSS - True Vertical Depth to Sub Sea
  • TVDBML - True Vertical Depth Below Mud Line
  • TVD - True Vertical Depth (assumed to be TVDKB)

Tip: For a graphical representation of each column label, see Height datums and abbreviations in the FAQ section.

Expected labels for X and Y locations are:

  • X (or UTMX) - X coordinate of the tie point
  • Y (or UTMY) - Y coordinate of the tie point

An example of a deviation file:

Deviation survey for Well-1
    MDKB       TVDSS       X            Y
    0.00       -20.06      39844.56     24589.34
    1000.00    1020.02     39844.47     24588.95
    2000.00    1990.05     39845.82     24590.47
    3000.00    2980.00     39895.21     24524.15
    4000.00    3410.03     40453.486    23864.922
    5000.00    3910.05     41009.257    23219.492
    6000.00    4890.06     41036.517    23192.534


Marker data describes particular points that are labeled along the well path. Marker files must contain at least two columns:

  • Marker name - Name of the markers.
  • Marker depth - Depth of the markers.

An example of a well markers file:

Label                        MDKB                TVDSS
Ddav                         2678.270020         2648.768067
IMH                          2983.290039         2953.645907
TopM                         3178.310059         3148.710059
Sand_B5                      3239.729980         3210.129980
Sand_C5                      3316.330078         3286.727245
Sand_D5                      3482.729980         3452.929980
Sand_E5                      3618.370117         3588.470117

You can directly pick well markers and edit the markers data in Insight in the section view, well correlation window or the marker spreadsheet. Subsequently, you can save the changes you have made to the markers when you save the current session.

For more information, see Picking Well Markers, Displaying Well Correlation and Opening Marker Classification Sheet.

Import Markers using .tsv format

You can also import and export markers directly from the marker table as a .tsv or ‘tab-separated variable’ file (also known as a text tab delimited file). This file must be formatted with the correct header components for Insight to read it.

Example .tsv file with three markers and a header :

The bolded cells should not change; other fields should be filled using values for your project.

Note: importing well markers as a .tsv file will replace the existing table.

  1. Enable the Allow Changes checkbox.
  2. Right click on the markers table and select Import whole table from file.
  3. Browse the .tsv file and click Open.

Append markers using Copy and Paste

Append new markers to an existing table.

  1. Right click on the markers table and select Copy whole table to clipboard.
  2. Paste the data into a spreadsheet.

Note: Insight does not allow duplicate marker names. In the case of duplicates, it will use the last value in the table.

  1. Edit the table to include the new or edited markers.
  2. Select the entire table including header and copy onto the clipboard.
  3. Paste the edited table into Insight.
    • Enable the Allow Changes checkbox.
    • Right click and select Paste whole table from the clipboard.
  • Values in blue are modifiable.
  • Values in green are calculated from the well path.
  1. Save your session to commit the changes to the database.