DLIS to CSV and Excel
Spreadsheets and scripts can't read DLIS, and a DLIS file rarely holds just one table: frames with different depth steps, repeat passes, time-indexed station data and image logs all live side by side. The converter writes each frame as its own table, so nothing is resampled or mixed up.
You get:
- One CSV per frame, with the depth (or time) in the first column and every curve after it.
The header row gives each column with its unit, for example
GR (gAPI)orRHOB (g/cm3). Choose the semicolon and decimal comma version if your Excel uses commas for decimals. - One Excel workbook per file with a summary sheet (well, field, company, service company, date, depth range and step of every frame), one sheet per frame with mnemonics and units in the first two rows, a sheet listing every curve with its minimum, maximum and mean, and a sheet with the well information, parameters, tools and remarks.
Empty samples are left blank in CSV and Excel (LAS uses -999.25), so averages and charts in Excel are not thrown off by placeholder values.
Array curves
Image logs and sector curves have several values per depth. In CSV and Excel they become one
column per value, numbered from 1: ROSI_01 to ROSI_16 for a 16-sector density image. Arrays
with more than 512 values per sample (waveforms) are left out of the tables and drawn as pictures
instead.
Large files
Files up to 2 GB are accepted, and several files or a ZIP can be converted in one go. Excel holds at most 1,048,576 rows per sheet; a longer frame is cut at the sheet limit in the workbook only, and the CSV and LAS files keep every sample.
Pitfalls
- Frames indexed by time (formation testers, coring tools) keep time in the first column; the depth is one of the other columns.
- Depth stored in tenths of an inch or millimetres is converted to feet or metres; the other curves keep the units of the file.
More about what this tool reads and writes: Well Log Converter (DLIS, LIS, LAS).