Scua Gocad Import Exportpdf Compress

SKUA® and GOCAD® User Guide
Part II: Data Import and Export

© 1997–2012 Paradigm Ltd. or its affiliates and subsidiaries. All rights reserved.
The information in this document is subject to change without notice and should not be construed as a commitment by
Paradigm Ltd. or its affiliates and subsidiaries (collectively, "Paradigm"). Paradigm assumes no responsibility for any
errors that mayappear in this document.
The Copyright Act of the United States, Title 17 of the United States Code, Section 501 prohibits the reproduction or
transmission of Paradigm’s copyrighted material in any form or by any means, electronic or mechanical, including
photocopying and recording, or by any information storage and retrieval system without permission in writing from
Paradigm. Violators of this statute will be subject to civil and possible criminal liability. The infringing activity will be
enjoined and the infringing articles will be impounded. Violators will be personally liable for Paradigm’s actual damages
and any additional profits of the infringer, or statutory damages in the amount of up to $150,000 per infringement.
Paradigm will also seek all costs and attorney fees. In addition, any person who infringes this copyright willfully and for the
purpose of commercial advantage or private financial gain, or by the reproduction or distribution of one or more copies of
a copyrighted work with a total retail value of over $1,000 shall be punished under the criminal laws of the United States of
America, including fines and possible imprisonment.
The following are trademarks or registered trademarks of Paradigm Ltd. or its affiliates and subsidiaries
(collectively,"Paradigm") in the United States or in other countries: Paradigm, Paradigm logo, and/or other Paradigm
products referenced herein. For a complete list of Paradigm trademarks, visit our Web site at www.pdgm.com. All other
company or product names are the trademarks or registered trademarks of their respective holders.
Alea and Jacta software under license from TOTAL. All rights reserved.
Some components or processes may be licensed under one or more of U.S. Patent Numbers 5,570,106; 5,615,171;
6,765,570; and 6,690,820.
Some components or processes are patented by Paradigm and/or one or more of its affiliates under U.S. Patent Numbers
5,563,949; 5,629,904; 5,838,564; 5,892,732; 5,930,730; 6,055,482; 6,092,026; 6,430,508; 6,819,628; 6,820,043;
6,859,734; 6,873,913; 7,095,677; 7,123,258; 7,295,929; 7,295,930; 7,328,139; 7,561,922; 7,584,056; 7,711,532; and
7,844,402. In addition, there may be patent protection in other foreign jurisdictions for these and other Paradigm products.
All rights not expressly granted are reserved.
Third-party software notices are located at www.pdgm.com/thirdparty/.
Published October 10, 2012

Contents

Chapter 1 Importing Data.......................................................................................... 1-1
1.1 Converters and Supported Formats................................................................ 1-2
1.2 Basic Concept for Importing Data .................................................................. 1-6
1.3 Common Process for Importing a Column-Based File ...................................... 1-8
1.4 Importing Basin Modeling Files .....................................................................1-15
1.4.1 Import Temis/Medica Files ................................................................1-15
1.4.2 Importing MPath Files .....................................................................1-18
1.4.3 Importing a PetroMod File ...............................................................1-19
1.5 Importing Cultural Data ...............................................................................1-21
1.5.1 Importing an ArcView File ...............................................................1-21
1.5.2 Importing a DXF File ........................................................................1-22
1.5.3 Importing a SeisWorks Cultural Data File ..........................................1-22
1.6 Importing Fault Interpretations Data .............................................................1-23
1.6.1 Importing a CPS3 ASCII Data (.dat) File ...........................................1-24
1.6.2 Importing a CPS3 Binary File ............................................................1-25
1.6.3 Importing a Column-Based File ........................................................1-25
1.6.4 Importing a FastEdit Scattered Data File ...........................................1-25
1.6.5 Importing an XYZ File ......................................................................1-26
1.6.6 Importing a Charisma Fault Interpretations File .................................1-26
1.6.7 Importing a CPS3 ASCII Data (.dat) File ............................................1-27
1.6.8 Importing a CPS3 ASCII Polygons (.ply) File.......................................1-27
1.6.9 Importing a CPS3 ASCII Fault Traces (.flt) File ....................................1-27
1.6.10 Importing a CPS3 Binary File ............................................................1-27
1.6.11 Importing a Column-Based File ........................................................1-28
1.6.12 Importing a Petrel Pillars File ............................................................1-28
1.6.13 Importing a SeisWorks Fault Sticks File .............................................1-28
Contents iii
1.6.14 Importing a Z-MAP Fault or Contour File ........................................ 1-28
1.6.15 Importing a Charisma Fault Polygons File ........................................ 1-29
1.6.16 Importing a CPS3 ASCII Polygons (.ply) File ...................................... 1-29
1.6.17 Importing a FastEdit Fault Polygons File ........................................... 1-30
1.6.18 Importing an Irap RMS Fault Polygons or Lines File ........................... 1-30
1.6.19 Importing a SeisWorks Fault Polygon File ......................................... 1-30
1.7 Importing Fault Surfaces Data...................................................................... 1-31
1.7.1 Importing a CPS3 ASCII 2D-Grid (.grd) File....................................... 1-31
1.7.2 Importing a CPS3 Binary File ........................................................... 1-31
1.7.3 Importing a FastEdit 2D-Grid File ..................................................... 1-31
1.7.4 Importing an Irap RMS Triangle Surface File ..................................... 1-32
1.7.5 Importing a Petrel Pillars File ........................................................... 1-32
1.7.6 Importing a RC2 2D-Grid File .......................................................... 1-32
1.7.7 Importing a Z-MAP ASCII 2D-Grid File ............................................. 1-33
1.8 Importing Horizon Interpretations Data ........................................................ 1-34
1.8.1 Importing a Charisma Horizon Points File......................................... 1-34
1.8.2 Importing a CPS3 ASCII Data (.dat) File............................................ 1-35
1.8.4 Importing a Column-Based File ....................................................... 1-35
1.8.5 Importing a FastEdit Scattered Data File........................................... 1-35
1.8.6 Importing a GSLib 2D Map File........................................................ 1-35
1.8.7 Importing a SeisWorks Inline Xline X Y Z File.................................... 1-36
1.8.8 Importing an X, Y, Z File ................................................................. 1-36
1.8.9 Importing an Adobe Contours File................................................... 1-37
1.8.10 Importing a CPS3 ASCII Data (.dat) File............................................ 1-37
1.8.12 Importing a Column-Based File ....................................................... 1-37
1.8.13 Importing a FastEdit Horizon Contour File........................................ 1-37
1.8.14 Importing a Z-MAP Contour File ...................................................... 1-38
1.9 Importing Horizon Surface Data................................................................... 1-39
1.9.1 Importing a CPS3 ASCII 2D-Grid (GRD) File ...................................... 1-39
1.9.3 Importing a FastEdit 2D-Grid File ..................................................... 1-40
1.9.4 Importing a Geoprobe 2D Grid (.gvw) File ....................................... 1-40
1.9.5 Importing a GSLib 2D Map as Surface File ....................................... 1-40
1.9.6 Importing an Irap RMS ASCII 2D-Grid File ........................................ 1-40
1.9.7 Importing an Irap RMS ASCII 2D-Grid Property File ........................... 1-41
1.9.8 Importing a Norsar Horizons File ..................................................... 1-41
1.9.9 Importing an RC2 2D-Grid File ........................................................ 1-41
1.9.10 Importing a RESCUE Model File ....................................................... 1-42
1.9.11 Importing a Z-MAP ASCII 2D-Grid File ............................................. 1-42
1.9.12 Importing a Z-MAP ASCII 2D-Grid Property File ................................ 1-42
iv Contents SKUA® and GOCAD® – Paradigm™ 2011

With Epos® 4.1 Data Management
1.10 Importing Image Files...................................................................................1-43

1.11 Importing Reservoir Grid Data ......................................................................1-45
1.11.1 Importing an ECLIPSE ASCII Grid File ................................................1-46
1.11.2 Importing an ECLIPSE Binary Grid File ...............................................1-47
1.11.3 Importing a CMG Grid and Simulation Results ..................................1-54
1.11.4 Importing a RESCUE Model (Grids, Horizons, Faults) File ...................1-56
1.11.5 Importing a VIP ASCII Grid File .........................................................1-56
1.11.6 Importing a VIP or ECLIPSE LGR File .................................................1-57
1.11.7 Importing ECLIPSE ASCII Properties File ............................................1-58
1.11.8 Importing an I J K Property File ........................................................1-59
1.11.9 Importing a VIP ASCII Properties File ................................................1-60
1.11.10 Importing an ECLIPSE ASCII Faults File ..............................................1-61
1.12 Importing Seismic Data ................................................................................1-62
1.12.1 Importing a SEG-Y 3D File as Voxet ..................................................1-62
1.12.2 Importing a VoxelGeo File as a Voxet ...............................................1-68
1.12.3 Importing a 2D SEG-Y File ...............................................................1-68
1.12.4 Importing an SEP File.......................................................................1-71
1.12.5 Importing a Norsar Depth Cube File .................................................1-71
1.12.6 Importing a 2D SEG-Y File as Seismic Lines .......................................1-72
1.12.7 Importing a SeisWorks Colormap .....................................................1-72
1.13 Importing Velocity Data ...............................................................................1-73
1.13.1 Importing a Jason ASCII Traces File...................................................1-73
1.13.2 Importing a ProMAX File .................................................................1-73
1.13.3 Importing a TDQ (.avf) File ...............................................................1-74
1.13.4 Importing a Velf File ........................................................................1-74
1.13.5 Importing a SEG-Y 3D as Voxet File ..................................................1-74
1.13.6 Importing an SEP File.......................................................................1-74
1.13.7 Importing a VoxelGeo File................................................................1-74
1.13.8 Importing a 2D SEG-Y as Surface File ...............................................1-74
1.13.9 Importing a 2D SEG-Y as SGrid File ..................................................1-75
1.14 Importing Well Data ....................................................................................1-76
1.14.1 Importing Well Paths and Logs.........................................................1-76
Importing a Column-Based File ........................................................1-76
Importing a CPS3 ASCII Data (.dat) File ............................................1-76
Importing an Excel File ....................................................................1-77
Importing an Irap RMS File ..............................................................1-78
Importing an LAS File ......................................................................1-79
Importing an RC2 File......................................................................1-84
Importing a Temis3D File .................................................................1-84
Importing a WITSML File..................................................................1-85
User Guide Contents v

1.14.2 Importing Well Paths ...................................................................... 1-86
Importing a Column-Based File ....................................................... 1-86
Importing an X Y Z File ................................................................... 1-86
Importing Coordinates from a Column-Based File ............................ 1-86
1.14.3 Importing Well Marker Data from a Column-Based File .................... 1-86
1.14.4 Importing Well Log Data ................................................................. 1-87
Importing Log Data from Column-Based File .................................... 1-87
Importing Log Data from an LAS File ............................................... 1-87
Importing Log Data from an ASCII File with a Header ....................... 1-88
1.14.5 Importing Well Symbol Data ........................................................... 1-89
1.14.6 Importing Well Completion Data ..................................................... 1-90
1.14.7 Importing Well Production Data ...................................................... 1-91
Importing Well Production Data from a General Format User File or
VOL File ......................................................................................... 1-91
Importing Well Production Data from an ECLIPSE Column-Based File 1-97
Importing Well Production Data from an ECLIPSE Binary File ........... 1-101
Importing Well Production Data from an ECLIPSE RSM File ............. 1-102
1.15 Importing Cross Section Data .................................................................... 1-104
1.15.1 Importing a DXF File ..................................................................... 1-104
1.15.2 Importing a GeoSec Cross Section File ........................................... 1-104
1.15.3 Importing a Locace File ................................................................. 1-104
Chapter 2 Exporting Data ......................................................................................... 2-1

2.1 Converters.................................................................................................... 2-2
2.2 Basic Procedures for Exporting Data ............................................................... 2-4
2.2.1 Exporting an Object to a Custom ASCII File ....................................... 2-5
2.2.2 Exporting an Object to a DFX File ...................................................... 2-7
2.2.3 Exporting Object Properties to Excel .................................................. 2-7
2.2.4 Exporting an Object to an Isatis File................................................. 2-12
2.2.5 Exporting Curves or 2D Grids to a Medica File ................................. 2-16
2.2.6 Exporting Velocity Data to an AVF File ............................................. 2-17
2.2.7 Exporting Velocity Data to a Velf File ............................................... 2-18
2.3 Exporting PointsSet Data ............................................................................. 2-19
2.4 Exporting Curve Data .................................................................................. 2-20
2.4.1 Exporting a Curve to a FastEdit Fault Polygon File ............................ 2-20
2.4.2 Exporting a Curve to an IRAP File .................................................... 2-21
2.4.3 Exporting a Curve to a SeisWorks Fault Sticks File ............................ 2-21
2.4.4 Exporting a Curve to a Z-MAP Faults File ......................................... 2-22
2.4.5 Exporting a Curve to a Z-MAP Contours File .................................... 2-23
2.5 Exporting Surface Data ............................................................................... 2-24
2.5.1 Exporting a Surface to a CUBIT Facet File......................................... 2-24
2.5.2 Exporting a Surface to a FastEdit File ............................................... 2-25
vi Contents SKUA® and GOCAD® – Paradigm™ 2011

2.5.3 Exporting a Surface to an IRAP File ..................................................2-26

2.5.4 Exporting a Surface to a GMI WellCheck MohrFracs File ....................2-26
2.6 Exporting 2D-Grid Data................................................................................2-28
2.6.1 Exporting a 2D-Grid to a CPS3 File ...................................................2-28
2.6.2 Exporting a 2D-Grid to a FastEdit File ...............................................2-29
2.6.3 Exporting 2D-Grid Data to an IRAP File.............................................2-29
2.6.4 Exporting 2D-Grid Data to a Z-MAP File ...........................................2-30
2.7 Exporting Voxet Data ...................................................................................2-31
2.7.1 Exporting a Voxet to a DDS File........................................................2-31
2.7.2 Exporting a Voxet to a SEG-Y File .....................................................2-32
2.7.3 Exporting a Voxet to an SEP File .......................................................2-33
2.7.4 Exporting a Voxet to a VoxelGeo File ................................................2-34
2.8 Exporting Seismic Line Data .........................................................................2-35
2.9 Exporting SGrid Data ...................................................................................2-36
2.9.1 About the Grid Origin .....................................................................2-37
2.9.2 Exporting an SGrid to a CMG File ....................................................2-38
2.9.3 Exporting an SGrid to an ECLIPSE ASCII File ......................................2-43
2.9.4 Exporting an SGrid to an ECLIPSE Binary File.....................................2-51
2.9.5 Exporting an SGrid to a RESCUE File ................................................2-53
2.9.6 Exporting an SGrid to a VIP File........................................................2-54
2.9.7 Exporting an SGrid to a Temis3D (libnf) File ......................................2-59
2.9.8 Exporting LGR Data from an SGrid to a Flow Simulator .....................2-59
2.10 Exporting Well Data .....................................................................................2-64
2.10.1 Exporting a Well to an IRAP File .......................................................2-64
2.10.2 Exporting a Well to an LAS File ........................................................2-65
2.10.3 Exporting Well Markers to an ASCII File............................................2-66
2.10.4 Exporting Well Logs to an ASCII File .................................................2-67
2.11 Exporting a View as an Image ......................................................................2-68
2.11.1 Exporting a View to a CGM File .......................................................2-68
2.11.2 Exporting a View to an Image File ....................................................2-70
2.11.3 Exporting a 3D Viewer Image to a VRML File ....................................2-71
2.12 Exporting an SGrid and Data to an Isatis File .................................................2-73
Appendix A Import File Formats .................................................................................. A-1

A.1 Import File Formats ....................................................................................... A-2
A.2 Column-Based Formats ................................................................................. A-4
A.3 CMG Formats ............................................................................................... A-5
A.4 CPS3 Formats ............................................................................................... A-6
A.5 ECLIPSE Formats ......................................................................................... A-12
A.6 FastEdit Formats ......................................................................................... A-14
A.7 Irap RMS Formats ....................................................................................... A-16
A.8 LAS Format ................................................................................................ A-20
User Guide Contents vii

A.9 MPath Formats ........................................................................................... A-22
A.10 SEG-Y Formats............................................................................................ A-26
A.11 SEP Format ................................................................................................. A-28
A.12 Velf Format................................................................................................. A-29
A.13 XYZ Format ................................................................................................ A-30
A.14 Z-MAP Formats ........................................................................................... A-31
A.15 VIP Formats ................................................................................................ A-33
viii Contents SKUA® and GOCAD® – Paradigm™ 2011

1
Importing Data
In this chapter • "Converters and Supported Formats," • "Importing Horizon Interpretations

page 1-2 Data," page 1-34
• "Basic Concept for Importing Data," • "Importing Horizon Surface Data,"
page 1-6 page 1-39
• "Common Process for Importing a • "Importing Image Files," page 1-43
Column-Based File," page 1-8
• "Importing Reservoir Grid Data,"
• "Importing Basin Modeling Files," page 1-45
page 1-15
• "Importing Seismic Data," page 1-62
• "Importing Cultural Data," page 1-21
• "Importing Velocity Data," page 1-73
• "Importing Fault Interpretations
Data," page 1-23 • "Importing Well Data," page 1-76
• "Importing Fault Surfaces Data," • "Importing Cross Section Data,"

page 1-31 page 1-104
Overview In Paradigm™ SKUA ® and Paradigm™ GOCAD ® , you can import many types of data
from numerous external sources. For example, you can import data in the form of industry
standard formats, raw data, and many formats from other software products. When you
import data, you can:
• Create a modeling object.
• Overwrite an existing object.
• Add property data to an existing object.
• Overwrite property data in an existing object.
You can find the importing commands from the File menu on the Import submenu. This
submenu is organized first by the categories of data you can import and then by the
supported programs or data types.
These topics explain how to import the related files and identify the objects that you can
create from the imported files.
Paradigm adds support for new formats based on client need. To inquire about new
options, contact us at: www.pdgm.com/support.
1-1
Before you begin The validity and accuracy of the data in your file determines the success of what you
import. Therefore, ensure that all files you want to import contain valid data and are in
the correct format. Reviewing ASCII files in an editor, like Notepad, before importing is a
good idea.
Appendix A, "Import File Formats," identifies the import formats that SKUA and GOCAD
support and describes how the converters read the files.
1.1 Converters and Supported Formats

Table 1–1 identifies the kind of data you can import, the programs or data types, the file
name extensions, and objects created from the imported data.
Note The Irap RMS converter supports RMS versions up to version 2009.
Table 1–1 Converters and

If you want to
resulting objects In this data format (or from With this common You can create
import this
this program) extension these objects
type of data
Basin Modeling Medica Fault Polygons .fau Curve
Medica Topographic Surface .g Surface
Medica Topographic Surface .g PointsSet, 2D Grid,
Advanced Surface, Voxet, SGrid
Temis3D Grid .td4 SGrid
Temis3D Colormap Colormap
MPath .act, .fid, .raw, .par PointsSet, Voxet
PetroMod .pmb
Cultural data ArcView .dbf, .shp, and .shx PointsSet, Curve
AutoCAD .dxf PointsSet, Curve, Surface
Seisworks cultural data .asc Curve
Digital Elevation Model (DEM) .ers DEM
ER Mapper 1
DEM binary1 DEM
Fault CPS3 ASCII data .dat PointsSet
interpretation - CPS3 ASCII polygons .ply PointsSet
points
CPS3 ASCII fault traces .flt PointsSet
CPS3 binary .svd PointsSet
Column-based file User defined PointsSet
FastEdit scattered data .dat PointsSet
XYZ User defined PointsSet
Fault Charisma fault interpretations Curve
interpretation - CPS3 ASCII data .dat Curve
fault sticks
CPS3 ASCII polygon .ply Curve
CPS3 ASCII fault traces .flt Curve
CPS3 binary .svd Curve
Column-based file User defined Curve
Petrel pillars .dat Curve
Seisworks fault sticks .dat Curve
Z-MAP fault or contour Curve
(Continued 1 of 4)
1-2 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

If you want to
In this data format (or from With this common You can create
import this
type of data
Fault Charisma fault polygons Curve
interpretation - CPS3 ASCII polygons .ply Curve
fault polygons or
traces FastEdit fault polygons Curve
Irap RMS fault polygons or lines Curve
SeisWorks fault polygons Curve
Fault surfaces CPS3 ASCII 2D-Grid .grd Surface
CPS3 binary .svd, .svs, .svf, .svp Surface
FastEdit 2D grid .dat Surface
Irap RMS triangle surface .dat Surface
Petrel pillars .dat Surface
RC2 2D grid .gz Surface
RESCUE .bin Surface
StrataModel 2D grid .smg Surface
Z-MAP ASCII 2D grid Surface
Horizon Charisma horizon points .gridexp PointsSet
interpretation - CPS3 ASCII data .dat PointsSet
points
CPS3 binary .svd PointsSet
Column-based file PointsSet
FastEdit scattered data .dat PointsSet
GSLib 2D map PointsSet
Seisworks Inline Xline X Y Z .asc PointsSet
XYZ User defined PointsSet
Horizon Adobe contours .esp Curve
interpretation - CPS3 ASCII data .dat Curve
contours
CPS3 binary .svf, .svp Curve
Column-based file User defined Curve
FastEdit horizon contours .dat Curve
Z-MAP contour .zmap Curve
Horizon surfaces CPS3 ASCII 2D grid .grd 2D Grid
CPS3 binary .svd, .svs, .svf, .svp 2D Grid
FastEdit 2D grid .dat PointsSet, Curve, 2D Grid
Geoprobe 2D grid .gvw 2D Grid
GSLib 2D map Surface
Irap RMS ASCII 2D-grid property 2D Grid properties
Norsar horizons Voxet
RC2 2D grid .gz 2D Grid
RESCUE .bin Surface
StrataModel 2D grid .smg 2D Grid
StrataModel 2D grid property .smg 2D Grid properties
Z-MAP ASCII 2D grid 2D Grid
Z-MAP ASCII 2D grid property 2D Grid properties
Images Images 2D Grid
(Continued 2 of 4)
User Guide 1.1 Converters and Supported Formats 1-3

If you want to
import this
type of data
Reservoir grid ECLIPSE ASCII grid .grdecl SGrid
ECLIPSE binary grid .grid, .egrid, .init, SGrid
.unrst
RESCUE (grids, horizons, faults) .bin SGrid
VIP ASCII grid .cor SGrid
VIP LGR .lgr SGrid
Reservoir grid - ECLIPSE ASCII properties .grdecl SGrid properties
properties I J K property SGrid properties
VIP ASCII properties .cor SGrid properties
ECLIPSE ASCII faults SGrid
Reservoir grid - CMG IMEX grid properties .irf, .IRF SGrid and properties,
simulation results wells and properties
ECLIPSE RSM file .rsm SGrid and properties,
wells and properties
ECLIPSE binary grid .GRID, .grid, SGrid and properties
.EGRID, .egrid,
.GRD
ECLIPSE column-based user file SGrid and properties,
Column-based file User defined SGrid and properties,
Seismic data - SEG-Y 3D as voxet .sgy, .segy Voxet
cubes VoxelGeo .vol Voxet
SEP .h Voxet
Norsar depth cube Voxet
Seismic data - 2D SEG-Y as SeismicLine .sgy, .segy SeismicLine
lines
Seismic data - SeisWorks .clr Colormap
color maps
Velocity functions Jason ASCII traces Curve with velocity
(Jason Geoscience Workbench) properties
Promax
TDQ .avf
Velf .velf Curve
Velocity cubes SEG-Y 3D as voxet .sgy, .segy Voxet
SEP .h Voxet
VoxelGeo .vol 2D Grid
Velocity lines 2D SEG-Y as SeismicLine .sgy, .segy SeismicLine
Well data - Column-based file User defined Well
path and logs CPS3 ASCII data .dat Well
Excel .xls Well
Irap RMS .log, .decode Well
LAS .las Well
RC2 .gz, .asc, .out Well
Temis3D Well
WITSML .gz, .xml Well
(Continued 3 of 4)

If you want to
import this
type of data
Well data - path Columns-based file User defined Well
X Y Z file User defined Well
Locations from column-based file Well

Well data - Column-based file User defined Well
markers
Well data - logs Column-based file User defined Well
LAS .las Well
ASCII file with header Well
Completion Well
Well data - Well status symbols Well
Symbols
Well data - ECLIPSE DATA file .DATA, .data Well
Completion data Column-based file User defined Well
Well data - ECLIPSE binary files Well properties
Production data ECLIPSE RSM file Well properties
ECLIPSE column-based user file Well properties
Column-based file User defined Well properties
Cross sections DXF .dxf PointsSet, Curve, or
Surface
Paradigm™ Geosec® .ihf Curve or PointsSet
Locace .ext Curve
Dip data1 Dip ASCII file with header Dip
Dip column-based file Dip
(Continued 4 of 4)
1. Importing a DEM or Dip data requires the Structural Analysis (Kine3D-1) module. For more information
about importing a DEM or Dip, see Part VII: Geologic Interpretation, "Importing a DEM" on page 4-13
or "Importing Dip Data" on page 4-30.
User Guide 1.1 Converters and Supported Formats 1-5

1.2 Basic Concept for Importing Data
For each importing command requires, you need to enter various options that the
converter needs to quickly and accurately import your data files. Some commands require
only basic information, such as the name of the file that contains your data, while other
require more detailed data.
This section explains the basic importing procedure and the remaining sections in this
chapter explain detailed procedures for specific converters.
Important When you import a file to create an object, the name of the new object is the
same name as the import file, without the extension. With the exception that the
commands comply with the SKUA and GOCAD naming conventions. If you import a file
that does not follow the naming conventions, the import command renames the file. For
example, an asterisk (*) is not allowed as a part of the file name. If your file is named
W1*1, the command renames the file as W1_1. For more information about naming
conventions, see Part I: Getting Started, "Naming Objects and Other Items" on page 3-9.
Basic procedure for 1 Select File > Import, point to the data type, and then click the appropriate
importing command. The dialog box for the specific command opens.
For example:
2 Click to open the Select Text File dialog box, browse for the file you want to
import, and then double-click the file name.
– or –
In the File name box, type the full path and file name.

3 To set the units indicating how the file is to be imported, click Advanced, and then
do any of the following:
a If the z-axis value in the file you are importing differs from the default z-axis set
for your project, change the domain for this new object. To change the z-axis
value from depth to time, or time to depth click the appropriate option.
Note SKUA or GOCAD automatically selects units based on the default z-axis setting (in
the New Project dialog box) chosen when the project was created.
b If the units in the file differ from the default units set for your project, select the
Specify Units of Selected File check box, and then click the appropriate units.
For information about setting units for your project, see Part I: Getting Started,
"Setting Units for a Project" on page 1-19.
4 Click OK or Apply.
User Guide 1.2 Basic Concept for Importing Data 1-7

1.3 Common Process for Importing a
Column-Based File
You can use the column-based import wizards to import ASCII files for multiple types of
data. Depending on the data in your files, you can create objects such as PointsSets,
Curves, and Wells, and many types of object properties.
For more information about the types of data that you can import and objects you can
create from data in this format, see "Converters and Supported Formats" on page 1-2.
For most column-based data, you can:
• Import all or only a portion of a file
• Import property data
• Specify a name for new objects (rather than automatically assigning a name or
reading the name from the file)
For point set or curve data, the import wizards create an object from each file that you
import. However, for well data, the wizard creates a Well object for each well identified in
the file.
The importing process is similar for most of the column-based importing wizards. The
following describes the general procedure. Where you encounter differences from this
procedure, follow the instructions in the wizard.
Note You can import certain types of data only if you load specific modules with SKUA or GOCAD.
For information about data that you can import with a particular module, see the topics that
describe the module.
For more information about common settings in column-based import wizards, see:
• "To access a column-based importing wizard," page 1-8
• "To specify the file type for a column-based file," page 1-9
• "Tips for specifying the data type for a column-based file," page 1-10
• "To specify the column separation for a column-based file," page 1-11
• "To specify miscellaneous information for a column-based file," page 1-12
• "To specify the column assignment for a column-based file," page 1-12
• "To complete the importing process," page 1-14
For information about specifying additional settings for well production data and time-
dependent grid properties, see:
• "Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97
• "Importing Well Production Data from a General Format User File or VOL File,"
page 1-91
To access a column-  Select File > Import, and then do one of the following to access the wizard.
based importing
wizard And create
To import this data Select
this object
Fault interpretations PointsSet Fault Interpretations > PointsSet > Column-
based file.
Horizon interpretations PointsSet Horizon Interpretations > PointsSet > Column-
based file.
Fault interpretations, fault Curve Fault Interpretations > Fault Sticks > Column-
sticks based file.
Horizon interpretations, Curve Horizon Interpretations > Contours > Column-
contours based file.

And create
To import this data Select
this object
Well data (X, Y, MD, TVDSS) Well Well Data > Path > Path and Logs > Markers,
Logs, or Completion Data (depending upon the
type of data in the file) > Column-based file.
Well production data Wells Well Data > Production Data > ECLIPSE User
File (column-based) or General Format User File
(column-based).
Figure 1–1 Wizard for importing fault interpretations as a point set
To specify the file In column-based importing wizards, File type is the first page in most wizards. Select the
type for a column- data file and specify the data type as follows:
based file
1 Type the path and file name or click , browse for the file or files that you want to
import, and then double-click the selected files.
Note In this step, you can select multiple files to import. All of the files that you select appear
in the Current file list. Settings that you make for one apply to all of the files in the list. Later,
you have the option to import them all with the same settings or import them one at a time,
adjusting the settings for each file.
Tip If the data is not what 2 The wizard automatically previews the first 400 lines of the file. If you want to see
you expect, click Cancel. more than 400 lines, click Preload all to preview the entire file.
You can select a different file
and then begin the import 3 If the width of each column in the file is a fixed number of characters, click Fixed
procedure again, or edit the width.
file in a text editor.
Otherwise, if the data is separated by specific characters such as commas, spaces,
tabs, semi-colons, or other characters, leave the Delimited setting.
User Guide 1.3 Common Process for Importing a Column-Based File 1-9
For more information, see "Tips for specifying the data type for a column-based file"
on page 1-10.
4 Click Next.
Tips for specifying When you import ASCII data by using a column-based import wizard, ensure that you
the data type for a specify the correct data type, either Delimited (the preselected setting) or Fixed width.
column-based file You can find this setting on the File type page (first page in most column-based wizards).
You can check for the following scenarios to help determine which setting to select:
• With the Delimited setting, if there are empty lines in the column headings, the
wizard will misalign the headings. For example:
Original data:
DATE FPRH FWPRH FGPRH FOPRH
barsa sm^3/d sm^3/d sm^3/d
FIELD FIELD FIELD FIELD
1/1/1988 397.802 0.0000 0.0 0.00
1/1/1989 307.55 0.0000 1356750.0 9000.00
1/1/1990 233.713 0.0000 1217807.5 9000.00
Misaligned data:
In this data, lines 2 and 3 in the "Date" column heading are empty, and the wizard
aligns the data as follows:
DATE FPRH FWPRH FGPRH FOPRH
barsa sm^3/d sm^3/d sm^3/d
FIELD FIELD FIELD FIELD
1/1/1988 397.802 0.0000 0.0 0.00
1/1/1989 307.55 0.0000 1356750.0 9000.00
1/1/1990 233.713 0.0000 1217807.5 9000.00
In this case, specify Fixed width instead.
• With the Delimited setting, when you advance to the next page of the wizard
(Column Separation) and select delimiters, the columns should be highlighted with
alternate colors. For example:
If the columns are not selected as shown, return to the previous page and select
Fixed width instead.
If you select Fixed width, when you advance to the next page in the wizard, you can
delineate the columns based on fixed field width.

To specify the column In column-based import wizards, the Column Separation page previews the column
separation for a structure of the file. Yellow highlighting appears in alternate columns.
column-based file
Figure 1–2 Column

separation for delimited
fault interpretation data
1 Specify the column separation by doing one of the following depending on the data
type:
For this data type Do this

Delimited 1 Select one or more of the check boxes: Tab, Semicolon, Comma,
Space, and Other. Tab and space are preselected.
Note You can select as many delimiters as needed.
2 If you select Other, type the delimiter in the box.
3 To specify a character that separates text from the data, select the
character in the Text qualifier box: double quotation mark, single
quotation mark, or none.
4 If the file contains comments, in the Comment string box, type the
characters that identify comment text. For example, in a 3DSL file, the
percent character (%) indicates a comment.
Fixed width Specify column breaks by clicking within the preview pane to add a column
break or double-clicking a break to remove it.
2 Click Next.
Note In the production data importing wizards, the next pages are specific to production data. For
information about these pages, see:
• "Importing Well Production Data from a General Format User File or VOL File," page 1-91
To specify In the column-based importing wizards, the Miscellaneous information page (see
miscellaneous example, Figure 1–3) presents a series of questions, one at a time. The questions vary
information for a depending on the type of object data you are importing. Follow the instructions in the
column-based file wizard to answer the questions.
Note Not all column-based importing wizards include this page. You can skip this section if you do
not see this page.
Figure 1–3 Miscellaneous information for fault interpretation data
1 To answer a question click Yes, No, or another option if a question has other options.
The area to the left of the questions presents additional information to help you
answer the questions.
2 When you finish answering all of the questions, click Next.
Note In the example shown,
• If there is no x-, y-, or z-column in the file, the wizard automatically assigns a value of zero for
that coordinate.
• If there is an x-, y-, or z-column, on the next page of the wizard, you need to specify the
location of this data in the file.
To specify the column In the column-based importing wizards, if items (such as x-, y-, or z-coordinates or the
assignment for a object name) are given in specific columns in the file, on the Column assignment page
column-based file (see example, Figure 1–4), you need to specify the location of the items in the file.
Note This page is not exactly the same in all column-based import wizards, and not all wizards
include this page. Where you encounter differences, follow the instructions in the wizard.

Figure 1–4 Column assignment for fault interpretation data
1 Depending on the option selected on the previous page (under To name the
objects), you may type a name for the new object in the Object name box, select a
column, or use the file name.
2 In the Start at line box, type the line number or click and pick the line number
where you want the converter to start reading the file. Do the same to identify the
line number where you want the converter to stop reading the file in the End at line
box. The defaults are (1,0) which means read the entire file. (Zero means end-of-file.)
3 Specify the column location for identified properties and parameters. Highlight the
value in the Property List and parameters box and then enter the column location
number in the Column number box.
4 To add a property or parameter:
a Click Add, type the name (any name you want) in the New Property Name box,
and then click OK.
b Select the property or parameter in the list, and then enter the column location
number in the Column number box.
The wizard will add the property in your file to the existing object.
5 To remove a property, select the name in the Property List and parameters box and
then click Remove.
6 If you want the wizard to read a specific value as a no-data value (a number always
read as null), select the Use no-data value check box, and then type the number in
the box.
Tip For well production data, use -99999 as the no-data value to prevent null data from
appearing as zeros in production plots. For more information about importing production data,
see "Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97.
7 If you want to specify the time or depth domain or the units of measurement for the
data, click Advanced, and then do the following as necessary:
• To specify the domain, click Time or Depth.
• To specify units, click the Specify units of selected files check box, and then
click options for the area, depth, and depth axis units.
Note The preselected options are those of the current project.
To complete the In a column-based importing wizard, when you finish adjusting the configuration settings,
importing process do the following to complete the importing process:
1 Review the file to ensure that all additions or changes you made are correct.
2 Import the data or adjust the settings for additional files as follows:
To do this Do this
Import only the file shown 1 Click Apply on current file.
in the preview pane and The wizard imports the data from only the current file.
then configure additional 2 Select another file in the Current file box
files.
The settings you made are preselected for the other files in the list.
3 Adjust the configuration settings throughout the wizard as
necessary.
4 Import the file.
Repeat the process for all of the files in the list.
Import multiple files with Click OK.
the same configuration The wizard imports the data from all of the files and closes the
settings as the current file. wizard.
Tip To save the new objects The wizard creates objects and any object properties from the imported data. You can
in your project, remember to find the new objects and properties in the Objects browser.
save the project.

1.4 Importing Basin Modeling Files

You can import various types of files that contain basin modeling data in the form of grids
or reservoir fluid transport models. You can create SGrid, Voxet, PointsSet, and Colormap
objects from these data files.
Supported import sources and how to import the specific files are described in this
section.
• "Import Temis/Medica Files," page 1-15
• "Importing MPath Files," page 1-18
• "Importing a PetroMod File," page 1-19
1.4.1 Import Temis/Medica Files

You can use the Temis1 converters to import fault polygon data and create a Curve object,
stratigraphic data to create an SGrid, and topographic data to create a Colormap object.
To import a Fault Use the Medica converter to create a Curve object from fault polygon data in a Medica
Polygon Medica file fault polygon file. The converter creates a Curve object for each import file.
as a Curve
 Select File > Import > Basin Modeling > Temis > Medica Fault Polygons, and
then select the file or type the full path and file name in the dialog box.
For more information about how to complete the importing process, see "Basic procedure
for importing" on page 1-6.
To import a Use the Medica converter to import Medica Surface Topographic files. These files have
Topographic Surface a .g or .top file name extension. A Medica Topographic file is a binary file that can
Medica file contains a regular map or a tartan map (Scottish map). The converter creates a Surface
object from each import file.
 Select File > Import > Basin Modeling > Temis >Medica Topographic Surface,
and then select the file or type the full path and file name in the dialog box.
To import a Medica Use the Medica converter to import a Temis 2D Grid file and create a PointsSet, 2D Grid,
2D Grid file Surface, Voxet, or SGrid object.
1 Select File > Import > Basin Modeling > Temis > Medica Topographic Surface
(Advanced) to open the Import Medica 2D Grid dialog box.
import, and then double-click the file name. The program enters the selected file
name in the File name box.
3 If you want the converter to do a calculated best-guess and fill holes where there is
missing data in the input file, click Fill holes.
1. Medica and Temis3D are software products available from Beicip-Franlab.
User Guide 1.4 Importing Basin Modeling Files 1-15

4 To select which object type you want the converter to create when importing the file,
click one of the following:
• Create PointsSet
• Create Surface. In the Decimation Level box, select how you want the
converter to use the data in the file.
• None. Keep all points.
• Level 1. Take into account all data points when creating the Surface.
• Level 2. Take into account four out of nine points when creating the Surface.
In the Maximum error box, type the value for maximum distance you want the
converter to use when computing errors.
Note Values are measured in the units you set for the project. To check the project units:
select File > Project Properties.
• Create Voxet. In the Property name box, type a name you want the converter
to use when storing the data values.
• Create SGrid
5 In the Output no data value box, type the value that you want the converter to
recognize as a no-data value.
6 If you want to assign a name for the imported file, rather than using the default of
having the converter assign a name, click the Use file name check box, and then
type a name in the GOCAD object name box.
To import a Temis3D You can use the Medica converter to import a Temis3D Grid file as an SGrid object. The
Grid file converter can create one or more objects from each import file. The name of the resulting
SGrid object will be the name of the Temis3D file plus the Roamer age.
1 Select File > Import > Basin Modeling > Temis > Temis 3D Grid (.t4d) to open the
Import Temis3d t4d File dialog box.
import, and then double-click the file name. The converter enters the selected file
name in the Temis3D file box. This should be a visco.t4d file.
As soon as you select the file, the dialog box is updated to show the following:
• Roamer (or Age). List of model ages (age of a layer deposition) in the selected
file.

• Variables. List of Temis3D properties.
• Vectors. List of Temis3D vectors.

3 Click one or more entries in the Roamer column. You can create an SGrid for each
entry in the list. Hold down the CTRL key to select more than one entry.
4 Click one or more properties in the Variables column.
Note If you select more than one entry in the Roamer column (meaning that you want to
create more than one SGrid), all the properties you select in the Variables column are imported
for each SGrid.
5 Click one or more entries in the Vectors column.

Note If you select more than one entry in the Roamer column (meaning that you want to
create more than one SGrid), all the entries you select in the Vectors column are imported for
each SGrid.
To import a Temis3D You can use the Medica converter to import a Temis3D Colormap. The converter will
Colormap create a Colormap for each import file.
1 Select File > Import > Basin Modeling > Temis > Temis 3D Grid Colormap to
open the Import Termis3D Colormap dialog box.
3 In the Colormap name box, type the name you want to use for the map. The default
name is Temis_Colormap.

1.4.2 Importing MPath Files
You can use the MPath converters to import reservoir fluid transport models and create
Voxet, PointsSet, and Colormap objects.
MPath is a high-resolution fluid transport modeling toolkit available from The Permedia
Research Group.
SKUA and GOCAD includes converters for importing four MPath file types:
• .act contains data values that represent simulation results at particular points in space
• .fid contains (in a 3D grid format) flow unit data values for each grid cell in the mode
• .raw contains single values for each grid cell
• .par contains petrophysical data values for each identified flow unit in the .fid file
To import MPath .act Use the MPath ACT converter to import an .act file that contains basin modeling data.
file as a Voxet The .act file can contain ASCII and binary formatted data.
The converter creates a Voxet or PointsSet object from each file that you import.
1 Select File > Import > Basin Modeling > MPath ACT to open the Import Permedia
ACT File dialog box.
import, and then double-click the file name. the converter enters the selected file
name in the ACT file box.
3 If you want the converter to create a PointsSet object click PointsSet. By default, the
converter imports this file and creates a Voxet object.
4 If you want to also import the related .fid and .par files, select the Import
Related .fid and .par File check box.
To import an Use the import MPath Raw file converter to create a Voxet object from a combined ASCII
MPath .raw file as a and binary MPath .raw file.
Voxet
 Select File > Import > Basin Modeling > MPath RAW, and then select the file or
type the full path and file name in the dialog box.

To import an Use the import MPath FID converter to create a Voxet object from a combined ASCII and
MPath .fid file as a binary MPath flow unit identification (.fid) file.
Voxet
 Select File > Import > Basin Modeling > MPath FID, and then select the file or type
the full path and file name in the dialog box.
To import an Use the import MPath PAR converter to create a color map from an ASCII MPath .par file.
MPath .par
(Colormap) file  Select File > Import > Basin Modeling > MPath PAR (Colormap), and then select
the file or type the full path and file name in the dialog box.
1.4.3 Importing a PetroMod File

Use the PetroMod1 converter to create an SGrid object from a PetroMod binary file that
contains basin modeling data.
The converter creates an SGrid object from each file that you import.
To import a PetroMod 1 Select File > Import > Basin Modeling > PetroMod to open the Import PetroMod
IES file as an SGrid ACT File dialog box.
1. PetroMod is a multi-dimensional modeling software system available from Integrated Exploration

Systems (IES).

2 Click to browse for the file you want to import, and then double-click the file
name.
3 Specify whether you want to import facies or overlays and create a cell-centered or
corner-point grid by clicking one of these:
• Facies. Creates a cell-centered SGrid.
• Overlays. Create a corner-point grid.
4 If you want to specify the domain or units of measurements for data in the selected
files, click Advanced and then do the following as necessary:
• Click either Time or Depth to specify the domain.
• Select the Specify units of selected files check box, and then click the
appropriate units for the Area units and Time units.

1.5 Importing Cultural Data

You can import data files (from various software products) that contain cultural data,
primarily in the form of geographical maps.
Cultural data is typically geographical representation data that lets you:
• Explore spatial data results
• Identify location information such as lease blocks
section.
• "Importing an ArcView File," page 1-21
• "Importing a DXF File," page 1-22
• "Importing a SeisWorks Cultural Data File," page 1-22
1.5.1 Importing an ArcView File

Use the ArcView 1 converter to create a PointsSet or Curve object from an ArcView Shape
(.shp) file that contains cultural topography data.
The converter requires three ASCII files be present for the import process. All three files
should have the same name but different file name extensions (.dbf, .shp, and .shx). The
file selector looks for only the shape (.shp) file; the other two files are necessary to
describe data in the shape file.
If the file contains geometry data for more than one object, the converter creates a
PointsSet or Curve object for each set of geometry data.
To import an ArcView  Select File > Import > Cultural Data > Arcview, and then select the file or type the
file full path and file name in the dialog box.
1. ArcView is a geographic information system available from the Environmental Systems Research
Institute (ESRI).
User Guide 1.5 Importing Cultural Data 1-21

1.5.2 Importing a DXF File
Use the DXF1 converter to create a PointsSet, Curve, or Surface (triangulated surface)
object from an AutoCAD .dxf drawing file that contains cultural topography data.
The .dxf format is a tagged data representation of all the information contained in an
AutoCAD drawing file.
If the file contains geometry data for more than one object, the converter creates a
PointsSet, Curve, or Triangulated Surface object for each set of geometry data.
To import a .dxf file 1 Select File > Import > Cultural Data > DXF to open the Import DXF file dialog box.
names in the File name box.
3 Select the Import text check box, if you want to include text as a part of the object.
Note Including text with the object significantly increases processing time.
1.5.3 Importing a SeisWorks Cultural Data File

Use the SeisWorks2 converter to create a Curve object from a SeisWorks (.asc) ASCII file
that contains cultural topography data.
If the file contains geometry data for more than one object, the converter creates a Curve
object for each set of geometry data.
To import a SeisWorks  Select File > Import > Cultural Data > SeisWorks Cultural Data (ASC), and then
file select the file or type the full path and file name in the dialog box.
1. A .dxf file is produced by AutoCAD, a software product available from Autodesk.

2. SeisWorks is a software product available from Landmark Graphics.

1.6 Importing Fault Interpretations Data

You can import various types of files that contain fault interpretation data in the form of
points, fault sticks, fault polygons, or traces. You can create PointsSet and Curve objects
from these data files.
Fault interpretation modeling lets you:
• Evaluate fault surface construction
• Estimate the temporal evolution of a flat network
• Appraise fault geometry and displacement
• Interpret 3D seismic data across a large fault area
The following topics provide information about import sources for each type of object and
how to import specific files.
For information about point sets, see:
• "Importing a CPS3 ASCII Data (.dat) File," page 1-24
• "Importing a CPS3 Binary File," page 1-25
• "Importing a Column-Based File," page 1-25
• "Importing a FastEdit Scattered Data File," page 1-25
• "Importing an XYZ File," page 1-26
For information about fault sticks (Curves), see:
• "Importing a Charisma Fault Interpretations File," page 1-26
• "Importing a CPS3 ASCII Polygons (.ply) File," page 1-27
• "Importing a CPS3 ASCII Fault Traces (.flt) File," page 1-27
• "Importing a SeisWorks Fault Sticks File," page 1-28
• "Importing a Z-MAP Fault or Contour File," page 1-28
For information about fault polygons or traces (Curves), see:
• "Importing a Charisma Fault Polygons File," page 1-29
• "Importing a CPS3 ASCII Polygons (.ply) File," page 1-29
• "Importing a FastEdit Fault Polygons File," page 1-30
• "Importing an Irap RMS Fault Polygons or Lines File," page 1-30
• "Importing a SeisWorks Fault Polygon File," page 1-30
User Guide 1.6 Importing Fault Interpretations Data 1-23

1.6.1 Importing a CPS3 ASCII Data (.dat) File
You will use the CPS3 1 ASCII Data converter to import a .dat ASCII file that contains fault,
horizon, or well data. You determine which object to create based on the type of data in
the .dat file, and then select the appropriate object in the import dialog box.
If your file contains fault interpretations points, the converter creates one PointsSet object
from each file that you import.
To import a .dat file 1 Select File > Import >, and then do one of the following to open the dialog box.
as a PointsSet, a
Curve, or a Well If you want to import this To create this
Do this
type of data type of object
Fault interpretations PointsSet Select Fault Interpretations > PointsSet >
CPS3 ASCII Data (.dat).
Horizon interpretations PointsSet Select Horizon Interpretations >
PointsSet > CPS3 ASCII Data (.dat).
Fault interpretations, fault sticks Curve Select Fault Interpretations >Fault Sticks
> CPS3 ASCII Data (.dat).
Horizon interpretations, Curve Select Horizon Interpretations >
contours Contours > CPS3 ASCII Data (.dat).
Well data (X, Y, TVDSS) Well Select Well Data > Path and Logs > CPS3
ASCII Data (.dat).
Either choice opens the same dialog box.
3 Do one of the following:
• To create a PointsSet object, click Import as PointsSet.
• To create a Curve object, click Curve.
• To create a Well object, click Well.

1. CPS3 (a mapping system) is a part of the GeoFrame software product available from Schlumberger.

1.6.2 Importing a CPS3 Binary File

You can use the CPS3 binary converter to create a PointsSet, Curve, or 2D Grid object
from a CPS3 binary file. However, if your file contains fault points, the converter expects
to read an .svd file and create a PointsSet object. The converter creates one object from
each imported file.
To import a CPS3  Select File > Import > Fault Interpretations > PointsSet > CPS3 Binary
binary .svd file as a (.svd, .svs, .svf, and .svp), and then select the file or type the full path and file
PointsSet name in the dialog box.
1.6.3 Importing a Column-Based File

You can use a column-based file wizard to import fault interpretation data (from an ASCII
file) and create a PointsSet object (or a Curve or Well object), depending on the type of
data in your file.
The procedure is similar whether you are importing Curve, PointsSet, or Well data. For
information, see "Common Process for Importing a Column-Based File" on page 1-8.
1.6.4 Importing a FastEdit Scattered Data File

Use the FastEdit Scattered Data converter to create a PointsSet from a FastEdit scattered
data file.
To import a FastEdit  Select File > Import > Fault Interpretations > FastEdit Scattered data, and then
Scattered Data file as select the file or type the full path and file name in the dialog box.
a PointsSet

1.6.5 Importing an XYZ File
Use the X Y Z file converter to create a PointsSet object from a fault interpretation X, Y, Z
ASCII data file. Each line in the file becomes a point in the PointsSet object, with the three
data values as X, Y, and Z coordinates.
To import an X, Y, Z 1 Select File > Import > Fault Interpretations > PointsSets > X Y Z to open the
ASCII file as a Import X Y Z ASCII File dialog box.
PointsSet
3 If you want the converter to ignore points with no data value, select the ignore
points with no data value check box, and in the no data value box, type the null
value. By default the converter considers all points to be active. The default no-data-
value is -9999. The no-data-value option is unavailable unless you select the ignore
points with no data value check box.
1.6.6 Importing a Charisma Fault Interpretations

File
Use the Charisma 1 Fault Interpretations converter to create a Curve object from a
Charisma ASCII file. The converter creates a Curve object for each import file.
To import a Charisma  Select File > Import > Fault Interpretations > Fault Sticks > Charisma Fault
file as a Curve Interpretations, and then select the file or type the full path and file name in the
dialog box.
For more information about how to complete the importing process, see "Basic Concept
for Importing Data" on page 1-6.
1. Charisma is a part of the GeoFrame software product available from Schlumberger.


You will use the CPS3 ASCII Data converter to import .dat data and create a PointsSet,
Curve, or Well object. For information about how to import this type of file, see
"Importing a CPS3 ASCII Data (.dat) File" on page 1-24.
If your file contains fault sticks data, the converter creates a Curve object from each file
that you import.
1.6.8 Importing a CPS3 ASCII Polygons (.ply) File

Use the CPS3 ASCII Polygons converter to create a PointsSet object from the X, Y data
coordinates in a CPS3 ASCII Polygons (.ply) file. The converter creates a PointsSet object
for each import file.
To import a .ply file as  Select File > Import > Fault Interpretations > PointsSet > CPS3 ASCII Polygons
a PointsSet (.ply), and then select the file or type the full path and file name in the dialog box.
1.6.9 Importing a CPS3 ASCII Fault Traces (.flt) File

Use the CPS3 ASCII Fault Traces converter to create a Curve object from a CPS3 ASCII
Fault Trace (.flt) file. The converter creates a Curve object for each import file.
To import a .flt file as  Select File > Import > Fault Interpretations > Fault Sticks > CPS3 ASCII Polygons
a Curve (.flt), and then select the file or type the full path and file name in the dialog box.

You can use the CPS3 Binary converter to create a PointsSet, Curve, or 2D-Grid object
from a CPS3 binary file. However, if your file contains fault sticks data, the converter
expects to read an .svf file and create a Curve object.
The converter creates a new object for each import file.
To import a CPS3  Select File > Import > Fault Interpretations > Fault Sticks > CPS3 Binary
binary .svf or .svp file (.svd, .svs, .svf, and .svp), and then select the file or type the full path and file
as a Curve name in the dialog box.

You can use a column-based file wizard to import fault stick data (from an ASCII file) and
create a Curve object (or a PointsSet or Well object), depending on the type of data in
your file.
The procedure is similar whether you are importing Well, PointsSet, or Curve data. For
1.6.12 Importing a Petrel Pillars File

Use the Petrel1 Pillars converter to create a Curve object from a Petrel Pillars file.
To import a Petrel  Select File > Import > Fault Interpretations > Fault Sticks > Petrel Pillars, and
Pillars file as a Curve then select the file or type the full path and file name in the dialog box.
1.6.13 Importing a SeisWorks Fault Sticks File

Use the Seisworks 2 fault sticks converter to create a Curve object from a SeisWorks fault
sticks file.
To import a SeisWorks  Select File > Import > Fault Interpretations > Faults Sticks > SeisWorks Fault
fault sticks file as a Sticks, and then select the file or type the full path and file name in the dialog box.
Curve
1.6.14 Importing a Z-MAP Fault or Contour File

Use the ZMAP 3 Fault or Contour converter to create a Curve object from a Zmap fault or
contour file.
To import a Zmap  Select File > Import > Fault Interpretations > Fault Sticks > Z-MAP Fault or
fault traces or Contour Files, and then select the file or type the full path and file name in the
contour file as a dialog box.
Curve
1. Petrel is a software product available from Schlumberger.

3. Z-Map is a software product available from Landmark Graphics.

1.6.15 Importing a Charisma Fault Polygons File

Use the Charisma Fault Polygons converter to create a Curve object from a Charisma Fault
Polygons ASCII file. The converter creates one Curve object from each file.
To import a Charisma 1 Select File > Import > Fault Interpretations > Fault Polygons (Curves) >
Fault Polygon file as a Charisma Fault Polygons to open the Import ASCII Charisma Fault Polygon To Curve
Curve dialog box.
3 Type the number that represents the distance between two segment extremities in
the maximum closure distance box. If the distance between two segment
extremities is within this number, the two extremities will be linked. The default is 25.
4 Type the no-data-value in the value when undefined box. The default is 0.
5 Clear the Use prefix check box if you do not want each Curve object imported from
this file to have the same prefix. The check box is selected by default (meaning each
Curve object will have the same prefix).
6 If you chose to use a prefix, type the prefix you want in the Fault prefix box.
1.6.16 Importing a CPS3 ASCII Polygons (.ply) File

Use the CPS3 ASCII Polygons converter to create a Curve object from a .ply file. The
converter creates one PointsSet object per import file.
To import a CPS3  Select File > Import > Fault Interpretations > Fault Polygons or Traces > CPS3
Polygons file as a ASCII Polygons (.ply), and then select the file or type the full path and file name in
Curve the dialog box.

1.6.17 Importing a FastEdit Fault Polygons File
Use the FastEdit Fault Polygons converter to create a Curve object from a FastEdit fault
polygons file.
To import a FastEdit  Select File > Import > Fault Interpretations > Fault Polygons or Traces >
fault polygons file as Fastedit Fault Polygons, and then select the file or type the full path and file name
a Curve in the dialog box.
1.6.18 Importing an Irap RMS Fault Polygons or Lines

File
Use the Irap1 RMS Fault Polygons or Lines converter to create a Curve object from an Irap
RMS lines file. The converter can import either the Irap RMS Classic or Mapping format.
The converter creates one Curve object from each import file.
To import an Irap RMS  Select File > Import > Fault Interpretations > Fault Polygons or Traces > Irap
file as a Curve RMS Fault Polygons or Lines, and then select the file or type the full path and file
name in the dialog box.
1.6.19 Importing a SeisWorks Fault Polygon File

Use the SeisWorks2 Fault Polygon converter to create a Curve object from a SeisWorks
fault polygon file. The converter expects to read X and Y coordinates file in the SeisWorks
default export format.
To import a SeisWorks  Select File > Import > Fault Interpretations > Fault Polygons or Traces >
Fault Polygon file as a SeisWorks Fault Polygons, and then select the file or type the full path and file
Curve name in the dialog box.
1. IRAP RMS is a software product available from ROXAR.


1.7 Importing Fault Surfaces Data

SKUA or GOCAD includes converters for importing various files that contain fault surface
data in the form of grids, triangle surface, or pillars. You can create Surface objects from
these data files.
section.
• "Importing a CPS3 ASCII 2D-Grid (.grd) File," page 1-31
• "Importing a FastEdit 2D-Grid File," page 1-31
• "Importing an Irap RMS Triangle Surface File," page 1-32
• "Importing a Petrel Pillars File," page 1-32
• "Importing a RC2 2D-Grid File," page 1-32
• "Importing a RESCUE Model File," page 1-32
• "Importing a Z-MAP ASCII 2D-Grid File," page 1-33
1.7.1 Importing a CPS3 ASCII 2D-Grid (.grd) File

Use the CPS3 ASCII 2D-Grid converter to create a 2D-Grid (gridded surface) object from a
CPS3 grid (.grd) file. The converter creates a new 2D-Grid object for each import file.
To import a CPS3 .grd  Select File > Import > Fault Surfaces > CPS3 ASCII 2D-Grid (.grd), and then select
file as a 2D-Grid the file or type the full path and file name in the dialog box.

You can use the CPS3 Binary converter to create a new PointsSet, Curve, or 2D-Grid
object from a CPS3 binary file. If your file contains fault surface data, the converter
creates a Surface object. The converter creates one object from each import file.
To import a CPS3  Select File > Import > Fault Surfaces > CPS3 Binary (.svd, .svs, .svf, and .svp),
binary .svs file as a and then select the file or type the full path and file name in the dialog box.
2D-Grid
1.7.3 Importing a FastEdit 2D-Grid File

Use the FastEdit 2D-Grid converter to create a 2D-Grid object from a FastEdit file.
To import a FastEdit  Select File > Import > Fault Surfaces > Fastedit 2D-Grid, and then select the file or
2D grid file as a 2D- type the full path and file name in the dialog box.
Grid
User Guide 1.7 Importing Fault Surfaces Data 1-31

1.7.4 Importing an Irap RMS Triangle Surface File
Use the Irap RMS Triangle Surface converter to create a Surface (triangulated surface)
object from an Irap RMS Triangle Surface file.
To import an Irap RMS  Select File > Import > Fault Surfaces > Irap RMS Triangle Surface, and then select
TriangleSurface file as the file or type the full path and file name in the dialog box.
a Surface
1.7.5 Importing a Petrel Pillars File

Use the Petrel1 Pillars converter to create a Surface object from a Petrel Pillars file.
To import a Petrel  Select File > Import > Fault Surfaces > Petrel Pillars, and then select the file or
Pillars file as a Surface type the full path and file name in the dialog box.
1.7.6 Importing a RC2 2D-Grid File

Use the RC2 2 2D-Grid converter to create a 2D-Grid object from an RC2 file.
To import an RC2  Select File > Import > Fault Surfaces > RC2 2D-Grid, and then select the file or
2DGrid file as a 2D type the full path and file name in the dialog box.
Grid
Importing a RESCUE Use the RESCUE Model converter to import a .bin file. Depending on the type of data in
Model File your file, you can:
• Create an SGrid object
• Create a Surface object
• Add property data to an existing SGrid object.
The converter imports grid data as an SGrid object and horizon or fault data as a girded
Surface object (2D Grid).
RESCUE, a Joint Industry Project managed by the Petrotechnical Open Software Corporation (POSC),
is an acronym for REServoir Characterization Using Epicentre.
A RESCUE file is typically composed of multiple file types. The converter reads only files
with a .bin file extension, and only files produced up to and including RESCUE Version 37.
Output from a RESCUE project typically contains different types of data: surfaces, grids
and properties. The converter can import grids, horizons, faults and properties.
Note The converter can read only horizons or faults that are represented by a regular I, J grid. This
converter cannot import Well data.
1. Petrel is a software product available from Schlumberger.

2. RC(2) Geostatistics for Stratamodel is a software product available from Landmark Graphics.

To import a RESCUE 1 Select File > Import > Reservoir Grid > RESCUE Model (Grids, Horizons, Faults)
file as an SGrid or to open the Import RESCUE as SGrid dialog box.
Surface (2D Grid)
2 Click to browse for and select the file you want to import.
3 If the data includes stratigraphic units and the logical order for those units, the
command creates a stratigraphic column resource from the data in the file. In the
New stratigraphic column name box, type a name for this new resource. (After the
import, you can find it in the Resources browser.)
4 Specify whether you want to load the following data:
• Load reservoir grid. Imports the grid and creates and SGrid object.
• Load properties. Imports property data as object properties.
• Load horizon and fault surfaces. Imports horizons and faults as triangulated
surfaces, gridded surfaces, point sets, and curves. If you deselect this option, the
command imports all horizon and fault data as 2D-Grid Surface objects.
5 If you want to extract fault block information from imported grid, in the Advanced
area, select the Recreate fault blocks check box.
1.7.7 Importing a Z-MAP ASCII 2D-Grid File

You can use the Z-MAP 1 converter to create a 2D-Grid object from a Z-MAP.
To import a Z-MAP 2D  Select File > Import > Fault Surfaces > Z-MAP ASCII 2D-Grid, and then select the
grid file as a 2D Grid file or type the full path and file name in the dialog box.
1. Z-MAP is a software product available from Landmark Graphics.
User Guide 1.7 Importing Fault Surfaces Data 1-33

1.8 Importing Horizon Interpretations Data
SKUA and GOCAD include converters for importing various files that contain horizon
interpretation data in the form of points, contours, or grids. You can create Point Sets,
Curves, or 2D-Grid objects from these data files.
The following topics provide information about supported import sources for specific
objects and how to import the files.
For information about point sets, see:
• "Importing a Charisma Horizon Points File," page 1-34
• "Importing a FastEdit Scattered Data File," page 1-35
• "Importing a GSLib 2D Map File," page 1-35
• "Importing a SeisWorks Inline Xline X Y Z File," page 1-36
• "Importing an X, Y, Z File," page 1-36
For information about contours (Curves), see:
• "Importing an Adobe Contours File," page 1-37
• "Importing a FastEdit Horizon Contour File," page 1-37
• "Importing a Z-MAP Contour File," page 1-38
1.8.1 Importing a Charisma Horizon Points File

Use the Charisma Horizon Points converter to create a PointsSet object from a Charisma
ASCII file. The converter creates a PointsSet object from each import file.
To import a Charisma Select File > Import > Horizon Interpretations > PointsSet > Charisma Horizon
file as a PointsSet Points, and then select the file or type the full path and file name in the dialog box.


"Importing a CPS3 ASCII Data (.dat) File" on page 1-24. If your file contains horizon
data, the converter creates a Point Set object from each file that you import.

from a CPS3 binary file. However, if your file contains horizon points data, the converter
expects to read an .svd file and create a PointsSet object. The converter creates one object
from each import file.
To import a CPS3  Select File > Import > Horizon Interpretations > CPS3 Binary (.svd, .svs, .svf,
binary .svd file as a and .svp), and then select the file or type the full path and file name in the dialog
PointsSet box.

You will use the column-based file wizard to import horizon data (from an ASCII file) and
create a PointsSet object (or a Well or Curve object), depending on the type of data in
your file.
The procedure for importing from a column-based file is similar for well, point sets, and
curve data. For information, see "Common Process for Importing a Column-Based File"
on page 1-8.
1.8.5 Importing a FastEdit Scattered Data File

Use the FastEdit Scattered Data converter to create a PointsSet, Curve, or 2D Grid object
from a FastEdit Scattered Data file.
To import a FastEdit  Select File > Import > Horizon Interpretations > FastEdit Scattered Data, and
scattered data file as then select the file or type the full path and file name in the dialog box.
a PointsSet
1.8.6 Importing a GSLib 2D Map File

Use the GSLib 2D Map converter to create a PointsSet object from a GSLib 2D Map file.
To import a GSLib 2D  Select File > Import > Horizon Interpretations > PointsSet > GSLib 2D Map, and
Map as a PointsSet then select the file or type the full path and file name in the dialog box.
User Guide 1.8 Importing Horizon Interpretations Data 1-35

1.8.7 Importing a SeisWorks Inline Xline X Y Z File
Use the SeisWorks Inline converter to create a PointsSet object from SeisWorks Inline Xline
X, Y, Z file.
To import a SeisWorks  Select File > Import > Horizon Interpretations > PointsSets > SeisWorks Inline
Inline file as a Xline X Y Z, and then select the file or type the full path and file name in the dialog
PointsSet box.
1.8.8 Importing an X, Y, Z File

Use the X, Y, Z converter to import a raw data ASCII file to create a PointsSet object. The
converter reads only the first three data fields in the file. Each line in the input file
becomes a point in the newly created object, with the X value as the first point, the Y
value as the second point, and the Z value as the third point.
To import an X, Y, Z 1 Select File > Import > Horizon Interpretations > PointsSets > XYZ to open the
file as a PointsSet Import X Y Z ASCII File dialog box.
3 Select the ignore points with no data value check box, if you want the converter
to ignore points with a specific data value. By default the converter considers all
points to be active.
4 If you select the ignore points with no-data value option, type the null value in the no
data value box. The default no-data-value is -9999. This option is unavailable unless
you turn on the ignore points with no-data-value option.

1.8.9 Importing an Adobe Contours File

Use the Adobe Contours converter to create a Curve object from an Adobe Contours file.
To import an Adobe  Select File > Import > Horizon Interpretations > Contours > Adobe Contours,
Contours as a Curve and then select the file or type the full path and file name in the dialog box.

If you file contains contour data, the converter creates a Curve object from each file that
you import.

from a CPS3 binary file. However, if your file contains contour data, the converter expects
to read an .svf or .svp file and create a Curve object.
The converter creates one object from each import file.
To import a CPS3  Select File > Import > Horizon Interpretations > Contours > CPS3 Binary
binary .svf or .svp file (.svd, .svs, .svf, and .svp), and then select the file or type the full path and file
as a Curve name in the dialog box.

You can use a column-based file wizard to import contour data (from an ASCII file) and
create a Curve object (or a PointsSet or Well object).
1.8.13 Importing a FastEdit Horizon Contour File

Use the FastEdit Horizon Contours converter to create a Curve object from a FastEdit
horizon contours file.
To import a FastEdit  Select File > Import > Horizon Interpretations > Fastedit Horizon contours, and
horizon contour file then select the file or type the full path and file name in the dialog box.
as a Curve
User Guide 1.8 Importing Horizon Interpretations Data 1-37

1.8.14 Importing a Z-MAP Contour File
Use the Z-MAP Contour converter to create a Curve object from a Z-MAP contour file.
To import a Z-MAP  Select File > Import > Horizon Interpretations > Z-MAP Contour Files, and then
Contour file as a select the file or type the full path and file name in the dialog box.
Curve

1.9 Importing Horizon Surface Data

SKUA and GOCAD includes converters for importing various files that contain horizon
surface data in the form of gridded surface data and property data. You can create
PointsSet, Curve, Surface, and 2D-Grid objects from these data files.
section.
• "Importing a CPS3 ASCII 2D-Grid (GRD) File," page 1-39
• "Importing a FastEdit 2D-Grid File," page 1-40
• "Importing a Geoprobe 2D Grid (.gvw) File," page 1-40
• "Importing a GSLib 2D Map as Surface File," page 1-40
• "Importing an Irap RMS ASCII 2D-Grid File," page 1-40
• "Importing an Irap RMS ASCII 2D-Grid Property File," page 1-41
• "Importing a Norsar Horizons File," page 1-41
• "Importing an RC2 2D-Grid File," page 1-41
• "Importing a RESCUE Model File," page 1-42
• "Importing a Z-MAP ASCII 2D-Grid File," page 1-42
• "Importing a Z-MAP ASCII 2D-Grid Property File," page 1-42
1.9.1 Importing a CPS3 ASCII 2D-Grid (GRD) File

You can use the CPS3 ASCII 2D-Grid converter to create a 2D-Grid object from a CPS3
ASCII grid (GRD) file. The converter creates a 2D-Grid object for each import file.
To import a .grd file  Select File > Import > Horizon Surfaces > CPS3 ASCII 2D-Grid, and then select the
as a 2D-Grid file or type the full path and file name in the dialog box.

You can use CPS3 Binary converter to create a PointsSet, Curve, or 2D-Grid object from a
CPS3 binary file. However, if your file contains surface data, the converter expects to read
an .svs file and create a 2D Grid object. The converter creates one object from each
import file.
To import a CPS3  Select File > Import > Horizon Surfaces > CPS3 Binary, and then select the file or
binary .svs file as a type the full path and file name in the dialog box.
2D-Grid
Supported file types include SVD, SVS, SVF, and SVP.
User Guide 1.9 Importing Horizon Surface Data 1-39

1.9.3 Importing a FastEdit 2D-Grid File
Use the FastEdit 2D-Grid converter to create a PointsSet, Curve, or 2D Grid object from a
FastEdit 2D-Grid file.
To import a FastEdit  Select File > Import > Horizon Surfaces > FastEdit 2D-Grid, and then select the
2D-Grid file as a 2D file or type the full path and file name in the dialog box.
Grid
1.9.4 Importing a Geoprobe 2D Grid (.gvw) File

You can use the Geoprobe 2D-Grid converter to create a 2D Grid object from
Geoprobe .gvw file.
To import a Geoprobe  Select File > Import > Horizon Surfaces > Geoprobe 2D-Grid (.gvw), and then
.gvw file as a 2D Grid select the file or type the full path and file name in the dialog box.
1.9.5 Importing a GSLib 2D Map as Surface File

You can use the GSLib 2D Map converter to create a Surface object from GSLib 2D Map
file.
To import a GSLib 2D  Select File > Import > Horizon Surfaces > GSLib 2D Map as Surface, and then
Map as a Surface select the file or type the full path and file name in the dialog box.
1.9.6 Importing an Irap RMS ASCII 2D-Grid File

You can use the IRAP RMS ASCII 2D-Grid converter to create a 2D Grid object from an
IRAP RMS ASCII grid file. The converter can import either the IRAP RMS Classic or
Mapping format. The converter creates one 2D-Grid object from each import file.
To import an IRAP  Select File > Import > Horizon Surfaces > Irap RMS ASCII 2D-Grid, and then
RMS ASCII grid file as select the file or type the full path and file name in the dialog box.
a 2D-Grid object

1.9.7 Importing an Irap RMS ASCII 2D-Grid Property

File
Use the IRAP RMS ASCII 2D-Grid converter to import properties for an existing 2D-Grid
object from an IRAP RMS ASCII grid file. The converter adds the properties identified in
the file to an existing 2D-Grid object.
To import an Irap RMS 1 Select File > Import > Horizon Surfaces > Irap RMS ASCII 2D-Grid Property to
ASCII grid file as 2D- open the Import Z-MAP ASCII as 2D-Grid Property dialog box.
Grid property
2 In the 2D-Grid box, specify the file name of the existing 2D-Grid object (for which
you want to import the properties).
3 In the File name box, specify the file you want to import. Click , browse for the
file you want to import, and then double-click the file name.
4 In the Property name box, type the name of the property you want to import.
1.9.8 Importing a Norsar Horizons File

You can use the Norsar converter to import an ASCII file and create a Voxet. For
information about how to import this type of file, see "Importing a Norsar Depth Cube
File" on page 1-71.
NORSAR-2D and NORSAR-3D are software products available from NORSAR.
1.9.9 Importing an RC2 2D-Grid File

Use the RC2 2D-Grid converter to create a 2D-Grid object from an RC2 file.
To import an RC2  Select File > Import > Horizon Surfaces > RC2 2D-Grid, and then select the file or
2DGrid file as a 2D type the full path and file name in the dialog box.
Grid
User Guide 1.9 Importing Horizon Surface Data 1-41

1.9.10 Importing a RESCUE Model File
You can use the RESCUE converter to import .bin data and create an SGrid or a Surface
object (if your file contains surface data). For information about the RESCUE Model and
importing this type of file, see "Importing a RESCUE Model File" on page 1-32.
1.9.11 Importing a Z-MAP ASCII 2D-Grid File

Use the Z-MAP 2D-Grid converter to create a 2D-Grid object from a ZMAP ASCII file.
To import a Z-MAP 2D  Select File > Import > Horizon Surfaces > Z-MAP ASCII 2D-Grid, and then select
grid file as a 2D-Grid the file or type the full path and file name in the dialog box.
1.9.12 Importing a Z-MAP ASCII 2D-Grid Property File

Use the Z-Map 2D-Grid Property converter to import property data from a Z-MAP ASCII
property file into an existing 2D-Grid object.
Important If you import a property value that already exists in the grid, the
converter will overwrite the existing property values with the new (imported) property
values. If you import a property value that does not exist in the grid, the converter
adds that property value to the existing grid.
1 Load an existing 2D-Grid object into your project or create a 2D-Grid object.
2 Select File > Import > Horizon Surfaces > Z-MAP ASCII 2D-Grid Property to open
the Import a Z-MAP file as a Property of the Grid dialog box.
3 In the 2D-Grid box, enter the file name of the existing 2D-Grid object for which you
want to import the properties.
4 Next to the File name box, click , browse for the file you want to import, and
then double-click the file name.
5 In the Property name box, type the name of the property you want to import.

1.10 Importing Image Files

SKUA and GOCAD include converters for importing images.
For information see:
• "To import an image log," page 1-43
• "To import an image log with SIF," page 1-44
• "To import a 2D image file as a Voxet," page 1-44
To import an image You can import an image log to use in a track in a well section or cross section view.
log
1 Select File > Import > Well Data > Logs > Image Log to open the Import Well
Image Log dialog box.
2 In the Well box, select the well for which you want to import the image log.
3 To select the image, click to open the Select Text File dialog box, browse for the
file you want to import, and then double-click the file name.
4 In the Image Top Measured Depth box, enter the top depth at which you want the
image to appear.
5 In the Sampling box, enter a value that is used to multiply the image height in pixels
to determine the height of the image. For example, if your image is 120 pixels in
height, and the sampling is 2 meters, the log image will be 240 meters in height.
Note The sampling unit is the measured depth unit, which can vary depending on the well.
User Guide 1.10 Importing Image Files 1-43

To import an image You can import an image log in SmartRaster Interchange Format (SIF) to use as an image
log with SIF track in a well section or cross section view. This format allows for a proper calibration
between the picture and the measured depth. For example, it corrects deformations
caused by scanning paper logs. A2D Technologies licenses SIF.
1 Select File > Import > Well Data > Logs > Image Log with SIF to open the Import
Well Image Log dialog box.
2 In the Filenames box, click to open the Select Text File dialog box, browse for
the SIF file you want to import, and then double-click the file name.
After you import the image log, you can attach the picture to the appropriate well. You
can determine which well to attach the image log by using the well API, which you can
check and edit in the well constant table. For more information about well constants, see
Part I: Getting Started, "Opening Well Constants from Epos" on page 4-17.
To import a 2D image Use the 2D Voxet converter to create a Voxet object from a 2D image file.
file as a Voxet
1 Select File > Import > Images > As 2D Voxet to open the Import Image as Voxet
dialog box.

1.11 Importing Reservoir Grid Data

SKUA and GOCAD include converters for importing various types of files that contain 3D
reservoir grid data from standard commercial flow simulators such as ECLIPSE
(Schlumberger), CMG IMEX, or VIP (Halliburton) or through standard formats such as
RESCUE and RESQML. You can create a reservoir grid (SGrid object) from these data files
or you can import the property data and assign them to existing SGrids.
For information about importing SGrids, see:
• "Importing an ECLIPSE ASCII Grid File," page 1-46
• "Importing an ECLIPSE Binary Grid File," page 1-47
• "Importing a CMG Grid and Simulation Results," page 1-54
• "Importing a RESCUE Model (Grids, Horizons, Faults) File," page 1-56
• "Importing a VIP ASCII Grid File," page 1-56
• "Importing a VIP or ECLIPSE LGR File," page 1-57
For information about importing SGrid object properties, see:
• "Importing ECLIPSE ASCII Properties File," page 1-58
• "Importing an I J K Property File," page 1-59
• "Importing a VIP ASCII Properties File," page 1-60
For information about importing faults, see "Importing an ECLIPSE ASCII Faults File,"
page 1-61.
For information about importing well completions as SGrid object properties, see
"Importing Well Completion Data," page 1-90.
User Guide 1.11 Importing Reservoir Grid Data 1-45

1.11.1 Importing an ECLIPSE ASCII Grid File
The ECLIPSE 1 ASCII Grid converter imports an SGrid object from an ECLIPSE ASCII file. If
the file contains property values, the command imports the grid properties at the same
time.
To import an ECLIPSE 1 Select File > Import > Reservoir Grid > SGrid > ECLIPSE ASCII Grid to open the
ASCII file as an SGrid Import ECLIPSE ASCII as SGrid dialog box.
2 In the File name box, enter the path and file name of the file that you want to
import.
3 To specify the advanced importing options, click Advanced, and then do the
following as necessary:
• To import the well completions along with the grid and properties, select the
Import well completions check box and enter a name for the production
scenario in the Completion scenario name box.
1. ECLIPSE (a reservoir simulation software) is a part of the Schlumberger Information Solutions suite
of simulators.

• To import local grid refinements (LGRs), select the Import LGR check box.
For information about LGRs, see Part X: Reservoir Production and Simulation,
"Local grid refinement (LGR)" on page 2-5.
• To change the origin of the grid, select Switch I, Switch J, and Switch K check
boxes as necessary.
For example, Switch I sets the origin of the grid to Imax instead of Imin.
Depending on the options selected, you can set the origin of the grid to any
corner.
• To change the Domain by clicking either Time or Depth.
For example, if the z-axis value in the file you are importing differs from the z-axis
set for your project, change the domain for this new object.
Note The command automatically selects units based on the domain (z-axis setting)
chosen when the project was created.
• If the units in the file differ from the default units set for your project, select the
Specify units of selected files check box, and then select the appropriate units.
For information about setting units for the project, see "Setting Units for a
Project" on page 1-19.
• If you want to extend dying faults, select the Propagate vertical cuts check box.
If selected, the command extends fault cuts from the top to the bottom of the
grid.
• If you want to automatically build faults, select the Automatically detect faults
check box. For example, this is useful if faults are not defined in the file by using
the FAULTS keyword.
Note If there is no FAULTS keyword in the file, you might want to turn off the automatic
detection of faults, and instead use the ECLIPSE ASCII Faults converter (File > Import >
Reservoir Grid > ECLIPSE ASCII Fault) to add fault data to the imported grid. For
information, see "Importing an ECLIPSE ASCII Faults File," page 1-61.
You can find the imported grid and properties in the Objects browser by expanding the
Flow Models category.
If you imported well completions, the completions appear as grid properties and the date
is included in the name (for example, completions_1998_01_01). The wells appear in the
Objects browser.
1.11.2 Importing an ECLIPSE Binary Grid File

You can use the ECLIPSE grid converter to create an SGrid object from an ECLIPSE binary
file. You can also import an .INIT file (containing initial properties) and .UNRST file
(containing time-dependant properties) at the same time. In addition, if you want to use
the imported data in the Production Data Analysis Workflow, you can specify the
simulation scenario for the data.
You can also import local grid refinements (LGR data) with this converter. When you
import a grid from an ECLIPSE binary file that contains LGRs, the converter automatically
imports all LGRs along with the grid. For more information about LGRs, such as why you
may want to use them in flow simulation and a description of the process to create or edit
them, see Part X: Reservoir Production and Simulation, "What Is Upscaling and
Downscaling?" on page 2-2.

Important The binary ECLIPSE file (*.GRID or *.EGRID), the initial reservoir data file
(*.INIT), and the unified restart data file (*.UNRST) should have the same root file
name, such as: name .GRID, name .INIT, and name .UNRST. In addition, all files should
be binary and should be located in the same folder.
Exception If you are importing more than one restart file, the extensions should
be .X0000, .X0001, and so on.
Note When you import dual-porosity data, matrix properties are prefixed with "M" (for example,
MPORO for matrix porosity) and fracture properties with "F" (for example, FPORO for fracture
porosity).
For more information, see the following procedure.
To import an ECLIPSE 1 Select File > Import > Reservoir Grid > ECLIPSE Binary Grid to open the Import
binary file as an SGrid ECLIPSE Binary Files dialog box.
2 In the Grid file box, enter the path and file name for the grid that you want to
import. Supported formats include: GRID and EGRID files.

When you select the grid file, if the INIT and UNRST files are in the same folder and
have the same root file name, the converter automatically selects them for you.
3 If you plan to work with the data in the Production Data Analysis Workflow or, later,
export the grid to a flow simulation program, in the Scenario box, type a name to
specify the simulation scenario.
For more information about Production Data Analysis, see Part X: Reservoir
Production and Simulation, Chapter 5, "Analyzing Production Data."
4 If the imported grid does not include some of the required information, complete
these steps on the General Information tab:
• If the grid origin is not defined in the file, type the coordinates in the X, Y, and Z
boxes to define the grid origin.
• If the map rotation is not defined in the file, type the angle in the Angle
(degrees, clockwise) box.
• If the areal and vertical units of measurement are not defined, click Feet or
Meters under Map units and Grid units.
5 If you want to import all the data contained in the binary file (all initial properties and
time-dependant properties from all report dates) and you do not want to make any
adjustments to the grid position, complete this procedure by clicking OK to import
the file and create the SGrid object.

Otherwise, choose which properties to import and adjust the grid if necessary by
completing the remaining steps in this procedure.

6 To specify initial properties to import:

a On the General Information tab, select the Select individual properties in
the initial properties panel check box.
b Click the Initial Properties tab.
c In the Properties box, select the initial properties that you want to import.
7 To specify time-dependent properties to import:
a Click the General Information tab.
b Select the Select Individual properties in the time-dependent properties
panel check box.
c Click the Time-Dependent Properties tab.
d In the Properties box, select the time-dependent properties.

8 To specify time-stamps for which to import time-dependent properties:
a Click the General Information tab, and then select the Select individual
report dates in the time-dependent properties panel check box.
b Click the Time-Dependent Properties tab, and then under Report dates, do
one of the following:
• To individually select report dates, click Select individual report dates in
the list below, and then select the dates in the list.
• To automatically select the dates according to frequency and start and end
dates, click Select one every n report dates, and then select the frequency
number. In the From and To boxes, select the start and end dates.
Important If you have only one restart file, the extension should be .UNRST
(meaning unified restart ). If you are importing more than one restart file, the
extensions should be .X0000, .X0001, and so on.

9 To change the grid origin or use INSPEC and RSSPEC files, click the Advanced tab.
a To change the origin of the imported grid, click one of the options for the Areal
origin of cells and for the Vertical origin of cells.
For information, see "About the Grid Origin" on page 2-37.
b If you want to use INSPEC and RSSPEC files to describe the arrays contained in
the initial (.INIT) and restart (.UNRST) files, select the Use INSPEC and RSSPEC
files when available check box.
c To automatically build faults, select the Automatically detect faults check box.
For example, you might want to do this if faults are not defined in the file with
the FAULTS keyword.
Note If faults are not defined in the file with the FAULTS keyword, you might want to turn
off the automatic detection of faults, and instead use the ECLIPSE ASCII Faults converter
(File > Import > Reservoir Grid > ECLIPSE ASCII Fault) to add fault data to the imported
grid. For more information, see "Importing an ECLIPSE ASCII Faults File," page 1-61.
You can find the imported grid and properties in the Objects browser in the Flow
Models category. Time-dependent properties appear under Property Groups.

1.11.3 Importing a CMG Grid and Simulation Results
You can import simulation results from a reservoir grid that was generated from the CMG
IMEX 1 black oil simulator. You can then analyze this simulation data in the Production
Data Analysis Workflow (see Part X: Reservoir Production and Simulation, "Analyzing
Production Data" on page 5-1).
In addition to importing the reservoir grid, optionally, you can import time-dependent grid
properties and any associated wells, production data, and well completions.
When you import simulation results, the command creates an SGrid object (and Wells, if
any) and adds the data as object properties.
Important Importing from CMG binary files is only available on Windows platforms and
requires the installation of Microsoft .NET Framework version 2.0. For information about
the installation requirements, see the Installation Guide .
Note You can also import a CMG grid and simulation results directly from the Production Data
Analysis Workflow. For information, see Part X: Reservoir Production and Simulation, "Specifying
Scenarios and Importing Historical Data" on page 5-24.
To import CMG 1 Select File > Import > Reservoir Grid > CMG Grid to open the Import CMG Grid
simulation results and Production Data dialog box.
2 Specify each of the settings as follows:
For this setting Do this

File name Type the path and file name of the CMG .irf or .IRF data file that you want
to import, or click to browse for the file.

Scenario If you plan to work with the data in the Production Data Analysis Workflow
or, later, export the grid to a flow simulation program, type a name to
specify the simulation scenario.
For more information about Production Data Analysis, see Part X: Reservoir
Realization Optionally, type a realization name for the CMG simulation model.
Unit system Specify the unit system for the CMG simulation run by typing in the box.
Valid entries include Metric and Field.
Import properties Select the check box to import any initial and time-dependent properties
(for example, permeability and pressure over time).
Or, clear the check box to import only the grid, excluding any grid
properties.
1. IMEX is a software product available from Computer Modeling Group (CMG).

For this setting Do this

Import Select the check box to import any well production data along with the grid,
productions or clear the check box to exclude any production data.
Import Select the check box to import any completion data along with the grid, or
completions clear the check box to exclude any completion data.
The command imports the CMG grid, creating an SGrid object (and Wells, if any) and
adding any properties and production or injection results as object properties.
Additionally, if you are working in the Production Data Analysis Workflow, you can find
the new data by accessing the Specify Scenarios task in the workflow. In the list of
scenarios, the data location for the named scenario appears as "Session," and the
associated grid is given the name of the .irf or .IRF file. Additionally, you can skip the next
two tasks in the workflow, Load Grid Properties and Load Production Results, for any
CMG scenarios for which you imported grid properties and production or injection results.
For information about specifying scenarios in the workflow, see Part X: Reservoir
Production and Simulation, "Specifying Scenarios and Importing Historical Data" on
page 5-24.

1.11.4 Importing a RESCUE Model (Grids, Horizons,
Faults) File
You can use the RESCUE converter to import .bin data and create an SGrid or a Surface
object. For information on the RESCUE Model and for information about how to import
this type of file, see "Importing a RESCUE Model File" on page 1-32.
1.11.5 Importing a VIP ASCII Grid File

Use the VIP1 ASCII Grid converter to import a VIP ASCII file and create an SGrid object. If
the file contains property values, you can import the grid properties at the same time. For
information about loading property data, see "Importing a VIP ASCII Properties File" on
page 1-60.
To import a VIP file as 1 Select File > Import > Reservoir Grid > SGrid > VIP ASCII Grid to open the Import
an SGrid an SGrid from VIP ASCII file dialog box.
2 In the File name box, enter the path and file name for the file that you want to
import.
3 In the SGrid name box, type a name for the new grid.
4 If you want to specify the size of the grid (for example, if your file does not contain
the NX, NY, and NZ keywords with corresponding directional values), do the
following:
a Select the Specify Grid Size check box.
b Type the number of cells for the I, J, and K directions in the appropriate Number
of cells box.
If you do not specify the size, the converter expects to read the values from the file.
1. VIP is a software product available from Landmark Graphics.

5 If you want to specify the domain or the units for the data in the selected files, click
Advanced to expand the dialog box, and then do the following:
• To change the domain, click Time or Depth.

• To specify the units, select the Specify units of selected files check box, and
then click either Feet, Meters, or Kilometers for the Area units and Depth
unit as necessary.
1.11.6 Importing a VIP or ECLIPSE LGR File

You can use the VIP 1 or ECLIPSE2 LGR converter to add local grid refinements (LGRs) to an
existing SGrid object in your project.
For more information about LGRs, such as why you may want to use them in flow
simulation and a description of the process to create them, see Part X: Reservoir
Production and Simulation, "What Is Upscaling and Downscaling?" on page 2-2.
To import a VIP or 1 To open the import converter, select File > Import > Reservoir Grid:
ECLIPSE LGR file
• VIP LGR. Opens the Import VIP ASCII LGR dialog box.
• ECLIPSE LGR. Opens the Import ECLIPSE ASCII LGR as SGrid dialog box.
import.
3 In the Stratigraphic grid box, enter the name of the existing SGrid object associated
with the local refinement data.
1. VIP is a software product available from Landmark Graphics.

2. ECLIPSE is a software product available from Schlumberger.

4 In the VIP converter, if you want to import property data for the LGRs, select the
Import properties check box, and then enter the path and file name of the file that
contains the property data in the Property file name box.
5 If you plan to work with the LGRs in the LGR and Upscaling Workflow, or later, export
the LGRs to a flow simulation program, type a name to identify the LGRs in the LGR
scenario box (for VIP) or Scenario box (for ECLIPSE).
For more information about LGR scenarios, see Part X: Reservoir Production and
Simulation, "Defining LGR Scenarios and Starting the Export Process" on page 2-118.
1.11.7 Importing ECLIPSE ASCII Properties File

You can use the ECLIPSE ASCII Properties converter to import properties from an ECLIPSE
ASCII file to existing SGrid objects. You can import properties for one or more SGrid
objects at the same time. The file you are importing may contain grid data, but the
converter imports only the property data.
To import ECLIPSE 1 Select File > Import > Reservoir Grid > Properties > ECLIPSE ASCII Properties to
properties into an open the Import ECLIPSE ASCII as SGrid Properties dialog box.
SGrid
2 In the Stratigraphic Grid box, select the names of the existing SGrid objects for
which you want to import the properties. If you have only one SGrid object loaded,
the correct name automatically appears in this box.
import.
Important If you import a property value that already exists in the grid, the
converter overwrites the existing property values with the new (imported)
property values. If you import a property value that does not exist in the grid, the
converter adds that property value to the grid.

1.11.8 Importing an I J K Property File

You can import properties for an existing SGrid or Voxet object from an I J K Property file.
You can apply the data in the file to more than one object in a single import step. The
converter adds the data to existing objects without changing the geometry of the grid.
The mapping of the property data is done by using the grid indexing, IJK-values. The
imported file should be an ASCII text file that contains up to four columns (I, J, K and
Property Value):
Column Meaning Values

1 I 0 to i -1 (as displayed in the Info panel of the grid)
or
1 to i
2 J 0 to i -1 (as displayed in the Info panel of the grid)
or
1 to i
3 K 0 to i -1 (as displayed in the Info panel of the grid)
or
1 to i
4 Value of the NA
property
Notes
• Not all indices are required. If one is missing, the imported value is assigned the no-data value.
• If there is more than one column describing the property, the property will be vectorial, with
each field described by a column.
• The total number of lines in the text file corresponds to the sum of I  J  K .
• If an index is out of range, the line is discarded.
You can easily create an I J K Property file by running a property script on an SGrid. For
example:
print > "File Path" I, J, K, Property Name;
where, File Path is the path where you want to save the file, and Property Name is the
name of the property you want to export.

To import an I J K 1 Select File > Import > Reservoir Grid > Properties > IJK Property to open the
property file to an Import I J K Property-Value File as Grid Property dialog box.
existing SGrid
2 In the Grid Object box, select the files or type the full path and file names of the
existing grid objects you want to update.
3 In the Property box, type or select the name of the property you are going to update.
import.
5 Select the Set as Property Control Node check box, if you want to set the property
values as control nodes, meaning that the values will not be moved (or moved only in
limited directions) when you run any of the Interpolation commands. By default the
property values are changed during any interpolation process (initialize property,
interpolate all properties, or interpolate selected property).
6 Select the indices start at 1 check box if the grid indices in the file start at one. By
default the converter starts the grid indices at zero.
1.11.9 Importing a VIP ASCII Properties File

You can import properties from a VIP ASCII file to an existing SGrid object. You can apply
the property data in this file to more than one SGrid object in a single import step. The
converter adds the data to existing objects without changing the geometry of the grid.
To import VIP 1 Select File > Import > Reservoir Grid > VIP ASCII Properties to open the Import
properties into an VIP ASCII as SGrid Properties dialog box.
existing SGrid

2 In the Stratigraphic Grid box, select the existing SGrid objects for which you want to
import the properties. If you have only one SGrid object in the project, the correct
name automatically appears in this box.
import.
1.11.10 Importing an ECLIPSE ASCII Faults File

Use the ECLIPSE ASCII Faults converter to add fault data to existing SGrid objects. You can
apply the data in this file to more than one SGrid object in a single import step. The
converter adds the fault data to existing objects without changing the geometry of the
grid.
To import ECLIPSE 1 Select File > Import > Reservoir Grid > Fault > ECLIPSE ASCII to open the Import
fault data into an Faults from ECLIPSE ASCII File dialog box.
SGrid
2 In the Stratigraphic grid box, enter the file names of the existing SGrid objects for
which you want to import the fault data. If you have only one SGrid object currently
loaded, the correct name automatically appears in this box.
import.
4 If the grid already contains faults and you want to overwrite them, select the Replace
all existing faults check box.

1.12 Importing Seismic Data
SKUA and GOCAD include converters for importing various files that contain seismic data.
You can create Voxet, Surface, or SGrid objects from these data files.
For information about importing seismic cubes, see:
• "Importing a SEG-Y 3D File as Voxet," page 1-62
• "Importing a VoxelGeo File as a Voxet," page 1-68
• "Importing a 2D SEG-Y File," page 1-68
• "Importing an SEP File," page 1-71
• "Importing a Norsar Depth Cube File," page 1-71
• "Importing a 2D SEG-Y File as Seismic Lines," page 1-72
• "Importing a SeisWorks Colormap," page 1-72
For information about importing seismic lines, see "Importing a 2D SEG-Y File as Seismic
Lines," page 1-72.
For information about importing color maps, see "Importing a SeisWorks Colormap,"
page 1-72.
1.12.1 Importing a SEG-Y 3D File as Voxet

Use the SEG-Y 3D as Voxet converter to create a Voxet object from a 3D SEG-Y file. The
converter creates a three-dimensional Voxet object by reading and interpreting a series of
traces in the data file.
The SEG-Y format is a standard developed by the Society of Exploration Geophysicists
(SEG). It is the most common format used for seismic data in the exploration and
production industry.
Important By default SKUA and GOCAD saves only the link to the file you import—
the data is not copied into your project. You can request that the data be saved in
your project; see step 6.

To import a 3D SEG-Y 1 Select File > Import > Seismic Data > Seismic Cubes > SEG-Y 3D as Voxet to
file as a Voxet open the SEGY 3D to Voxet dialog box.
This example shows a 3D SEG-Y file already selected in the SEG-Y file box so that you
can see what is displayed in the dialog box window.
2 In the SEG-Y file box, enter the path and file name of the file that you want to
import.
3 Review the information in the preview. If the information is correct, skip to step 8. If
you want to edit some of the data, continue to step 4.
User Guide 1.12 Importing Seismic Data 1-63

4 If you want to edit the dimensions in the file, click Settings to edit the SEGY import
settings, and then do any of the following:
Important After you complete your edits (all tabs), you can click Rescan and the
converter will recalculate all the values in the file. Click Close to close the dialog box
and return to the 3D-Seg-Y as Voxet dialog box. Depending on the size of the file,
this process could take a significant amount of time.
• To change the line and trace byte locations, on the Edit Dimensions tab, select
the Override Line and Trace byte location check box and type the correct byte
locations in the boxes.
Note The converter uses trace header keywords to determine where the line and trace
data is located and these values are displayed in the dimmed boxes.
• To change the volume dimensions, select the Override volume dimensions

check box and type the new value in the #Samples in TimeDepth, #Samples
per Inline/Number of Crosslines, and/or the #Samples per Crossline/
Number of Inlines boxes.
• To change the beginning (minimum) and ending (maximum) Inline and Crossline
values, select the Override starting and ending inlines & crossline numbers
check box and type the new values in the Inline number and the Crossline
number boxes.

5 If you want to edit the geometry in the file click the Geometry tab.
Note The Edit Geometry dialog box displays data about the Voxet object geometry, based on
interpretations the converter made during the import process. If the information is incorrect,
you can change the values in this dialog box.
• To change the coordinate byte locations, select the Override Coordinate byte
location.
• To change the volume geometry values, select the Override volume geometry
check box and type the correct values in the boxes.
Note The coordinates represent the Voxet object anchor point as specified by its (X, Y, Z/T)
Origin, location and the step vector coordinates Time/Depth Axis step (Z/T), Inline Step
(X, Y), CrossLine Step (X, Y), Inline End Point (X, Y), and CrossLine End Point (X, Y).

6 If you want to edit values, other than dimensions or geometry, click the Advanced
tab to open the SEGY 3D import settings dialog box.
a To override the sample format, select the Override sample format check box
and then select the format you want. The default is 6.8 bit (non standard).
b Select the Use Trace Weighting Factor check box, if you want the converter to
use the rescaling factor.
Note You can elect to use the rescaling factor at any time, however, it is most effective
when you select an 8-bit format as the Override sample format.
c To override the scaling factor, select the Override Coordinate Scaling check box
and then type the value you want to use in the box. By default, all coordinate
values are unscaled (that is, all coordinates are scaled by a factor of one).
d To override the coordinate format, select the Override Coordinate Format
check box and then select the format you want. The default is 32-bit integer.
e To change the name of the property, type the new name in the Property Name
box. The default is amplitude.
f If you want to specify whether the property is signed, select the Property is
Signed check box. A signed value can be negative, 0 or positive, while an
unsigned value can be only 0 or positive.
Note This option is applicable only for 8 or 16 bit data.
If there are missing traces in the file, select the Some Traces are missing check box.
g If the format of the raw data has the most significant digits stored on the right
(the little end), select the File is a little endian check box. Otherwise, leave the
check box cleared to indicate the order is big endian; that is, an order in which
the "big end" (the most significant digits) are stored first.
Little endian is the format commonly used in the Windows and Linux operating
environments. Big endian is the format commonly used in the UNIX environment.

h Select the Copy SEG-Y data inside GOCAD Project check box, if you want the
converter to copy all the data in your file into the project. By default the
converter saves a link to the file.
i To add a property to an existing Voxet in your project, select the Add property
to an existing Voxet check box, and then select the Voxet.
Note You can add a property only to an existing voxet that has the same number of
samples as the SEGY data. In addition, make sure the orientation of the data is the same
(the three axis directions in the voxet match the directions in the SEGY data).
j The typical workflow for that is that you have many properties for several objects
then you export them to one object that you can work with together in one
voxet.
7 If you want to see the different headers that are in the file, click the SEG-Y Headers
tab to open the SEGY 3D import settings dialog box.
EBCDIC
header
a In the SEGY HEADERS box, the EBCDIC header contains information about the
general content of the file, such as company name, the Voxet object name, the
instruments and processing methods used, and so on. This data is optional, the
converter does not need to read it to import the file.
b The Binary header area contains specific information about the data, such as
the job identification number (jobid), the number of data traces per record (lino),
the measurement system in meters or feet (mfeet), and so on. The converter
requires this data when importing the file.

c Each trace has its own 240-byte header, which can be displayed in the Trace
header area. Type a trace number in the Trace number box, or click Next Trace,
or Prev trace to move from one trace header to another. The converter requires
this data when importing the file.
8 When you are sure that all the data appearing in the dialog boxes is correct, in the
SEGY 3D to Voxet dialog box, click OK or Apply.
1.12.2 Importing a VoxelGeo File as a Voxet

You can use the VoxelGeo converter to create a Voxet object from a VoxelGeo file (8 bytes
only). The converter does not duplicate the geometry of the cube. After you import the
file, you need to edit the geometry of the Voxet by using either of the Voxet commands
(Edit menu) Resize with Points or Resize with Vectors. In a future version, the
geometric information will be read directly from the VoxelGeo file.
1.12.3 Importing a 2D SEG-Y File

Use the 2D SEG-Y as Seismic Line converter to create a SeismicLine object from a 2D SEG-
Y file. The converter creates a SeismicLine object that contains multiple seismic lines by
reading and interpreting a series of traces in the data file.
The 2D SEG-Y as Seismic Line converter supports only post-stack data.
The SEG-Y format is a standard developed by the Society of Exploration Geophysicists
(SEG). It is the most common format used for seismic data in the exploration and
production industry.
Important By default the command saves only the link to the file you import—the
data is not copied into your project. You can request that the data be saved in your
project; see step 4.

To import a 2D SEG-Y 1 Select File > Import > Seismic Data > Seismic Lines > 2D SEG-Y as Seismic Lines
file as seismic lines to open the Import 2D SEG-Y dialog box.
2 In the File name box, enter the path and file name of the 2D SEG-Y file that you
want to import.
3 In the Survey name box, type the name of the survey to associate with the seismic
lines.
A survey carries several seismic lines from a specific seismic acquisition. You group
seismic lines into a survey for easier manipulation.
4 Select the Copy SEG-Y data inside GOCAD Project check box, if you want the
converter to copy all the data in your file into the project. By default the converter
saves a link to the file.

5 To change the coordinate byte locations (index numbers) or the common depth point
location (CDP) that are read from the file, type them in the X byte location, Y byte
location, or CDP byte location boxes.
Note The X byte and Y byte coordinates represent the shot line anchor point of the vertical
trace as specified by its (X, Y) origin location.
6 If necessary, change the geometry data format used to represent floating numbers:
• Integer
• IBM Float
• IEEE Float
7 If you want to manually specify the minimum depth or time, select the specify minzt
check box. If you do not select this check box, the converter computes the value from
the SEG-Y header.
8 If you want to manually specify the maximum depth or time, select the specify
maxzt check box. If you do not select this check box, the converter computes the
value from the SEG-Y header.
• If your SEG-Y file does not contain geometry information, select the Use
navigation data check box and go to step 10.
• If your SEG-Y file contains geometry information, go to step 11.
10 Specify the following information about the navigation file:
a In the Navigation file box, enter the path and file name of the file that you
want to import.
Note The navigation file contains seismic line data that tells the converter how to read the
SEG-Y trace data. You need to specify which columns in the navigation file represent the
The navigation data files should be space delimited and formatted into columns. It should
contain the name of the seismic line, the shotpoint number, and the coordinates, as shown
in the following example:
bh34_112_14_11 1 451346 1390689

bh34_112_14_11 2 451304 1390653
bh34_112_14_11 3 451262 1390617
bh34_112_14_11 4 451220 1390580
bh34_112_14_11 5 451178 1390544
b In the line name box, type the name of the line of data (using this format:
Linename Shotpoint X Y) to be selected inside the navigation file.
Note This entry is required if the navigation file contains multiple lines; otherwise, use the
default line name: none.
c Because the SEG-Y data is ordered by trace, which is rarely the same as a seismic
line, you need to specify the relationship between the trace number in the SEG-Y
file and the seismic line number in the navigation file:
• In the first shot point box, type the seismic line number of the first trace in
the navigation file. The default is 0.
• In the number of trace per sp box, type the number of traces per seismic
line (delta between two seismic lines). The default is 1.
• If the seismic line number decreases with the trace number, select the sp
decrease with trace number check box.

11 If necessary, change the domain and the units used in the imported SEG-Y file by
selecting the Time or Depth option and by selecting the Specify units of selected
files check box, and selecting the units.
To improve performance, seismic lines are not displayed in the 3D Viewer when you
import them. To display them, select the imported seismic lines in the Objects browser. In
addition, the property is not loaded in memory until you display it and apply commands
on it.
1.12.4 Importing an SEP File

You can use the SEP 1 converter to create a Voxet object from a Stanford Exploration
Project (SEPlib) file. The converter reads the axis information from the file and creates a
corresponding Voxet. This converter does not import property data, because it does not
read the binary data file.
To import an SEP file  Select File > Import > Seismic Data > SEP, and then select the file or type the full
as a Voxet path and file name in the dialog box.
1.12.5 Importing a Norsar Depth Cube File

You can use the Norsar Depth Cube converter to create a Voxet object from a Norsar
Interface and a Norsar Trend Map. The converter imports the trend cube as an xyt-Voxet
(time) with x-depth, y-depth and z-depth as extra properties, which are used during the
time-to-depth conversion.
To import Norsar file 1 Select File > Import > Seismic Data > Seismic Cubes > Norsar Depth Cube to
as a Voxet open the Import Norsar 2.1 Object into Gocad dialog box.
1. The Stanford Exploration Project (SEP) is an industry-funded academic consortium devoted to

seismic imaging. SEPlib is a freely distributed seismic data processing software product developed
by SEP.

2 In the Norsar project root box, enter the path and file name of the file you want to
import.
3 In the Norsar object box, enter the path and file name of the file you want to
import.
4 In the object type box, select the type of object being imported. The default is
Interface.
1.12.6 Importing a 2D SEG-Y File as Seismic Lines

Use the 2D SEG-Y as SeismicLine converter to create a SeismicLine object from a 2D SEG-
Y file. For information about how to import a 2D SEG-Y file, see "Importing a 2D SEG-Y
File" on page 1-68.
1.12.7 Importing a SeisWorks Colormap

You can use the SeisWorks converter to create a color map from a SeisWorks Colormap
file.
To import a SeisWorks  Select File > Import > Seismic Data > Colormaps > SeisWorks, and then select the
Colormap file or type the full path and file name in the dialog box.

1.13 Importing Velocity Data

SKUA and GOCAD include converters for importing various files that contain velocity
data. You can create Surface or SGrid objects from these data files.
These topics provide information about the supported import sources for specific objects
and how to import the files.
For information about importing velocity functions, see:
• "Importing a Jason ASCII Traces File," page 1-73
• "Importing a ProMAX File," page 1-73
• "Importing a TDQ (.avf) File," page 1-74
• "Importing a Velf File," page 1-74
For information about importing velocity cubes, see:
• "Importing a SEG-Y 3D as Voxet File," page 1-74
• "Importing an SEP File," page 1-74
• "Importing a VoxelGeo File," page 1-74
For information about importing velocity lines, see:
• "Importing a 2D SEG-Y as Surface File," page 1-74
• "Importing a 2D SEG-Y as SGrid File," page 1-75
1.13.1 Importing a Jason ASCII Traces File

Use the Jason1 ASCII import converter to create a Curve object from a Jason ASCII Traces
file. The command converts the traces into a Curve that has velocity data as properties.
To import a Jason  Select File > Import > Velocity Data > Velocity Functions > Jason ASCII Traces,
trace file and then select the file or type the full path and file name in the dialog box.
1.13.2 Importing a ProMAX File

Use the ProMAX 2 converter to import velocity data from a ProMAX file and create an
object.
To import a Promax  Select File > Import > Velocity Data > Velocity Functions > Promax, and then
file select the file or type the full path and file name in the dialog box.
1. Jason Geoscience Workbench is a software product available from Fugro-Jason BV.

2. ProMAX is a seismic processing software product available from Landmark Graphics.
User Guide 1.13 Importing Velocity Data 1-73

1.13.3 Importing a TDQ (.avf) File
Use the TDQ 1 converter to import velocity data from a TDQ file and create a Curve object.
To import a TDQ file  Select File > Import > Velocity Data > Velocity Functions > TDQ (.avf), and then
as a Curve select the file or type the full path and file name in the dialog box.
1.13.4 Importing a Velf File

Use the Velf converter to import trace data from Western Geophysical to create a Curve
object from a Velf ASCII file.
To import a Velf file Select File > Import > Velocity Data > Velf, and then select the file or type the full path
as a Well and file name in the dialog box.
1.13.5 Importing a SEG-Y 3D as Voxet File

You can use the 3D SEG-Y converter to import SEG-Y data and create a Voxet object. For
information about how to import this type of file, see "Importing a SEG-Y 3D File as
Voxet" on page 1-62.
1.13.6 Importing an SEP File

You can use the SEP converter to import SEP data and create a Voxet object. For
information about how to import this type of file, see "To import an SEP file as a Voxet"
on page 1-71.
1.13.7 Importing a VoxelGeo File

You can use the VoxelGeo converter to import 2D grid data and create a 2D-Grid object.
For information about how to import this type of file, see "Importing a VoxelGeo File as a
Voxet" on page 1-68.
1.13.8 Importing a 2D SEG-Y as Surface File

The 2D SEG-Y-as Surface converter, creates a Cross Section object (carrying the geometry
data) and a Voxet object (carrying the property data).
If your file contains surface data, the converter will create a Surface object.
You can use the 2D SEG-Y converter to import SEG-Y data and create a Surface object.
For information about how to import this type of file, see "Importing a 2D SEG-Y File" on
page 1-68.
1. TDQ is a software product available from Landmark Graphics.

1.13.9 Importing a 2D SEG-Y as SGrid File

You can use the 2D SEG-Y converter to import SEG-Y data and create an SGrid object. For
information about how to import this type of file, see "Importing a 2D SEG-Y File" on
page 1-68.
User Guide 1.13 Importing Velocity Data 1-75

1.14 Importing Well Data
SKUA and GOCAD includes converters for importing several types of well data. For
example, paths, logs, markers, deviations, and picks.
Note Some data formats are listed more than once in these topics because you can import multiple
types of data in these formats. For example, you can import column-based files that contain path
and log data, just path data, or just log data; therefore, you can find information about importing
column-based files in at least three topics.
For information about importing well data, see:

• "Importing Well Paths and Logs," page 1-76
• "Importing Well Paths," page 1-86
• "Importing Well Marker Data from a Column-Based File," page 1-86
• "Importing Well Log Data," page 1-87
• "Importing Well Symbol Data," page 1-89
• "Importing Well Completion Data," page 1-90
• "Importing Well Production Data," page 1-91
1.14.1 Importing Well Paths and Logs

You can import well paths and logs from a column-based file and CPS3, Excel, Irap RMS,
LAS, RC2, Temis3D and WITSML files to create Well objects and well logs.
For information, see:
• "Importing an Excel File," page 1-77
• "Importing an Irap RMS File," page 1-78
• "Importing an LAS File," page 1-79
• "Importing an RC2 File," page 1-84
• "Importing a Temis3D File," page 1-84
• "Importing a WITSML File," page 1-85
Importing a Column-Based File

You can use a column-based file wizard to import path and log data (from an ASCII file)
and create a Well object (or a PointsSet or Curve object), depending on the type of data in
your file. The procedure is similar whether you are importing Well, PointsSet, or Curve
data. For information, see "Common Process for Importing a Column-Based File" on
page 1-8.
Importing a CPS3 ASCII Data (.dat) File

You can use the CPS3 ASCII Data converter to import .dat data and create a PointsSet,
If your file contains well path and log data, the converter creates an object for each well
identified in the file.

Importing an Excel File

You can create a Well object from well data in a Microsoft Excel spreadsheet.
To import an Excel 1 Select File > Import > Well Data > Path and Logs > Excel to open the Import Well
spreadsheet as a Well from excel file dialog box.
3 The default is to import only one sheet from the Excel file. Click all sheets if you
want to import more than one.
4 If you selected
5 one sheet only, type the name of the sheet you want to import in the sheet name
box. If you selected all sheets, the box is unavailable.
6 The well name from sheet name check box is selected by default and the converter
reads the name of the well from the spreadsheet. If you want to specify the well
name, clear the check box and type the name in the Well name box.
7 In the Properties name line box, type the line number that identifies the location of
the property names in the file. The default is 1.
8 In the X name, Y name, Z name, and ZM name boxes, type the name of the
coordinates/properties as they appear in the spreadsheet. The defaults are X, Y, Z, and
ZM respectively.
User Guide 1.14 Importing Well Data 1-77

9 If you want to import an additional property, select the import other properties
check box, and then do the following:
• Type the property name in the properties box
• If the no-data value is different from the default (-99999) type the value in the
No data value box.
Importing an Irap RMS File

Use the Irap RMS converter to create a Well object from an Irap RMS well file. The
converter will import well geometry, well properties, and well markers as a property called
marker.
The converter imports one file at a time and creates one Well object, or adds property
values to an existing Well object.
The Irap RMS converter supports RMS versions up to version 2009.
To import an Irap well 1 Select File > Import > Well Data > Path and Logs > Irap RMS to open the Import
file as a Well Irap RMS as Wells dialog box.
3 In the Null Value box, type the no data value. The default is -999.0.
4 If you want to create actual well markers, select the Create Markers on Block Logs
check box. By default, the converter loads well markers as a Property called markers.
The converter reads the block logs and adds a marker at each value change.

Importing an LAS File

You can use the LAS converter to create a Well object from an LAS 1 ASCII file (up to
version 2.0) or to add data to an existing Well object.
Important If the LAS file does not contain units, you can specify them during the import.
If the LAS file does contain units, the converter automatically uses these units, regardless
of the units that you specify during import.
For more information about importing an LAS file, see:
• "Importing an LAS File as a Well," page 1-79
• "Importing Data from LAS to Update an Existing Well," page 1-83
Importing an LAS File as a Well

Tip Before you import the Based on data contained in the LAS file, the converter creates a Well object with surface
file, ensure that the data is location, logs, picks, and deviation data, or it creates a Well object with incomplete
what you expect it to be and information (you can update the Well object at a later time.)
that the format is correct.
If the LAS file does not contain location data for the Well object, the converter sets the X,
Y, and Z surface location coordinates to zero.
To import a new well 1 Select File > Import > Well Data > Path and Logs > LAS to open the Import LAS
object from an LAS Data Files dialog box.
file
2 Click to browse for and select the files you want to import, and then click Open.
1. The Log ASCII Standard (LAS) was first proposed in 1990 by the Canadian Well Logging Society to
facilitate exchange of digital well log data between logging service companies and clients. It has
since become an industry standard.

3 Choose one of the following options for specifying well location information:
• If the LAS file does not contain well location data (or you do not want to use the
well location data), click Input well location and then do one of the following:
• If you do not want to specify the well location data, leave the default values
in the boxes for the X, Y, and Z coordinates.
• To specify the well location, select the coordinates from the 3D Viewer.
Click and then click (with the resulting crosshair) on the coordinate
locations in the 3D Viewer. The x-, y-, and z-coordinates of the points you
click appear automatically in the X, Y, and Z boxes.
• To use the well location data that is specified in the LAS file, click Well location
in LAS file. Then instruct the converter to search for the location coordinates
within the LAS file you are importing by using keywords that you supply (the
default keywords are XCOORD, YCOORD, and ELEV).
• To use a well location that is specified in a different external file, click Well
location in external file, click to browse for the external file, and then
double-click the file name to enter it in the Well location file box.
4 To load deviation survey data, select the Deviation survey information is in the
LAS file(s) or in external files(s) check box. Another dialog box opens.
Or, if the file does not contain deviation data, skip to step 6.
Important If the LAS file contains deviation survey data and you do not select the
Deviation survey information is in the LAS file(s) or in external file(s) check
box, the converter loads the deviation data as properties and the well path will
appear as a straight line.

a If the deviation data that you want to import is in a separate file:

• Select the Deviations are in external file check box and then, in the
Deviation survey file suffix box (at the bottom of the dialog box), type the
file name extension for the file that contains the deviation data. The default
extension is . dev.
• In the ZM Column box, specify where the converter should look for the
measured depth data values in the deviation file by typing the correct column
number.
b Specify which columns (in the LAS file) contain the TVDSS, X deviation, and Y
deviation data values. The default data columns are 2, 3, and 4, respectively.
c Specify how the converter should interpret the deviation data by clicking the
appropriate option:
• Deviations are absolute values. The dX and dY coordinates represent
actual X, Y locations.
• Deviations are cumulative delta. The dX and dY coordinates are
calculated according to their distance from the well surface location.
• Deviations are incremental delta. The dX and dY coordinates are
calculated according to their distance from the previous point.
d Click Close to close this dialog box and return to Import LAS Data File dialog box.

5 If the LAS file does not contain units, click Options, and then do the following to
specify the units:
Note If the LAS file contains units, the units that you specify in the Import LAS Data Files dialog
box are ignored.
• In the Measured Depth Unit box, select the appropriate units.
• If the z-axis value in the file you are importing differs from the default z-axis set
for your project, change the domain for this new object. To change the z-axis
value from depth to time, or time to depth click the appropriate option.
Note The converter automatically selects units based on the default z-axis setting (in the
New Project dialog box) chosen when the project was created.
• Select the Specify units of selected files check box, and then click the
appropriate area units and depth unit for deviation data.
6 To specify how to import the name of the well, choose one of the following options:
• To use the LAS standard keyword, click Use standard keyword.
• To use the LAS filename, click Use filename.
• To specify a keyword that is used in the LAS file to indicate the well name, click
Specify keyword and then type the keyword.
If the LAS data file contains log data that are integers, the command asks you whether
you want to associate the log to a classification.

Importing Data from LAS to Update an Existing Well

When you import new well logs or picks for an existing Well object, the LAS converter
loads the new data and overwrites all previous logs and picks of the same name.
When you want to import data for an existing Well object, the name of the existing Well
object need to match exactly the well name in the LAS file (the converter is case sensitive).
If it does not find an exact match, the converter creates a new Well object with a default
straight well path.
To import data from 1 Select File > Import > Well Data > Logs > LAS to open the Import Well Log from
an LAS file to update LAS File dialog box.
an existing well
2 Click to browse for and select the files you want to import, and then click Open.
3 To specify the measured depth unit or how to import the name of the well, click
Options for the name of the well, and then do the following as necesary:
• In the Measured depth unit box, select the unit of measurement.
• Specify the well name by selecting one of these options:
• Use standard keyword. Use the LAS standard keyword.

• Use filename. Use the LAS filename.
• Specify keyword. Use a keyword from the LAS file to indicate the well
name. In the Keyword box, type the keyword.
If the LAS data file contains log data that are integers, the command asks you whether
you want to associate the log to a classification.

Importing an RC2 File
Use the RC2 converter to create a Well object from an RC2 ASCII file. The object will
contain well path, logs, and marker data (if that data is in the file).
To import a RC2 file as  Select File > Import > Well Data > Path and Logs > RC2, and then select the file or
a Well type the full path and file name in the dialog box.
Importing a Temis3D File

Use the Temis3D converter to create a Well object from a Temis3D file. The object will
contain well path, logs, and marker data (if that data is in the file).
To import a Temis3D  Select File > Import > Well Data > Path and Logs > Temis3D, and then select the
file as a Well file or type the full path and file name in the dialog box.

Importing a WITSML File

Use the WITSML converter to create a Well object from a WITSML 1 file. The converter
creates one Well object for each file.
To import a WITSML 1 Select File > Import > Well Data > Path and Logs > WITSML to open the Create
file as a Well Well from WITSML File dialog box.
2 Click to browse for the files, and then double-click the file name. The command
automatically enters the selected file names in the File name box.
3 In the Well Location boxes, enter the X, Y, and Z(KB) coordinates for the well.
• If you want to stop the timer to check the data, click stop timer.
• If you want to continue the timer after stop, click continue timer (this is the
default), and type the number of seconds you want to stop between file checks
in the timer interval seconds box.
5 If you want to stop the streaming, clear the keep streaming check box. The default
is to keep streaming, even if the WITSML file does not change.
1. WITSML is an acronym for Wellsite Information Transfer Standard Markup Language and is an
industry standard for transferring data.

1.14.2 Importing Well Paths
You can import well paths from a column-based ASCII or XYZ file or import coordinates
from a column-based file to create a Well object.
For information, see:
• "Importing an X Y Z File," page 1-86
• "Importing Coordinates from a Column-Based File," page 1-86
Importing a Column-Based File

You can use a column-based file wizard to import well path data (from an ASCII file) and
create a Well object (or a PointsSet or Curve object), depending on the type of data in
your file.
Importing an X Y Z File
Use the X Y Z converter to create a Well object from an ASCII file that contains three
columns of well data: X coordinate, Y coordinate, and TVDSS value.
To import an X Y Z file  Select File > Import > Well Data > Path > X Y Z file, and then select the file or type
as a Well the full path and file name in the dialog box.
Importing Coordinates from a Column-Based File

You can use a column-based file wizard to import location data (coordinates) from an
ASCII file and create a PointsSet, Curve, or Well object. For information about how to
import this type of file, see "Common Process for Importing a Column-Based File" on
page 1-8.
1.14.3 Importing Well Marker Data from a Column-

Based File
You can use a column-based file wizard to import and add well marker data (from an
ASCII file) to an existing Well object.
The procedure for using the wizard is similar whether you are importing Well, PointsSet,
or Curve data and therefore is explained only once. For information, see "Common
Process for Importing a Column-Based File" on page 1-8.

1.14.4 Importing Well Log Data

You can import log data from a column-based, LAS, or ASCII file to add logs to existing
Well objects.
For more information, see:
• "Importing Log Data from Column-Based File" on page 1-87
• "Importing Log Data from an LAS File" on page 1-87
• "Importing Log Data from an ASCII File with a Header" on page 1-88
For information about importing image logs, see "Importing Image Files" on page 1-43.
Importing Log Data from Column-Based File

You can use a column-based file wizard to import log data (from an ASCII file) and create
a Well object (or a PointsSet or Curve object), depending on the type of data in your file.
Importing Log Data from an LAS File

You can use the LAS file converter to import an ASCII file and create a Well object or add
data to an existing Well object. For information about how to import this type of file, see
"Importing an LAS File" on page 1-79.

Importing Log Data from an ASCII File with a Header
Use the ASCII File with Header converter to add log data (from an ASCII file) to an existing
Well object.
To import log data for 1 Select File > Import > Well Data > Logs > ASCII File with Header to open the Add
a well Log From Ascii File dialog box.
2 In the Well box, enter the name of the existing Well object.
3 Click to browse for the file you want to import, and then double-click the file
name. The command enters the selected file names in the File name box.
4 In the Z Column name box, type the name of the Z column.
5 Clear the True z check box, if the data value in your file represents measured depth.
6 In the Property Interpolation Method box, select the method you want the
converter to use when estimating a value between two known values.

1.14.5 Importing Well Symbol Data

You can use the Well Status Symbols converter to import well symbol data for existing
Well objects. Typically, symbols define the well status (gas, dry, producer, and so on). The
converter reads from a file with at least two columns: well_name and symbol_type (in the
command, you can indicate which column is which).
For example:
Well1 Gas
Well2 Dry
Notes
• If you experience difficulty importing statuses that include spaces, add quotation marks
surrounding the text in your file.
• You can also edit the well status (change the symbol) for an existing well. For information, see
Part IV: Foundation Modeling, "Setting the Well Status" on page 9-10.
• For users running SKUA from the Paradigm™ Session Manager, the well status that you can set
with this command includes the same list of well symbols that you can assign from the
Paradigm Well Data Manager. For information about sharing well data with other Paradigm
applications or setting well status in an Epos ® project, see:
• Part I: Getting Started, Chapter 4, "Sharing Data with Paradigm Applications."
• Paradigm 2011 Help > Data Management and Import/Export > Well Data Manager >
Assigning Well Symbols.
To import well status 1 Select File > Import > Well Data > Constants > Well Status Symbols to open the
symbols Import Well Symbols dialog box.
3 In the Well Name Column box, type the number for the column that includes the
well names (matching the names of existing wells in the project).
4 In the Symbol Name Column box, type the number for the column that includes the
symbol data.
5 In the Start at Line box, type the line number where you want the converter to start
reading the import file.
The command issues an error message if wells listed in the file are not present in the
project or a symbol listed in the file is an unrecognized type. (To see messages or errors,
select View > Terminal to access the session history.)

1.14.6 Importing Well Completion Data
You can import well completion data from ECLIPSE DATA files related to an existing SGrid
object. The command adds the completions to wells, if necessary, and adds the
completions to the new wells.
Notes
• You can also import completion data along with CMG? or ECLIPSE production data. For
information, see:
• "Importing an ECLIPSE ASCII Grid File," page 1-46
• "Importing a CMG Grid and Simulation Results," page 1-54
• "Importing Well Production Data from an ECLIPSE Binary File," page 1-101
• You can import completion data as well logs by using the column-based file wizard for
importing well paths and logs (File > Import > Well Data > Paths and Logs > Column-Based
File). For more information, see "Common Process for Importing a Column-Based File" on
page 1-8.
To import well 1 Select File > Import > Well Data > Completions > ECLIPSE Data File to open the
completions from an Import ECLIPSE Well Completions dialog box.
ECLIPSE file
2 In the Stratigraphic grid box, enter the name of the SGrid object associated with
the well completion data.
3 Next to the File name box, click browse for the file you want to import (.DATA or
.data files), and then double-click the file name.
4 In the Scenario name box, enter a unique name for the simulation scenario.
The scenario name is useful if you plan to use the data in the Reservoir Simulation
Link Workflow or the Production Data Analysis Workflow.
5 Indicate whether you also want to create properties in the associated grid to store the
completion data by selecting or clearing the Create completion properties check
box. (Initially preselected.)
If selected, the command adds the completion data to both the wells and the grid.
If cleared, the command adds the completion data only to the wells.
After you import completions, you can find them in an object browser.

1.14.7 Importing Well Production Data

You can import historical production data and simulation results from ECLIPSE files and
general format, column-based files.
Note You can also import well production data (wells and well data) from CMG simulation results.
For information, see "Importing a CMG Grid and Simulation Results" on page 1-54.
For more information about importing well production data, see:

• "Importing Well Production Data from a General Format User File or VOL File,"
page 1-91
• "Importing Well Production Data from an ECLIPSE Binary File," page 1-101
• "Importing Well Production Data from an ECLIPSE RSM File," page 1-102
For information about displaying and working with production data after you import it,
see Part IV: Foundation Modeling, "Working with Engineering and Production Data" on
page 9-29.
Importing Well Production Data from a General Format

User File or VOL File
You can use the General Format import wizard to import production data from column-
based user files and VOL1 files. The command adds the data to existing Well objects.
Note The format of VOL files is not strictly column-based. The well name is on a row by itself, and
the production data for that well is in column format following the well name. The converter reads
the columns of data for the first well until it encounters the next well name on a row by itself, and
then begins reading the columns for this well.
This wizard includes many settings that are common to other column-based import
wizards. This topic describes only the steps that are specific to importing production data.
For information about how to configure the common settings, see "Common Process for
Importing a Column-Based File" on page 1-8.
Tip For production data, specifying a no-data value of -99999 prevents null data from appearing as
zeros in production plots. For information about how to specify a no-data value in the wizard, see
step 6 in "To specify the column assignment for a column-based file" on page 1-12.
For more information about importing production data, see:

• "To access the import wizard for column-based production data," page 1-91
• "To specify the production data type and scenario," page 1-92
• "To specify the date format," page 1-93
• "To specify the phase units," page 1-95
• "To specify line and column assignments," page 1-96
To access the import  Select File > Import > Well Data > Production Data > General Format User File
wizard for column- to open the Column as Production Data - General Format wizard.
based production
data
1. VOL is an output format for production data from Schlumberger’s Schedule software.

To specify the After you access the Column as Production Data importing wizard and complete the
production data type common settings on the first pages (see "Common Process for Importing a Column-Based
and scenario File" on page 1-8), specify the type of production data that you are importing and the
scenario as follows:
1 Ensure that the file you want to configure is selected in the Current file box.
2 Specify whether you are importing historical data by selecting or clearing the
Historical production data check box, and then do the following as necessary:
• If you specified historical data, you do not need to define a scenario for this data,
because the command imports historical data into the Project (root) scenario.
• If the production data is not historical, specify the scenario by doing one of the
following:
• To use the file name to identify the scenario, click Use filename.
• To provide a name, click Select or type it, and then enter a unique scenario
name in the box.
• To specify a line in the file that identifies the scenario, click Select line, and
then type the line number in the box, or click , and then click the line in the
preview pane.

The scenario name is useful, for example, to help you differentiate between
multiple sets of production data.
3 Click Next.
To specify the date Specify the date format of the production data as follows:
format
1 For the question What is the type of your dates?, click either:
• Date value. Time is given as a date.
• Elapsed time value. Time is given as years, days, hours, minutes, or seconds.

2 Depending on the date format selected, specify additional information about the data
as necessary:
Setting Description
Elapsed time unit The time is given in years, days, hours, minutes, or seconds.
Date format Click either One column (if the date or time is given in a single column) or
Multiple columns (if the date or time is given in multiple columns), and then
select the date format for the time or the start date.
If you select multiple columns, later in the wizard, on the Line and Column
Assignment page, you can specify what each column represents.
Start date The start date of production (for example, 01/01/1983).
Tip Change the date by highlighting the month, day, or year in the box, and
then increase or decrease the number with the buttons.
3 Specify the type of production data, unit system, and object type as follows:
Setting Description
Data type The data includes daily rates, interval volumes, or total volumes.
Units system The data is given in field, ECLIPSE-metric, or metric units.
Producing object The data includes well data, data from a group of wells, or the entire field.
4 If you want to import production data only for existing wells, ignoring any additional
production data for other wells, select the Load only on existing objects check
box.
5 Click Next.

To specify the phase  On the Selection of the phase units page, the units for each value are preselected
units based on the Units system selected on the prevous page in the wizard. Change the
units for any production value as necessary (following the instructions in the wizard),
and then click Next.

To specify line and 1 On the Line and Column Assignment page, assign each type of data to the
column assignments appropriate column in the file (following the instructions in the wizard), and clear the
check box for any data that is not included in the file.
Notes
• If you indicated that date or time values are given in multiple columns, this page has
additional options for indicating which columns represent each part of the date or time
value (For example, Day column, Month column, and Year column).
• If you are importing a VOL file, Well or Group name column is not available (appears
dimmed). In VOL files, well names are on rows by themselves (not in columns), and the
converter finds the well names automatically.
• The Days produced column should specify the number of days of actual well production
during the specified period. If you indicate that you want to compute missing production
data (see step 2), this number affects the daily production rate calculation. For example, if
production is not a full month, you need to specify the number of actual producing days.

Tip If you calculate this 2 If you want to calculate any missing production data, select the Compute missing
data, you can display it as production data check box.
bubble maps for the wells in
3D and 2D views. For more Depending on the type of production data (cumulative volumes, production rates, or
information, see Part III: interval volumes), the command can calculate:
Visualization, "Displaying
Production Data as Bubble • Production rates from cumulative or interval volume
Maps" on page 3-21. • Cumulative volume from production rate or interval volume
3 When you finish specify the column assignments, complete the steps in "To complete
the importing process" on page 1-14.
Importing Well Production Data from an ECLIPSE Column-

Based File
You can use the ECLIPSE column-based import wizard to import production data from
ECLIPSE files and add the data to existing Well objects.
This wizard includes many settings that are common to other column-based import
wizards. This topic describes only the steps that are specific to importing production data.
For information about how to configure the common settings, see "Common Process for
Importing a Column-Based File" on page 1-8.
Tip For production data, specifying a no-data value of -99999 prevents null data from appearing as
zeros in production plots. For information about how to specify a no-data value in the wizard, see
"To specify the column assignment for a column-based file" on page 1-12.
For more information about importing production data, see:
• "Tips for preparing and importing historical data," page 1-97
• "To access the import wizard for ECLIPSE column-based production data," page 1-98
• "To specify the production data type and date format," page 1-98
• "To specify the production scenario," page 1-99
• "Completing the importing process," page 1-100
Tips for preparing You can easily import ASCII historical data by using the column-based importing wizard as
and importing follows:
historical data • Identify the columns that contain standard ECLIPSE data keywords followed by "H."
For example, historical field oil-production data becomes FOPRH; similarly, historical
well water-cut data becomes WWCTH. For a list of the most common ECLIPSE
keywords, see Part X: Reservoir Production and Simulation, "Primary ECLIPSE
FrontSim production data" on page 5-13.
• Identify the units in the historical data by using these unit identifiers:
• Pressure. barsa and psia
• Rates. sm3/d, stb/d, and Mscf/d
• Ratios. sm3/sm3, Mscf/stb, and stb/stb
• Identify the objects by these names: FIELD, WELL, or GROUP.
The following is an excerpt from a comma-separated values (CSV) file containing historical
field data:
DATE,FPRH,FWPRH,FGPRH,FOPRH
,barsa,sm^3/d,sm^3/d,sm^3/d
,FIELD,FIELD,FIELD,FIELD
1/1/1988,397.8,0.0000,0.0,0.00
1/1/1989,307.6,0.0000,1356750.0,9000.00
1/1/1990,233.7,0.0000,1217807.5,9000.00
4/1/1990,221.9,0.0000,1183632.1,9000.00

In this example, the first line identifies the ECLIPSE data types with an "H" to indicate
historical data. The second line identifies the units for each data type, and the third line
indicates the object, FIELD. The data is delimited by commas, with the date in the first
column followed by pressure, water production rate, gas production rate, and oil
production rate.
To access the import  Select File > Import > Well Data > Production Data > ECLIPSE User File to open
wizard for ECLIPSE the Column as Production Data - ECLIPSE format wizard.
column-based
production data
To specify the After you access the Column as Production Data importing wizard and complete the
production data type common settings on the first pages (see "Common Process for Importing a Column-Based
and date format File" on page 1-8), specify the type of production data that you are importing and the
date format as follows:
1 Ensure that the file you want to configure is selected in the Current file box.
2 For the question What is the type of your production data?, click one of the
options: Historical or ECLIPSE name convention.
Note If the production data names have an "H" at the end of the string (FWPTH, for example)
indicating historical data, you can select either option.

3 For the question What is the format of your dates?, click either:
• Date value. Time is given as a date.
• Elapsed time value. Time is given as years, days, hours, minutes, or seconds.
4 Depending on the date format, specify additional information about the data as
necessary:
Setting Description
Elapsed time unit The time is given in years, days, hours, minutes, or seconds.
Date format The date format for the time or the start date.
Start date The start date of production (for example, 01/01/1983).
Tip Change the date by highlighting the month, day, or year in the box, and
then increase or decrease the number with the buttons.
5 Click Next.
To specify the In the Column as Production Data import wizard, specify the scenario as follows:
production scenario
Note This page appears only if the file does not contain historical data. If the file contains historical
data, the command automatically imports the data into the Project (root) scenario. You cannot
specify a production scenario for historical data.
1 Ensure that the file that you want to configure is selected in the Current file box.

2 Name the production scenario as follows:
• To use the file name to identify the scenario, click Use filename.
• To provide a name, click Select or type it, and then enter a unique scenario
name in the box.
• To specify a line in the file that identifies the scenario, click Select line, and then
type the line number in the box, or click , and then click the line in the preview
pane.
The scenario name is useful, for example, to help you differentiate between multiple
sets of production data.
3 The scenario name is useful, for example, to help you differentiate between multiple
sets of production data.Click Next.
Completing the For more information about configuring the remaining settings in the wizard and how to
importing process complete the importing process, see "Common Process for Importing a Column-Based
File" on page 1-8.

Importing Well Production Data from an ECLIPSE Binary

File
You can use the production data converter to import well production data from an
ECLIPSE binary data file. .The command can add the data to existing wells or create the
wells from simulation data previously imported from ECLIPSE.
Note You can also import well production data from ECLIPSE by using the Production Data Analysis
Workflow. For information, see Part X: Reservoir Production and Simulation, Chapter 5, "Analyzing
Production Data."
To import Production 1 Select File > Import > Well Data > Production Data > ECLIPSE Binary File to open
data for an existing the Import ECLIPSE Binary Production Data dialog box.
Well
2 In the File name box, type the full path and file name or click to browse for the
file.
3 If you want to associate the well production data with simulation results that were
previously imported from ECLIPSE as an SGrid object, select the Use grid check box,
and then enter the grid in the Stratigraphic grid box.
If the wells associated with the production data do not already exist, with this option
selected, the command creates the wells by approximating the well paths from the
grid data and associates the new wells and production data with the selected grid.
If cleared, the command creates the wells without well paths and without associating
them with any existing data.
4 To specify advanced importing options, click Advanced, and then do the following as
necessary.
• Scenario. Type a name to specify a production scenario. If specified, the

command adds the production data to a new or existing scenario.
For information about the workflow, see Part X: Reservoir Production and
Simulation, Chapter 5, "Analyzing Production Data."
• Realization. Type a name to specify the realization.

• Update historical data. Updates any previously imported production data.
If cleared, the command ignores any historical production data in the file.
• Import Completions. Imports any completion data included in the file along
with the production data.
If cleared, the command ignores any completion data in the file.
The command imports the data, creating Well objects (if necessary) and adding the
production data and completions (if any) to the wells. You can find the new production
data and any completions in the Objects browser by expanding the productions or
completions category for the wells.
Importing Well Production Data from an ECLIPSE RSM File

You can import well production data from ECLIPSE RSM files. The command can add the
data to existing wells or create the wells and add the data to the new wells.
To import production 1 Select File > Import > Well Data > Production Data > ECLIPSE RSM file to open
data from an ECLIPSE the Import Production Data from ECLIPSE RSM File dialog box.
RSM file
2 In the File name box, type the file names. Or, click , browse for the file or files,
and then double-click the selected files.
Supported file types include .RSM and .rsm.
3 In the Scenario name box, select an existing scenario or type a name a new
production scenario.
The scenario name is useful if you plan to use the data in the Production Data
Analysis Workflow. For information about the workflow, see Part X: Reservoir
4 The command automatically checks for existing well properties and does not
overwrite them. If you want to overwrite properties, clear the Check existing
properties check box.
5 If you want to calculate any missing production data, select the Compute missing
production data check box.
Depending on the type of production data (cumulative production volumes or
production rates), the command can calculate:
• Production rates from cumulative volume
• Cumulative volume from production rates

The command imports the data, creating wells (if necessary) and adding the production
data and properties (if any) to the wells. You can find the new production data and any
new well properties in the Objects browser by expanding the productions, properties,
or property groups category for the wells.
Note If the wells do not already exist, the command creates the wells without well paths.

1.15 Importing Cross Section Data
When you import a file that contains cross section data, the converter creates a series of
PointsSet, Curve, or Surface objects to store the data, depending upon the type of data in
your file.
• "Importing a DXF File," page 1-104
• "Importing a GeoSec Cross Section File," page 1-104
• "Importing a Locace File," page 1-104
1.15.1 Importing a DXF File

Use the DXF converter to create an object from a .dxf file. If the file contains geometry
data for more than one object, the converter creates a PointsSet, Curve, or Surface object
for each set of geometry data.
For information about how to import a .dxf file, see "To import a .dxf file" on page 1-22.
1.15.2 Importing a GeoSec Cross Section File

You can use an import converter to create an object from a Paradigm™ GeoSec® Cross
Section file, an .ihf file. If the file contains geometry data for more than one object, the
converter creates a Curve or PointsSet object for each set of geometry data. The converter
supports ASCII .ihf files.
To import a Geosec  Select File > Import > CrossSections > Geosec, and then select the file or type the
file as a Curve full path and file name in the dialog box.
1.15.3 Importing a Locace File

You can use the Locace 1 converter to import a Locace file. By default the converter
creates a Curve object from the data in this file.
To import a Locace  Select File > Import > CrossSections > Locace, and then select the file or type the
file as a Curve full path and file name in the dialog box.
1. Locace is a software product available from Beicip-Franlab.

2
Exporting Data
In this chapter • "Converters," page 2-2 • "Exporting Voxet Data," page 2-31
• "Basic Procedures for Exporting • "Exporting Seismic Line Data,"
Data," page 2-4 page 2-35
• "Exporting PointsSet Data," • "Exporting SGrid Data," page 2-36
page 2-19
• "Exporting Well Data," page 2-64
• "Exporting Curve Data," page 2-20
• "Exporting a View as an Image,"
• "Exporting Surface Data," page 2-24 page 2-68
• "Exporting 2D-Grid Data," page 2-28 • "Exporting an SGrid and Data to an
Isatis File," page 2-73
Overview Paradigm™ SKUA ® and Paradigm™ GOCAD ® includes several converters that you can
use to export objects and viewer images to numerous file formats.
You can find the exporting commands from the File menu on the Export submenu. This
submenu is organized first by the object types that you can export and then by file
formats.
These topics explain how to use the data converters to export modeling objects.
You will notice that some file format types are listed more than once on the Export
menus. When SKUA and GOCAD provide support for exporting multiple objects types to
the same file format type, the export option appears under each object type.
Paradigm adds support for new formats based on customer needs. To inquire about new
options, contact us at www.pdgm.com/support.
2-1
2.1 Converters
This table identifies the software programs to which you can export, the object types that
you can export to each software program, and the common extension for the exported
file (where applicable).
Table 2–1 Exportable

You can export this To these programs or data With these common
objects
object type types extensions
PointsSet Custom ASCII .dat, .txt
DXF (AutoCAD) .dxf
FastEdit
Excel .xls
Isatis
Curve Custom ASCII .dat, .txt
DXF .dxf
FastEdit Fault Polygon .dat
IRAP
Medica .fau
SeisWorks Fault Sticks .dat
Z-MAP Faults .zmap
Z-MAP Contours .zmap
Excel .xls
Isatis
Surface CUBIT Facet
Custom ASCII .dat, .txt
DXF .dxf
FastEdit Contours .dat
IRAP
Excel .xls
GMI WellCheck MohrFracs
2D-Grid CPS3 .grd
FastEdit
IRAP
Medica .fau
Z-MAP .zmap
Excel .xls
Isatis
Voxet AVF
DDS
SEGY .sgy, .segy
SEP .H
Velf .velf
VoxelGeo .vol
Excel .xls
Isatis
SGrid CMG
(Continued 1 of 2)
2-2 Exporting Data SKUA® and GOCAD® – Paradigm™ 2011

You can export this To these programs or data With these common
object type types extensions
ECLIPSE ASCII: .grdecl
Binary: .grid, .egrid, .init, .unrst
RESCUE .bin
VIP .cor
AVF .avf
Velf .velf
Temis3D (libnf)
Excel .xls
Isatis
Well IRAP
LAS .las
Well Markers to ASCII
Well Path and Logs to ASCII
Logs to Excel .xls
Viewer images CGM
Picture .jpeg, .bmp, .pbm, .pgm, .png,
.ppm, .rgb, .tiff, .xbm, .xpm
VRML .vrml
SGrid + data Isatis
(Continued 2 of 2)
User Guide 2.1 Converters 2-3

2.2 Basic Procedures for Exporting Data
Each export process requires you to specify information that the converter needs to export
your data. Some converters require only basic information, such as the name of the file or
object that contains your data, while others require more detailed information.
This topic covers the common export procedures that apply to more than one object type.
The subsequent topics in this chapter explain the unique, specialized procedures for
specific converters.
• "Exporting an Object to a Custom ASCII File," page 2-5
• "Exporting an Object to a DFX File," page 2-7
• "Exporting Object Properties to Excel," page 2-7
• "Exporting an Object to an Isatis File," page 2-12
• "Exporting Curves or 2D Grids to a Medica File," page 2-16
• "Exporting Velocity Data to an AVF File," page 2-17
• "Exporting Velocity Data to a Velf File," page 2-18

2.2.1 Exporting an Object to a Custom ASCII File

You can export the data of a PointsSet, Curve, or Surface object to a custom ASCII file.
With a custom ASCII file, you define the columns and choose what information to include
in them.
To export an object to 1 Select File > Export > Object Type (PointsSet, Curve, or Surface) > Custom ASCII
a custom ASCII file to open the Export to Generic ASCII File dialog box.
2 In the Object box, enter the objects to export.

3 In the Output file box, enter the path and file name of the file to which you are
exporting the object. The converter will either create a new file or overwrite an
existing one.
4 To export each object in a separate file, select the Output each object in a separate
file check box.
5 In the Format area, click one of these options:
• To format the columns at a non fixed length, click Delimited (preselected
option).
• To format each column at a fixed length, click Fixed Width.
User Guide 2.2 Basic Procedures for Exporting Data 2-5

6 If you specified the delimited format in step 5, in the Delimeter area, click one of
these options to specify how to set the data format boundaries:
• Space
• Tab
• Comma
• Semi-column
• Custom. If you select this option, type the custom delimeter format (any single
character) in the box.
7 In the Header area, click one of these options:
• If you do not want to output a header, click None.
• If you want to output a header, click As Column Title. The first row will be the
column title.
8 In the Number of fields box, enter a numeric value to determine the number of
fields you want the output file to consist of. The program creates a box in the field
column for each field.
9 For each Field box, select the option you want to assign. The options are:
• Name. Select this option to output the name of the current object in the selected
column.
• Part ID. Select this option to output the part identification number of the current
object in the selected column.
• X, Y, or Z. Select any of these options to output their coordinate data.
• Other existing properties. You can select any additional properties existing on
the object.
Notes
• You can add or remove fields by clicking Add, Insert, and Remove. You can arrange the
sequence by clicking Up and Down.
• The options available here depend on what object you choose above in the Object box.
Each field contains the name, part ID, and the union of all the properties that exist on the
selected objects.

2.2.2 Exporting an Object to a DFX File

Use this procedure to export the geometric data of several objects (PointsSet, Curves, and
Surfaces) to a DXF file.
If you are exporting multiple objects simultaneously, the converter creates a single DFX file
containing separate data for each object.
To export an object to 1 Select File > Export > Object Type (PointsSet, Curve, or Surface) > DFX to open
a DFX file the Export to DXF format dialog box.
2 In the File name box, enter the path and file name of the file to which you are
existing one.
3 In the Objects box, enter the objects to export.
Note If you have just one object loaded, its name automatically appears in the Objects box.
2.2.3 Exporting Object Properties to Excel

Use this procedure to export object properties from SKUA or GOCAD to Excel. You can
export properties of the following object types to Excel:
• PointsSet • Curve
• Surface • 2D-Grid
• Voxet • SGrid
• Well • Solid
• Channel
• "To export object properties to Excel," page 2-8
• "To compute the statistics in Excel," page 2-9
• "2D cross plots," page 2-10
• "To compute a cross plot in Excel," page 2-11

To export object 1 Select File > Export > Object Type (PointsSet, Curve, Surface, 2D-Grid, Voxet,
properties to Excel SGrid, or Well) > Export Properties to Excel to open the Export Properties to Excel
dialog box.
Note If you are exporting a well, then you should click Logs to Excel, not Export Properties
to Excel.
2 In the Objects box, enter the objects to export.

3 In the Properties box, enter the properties to export. You can export any number of
properties.
4 In the Regions box, enter the regions from which the properties will be exported.
5 To adjust the rate of data sampling, move the Sampling rate slider to the setting
that you want, between 0 and 1.
Note The converter can sample the data when you export the properties. You can set the
sampling rate anywhere between 0 and 1. The converter preselects a sampling rate of 1, which
means that the converter exports all the data (no sampling). If you move the slider to 0, then
the converter does not export any data.
After you complete the Export Properties to Excel dialog box, the converter automatically
launches an Excel spreadsheet, which populates with the exported data.

Notes
• This spreadsheet contains information about the object and region selected, the number of
data exported, and the sampling rate. Also, there is a column for each property exported.
• Two macros are available to compute statistics and then cross-plot the selected properties in
Excel.
To compute the 1 On the Excel spreadsheet, click Compute Statistics to display an Excel spreadsheet
statistics in Excel named Statistics Sheet.
2 In the Nb class box, select a numeric value to set the number of bins that display on
a histogram.
3 In the Select source box, click the object source.
Note If you are exporting several objects, you need to specify for which object you want to
compute the distribution. The source name is composed of the name of the object, space, and
region.
4 In the Select property box, click the property to use to compute the statistics.
5 Click Compute Statistics. Excel computes a histogram that presents the property
distribution.

2D cross plots A 2D cross-plot provides:
• A cross plot between two properties.
• The statistics of both properties and the cross-property statistics.

To compute a cross 1 In the Excel spreadsheet, click Compute Cross-Plot to display an Excel spreadsheet
plot in Excel named Cross-Plot Sheet.
2 In the Select source box, click the object source that contains the two properties to
analyze.
Note If you are exporting several objects, you need to specify which object you want to
analyze. The source name is composed by the name of the object, a space, and then region.
3 In the Select property X box, select the property to plot as the X-axis.
4 In the Select property Y box, select the property to plot as the Y-axis.

5 Click Compute Cross Plot. Excel computes a 2D cross-plot that presents the
correlation between the properties.
2.2.4 Exporting an Object to an Isatis File

You can export an object to an Isatis1 file.
Connection with SKUA or GOCAD connects to the Isatis database by using the GTXserver, a program
Isatis provided by Geovariances. This program is installed with Isatis. If you have Isatis installed
on the same machine as SKUA or GOCAD, there is no need to separately download and
install them.
However, if Isatis is not installed, you can download GTXserver, free of charge, directly
from the Geovariances Web site (www.geovariances.com). This program is available for
several platforms.
To access the database, you need to first open a connection with the database and then
use the GTXserver for loading or saving data. The connection closes once the load or save
is done.
1. For information about Isatis, visit Geovariances at www.geovariances.com.

About the GTXserver Typically, a new GTXserver runs from a location on your machine that is designated during
advanced parameters the Isatis installation. Therefore, the default option in the Advanced parameters is Run
GTXserver and the Force GTXserver check box is cleared.
Your particular situation may require you to set different parameters. For example:
• If you do not have Isatis installed, but you have an Isatis database available, you can
extract the GTXserver package from Geovariances Web site, select the Force
GTXserver check box, and then type the path location of the executable file in the
GTXserver box.
• If you need to access a database stored on another machine, you may need to run
GTXserver on that machine. You would click the Use already running GTX server
and then type the entries for the Host Name and Port boxes.
• If the Run GTXserver option is not working, the reason may be that it cannot be
found due to a registry problem or an environment variable. To fix this, you can select
the Force GTXserver check box and reset the location, or click the Use already
running GTX server to run GTXserver manually.
The default values for the advanced parameters are set when you initially use the Export
to Isatis dialog box. The parameters remain set, unless you change them. This prevents
you from having to re-enter the same parameters multiple times.
Architecture of the In Isatis, the GTX_INIT directory contains all of the available studies (this directory is also
Isatis database known as $HOME/.isatis for Linux and %APP_DATA%\Geovariances\Isatis for Windows).
You can reference the location of this directory from the Isatis Help menu by clicking
About.
The structure of each study is:
Isatis objects Isatis contains a set of files corresponding to SKUA and GOCAD object types. This table
shows the relationship between SKUA and GOCAD objects and the corresponding Isatis
file types.
SKUA and GOCAD object Isatis file type

PointsSet or Well PointsSet
Curve Line or 2D fault
2D-Grid 2D regular grid
Surface 3D fault
Voxet 3D regular grid
SGrid 3D regular grid

Properties in the Isatis Properties can be attached to Grids, PointsSets, or Curves.
database
Isatis property types:
• Character variables (string)
• 1-bit variable, defines subsets of objects (equivalent to a region in SKUA and GOCAD)
• Scalar variable
• Macro variable for multi-realization property representation
This table shows the relationship between SKUA and GOCAD properties and the
corresponding Isatis variables.
SKUA and GOCAD property Isatis variable

Region flag Selection variable/1-bit variable
1-dimension float property Float variable
Multidimensional variable Macro variable
To export an object to 1 Select File > Export > Object Type (PointsSet, Curve, Surface, 2D-Grid, Voxet,
an Isatis file SGrid, or Well) > Export Isatis to open the Export VSet to Isatis dialog box.
2 To set the advanced connect parameters, click Advanced to open the Advanced
Connect Parameters dialog box.
Note step 2 and step 3 are necessary only if you need to edit these settings. Typically, you will
not need to change the preselected settings.

3 Do the following:
a Click one of these options:
• Run GTX server. Creates a new GTXserver instance (default).
• Use already running GTX server box. Uses the GTXserver that is currently
running.
b If you clicked the Run GTX server option, and you want to place the GTXserver
in a location other than the default path, select the Force GTXserver check box.
By default, this check box is cleared.
c If you clicked the Run GTX server option, and selected the Force GTXserver
check box, enter the GTXServer path in the GTXServer path box.
Notes
• This path corresponds to the full GTXserver executable path. Normally, this path is in
the bin directory of the Isatis installation path.
• You only have to force the GTXserver executable when you do not have Isatis
installed. If Isatis is installed, GTXserver is automatically installed under Windows.
• For Linux users, you may need to define the GTX_HOME environment variable and
then restart SKUA or GOCAD.
d If you clicked the Use already running GTX server option, and the GTXserver is
running on another machine, type the name of the machine where the server in
running in the Host Name box.
Note The default is localhost. If the GTXserver is running on your machine, skip this step.
e If you clicked the Use already running GTX server option, and the GTXserver is
running on another machine, enter the port number in the Port box.
Note The port is the logical number on which a network program can choose to wait on.
The default port is 5500, Change this setting only if you use the "-port" option of
GTXserver and you are running the server manually.
f In the DATA path box, enter the full data path. This path corresponds to the
Isatis database directory.
g Click OK to return to the Export to Isatis dialog box.

4 Click Connect to connect to the GTXserver.
Note If the connection is successful, the dialog box is made available. If the connection is not
successful, the program displays a message indicating that the connection failed,
5 In the Study box, select the study where the object has to be saved. The list is
activated if the selected database contains at least one study.
6 In the Directory box, select the directory of the selected study where you want to
save the object.
7 In the Gocad Object box, enter the object name to be exported to Isatis.
8 To attach faults to the Isatis file, select the Store Faults check box.
9 In the Fault box, enter the faults to export.
Note You can export the fault curves or fault surfaces at the same time as the 2D-Grid. If you
are exporting a Voxet, this domain is not available.
10 In the Float variables box, enter the float variables to export. Variables are the
equivalent of SKUA and GOCAD properties.
11 In the Regions box, enter the object regions to export to Isatis.
2.2.5 Exporting Curves or 2D Grids to a Medica File

You can export the geometric data of two object types (Curves or 2D-Grids) to a Medica 1
file.
To export an object to 1 Select File > Export > Object Type (Curve or 2D-Grid) > Medica to open the Export
a Medica file 2D-Grid to Medica dialog box.
Note The image below is an example of the Export 2D-Grid to Medica dialog box. The Export
Fault Polygons to Medica (used for exporting curves) is virtually identical (the only difference, aside
from the name of the dialog box, is the name of the object box).
2 For a 2D-Grid, enter the name of the grid in the 2D-Grid object box.
3 For curves, enter the name of the Curve objects in the Curves box.
existing one.
1. Medica is a mapping product embedded in the Temis3D program developed by IFP, and sold by
Beicip. For more information, visit www.beicip.com.

2.2.6 Exporting Velocity Data to an AVF File

You can export velocity properties from a Voxet or SGrid object to an AVF file.
To export an object to 1 Select File > Export > Object Type (Voxet or SGrid) > AVF to open the Export 3D
an AVF file Grid Property to AVF dialog box.
2 In the Grid Object box, select the objects (Voxet or SGrid) to export.
3 In the Property box, select the property name that represents the velocity.
existing one.
5 In the Unit box, select one of these unit types:
• Meters
• Feet
6 In the Function Type box, select the type of velocity function to export:
• Time, average velocity • Time, internal velocity
• Time, RMS velocity • Depth, average velocity
• Depth, internal velocity • Depth, RMS velocity
• Depth, two-way time
Caution If the object you are exporting is large, the export will take longer and the
exported file will require increased disk space.

2.2.7 Exporting Velocity Data to a Velf File
You can export velocity properties from Voxets or SGrids to a Velf file.
To export an object to 1 Select File > Export > Object Type (Voxet or SGrid) > Velf to open the Export 3D
a Velf file Grid Property to Velf dialog box.
2 In the Grid Object box, enter the objects (Voxet or SGrid) to export.
3 In the Property box, select the property name that represents the velocity.
existing one.

2.3 Exporting PointsSet Data

You can export PointsSet data to a FastEdit1 file.
Note You can also export PointsSet data to other file types (see Table 2–2), as described in "Basic
Procedures for Exporting Data" on page 2-4.
Table 2–2 Export formats

for point set data Program or file type For information, see
ASCII "Exporting an Object to a Custom ASCII File" on page 2-5
DXF "Exporting an Object to a DFX File" on page 2-7
Excel "Exporting Object Properties to Excel," page 2-7
Isatis "Exporting an Object to an Isatis File," page 2-12
To export a PointsSet Use this procedure to export PointsSet object to a FastEdit file.
to a FastEdit file 1 Select File > Export > PointsSet > FastEdit to open the Export PointsSet to FastEdit
Scattered Data Format dialog box.
2 In the PointsSet box, enter the point sets to export.

existing one.
1. For information about FastEdit, visit Consolidated Graphics Group at www.cgginc.com.
User Guide 2.3 Exporting PointsSet Data 2-19

2.4 Exporting Curve Data
You can export Curve objects (segmented lines) and associated data to various programs
and data types.
• "Exporting a Curve to a FastEdit Fault Polygon File," page 2-20
• "Exporting a Curve to an IRAP File," page 2-21
• "Exporting a Curve to a SeisWorks Fault Sticks File," page 2-21
• "Exporting a Curve to a Z-MAP Faults File," page 2-22
• "Exporting a Curve to a Z-MAP Contours File," page 2-23
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
curve data to the programs in this table.
Program or file type For information, see

ASCII "Exporting an Object to a Custom ASCII File," page 2-5
DXF "Exporting an Object to a DFX File," page 2-7
Medica "Exporting Curves or 2D Grids to a Medica File," page 2-16
2.4.1 Exporting a Curve to a FastEdit Fault Polygon

File
Use this procedure to export Curve objects to a FastEdit fault polygon file. If you are
exporting more than one Curve, the converter creates a single file containing the data for
each curve in turn.
What is a FastEdit A FastEdit fault polygon file is a simple ASCII file containing a series of X and Y data
polygon file? points, each separated by one or more spaces. A brief header (marked by $$) specifies the
type of file. Each line of the Data portion of the file contains a Segment ID (Part number)
followed by the X and Y data points.
To export Curves to a 1 Select File > Export > Curve > FastEdit to open the Export Curve to FastEdit Fault
FastEdit polygon file Polygon dialog box.
2 In the Curve box, enter the curves to export.

existing one.

2.4.2 Exporting a Curve to an IRAP File

Use this procedure to export the geometry of a Curve to an IRAP1 file.
To export a Curve to 1 Select File > Export > Curve > IRAP to open the Export Curve to Irap Classic Format
an IRAP file dialog box.
2 In the Curve box, enter the Curves to export.

existing one.
2.4.3 Exporting a Curve to a SeisWorks Fault Sticks

File
You can export a Curve object to a SeisWorks2 Fault Sticks file.
To export a Curve to a 1 Select File > Export > Curve > SeisWorks Fault Sticks to open the Export Fault
SeisWorks Fault Sticks polygons to SeisWorks dialog box.
file
2 In the Curve Fault Sticks box, enter the Curve objects that you want to export to a
SeisWorks Fault Sticks file.
existing one.
4 In the Interpreter Name box, type the interpreter name. This is the user name.
5 In the Survey Name box, type the survey name.
1. For information about Irap RMS, visit Roxar at www.roxar.com.

2. For information about SeisWorks, visit Landmark at www.halliburton.com.
User Guide 2.4 Exporting Curve Data 2-21

2.4.4 Exporting a Curve to a Z-MAP Faults File
Use this procedure to export a Curve object (Fault Polygons) into a Z-Map1 ASCII curve
format file.
An ASCII Z-Map curve format file consists of header information followed by a series of
fault polygon location coordinates and associated part numbers.
Z-Map headers The Z-Map header is set off by an @ symbol at the beginning and the end. The header
should contain the keyword "FAULT" or "CARTOGRAPHIC." It can also contain other
information, such as the name of the curve you are importing. However, the converter
ignores most of this data.
Curve data Each line of data contains location information for a single node on the Curve object. A
line consists of three items, each separated by one or more spaces:
• X coordinate
• Y coordinate
• Segment ID (For each new Curve part, the converter creates a new value on this line.)
To export a Curve to a 1 Select File > Export > Curve > Z–MAP Faults to open the Export Fault polygons to
Z–MAP Faults file Z-MAP dialog box.
2 In the Curve Fault Polygons box, enter the curves to export.

existing one.
1. For formation about Z-Map, visit Landmark at www.halliburton.com.

2.4.5 Exporting a Curve to a Z-MAP Contours File

Use this procedure to export a Curve object (contours) into a Z-Map1 ASCII curve format
file.
Curve data Each line of data contains location information for a single node on the Curve object. A
line consists of three items, each separated by one or more spaces:
• X coordinate
• Y coordinate
• Segment ID (For each new Curve part, the converter creates a new value on this line.)
To export a Curve to a 1 Select File > Export > Curve > Z–MAP Contours to open the Export Curves as
Z–MAP Contours file contours to Z-MAP dialog box.
2 In the Curve Contours box, enter the curves to export.

existing one.
1. For information about Z-Map, visit Landmark at www.halliburton.com.
User Guide 2.4 Exporting Curve Data 2-23

2.5 Exporting Surface Data
You can export Surface object data to various programs and data types.
• "Exporting a Surface to a CUBIT Facet File," page 2-24
• "Exporting a Surface to a FastEdit File," page 2-25
• "Exporting a Surface to an IRAP File," page 2-26
• "Exporting a Surface to a GMI WellCheck MohrFracs File," page 2-26
surface data to the programs in this table.

ASCII "Exporting an Object to a Custom ASCII File" on page 2-5
DXF "Exporting an Object to a DFX File" on page 2-7
2.5.1 Exporting a Surface to a CUBIT Facet File

Use this procedure to export a Surface object to a CUBIT 1 Facet file.
To export a Surface to 1 Select File > Export > Surface > CUBIT Facet to open the Export Surface To CUBIT
a CUBIT Facet file Facet ASCII file dialog box.
2 In the Surface box, enter the Surface objects to export.

existing one.
1. For information about CUBIT, visit Sandia at http://cubit.sandia.gov.

2.5.2 Exporting a Surface to a FastEdit File

The Export Surface to FastEdit1 Contours converter computes contours on the surface and
writes the results to the file.
To export a Surface to 1 Select File > Export > Surface > FastEdit to open the Export Surface to FastEdit
a FastEdit file Contours dialog box.
2 In the Surface box, enter the Surface objects, one by one, to export.
3 In the Step box, type a numeric value to specify the interval spacing for the contour
lines created in the FastEdit file.
4 In the Alignment box, type a numeric value to specify the reference value from
which the contour lines are computed. By default, this value is 0.
Note This parameter corresponds to the Contour shift setting in the Style dialog box.
existing one.
1. For information about FastEdit, visit Consolidated Graphic Group at www.cgginc.com.
User Guide 2.5 Exporting Surface Data 2-25

2.5.3 Exporting a Surface to an IRAP File
Use this procedure to export the geometry of a Surface to an IRAP1 file.
To export a Surface to 1 Select File > Export > Surface > IRAP to open the Export Surface To IRMS as Triangle
an IRAP file Surface file dialog box.
2 In the Surface Objects box, enter the surfaces to export.

3 In the Files prefix box, enter the path and file name of the file to which you are
exporting the object.
The converter either creates new files or overwrites existing ones. It creates one file for
each surface. The name of the exported file surface is the prefix defined in the dialog box
concatenated with the surface name.
2.5.4 Exporting a Surface to a GMI WellCheck

MohrFracs File
Use this procedure to export a Surface object to a GMI WellCheck MohrFracs2 file.
To export a Surface to 1 Select File > Export > Surface > GMI WellCheck MohrFracs to open the Export
a GMI WellCheck Surfaces to MohrFracs dialog box.
MohrFracs file
2 In the Surface box, enter the Surface objects to export.

2. For information about GMI WellCheck, visit Geomechanics at www.geomi.com.

3 In the File name prefix box, enter the path and file name of the file to which you are
existing one.
4 In the Dip property box, select the Dip property to export.
5 In the AziDip property box, select the Azimuth property to export.
User Guide 2.5 Exporting Surface Data 2-27

2.6 Exporting 2D-Grid Data
You can export 2D-Grid object (gridded surface) data to various programs and data types.
• "Exporting a 2D-Grid to a CPS3 File," page 2-28
• "Exporting a 2D-Grid to a FastEdit File," page 2-29
• "Exporting 2D-Grid Data to an IRAP File," page 2-29
• "Exporting 2D-Grid Data to a Z-MAP File," page 2-30
2D grid data to the programs in this table.
Program or File Type For information, see

Medica "Exporting Curves or 2D Grids to a Medica File," page 2-16
2.6.1 Exporting a 2D-Grid to a CPS3 File

Use this procedure to export a 2D-Grid object to a CPS31 file.
Note The CPS3 format does not support rotation. If your 2D-Grid is not aligned to XY, the converter
still exports it.
To export a 2D-Grid 1 Select File > Export > 2D-Grid > CPS3 to open the Export 2D-Grid Geometry or
object to a CPS3 file Properties to CPS3 dialog box.
2 In the 2D-Grid Object box, enter the 2D-Grid to export.

3 In the Property box, select the property to export.
existing one.
1. For information about CPS3, visit Schlumberger at www.slb.com.

2.6.2 Exporting a 2D-Grid to a FastEdit File

Use this procedure to export a 2D-Grid object to a FastEdit1 file.
To export a 2D-Grid 1 Select File > Export > 2D-Grid > FastEdit to open the Export 2D-Grid Geometry or
object to a FastEdit Properties to FastEdit dialog box.
file

3 In the Property box, select the property to export along with the 2D-Grid object
geometric data.
existing one.
2.6.3 Exporting 2D-Grid Data to an IRAP File

Use this procedure to export a 2D-Grid object into an IRAP2 RMS Grid file.
To export a 2D-Grid to 1 Select File > Export > 2D-Grid > IRAP to open the Export 2D-Grid Geometry or
an IRAP file Properties to Irap RMS dialog box.

3 In the Property box, enter the property to export with the 2D-Grid geometric data.
existing one.
1. For information about FastEdit, visit Consolidated Graphics Group at www.cgginc.com.

User Guide 2.6 Exporting 2D-Grid Data 2-29

2.6.4 Exporting 2D-Grid Data to a Z-MAP File
Use this procedure to export 2D-Grid geometric and property data into a Z-MAP 1 file.
Note The Z-MAP format does not support rotation. If your 2D-Grid is not aligned to XY, the
converter still exports it.
To export a 2D-Grid to 1 Select File > Export > 2D-Grid > Z-MAP to open the Export 2D-Geometry or
a Z-Map file Properties to Z-MAP dialog box.
2 In the 2D–Grid Object box, enter the 2D-Grid to export.

3 In the Property box, enter the property carried by the 2D-Grid to export.
exporting the object. The converter with either create a new file or overwrite an
existing one.
1. For information about Z-Map, visit Landmark at www.halliburton.com.

2.7 Exporting Voxet Data

You can export Voxet object (volume) data to various programs and data types.
• "Exporting a Voxet to a DDS File," page 2-31
• "Exporting a Voxet to a SEG-Y File," page 2-32
• "Exporting a Voxet to an SEP File," page 2-33
• "Exporting a Voxet to a VoxelGeo File," page 2-34
Voxet data to the programs in this table:

AVF "Exporting Velocity Data to an AVF File," page 2-17
Velf "Exporting Velocity Data to a Velf File," page 2-18
2.7.1 Exporting a Voxet to a DDS File

Use this procedure to export Voxet geometric and property data to a DDS 1 (data
dictionary system) file.
Note The DDS format does not support rotation. If your Voxet is not aligned to XY, the converter
still exports it.
To export a Voxet to a 1 Select File > Export > Voxet > DDS to open the Export Voxet to DDS dialog box.
DDS file
2 In the Voxet box, enter the voxets to export.

3 In the Property box, enter the property carried by the voxet to export.
exporting the object. The converter with either create a new file or overwrite an
existing one.
1. For information about DDS, visit DDS at www.freeusp.org/DDS.
User Guide 2.7 Exporting Voxet Data 2-31

2.7.2 Exporting a Voxet to a SEG-Y File
Use this procedure to export a voxet to a SEG-Y 1 file. You need to supply information
about the minimum inline, delta inline, minimum crossline, delta crossline values, and the
time-depth axis. The converter uses the existing voxet geometry to create a new binary
file that contains a series of data traces.
To export a voxet to a 1 Select File > Export > Voxet > SEGY to open the Export Voxet to SEG-Y dialog box.
SEGY file
2 In the Object box, enter the Voxet objects to export.

3 In the Property box, enter the Voxet property to export.
4 In the Output file box, enter the path and file name of the file to which you are
existing one.
5 In the Axis Name boxes, enter the mapping between the Voxet and the crossline,
inline axes, and vertical axis. For example, indicate if U is time, crossline, or inline, and
then do the same for V and W.
6 In the Start and End boxes, verify the line numbers that correspond to the first and
last inline section, crossline section, and vertical section.
7 To specify where in the SEGY file to store the line, trace, X, and Y information, enter
the byte location (index number) for each value.
Note X and Y represent the coordinates of the location of the vertical trace, Line represents
inline in SEGY, and Trace represents crossline in SEGY.
8 To format the numbers in the IEEE format, clear the Save in IBM format check box.
1. For information about SEG-Y, visit the Society of Exploration Physicists at www.seg.org.

2.7.3 Exporting a Voxet to an SEP File

Use this procedure to export Voxet geometric and property data to an SEP file. The
converter creates two files; a small ASCII file that contains the Voxet geometric data and a
large binary file that contains the Voxet property data.
To export a Voxet to 1 Select File > Export > Voxet > SEP to open the Export Voxet to SEP dialog box.
an SEP file
2 In the Voxet box, enter the voxet to export.

3 In the Property box, enter the property carried by the voxet to export.
existing one.
5 In the Time axis, Crossline axis, and Inline axis boxes, enter U, V, or W.
Note You need to set the mapping between the Voxet and the time, crossline, and
inline axes. Indicate if U is time, crossline, or inline, and then do the same for V and
W.
User Guide 2.7 Exporting Voxet Data 2-33

2.7.4 Exporting a Voxet to a VoxelGeo File
Use this procedure to export a Voxet object to a Paradigm™ VoxelGeo ® data file.
To export a voxet to a 1 Select File > Export > Voxet > VoxelGeo to open the Export Voxet To VoxelGeo
VoxelGeo file dialog box.
2 In the Voxet box, enter the Voxet objects to export.

3 In the Property box, select the property to export along with the Voxet object
geometric data.
existing one.
5 To export the property as an 8-bit property, select the Export in 8-bit check box.
Note If you clear this check box, the converter exports the property as a 32-bit property.

2.8 Exporting Seismic Line Data

You can export seismic line (shotline) data to 2D SEG-Y.
To export seismic 1 Select File > Export > Seismic Lines > SEGY to open the Export Seismic Line to 2D
lines to a 2D SEG-Y SEG-Y dialog box.
file
2 In the Seismic Line Lines box, enter the seismic lines to export.
3 In the Property box, select the property to export along with the seismic line
geometric data.
existing one.
Note If you select several seismic lines to export, the program saves them as multiple files; it
names each file by appending the shot line name to the file name that you provide
( filename_linename.sgy).
5 To format the numbers in the IEEE format, clear the Save in IBM format check box.
User Guide 2.8 Exporting Seismic Line Data 2-35

2.9 Exporting SGrid Data
You can export SGrid object data to various programs and data formats. You can access
these commands from the File menu (Export > SGrid submenu).
Important Exporting and reimporting an SGrid created by using the SKUA Flow
Simulation Grid Workflow breaks the link between the SGrid and the workflow,
removing the ability to use important functionality with the SGrid (for example,
property upscaling from a Geologic Grid object).
• "About the Grid Origin," page 2-37
• "Exporting an SGrid to a CMG File," page 2-38
• "Exporting an SGrid to an ECLIPSE ASCII File," page 2-43
• "Exporting an SGrid to an ECLIPSE Binary File," page 2-51
• "Exporting an SGrid to a RESCUE File," page 2-53
• "Exporting an SGrid to a VIP File," page 2-54
• "Exporting an SGrid to a Temis3D (libnf) File," page 2-59
• "Exporting LGR Data from an SGrid to a Flow Simulator," page 2-59
For information about how to export SGrids to other programs or file types, see "Basic
Procedures for Exporting Data" on page 2-4 and the following:
Program or file type For information see

AVF "Exporting Velocity Data to an AVF File," page 2-17
Velf "Exporting Velocity Data to a Velf File," page 2-18

2.9.1 About the Grid Origin

When you export an SGrid to a flow simulation program, the export converter detects the
origin of your grid and preselects the appropriate settings to change the origin to the
location that the simulation program requires. In most cases, you will not need to change
these settings. However, if you want to change the grid origin or orientation of cells, you
can edit the settings on the Advanced tab in the converter. For example, see Figure 2–1
and Figure 2–2.
Figure 2–1 ECLIPSE grid

origin settings
Figure 2–2 Changing the 2 (max, min) 3 (max, max)

areal origin
Original origin: point 1 (min, min)
Target origin: point 2 (max, min)
I
1 (min, min) 4 (min, max)
J
If the origin of the SGrid in this figure were at point 1 in the bottom-left corner, to change
the origin to point 2 in the upper-left corner, you would specify the new origin at
I = maximum and J = minimum (zero).
User Guide 2.9 Exporting SGrid Data 2-37

2.9.2 Exporting an SGrid to a CMG File
You can export an SGrid object (stratigraphic grid) to a CMG ASCII data file. You can
create a single file that contains both geometric and property information or two or more
separate files. You can export files that contain well path data for any Well objects that
intersect the grid, and you can export multiple properties and multiple wells.
All you need to do to quickly export the grid geometry is to select the grid that you want
to export and specify the path name to save the file. Specifying data for the remaining
items is optional. You only need to enter information for the specific types of data that
you want to export.
Notes
• For exported files that contain well path data, the converter uses the ECLIPSE format, which
CMG can read.
• If you export an SGrid that was created by using the SKUA Flow Simulation Grid Workflow and
the SGrid includes mixed or reverse faults, CMG might not be able to read all the connections
between the cells. This capability requires the CMG keyword SCONNECT, which the converter
does not currently export.
For information about how to specify data in the CMG converter, see:
• "To export grid data from an SGrid to a CMG file," page 2-39
• "To export well data from an SGrid to a CMG file," page 2-41
• "To set the advanced options for exporting to a CMG file," page 2-42
For information about exporting local grid refinement (LGR) data from an SGrid to a CMG
ASCII file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on page 2-59.

To export grid data 1 Select File > Export > SGrid > CMG to open the Export SGrid to CMG File dialog
from an SGrid to a box.
CMG file
2 In the Reservoir Grid box, enter the SGrid to export.

3 To separate the output into two files (one contains geometric information, the other
contains property information), click Separate Files.
Note If you click Separate Files, the dialog box displays two boxes, Output Directory and
Prefix.
4 Specify the output file by doing one of the following:

• If you are generating a single file, enter the path and file name of the file to
which you want to generate the output in the Output File box.
• If you are generating separate files, enter the path to the folder where you want
to generate the output in the Output Directory box, and then type the prefix
that the geometry and property files will share in the Prefix box.
When you carry out the conversion, the command creates two or more data files.
The geometry file has the name prefix_ReservoirGrid.DAT. Each property file has
the file name prefix_PropertyName .DAT (where prefix is the name you specified;
ReservoirName is the name of the SGrid; and PropertyName is the CMG keyword
for that property).
5 If you want to change the units to express the grid geometry, click Feet. Otherwise,
the grid geometry is expressed in meters in the file.

6 To generate a grid property file that does not include geometric information, clear the
Export geometry check box.
7 To specify the CMG keyword for each of the properties that you want to export, do
either of the following as necessary:
• For a property that has an equivalent CMG keyword in the list, select the name of
the property in the Gocad Property box.
For a list of the CMG keywords (Flow Simulator Keyword column) that
correspond to SKUA or GOCAD properties, see Table 2–3 on page 2-40.
• For properties that correspond to custom CMG keywords, add them by using the
blank row at the bottom of the list. You also need to import the corresponding
CMG keyword.
The converter automatically adds an empty row at the end so that you can add
multiple keywords.
Table 2–3 Equivalent CMG keywords
CMG keyword SKUA and GOCAD property CMG keyword SKUA and GOCAD property
POR Porosity. TRANSLI Direction transmissibility multipliers for faces
contacting lower indexed blocks along I.
PERMI I direction absolute permeability. TRANSLJ Direction transmissibility multipliers for faces
contacting lower indexed blocks along J.
PERMJ J direction absolute permeability. TRANSLK Direction transmissibility multipliers for faces
contacting lower indexed blocks along K.
PERMK K direction absolute permeability. S0 Oil saturation.
NETGROSS Net to gross thickness ratios. SW Initial water saturations.
TRANSI Direction transmissibility multipliers along I. RTYPE Rock type number for rock-fluid data.
TRANSJ Direction transmissibility multipliers along J. PTYPE Porosity type number for rock-fluid data.
TRANSK Direction transmissibility multipliers along K NULL Null blocks/cells.

To export well data 1 Select File > Export > SGrid > CMG to open the Export SGrid to CMG File dialog
from an SGrid to a box.
CMG file
2 From the Well Data tab, select the Export Well Data check box to enable the
options for exporting well data.
3 To select the wells to export, enter the well names in the Wells box.
4 In the Well connection file box, enter the full path and file name of the file where
you want save the exported well connection data (for example, the cell geometry
data for any of the grid cells that the wells intersect).
5 In the Well completion file box, enter the full path and file name of the file where
you want to save any exported well completion data.

To set the advanced 1 Select File > Export > SGrid > CMG to open the Export SGrid to CMG File dialog
options for exporting box.
to a CMG file
Note The converter automatically detects the origin of your grid and preselects the settings to
change the areal and vertical origin to the location that the simulation program requires.
2 If you want to change the orientation of the grid relative to the SGrid, on the
Advanced tab, click one of the options for the Areal Origin of Cells and the
Vertical Origin of Cells.
Note CMG requires that the grid origin is in the upper-left corner.
For more information, see "About the Grid Origin" on page 2-37.
3 If you want to restore the preselected settings for the areal and vertical origin, click
Restore Defaults.
4 To reverse the I- and J-axes in the output file, select the Switch I and J axis check
box.
5 To change the unit of the vertical scale in the output file, select the corresponding
factor value to run the unit conversion in the Vertical Scale box.
6 To change the horizontal scale in the output file, select the corresponding factor value
to do the unit conversion in the Horizontal Scale box. (Typically 3.2808 or 0.3048 to
convert meters to feet or feet to meters.)
7 To exclude the inactive cells when writing out the NULL keyword (NULL: Null cells),
clear the Include dead cells for NULL keyword check box.

2.9.3 Exporting an SGrid to an ECLIPSE ASCII File

You can export a stratigraphic grid or SKUA flow simulation grid (SGrid object) as an
ECLIPSE 1 ASCII data file. When you export a grid in ECLIPSE format, you can:
• Create a single file containing both geometric and property information, or create
two or more separate geometry and property files.
• Create files containing well connection and completion data for any Well objects
intersecting the grid.
• Export multiple properties and multiple wells.
• Export fault information, if the grid is a SKUA flow simulation grid created with the
SKUA Flow Simulation Grid Workflow.
You can choose to define faults by using nonneighbor connections (NNCs) or the
MULTNUM keyword. If you choose these methods to define faults, you need to
compute the NNCs or the MULTNUM keyword values before you export the grid. For
information, see Part VIII: 3D Grid Building, "Using NNCs or the MULTNUM Keyword
to Define Faults" on page 2-132.
All you need to do to quickly export grid geometry is to select the grid that you want to
export and specify the path name to save the file. The remaining items are optional. You
only need to enter information for the specific types of data that you want to export.
• "ECLIPSE keywords," page 2-43
• "To export grid data from an SGrid to an ECLIPSE ASCII file," page 2-44
• "To export well data from an SGrid to an ECLIPSE ASCII file," page 2-46
• "To export fault data from an SGrid to an ECLIPSE ASCII file," page 2-47
• "To export region data from an SGrid to an ECLIPSE ASCII file," page 2-48
• "To set the advanced options for exporting an SGrid to an ECLIPSE ASCII file,"
page 2-49
For information about exporting local grid refinement (LGR) data from an SGrid to an
ECLIPSE ASCII file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on
page 2-59.
ECLIPSE keywords Because ECLIPSE requires keywords to define properties, you need to specify the mapping
between the ECLIPSE keyword and the SKUA or GOCAD properties that you want to
export. For information about how to specify the keywords, see step 7 on page 2-45.
1. For information about ECLIPSE, visit Schlumberger at www.slb.com.

To export grid data 1 Select File > Export > SGrid > ECLIPSE > ASCII to open the Export SGrid to ECL File
from an SGrid to an dialog box.
ECLIPSE ASCII file
2 In the Reservoir Grid box, enter the name of the SGrid that you want to export.
3 If you want to generate a single output file that includes the grid geometry and
properties, enter the path and file name where you want to save the file in the
Output File box.
4 If you want to separate the output into two files, one for geometric information and
one for property information, click Separate Files, and then do the following:
a In the Output Directory box, enter the path to the folder where you want to
save the files.
b In the Prefix box, type a prefix for the file names that the geometry and property
files will share.

Note When you carry out the command, the converter creates two or more data files. The
geometry file will have the name prefix_ReservoirGridName .GRDECL. Each property file will
have the prefix_PropertyName.GRDECL. Where PropertyName indicates the ECLIPSE
keyword for the property.
5 If you want to change the units of the grid in the exported file, click Feet. Otherwise
the grid units will be meters.
6 To generate an ASCII property file that contains no geometric information, clear the
Export geometry check box.
7 To specify the ECLIPSE keyword for each of the properties that you want to export,
enter the name of the equivalent property in the Gocad Property box.
ECLIPSE keyword SKUA and GOCAD property

PORO Porosity
PERMX Direction absolute permeabilites along X
PERMY Direction absolute permeabilites along Y
PERMZ Direction absolute permeabilites along Z
NTG Net to gross thickness ratios
ACTNUM Active cell
PORV Grid pore volume
MULTX Direction transmissibility multipliers along X
MULTY Direction transmissibility multipliers along Y
MULTZ Direction transmissibility multipliers along Z
MULTNUM Direction transmissibility across regions
SGAS Initial Gas Saturations
SWAT Initial Water Saturations
SWL Scaled Connate Water Saturations
DZNET Net Thicknesses
Note If you want to export additional properties that correspond to unlisted ECLIPSE keywords,
add them using the blank row at the bottom of this box. You also have to import the
corresponding ECLIPSE keyword. The converter automatically adds a new empty column at the
end.

To export well data 1 Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
from an SGrid to an click the Well Data tab.
ECLIPSE ASCII file
2 Select the Export Well Data check box to enable the exporting options.
3 In the Wells box, enter the names of the wells that you want to export.
4 In the Well Connection File box, enter the path and file name (including the file
name extension .trj) where you want to save the well connection data (for example,
the cell geometry data for any grid cells that the wells intersect).
5 In the Well Completion File (COMPDAT) box, enter the file to which the converter
will export the completion specification data (for example, the cell index for the grid
cells penetrated by the wells, corresponding to the ECLIPSE keyword COMPDAT).
6 To limit the export to only the perforated intervals, select the well property in the
Perforation Log list.
Note You need a log that indicates the perforation of the reservoir (and the log should be
equal to zero when not perforated).

To export fault data 1 Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
from an SGrid to an click the Fault Data tab.
ECLIPSE ASCII file
2 Select the Export Fault Data check box to enable the exporting options.
3 To export the fault data in a separate .FAULTS file, clear the Include it with Grid
Data Output check box.
If you are exporting faults for a SKUA flow simulation grid, the command generates
the following additional files:
• .NNC file. Contains the indexes of the nonneighbor cells (NNCs) and the
transmissibility values. For more information, see Part VIII: 3D Grid Building,
"Using NNCs or the MULTNUM Keyword to Define Faults" on page 2-132.
• .EDITNNC file. Contains the indexes of the nonneighbor cells and the
transmissibility multiplier values. For more information, see Part VIII: 3D Grid
Building, "Computing the MULTNUM Keyword to Describe Faults" on
page 2-133.
To view a sample file that shows the content of these files, see Figure 2–3 on
page 2-47.
Figure 2–3 Sample content from a .EDITNNC file and an .NNC file

To export region data 1 Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
from an SGrid to an click the Region Data tab.
ECLIPSE ASCII file
2 If you do not want to include the region data with the grid data output, clear the
Include Region Data with Grid Data Output check box.
3 In the Region File box, enter the path and file name of the file where you want to
save the exported data. The converter will either create a new file or overwrite one.
4 To specify the ECLIPSE keyword for each of the properties you want to export, enter
the name of the equivalent property in the Gocad Property box.
ECLIPSE keyword Property in SKUA and GOCAD

EQLNUM Equilibration region number
FIPNUM Fluid-in-place region number
PVTNUM PVT region number
SATNUM Saturation function region number
Note If your SGrid has any properties that are not listed in this dialog box, add them by using
the blank rows at the bottom of the list. You need to know the name of the corresponding
ECLIPSE keyword to do this.

To set the advanced 1 Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
options for exporting click the Advanced tab.
an SGrid to an
ECLIPSE ASCII file
2 To specify a local coordinate system for the grid (that is defined by the bottom left of
the SGrid cage), do the following:
a Select the Output MAPAXES check box.
b To specify a different origin point, enter the new coordinates for the Origin in
the X and Y boxes. Otherwise, the converter defines the grid origin as the top
left corner of the SGrid cage.
c To change the direction of the vectors, enter numeric values for the X vector in
the X and Y boxes.
Note An example when you might choose to redefine the vector coordinates is when you
are working in a different coordinate system.

3 To change the origin of the ECLIPSE grid relative to the SGrid, click one of the options
for the Areal Origin of Cells and for the Vertical Origin of Cells.
Note For information, see "About the Grid Origin" on page 2-37.
Restore Defaults.
5 To reverse the I- and J-axes in the output file, select the Switch I and J axis check
box.
6 To change the unit of the vertical scale in the output file, select the corresponding
factor value to run the unit conversion in the Vertical Scale box.
7 To change the horizontal scale in the output file, select the corresponding factor value
to do the unit conversion in the Horizontal Scale box. (Typically 3.2808 or 0.3048 to
convert meters to feet or feet to meters.)
8 In the Grid Data Options area, select any of these check boxes:
• Output PINCH keyword. Generates the ECLIPSE PINCH keyword as part of the
output file.
Note The PINCH keyword generates connections across pinched-out layers.
• Include dead cells for ACTNUM keyword. Indicates which cells are inactive in
the output property when writing out the ACTNUM keyword (ACTNUM: Active
cells).
• Keep GOCAD no-data value. Exports null values that are compatible with SKUA
and GOCAD rather than translating them to ECLIPSE-compatible null values.

2.9.4 Exporting an SGrid to an ECLIPSE Binary File

You can export an SGrid object to an ECLIPSE 1 binary data file. The converter creates two
files: a binary grid file that contains the grid data (the converter generates a binary file
with an extension of .grid), and a .init file that contains information about the initial state
of the reservoir (initial water saturation, pressure, and so on).
For information about exporting local grid refinement (LGR) data from an SGrid to an
ECLIPSE binary file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on
page 2-59.
To export an SGrid to 1 Select File > Export > SGrid > ECLIPSE > Binary to open the Export SGrid to
an ECLIPSE binary file ECLIPSE Binary dialog box.
1. For information about ECLIPSE, visit Schlumberger at www.slb.com.

2 In the Stratigraphic grid box, enter the SGrid object to export.
3 In the File name box, enter the path and file name for the exported file. The
converter will either create a new file or overwrite an existing one.
4 In the Origin Relative to SGrid area, select min or max as the coordinate of the
grid origin for the X, Y, and Z boxes.
Note For information to help you decide which option to choose, see "About the Grid Origin"
on page 2-37.
5 To switch the orientation of U for V, select the Switch U and V check box.
6 If you want to translate the SGrid X, Y, and Z coordinates according to a specified
translation vector, enter numeric values in the X, Y, and Z boxes in the Translate
SGrid by area (this step is optional).
7 To indicate the number that the converter uses to multiply the X and Y coordinates of
the SGrid, type a numeric value in the Convert areal by a factor of box.
Note Use this option when you want to transform the SKUA or GOCAD coordinates in feet
into ECLIPSE coordinates in meters and vice versa.
8 To indicate the number that the converter uses to multiply the Z coordinate of the
SGrid, type a numeric value in the Convert vertically by a factor of box.
Note Use this option when you want to transform SKUA or GOCAD coordinates in feet into
ECLIPSE coordinates in meters and vice versa.
9 To specify the ECLIPSE keyword for the PORV property, enter the name of the
equivalent property in the PORV box. Pore volume (PORV) is required for the file to be
used by ECLIPSE.
10 To specify the ECLIPSE keyword for each of the properties you want to export, enter
the name of the equivalent property in the Gocad Property box.
ECLIPSE ECLIPSE
SKUA and GOCAD property SKUA and GOCAD property
keyword keyword
PORO Porosity FIPNUM Fluid-in-place region number
PERMX Direction absolute permeabilites along X PVTNUM PVT region number
PERMY Direction absolute permeabilites along Y SATNUM Saturation function region number
PERMZ Direction absolute permeabilites along Z SGAS Initial gas saturations
NTG Net to gross thickness ratio SWAT Initial Water Saturation
ACTNUM Active cells SWL Scaled connate water saturation
MULTX Direction transmissibility multipliers along X TOPS Depth of the top face of each grid block
MULTY Direction transmissibility multipliers along Y DX Direction bloc size along X
MULTZ Direction transmissibility multipliers along Z DY Direction bloc size along Y
PORV Grid pore volume DZ Direction bloc size along Z
EQLNUM Equilibration region number DZNET Net thicknesses

2.9.5 Exporting an SGrid to a RESCUE File

You can convert an SGrid object into a RESCUE1 ASCII or binary grid file (up to
version 35). The converter exports the SGrid geometry (including split nodes and dead
cells) and property data. The converter also exports the associated fault surfaces as
triangulated surfaces.
Export tips Ensure that all horizon and fault surfaces used to construct the SGrid are present in the
project. If you constructed the SGrid using the SKUA Flow Simulation Grid Workflow or
the GOCAD 3D Reservoir Grid Building Workflow, most of the information needed by the
converter is automatically provided.
For information about creating SGrids with:
• SKUA Flow Simulation Grid Workflow, see Part VIII: 3D Grid Building, Chapter 3,
"Building a Flow Simulation Grid in SKUA."
• GOCAD 3D Reservoir Grid Building Workflow, see Part VIII: 3D Grid Building,
Chapter 6, "Building a 3D Reservoir Grid in GOCAD."
Each of the SGrid FaceSets links to a set of grid faces attached to a fault of the same
name. If the SGrid has no FaceSets, or if you have not assigned the FaceSets to specific
faults, the converter only exports the grid, not the fault surfaces.
Before exporting an SGrid to RESCUE, verify that all the fault surfaces are loaded into the
project and that all the FaceSets are assigned to faults. You can do this by selecting the
SGrid in the Style dialog box and opening the Advanced page.
If no FaceSets are listed in the Style dialog box, the export converter cannot retrieve any
fault data. If any FaceSets are listed as "lost faces," assign each of these lost faces to a
real fault by using the following commands:
• In GOCAD, use the Rename/Merge Faults command (see Part VIII: 3D Grid Building,
"Editing Faults," page 6-115).
• In SKUA, use the Rename Grid Fault command (SGrid commands > Tools).
1. For information about RESCUE, visit the Petrotechnical Open Standards Consortium at
www.posc.org/rescue.

To export an SGrid to 1 Select File > Export > SGrid > RESCUE to open the Export SGrid to RESCUE dialog
a RESCUE file box.
2 In the Stratigraphic grid box, enter the SGrids to export.

3 In the File name box, enter the RESCUE output path and file name.
4 To save the RESCUE file as a binary grid file, select the Binary file check box. If toggle
is off, the file will be saved as a RESCUE ASCII grid file.
5 In the Version number box, type the numeric value to indicate the RESCUE version
that you are exporting to.
6 If you want to export layers, horizons, and fault surfaces, select the Export
structural model check box.
2.9.6 Exporting an SGrid to a VIP File

Use this procedure to export a SGrid object to an VIP 1 file.
In this export converter, all you need to do to quickly export the grid geometry is to select
the grid that you want to export and specify the path name to save the file. Specifying
data for the remaining items is optional. You only need to enter information for the
specific types of data that you want to export.
For information about how to specify data in the VIP converter, see:
• "To export grid data to a VIP file," page 2-55
• "To export wells data to a VIP file," page 2-56
• "To export fault data to a VIP file," page 2-57
• "To export region data to a VIP file," page 2-57
• "To set the advanced options for exporting data to a VIP file," page 2-58
For information about exporting local grid refinement (LGR) data from an SGrid to a VIP
file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on page 2-59.
1. For information about VIP, visit Landmark at www.halliburton.com.

To export grid data to 1 Select File > Export > SGrid > VIP to open the Export SGrid to VIP File dialog box.
a VIP file
2 In the Reservoir grid box, enter the SGrid to export.

3 To separate the output into two files (one contains geometric information, the other
contains property information), click Separate files.
Note If you click Separate files, the dialog box displays two boxes, Output directory and
Prefix.

• If you are generating a single file, enter the file and location to which you want
to generate the output in the Output file box.
• If you are generating separate files, enter the location to which you want to
generate the output in the Output directory box, and then type the prefix that
the geometry and property files will share in the Prefix box.
Note When you run the converter, it creates two or more data files. The geometry file has
the name prefix_ Reservoir Grid Name.COR added to it. Each property file has the
prefix_Property Name.COR added to it (where Reservoir Grid Name indicates the name of
the SGrid and Property Name indicates the VIP keyword for that particular Property).
5 In the Export grid in the following unit area, click Feet if you want to export the
grid in feet.
6 To generate an ASCII grid property file that contains no geometric information, clear
the Export geometry check box.

7 To specify the VIP keyword for each of the properties you want to export, enter the
name of the equivalent property in the Gocad property box.
VIP keyword SKUA and GOCAD property

NETGRS Net to gross
POR Porosity
KX Permeability in X
KY Permeability in Y
KZ Permeability in Z
SWR Residual water saturation
SWRO Calculated water saturation at residual oil
SGR Residual gas saturation
SGRO Calculated gas saturation at residual oil
SO Oil saturation
SG Gas saturation
SW Water saturation
Note If you want to export additional properties that correspond to unlisted VIP keywords, add
them using the blank row at the bottom of this box. You also have to import the corresponding
VIP keyword. The converter automatically adds a new empty column at the end.
To export wells data 1 Select File > Export > SGrid > VIP to open the dialog box, and then click the Well
to a VIP file Data tab.
2 Select the Export Well Data check box to enable the exporting options.
3 To select the wells to export, enter the well names in the Wells box.
4 In the FPERF well file box, enter the path and file name (including the file name
extension, .trj) for the exported file. The converter will either create a new file or
overwrite an existing one.

To export fault data 1 Select File > Export > SGrid > VIP to open the dialog box, and then click the Fault
2 Select the Export Fault Data check box to enable the exporting options.
3 In the Fault File box, enter path and file name of the file to which you are exporting
the object. The converter will either create a new file or overwrite an existing one.
4 If you want to compute the transmissibility, select the Compute transmissibility
check box, and then select the permeability property in the Permeability Property
box.
The property data is required for use in the VIP transmissibility formula:
d1 + d2
Transmissibility = area/length × ----------------------------- , where k i = permeability in the cell.
d d
 -----1- +  -----2-
   
k1 k2
5 If you do not want to export the transmissibility, clear the Compute transmissibility
check box.
To export region data 1 Select File > Export > SGrid > VIP to open the dialog box, and then click the Region
2 Select the Export Regions check box, to enable the exporting options.

3 In the Region File box, enter the path and file name of the file to which you are
existing one.
4 In the Regions box, enter the names of the regions that you want to export.
To set the advanced 1 Select File > Export > SGrid > VIP to open the dialog box, and then click the
options for exporting Advanced tab.
data to a VIP file
2 To change the orientation of the VIP grid relative to the SGrid, click one of the options
for the Areal Origin of Cells and for the Vertical Origin of Cells.
Note VIP requires that the grid origin is in the upper-left corner.
For more information, see "About the Grid Origin" on page 2-37.
Restore Defaults.
4 To reverse the I and J-axes in the output file, select the Switch I and J axis check
box.
5 To change the unit of the vertical scale in the output file to a negative, click the
corresponding factor value in the Vertical Scale box to convert the unit.
6 To change the horizontal scale in the output file to a negative, select -1 in the
Horizontal Scale box.

2.9.7 Exporting an SGrid to a Temis3D (libnf) File

Use this procedure to export an SGrid to a Temis3D1 file.
To export an SGrid to 1 Select File > Export > SGrid > Temis3D to open the Save SGrid Geometry and
a Temis3D file Properties as Temis3D Format dialog box.
2 In the SGrid box, enter the SGrid object that you want to export.
3 In the Lithology box, select the discrete property that represents the lithology.
4 In the Output Type Format box, select Binary or ASCII.
5 In the Directory box, enter the path to the folder where you want to save the
exported file. The converter will either create a new file or overwrite an existing one.
2.9.8 Exporting LGR Data from an SGrid to a Flow

Simulator
With the LGR and Upscaling module, you can export local grid refinements (LGRs) within
a stratigraphic grid along with property data to a flow simulation program. With this
module, you can export LGRs in ASCII format to the CMG, ECLIPSE, and VIP flow
simulators, and in binary format to ECLIPSE.
Note For more information about LGRs, such as why you may want to use them in flow simulation
and a description of the process to create them, see Part X: Reservoir Production and Simulation,
"What Is Upscaling and Downscaling?" on page 2-2.
Caution ECLIPSE requires that the names of LGRs are eight characters or less. If you
export LGRs with longer names, the converter truncates the names, which may cause
ambiguity if the names are similar. In this case, you should rename the LGRs before
you export them.
Binary format. When you export an SGrid in the ECLIPSE binary format, you do not need
to specify any special information for LGRs. The exported GRID file (*.grid) automatically
includes the geometry of the grid and all LGRs within the grid, and the INIT file (*.init)
contains the property data, which is the same for the grid and the LGRs.
1. For information about Temis3D, visit Beicip at www.beicip.com.

ASCII format. When you export an SGrid in ASCII format to a flow simulator, in the
export converter, you will see an additional tab (LGR) for you to specify information about
LGRs (see Figure 2–4). The information that you need to specify is similar for all of the
ASCII file types that you can export.
For information about the prerequisites and the steps to specify this information, see:
• "Prerequisites for exporting LGRs," page 2-61
• "To export local grid refinements (LGRs) to an ECL, VIP, or CMG ASCII file," page 2-61
Figure 2–4 LGR export options

Prerequisites for Before you can export LGRs, you will need to do the following.
exporting LGRs
For information about this See this topic
Load the LGR and Upscaling Part I: Getting Started, "Choosing Modules for a Project," page 1-11
module
Import or create LGRs within Part II: Data Import and Export, "Importing an ECLIPSE ASCII Grid File,"
an SGrid object* page 1-46 or "Importing a VIP or ECLIPSE LGR File," page 1-57
– or –
*ECLIPSE requires LGR names Part X: Reservoir Production and Simulation, "Creating Local Grid
of eight characters or less. Refinements (LGRs)," page 2-90
Define an LGR export Part X: Reservoir Production and Simulation, "Defining LGR Export
scenario 1 Scenarios for Flow Simulation," page 2-111
1. The ECLIPSE binary converter does not support LGR export scenarios. This converter automatically
exports all LGRs within the grid.
To export local grid After you define an LGR export scenario for the LGRs in your grid, do the following:
refinements (LGRs) to
1 Select File > Export > SGrid, and then, depending on the simulator that you selected
an ECL, VIP, or CMG in the export scenario, click either CMG or VIP or point to ECLIPSE and click ASCII.
ASCII file
Note You can also open the export converter from:
• The context menu for the SGrid object in the Objects browser (right-click the name of the
grid to access the menu).
• The LGR and Upscaling Workflow in the Defining LGR Export Scenarios > Define Scenarios
and Export task).
2 If necessary enter the name of the stratigraphic grid (SGrid object) that contains the
LGRs in the Reservoir Grid box.
3 Click the LGR tab, and then select the Export LGR check box to enable the export
options.
4 In the LGR file box, enter a path and file name (including the file name extension,
.lgr) for the exported file.

5 In the LGR export scenario box, select the name of the scenario (that you created in
the LGR and Upscaling Workflow), which contains the list of LGRs that you want to
export from the selected grid.
Review the names of the LGRs in the Scenario Content list.

6 If you want to export property data along with each LGR, select the Export
properties check box.
7 In the ECLIPSE converter, do the following:
a If you want to include any AMALGAM keyword data that you specified in the LGR
export scenario, select the Export AMALGAM keyword check box.
For information about how to specify the data for the keyword in the LGR and
Upscaling Workflow, see Part X: Reservoir Production and Simulation, "Defining
LGR Export Scenarios for Flow Simulation" on page 2-111.
b Click Check LGR names to determine if the names of the LGRs are compatible
with the ECLIPSE requirement (that is, eight characters or less).
The converter displays a message if you need to rename any of the LGRs.
Caution If you rename any of the LGRs, you will need to resave the LGR export
scenario from the LGR and Upscaling Workflow, and then reselect the scenario in
the converter.
8 In the VIP converter, if you want to include any OMIT or INGRID keyword data that
you specified in the LGR export scenario, select the Export OMIT and INGRID
keywords check box.
For information about how to specify the data for the keyword in the LGR and
Upscaling Workflow, see Part X: Reservoir Production and Simulation, "Defining LGR
Export Scenarios for Flow Simulation" on page 2-111.

9 To export additional data from the selected SGrid, click another tab in the converter
and enter information as necessary. For information, see:
• "Exporting an SGrid to an ECLIPSE ASCII File" on page 2-43
• "Exporting an SGrid to a VIP File" on page 2-54
• "Exporting an SGrid to a CMG File" on page 2-38
Carrying out the command converts the LGR data to ASCII format and saves the file in the
folder that you specified.

2.10 Exporting Well Data
You can export Well object data to various programs and data types.
• "Exporting a Well to an IRAP File," page 2-64
• "Exporting a Well to an LAS File," page 2-65
• "Exporting Well Markers to an ASCII File," page 2-66
• "Exporting Well Logs to an ASCII File," page 2-67
Well object data to Excel. For information, see "Exporting Object Properties to Excel" on
page 2-7.
2.10.1 Exporting a Well to an IRAP File

Use this procedure to export the properties and the geometry of a Well to an IRAP1 file.
To export a Well to an 1 Select File > Export > Wells > IRAP to open the Export Wells To Irap RMS dialog
IRAP file box.
2 In the Curve box, enter the Wells to export.

exporting the object. The converter either creates a new file, or overwrites an existing
one.

2.10.2 Exporting a Well to an LAS File

Use this procedure to export Well objects to an LAS 1 file.
To export a Well to an 1 Select File > Export > Well > LAS to open the Export Wells To LAS dialog box.
LAS file
2 In the Wells box, enter the Well objects to export.

one.
Note The converter adds the well name to the file prefix.
4 In the Property box, enter the properties to export.

5 To export the X,Y, and TVDSS data, select the Include deviation check box.
6 To resample the curves at the specified sampling intervals, do the following:
a Select the Specify sampling check box.
b In the Sampling interval box, type a numeric value to indicate the distance
between each sample.
1. For information about LAS, visit the Canadian Well Logging Society at http://cwls.org.
User Guide 2.10 Exporting Well Data 2-65

2.10.3 Exporting Well Markers to an ASCII File
Use this procedure to export a well markers to an ASCII file.
To export well 1 Select File > Export > Well > Well Markers to ASCII to open the Export Well
markers to an ASCII Markers to ASCII file dialog box.
file
2 In the Wells box, enter the Well objects to export.

one.
4 To specify markers, do the following:
a Select the Specify markers check box.
b In the Marker names box, enter the list of markers to export.
5 To export Dip and Azimuth data, select the Export Dip and Azimuth check box.
Note When you select this check box, two columns are added to the file, Dip and Azimuth
(from North), in a clockwise direction. The angle is in degrees.

2.10.4 Exporting Well Logs to an ASCII File

You can use the converter to export well log data for one or more wells to an ASCII file.
Note From a well section view, you can also export all the logs displayed in the view to a comma-
separated values (CSV) file. For information, see Part III: Visualization, "Exporting Logs to a CSV File"
on page 4-138.
To export well logs to 1 Select File > Export > Well > Well Path and Logs to ASCII to open the Export Well
an ASCII file Curves as a Column File dialog box.
2 In the Wells box, enter the wells to export.

one.
4 In the Region box, select the region for which you want to export the curve data.
5 In the Properties box, enter the properties to export.
User Guide 2.10 Exporting Well Data 2-67

2.11 Exporting a View as an Image
You can export the active view to various programs and data types.
• "Exporting a View to a CGM File," page 2-68
• "Exporting a View to an Image File," page 2-70
• "Exporting a 3D Viewer Image to a VRML File," page 2-71
2.11.1 Exporting a View to a CGM File

You can export the displayed view to a CGM file, and then you can send the CGM file that
you create to a plotter for printing.
To export a 1 Select File > Export > View > CGM from 3D Viewer to open the Print Window to a
3D Viewer image to a CGM File dialog box.
CGM file
2 In the Camera box, enter the name of the view that you want to export.
The view name appears on the title bar for the view window. (Or, if the view is
maximized, the view name appears on the title bar of the SKUA or GOCAD window).
3 In the CGM file box, enter the path and file name of the file to which you are
one.
4 To define the plot dimension, click one of these options:
• Use height. If you select this option, you need to specify a height. This number
corresponds to the plot height in centimeters.

• Use scale. If you select this option, you need to define a scale factor. This
number, which is in real world units, corresponds to one plot centimeter.
5 Do one of the following steps:
• If you clicked Use height, type a numeric value in the Height cm box to specify
the height number.
• If you clicked Use scale, type a numeric value in the Scale box to define the scale
factor.
6 To adjust the DPI (dots per inch) setting, type a numeric value in the Dots per inch
box.
Note Dots per inch (DPI) is a measure of printing resolution, in particular the number of
individual dots of ink a printer or toner can produce within a linear one-inch space. The
converter only uses this number when a raster interpolation is required.
7 In the CGM encoding box, select one of these options to determine how the
converter encodes the exported CGM file:
• binary
• clear text
Note Binary is quicker and more compact than clear text but cannot be edited.
User Guide 2.11 Exporting a View as an Image 2-69

2.11.2 Exporting a View to an Image File
You can export the display in a 3D, 2D, or plot view to an image file. Supported file
formats include:
• BMP • ICO
• JPEG • JPG
• PNG • PPM
• TIF • TIFF
• XBM • XPM
The command takes a screen capture of the image at the same size and scale as it appears
on screen. Any dialog boxes obscuring the view are also captured. Before you carry out
the command, you should clear the view of any overlapping windows.
To export a view to 1 With the view open and set up how you want it to appear in the image, do one of the
an image file following to open the Snapshot dialog box:
• Select File > Export > View > Snapshot.
• From the 3D Viewer, on the 3D Viewer toolbar, click Save Snapshot As .
• From a 2D view or plot view, on the File toolbar, click Snapshot .
2 In the View box or Camera box (as applicable), enter the name of the view that you
want to export.
3 Specify where you want to save the file by doing one of the following:
• Click Save in project. Save the image file in the project folder (*.prj). With this
option, the image will be available for review in the Images browser, on the
Results tab.
• Click External file, and then in the Snapshot file box, enter the path and file
name where you want to save the image.
With this option, the command either creates a file or overwrites an existing one.
4 In the User comment box, type any text that you want to associate with the image.

If you save the image in the project, this text appears below the image in the Images
browser.
5 In the Image format box, select the file format that you want to use to save the
image.
6 If you want to specify the size of the image, select the Resize snapshot check box,
and then type numeric values (in pixels) in the Width and Height boxes. (In the
3D Viewer, the maximum is 2000 by 2000 pixels.)
If cleared, the command takes a screen capture of the view at the same size and scale
as it appears on screen.
Note If you are working with a remote connection with limited graphics support or with an
early version of OpenGL, such as OpenGL 1.1, resizing is not supported.
You can find the new image file by using a file management program to browse to the
folder you specified. And, if you saved the file to the project folder, you can also view the
file by using the Images browser on the Results tab (for more information, see Part IV:
Foundation Modeling, "Reviewing and Comparing Images" on page 17-14).
2.11.3 Exporting a 3D Viewer Image to a VRML File

You can export the contents of the 3D Viewer to a single VRML1 2.0 file.
VRML export The converter does not support 2D and 3D textures. All Voxet sections and 2D images
limitations appear as white in the VRML file.
The Predefine Viewpoint function may not work in some VRML viewers.
To export a 1 Select File > Export > Camera > VRML to open the Print Window to VRML dialog
3D Viewer image to a box.
VRML file
2 In the Camera box, enter the name of the view that you want to export.
1. For information about VRML format, visit the Web 3D Consortium at www.web3d.org/x3d/vrml.
User Guide 2.11 Exporting a View as an Image 2-71

3 In the VRML file box, enter the path name of the file to which you are exporting the
object. The command will either create a new file or overwrite an existing one.
4 To save data (such as geometry and shading) from the hidden parts of objects, select
the Add back face information check box.
Notes
• Select this option to overcome the effects of backface culling that occur with some VRML
viewers.
• If you select back face culling (not selecting and drawing what is not in front of the 3D
view), any object or part of an object (such as triangles, nodes, or other objects) that face
away from your point of view is eliminated.

2.12 Exporting an SGrid and Data to an Isatis

File
You can export an SGrid along with other objects (usually, point sets or wells), creating a
regular 3D Isatis 1 grid. The converter exports the additional object with the coordinates
modified to maintain the correlation between the object and the SGrid cells that it
crosses.
Connection with SKUA or GOCAD connects to the Isatis database by using the GTXserver, a program
Isatis provided by Geovariances. This program is installed with Isatis. So if you have Isatis
installed on the same machine as SKUA or GOCAD, there is no need to do a separate
download and install.
However, if you do not have Isatis installed, you can download this program, free of
charge, directly from the Geovariances Web site (www.geovariances.com). This program is
available for several platforms.
To access to the database, you need to first open a connection with the database and
then use the GTXserver for loading or saving data. The connection is closes once the load
or save is done.
About the GTXserver Typically, a new GTXserver runs from a location on your machine that is designated during
advanced parameters the Isatis installation. Therefore, the default option in the Advanced parameters is Run
GTXserver and the Force GTXserver check box is cleared.
Depending on your situation, you may need to set different parameters. For example:
• If you do not have Isatis installed, but you have an Isatis database available, you can
extract the GTXserver package from Geovariances Web site, select the Force
GTXserver check box, and then type the path location of the executable file in the
GTXserver box.
• If you need to access a database stored on another machine, you may need to run
GTXserver on that machine. You would click the Use already running GTX server
and then type the entries for the Host Name and Port boxes.
• If the Run GTXserver option is not working, the reason may be that it cannot be
found due to a registry problem or an environment variable. To fix this, you can select
the Force GTXserver check box and reset the location, or click the Use already
running GTX server to run GTXserver manually.
The preselected values for the advanced parameters are set when you initially use the
Export to Isatis command. The parameters remain set, unless you change them.
1. For information about Isatis, visit Geovariances at www.geovariances.com.
User Guide 2.12 Exporting an SGrid and Data to an Isatis File 2-73
Architecture of the In Isatis, the GTX_INIT directory contains all of the available studies (this directory is also
Isatis database known as $HOME/.isatis for UNIX and %APP_DATA%\Geovariances\Isatis for Windows).
You can reference the location of this directory from the Isatis Help menu by clicking
clicking About.
The structure of each study is:
Isatis objects Isatis contains a set of files corresponding to SKUA and GOCAD objects. This table shows
the relationship between the object types and the corresponding Isatis file types.
SKUA and GOCAD object Isatis file type

PointsSet or Well PointsSet
Curve Line or 2D fault
2D-Grid 2D regular grid
Surface 3D fault
Voxet 3D regular grid
SGrid 3D regular grid
Properties in the Isatis Properties can be attached to Grids, PointsSets, or Curves. Isatis property types:
database
• Character variables (string)
• 1-bit variable, defines subsets of objects (equivalent to SKUA or GOCAD regions)
• Scalar variable
• Macro variable for multi-realization property representation
This table shows the relationship between the SKUA and GOCAD properties and the
corresponding Isatis variables.
SKUA and GOCAD property Isatis variable

Region flag Selection variable/1-bit variable
1-dimension float property Float variable
Multidimensional variable Macro variable

To export an SGrid 1 Select File > Export > SGrid + Data > Isatis to open the Export unit to Isatis dialog
and data to an Isatis box.
file
2 To set the advanced connect parameters, click Advanced to open the Advanced
Connect Parameters dialog box, and then do the following:
Note Steps 2 is necessary only if you need to maintain these parameters. Once set, you will not
have to complete these steps.
a Click one of these options:

• Run GTX server. Creates a new GTXserver instance (default).
• Use already running GTX server box. Uses the GTXserver that is currently
running.
b If you clicked the Run GTX server option, and you want to place the GTXserver
in a location other than the default path, select the Force GTXserver check box.
User Guide 2.12 Exporting an SGrid and Data to an Isatis File 2-75
c If you clicked the Run GTX server option, and selected the Force GTXserver
check box, enter the GTXServer path in the GTXServer path box.
Notes
• This path corresponds to the full GTXserver executable path. Normally, this path is in
the bin directory of the Isatis installation path.
• You only have to force the GTXserver executable when you do not have Isatis
installed. If Isatis is installed, GTXserver is automatically installed under Windows.
• For Linux users, if necessary, you may need to define the GTX_HOME environment
variable and restart SKUA or GOCAD.
d If you clicked the Use already running GTX server option, and the GTXserver is
running on another machine, type the name of the machine where the server in
running in the Host Name box.
Note The default entry is localhost. If the GTXserver is running on your machine, skip this
step.
e If you clicked the Use already running GTX server option, and the GTXserver is
running on another machine, enter the port number in the Port box.
Note The port is logical number on which a network program can choose to wait on. The
default port is 5500, Change this setting only if you use the "-port" option of GTXserver
and you are running the server manually.
f In the DATA path box, enter the full data path. This path corresponds to the
Isatis database directory.
g Click OK to return to the Export to Isatis dialog box.
3 In the DX, DY, and DZ boxes, type numeric values to set the direction block size
parameters.
4 To export the grid properties, select the Export grid properties check box.
5 To export the original data coordinates, select the Export original data coordinates
check box.
6 In the Study box, select the corresponding Isatis study.
7 In the Directory box, select the directory you are exporting to.
8 In the Gocad Grid object box, enter the SGrid to export.
9 In the Gocad Data object box, enter the data object to export.

A
Appendix A Import File
Formats
In this appendix • "Import File Formats," page A-2 • "MPath Formats," page A-22
• "Column-Based Formats," page A-4 • "SEG-Y Formats," page A-26
• "CMG Formats," page A-5 • "SEP Format," page A-28
• "CPS3 Formats," page A-6 • "Velf Format," page A-29
• "ECLIPSE Formats," page A-12 • "VIP Formats," page A-33
• "FastEdit Formats," page A-14 • "Z-MAP Formats," page A-31
• "Irap RMS Formats," page A-16 • "XYZ Format," page A-30
• "LAS Format," page A-20
Overview In Paradigm™ SKUA ® and Paradigm™ GOCAD ® , where possible, the import converters
provide a high degree of flexibility and can identify and import data files without requiring
rigid file formats. However, some converters, because of the specific data being imported,
require explicit formatting and precise data to import a file. This appendix describes the
converters and file format requirements.
Table A–1 on page A-2 is a summary of the file formats that you can import.
A-1
A.1 Import File Formats
The following is a summary of the supported import file formats:
Table A–1 Import file formats
With this common With this common

Data format (or program) Data format (or program)
extension extension
Adobe contours .esp LAS .las
ArcView .dbf, .shp, and .shx Locace .ext
ASCII file with header Locations from column-based file
AutoCAD .dxf Medica Fault Polygons .fau
Charisma fault interpretations Medica Topographic Surface .g
Charisma fault polygons Medica Topographic Surface Advanced .g
Charisma horizon points .gridexp MPath .act, .fid, .raw, .par
Column-based file Norsar depth cube
Completion Norsar horizons
CPS3 ASCII 2D grid .grd Octopus
CPS3 ASCII data .dat Petrel pillars .dat
CPS3 ASCII fault traces .flt PetroMod .pmb
CPS3 ASCII polygon .ply Promax
CPS3 binary .svd, .svs, .svf, .svp RC2 .gz, .asc, .out
Digital Elevation Model (DEM) binary1 RC2 2D grid .gz
DEM ER Mapper1 .ers RESCUE (grids, horizons, faults) .bin
Dip ASCII file with header 1 SEG-Y 2D as SGrid .sgy, .segy
Dip column-based file 1 SEG-Y 2D as Surface .sgy, .segy
DXF .dxf SEG-Y 3D as Voxet .sgy, .segy
ECLIPSE .DATA file .data SeisWorks .clr
ECLIPSE ASCII faults Seisworks cultural data .asc
ECLIPSE ASCII grid .grdecl SeisWorks fault polygons
ECLIPSE ASCII properties .grdecl Seisworks fault sticks .dat
ECLIPSE binary files Seisworks Inline Xline X Y Z .asc
ECLIPSE binary grid .grid, .egrid, .init, SEP .h
.unrst
ECLIPSE column-based user file StrataModel 2D grid .smg
ECLIPSE RSM file StrataModel 2D grid property .smg
Excel .xls TDQ .avf
FastEdit 2D grid .dat Temis3D
FastEdit fault polygons Temis3D Colormap
FastEdit horizon contours .dat Temis3D Grid .td4
FastEdit scattered data .dat Velf .velf
General format column-based files VIP ASCII grid .cor
Geoprobe 2D grid .gvw VIP ASCII properties .cor
Paradigm™ Geosec ® .ihf VIP LGR .lgr
GSLib 2D map Paradigm™ VoxelGeo® .vol
I J K property Well Status Symbols
Images WITSML .gz, .xml
(Continued 1 of 2)
A-2 Import File Formats SKUA® and GOCAD® – Paradigm™ 2011

With this common With this common

Data format (or program) Data format (or program)
extension extension
Irap RMS .log, .decode XYZ
Irap RMS ASCII 2D-grid property Z-MAP ASCII 2D grid
Irap RMS fault polygons or lines Z-MAP ASCII 2D grid property
Irap RMS triangle surface .dat Z-MAP contour .zmap
Jason ASCII traces Z-MAP fault or contour
(Jason Geoscience Workbench)
(Continued 2 of 2)
1. You can import DEM and Dip data with the Structural Analysis (Kine3D-1) module. For more information about importing
DEMs and Dips, see Part VII: Geologic Interpretation, "Importing a DEM" on page 4-13 and "Importing Dip Data" on
page 4-30.
User Guide A.1 Import File Formats A-3

A.2 Column-Based Formats
The converter for column-based files lets you import the following types of data:
• Fault interpretation data to create a PointsSet or Curve object (including property
data)
• Horizon interpretation data to create a Curve object (including property data)
• Well data (including paths, logs, and markers) to create a Well object
The converter expects to read a set of points from an ASCII file that contains columns of
data. The file should contain a column of X data, a column of Y data, a column of Z data,
and (optionally) additional columns for different properties. The file does not have to be
structured.
Free-form or fixed- The file format can be either free-form (fields are separated by blanks and/or
width columns tabs) or fixed-width columns (each column can be of a different width).
Column position The X, Y, Z coordinate values do not have to be the first three columns.
Properties In addition to the required X, Y, Z coordinates, you can import additional
property values by specifying, for each additional property, a property name and
its corresponding data column position in a line.
Partial importing By default the converter reads the entire file, but you can also import just a
portion of the file. This also means that you can read in different parts of the
same file separately if they represent different objects or have different formats
or information.
Object name The converter can read the object name from the file, or you can specify the
name of the object during the import procedure (in the appropriate dialog box).
Here are two examples of column-based file formats. Each column is separated by one or
more spaces.
Free-format 89 19007.7265625 14363.2675781 -6132.31298828 0.22135 2

(delimited), used for 90 18584.1503906 14835.2939453 -6198.53662109 0.2 2
91 19126.3125 15011.7792969 -6135.501953312 0.209244 2
PointsSet objects 92 18594.4609375 15469.2011719 -6217.72705078 0.176622 2
.
.
.
99 1684.2617188 14603.4023438 -6507.99951172 0.146733 2
Free-format GEOLOGICAL TYPE top

(delimited) used for PROPERTY_CLASS_HEADER Z
*lov_clip:5696.36
Curve objects *high_clip:-5309.55
*pclip:99
Inline
1 764073.6875 1032205 -7518.53759766
2 763926.75 1032205 -7528.90478516
3 763779.75 1032205 -7539.27197266
4 763632.8125 1032205 -7527.42871094
.
.
.
15 763322 1031785.25 -7504.46435547

A.3 CMG Formats

Each run of the CMG IMEX black oil simulator creates an Output file (OUT), Index Results
File (IRF), and Main Results File (MRF). The IRF and MRF work together. Thus, an IRF is not
useful without an MRF and vice versa. The IRF contains an index of the MRF—that is, the
IRF is a user-readable ASCII file that provides details about the contents of the binary MRF.
Important If you plan to use IMEX data in the Production Data Analysis Workflow, you
need, at least, the IRF and the MRF files.
User Guide A.3 CMG Formats A-5

A.4 CPS3 Formats
The converter for CPS3 ASCII files lets you import the following types of data to create a
PointsSet, Curve, Well, or 2D-Grid object.
Data in the ASCII file Creates this object

X, Y, Z PointsSet or Curve
X, Y, TVDSS, MD Well
X, Y Curve
Fault trace Curve
• X, Y,
• X, Y, Z
• X, Y, Object name
• X, Y, X, Object name
2D grid data - Z (or W) 2D-Grid
coordinates
Data in your binary file Creates this object

.svd PointsSet
.svf or .svp Curve
.svs 2D-Grid
CPS3 X, Y, Z format You choose whether to create a PointsSet, a Curve, or a Well object from an X, Y, Z ASCII
data file, depending upon the type of data in your file. The converter expects to read a file
that contains header data followed by a series of coordinates and data values (depending
upon which object you want to create).
Header The converter ignores all data in the header, except for the FFASCI or FDASCI
keywords. If either of these keywords are present, the converter reads the number
following the keyword as the no-data-value.
Data The converter expects to start reading data immediately following an arrow symbol (-
>).
The data portion should contain xyz-coordinates in columns separated by one or
more spaces.
This sample file contains X, Y, and Z coordinates that you can import as a PointsSet or
Curve object.
FDASCI 0 1 "Computed" 0 1E30 0

FDATTR 4 2 2 0
FDATNM 1 "TimeInterpretation real"
! Coordinate System:
! Secondary Horizontal : Units: m Per/Meter: 1.0000000000
! Geodetic Datum : NAD27 Ellipsoid CL66
(3E15.7)
-> Grid: AA, red, 1, TimeInterpretaion, [ms]
0.11272825E+07 0.2307070E+06 0.2664000E+04
0.11272825E+07 0.2311172E+06 0.2656000E+04
0.11272825E+07 0.2315224E+06 0.2612000E+04

CPS3 X, Y, TVDSS, MD The converter imports an ASCII file that contains X, Y, TVDSS, and MD data as a Well
format object.
Header The converter expects to read a series of standard well-related keywords that provide
information about the well.
Required keywords:
FDASCI
FDATTR
FDATNM
Lines with an exclamation point (!) in column one are comments; the converter
ignores these lines.
>).
• The data portion should contain xy-coordinates in columns one and two, and
TVDSS values in column three. If MD values are included, they should be in
column four. Each column should be separated by one or more spaces.
• The name of the well should immediately follow the arrow symbol (->); if the file
contains data for more than one well, a new arrow symbol and a new well name
should appear at the start of each.
Note The converter assumes TVDSS coordinates are elevation values (negative
subsea values). If your data represents depth (positive subsea values), you can
run a script (Z = -Z;) that will correct the problem by inverting the well data. For
information, see "Applying a Script on an Object Property" on page 12-33.
Here is an example file that contains X, Y, TVDSS, and MD data for a well named 30/6-1.
FDASCI 0 1 "Computed" 0 1E30 0

FDATTR 4 2 2 0
FDATNM 1 "TimeInterpretation real"
.
.
.
(3E15.7)
-> 30/6-1
0.11272825E+07 0.2307070E+06 0.2664000E+04 0.0000000E+03
0.11272825E+07 0.2311172E+06 0.2656000E+04 0.0188000E+03
0.11272825E+07 0.2315224E+06 0.2500000E+02 0.2722000E+04
.
.
.
User Guide A.4 CPS3 Formats A-7

CPS3 X, Y polygons The converter imports a CPS3 ASCII polygons (.ply) as a Curve object. The converter
format expects an ASCII file that contains header data followed by a series of xy-coordinates.
Header The converter ignores all header data. This file usually contains a single line of text,
in parentheses, that describes the format of the data.
>).
The data portion should contain two columns of xy-coordinates, with each column
separated by one or more spaces.
If the imported Curve object has several separate segments (parts), each part should
be designated by a new arrow symbol and segment ID.
Here is an example file that contains X, Y coordinates for two polygons: (2E15.7) and
(P-2a). The converter will create one Curve object with two parts, from the data in this
file.
(2E15.7)
->
0.1280157E+07 0.2583688E+06
0.1287104E+07 0.2458821E+06
0.5128826E+07 0.2419755E+06
->
.
.
.
(P-2a)
0.12875781E+07 0.2563888E+06
0.12857812E+07 0.2452881E+06
0.51284826E+07 0.2419556E+06
.
.
.

CPS3 fault trace The converter imports CPS3 ASCII fault trace data (.flt) as a Curve object. The converter
format expects an ASCII file that contains header data followed by a series of coordinates.
Header The converter requires the FFASCI keyword be in the header.

Data The converter starts reading data immediately following an arrow symbol (->)
The data portion can contain up to four (but should have at least two columns)
of coordinates (or values), with each column separated by one or more spaces. The
converter expects coordinates or data as follows:
2 columns: X, Y
3 columns: X, Y, Z (if the third column is a number) or X, Y, object name (if the third
column is a word)
4 columns: X, Y, Z, object name
If the imported Curve object has several separate segments (parts), each part should
be designated by a new arrow symbol and segment ID, and the segment ID becomes
a part of the Curve object name.
Here is an example file that contains three columns of X, Y, Z data coordinates.
FFASCI 0 1 "Computed" 0 1E30 0

FDATTR 4 2 2 0
(3E15.7)
.
.
.
-> F 1
0.11272825E+07 0.2307070E+06 0.2664000E+04
0.11272825E+07 0.2311172E+06 0.2656000E+04
0.11272825E+07 0.2315224E+06 0.2500000E+02

CPS3 2D grid format The converter expects to read a CPS3 ASCII 2D grid file (.grd) and create a 2D-Grid object.
It can read the common-keyword format and the individual-parameters format.
Header In the common-keyword and the individual-parameters formats, the header should
contain a series of required keywords (unique for each format) followed by
information that tells the converter how to read the file and construct the grid.
Lines in the header portion of the file that contain comments should have an
exclamation point (!) in column one.
Data The data portion of the file begins immediately following an arrow symbol (->). The
converter expects to read z-coordinates for the 2D grid defined in the header. Each
coordinate identifies the z-location of a particular grid node. The nodes are laid out
column by column, row by row, starting in the upper-left corner of the grid and
moving down along the y-axis.
Important The grid origin is always located (top view) in the lower-right corner. In CPS3 data, the
origin is always located in the upper-left corner.
Required keywords
Common-keyword format Individual-parameters format

• FSASCI - specifies the no-data-value (The • FSASCI - specifies the no-data-value (The
converter ignores all coordinates with this converter ignores all coordinates with this
value.) value.)
• FLSIMI - defines the limits of the 2D grid • XMIN - minimum limit value for X
as follows: XMIN, XMAX, YMIN, YMAX, • XMAX - maximum limit value for X
ZMIN, and ZMAX • YMAX - maximum limit value for Y
Note The converter ignores the ZMIN and • YMIN - minimum limit value for Y
ZMAX keywords.
• FSNROW - defines the number of grid • XINC - Increment between 2-grid cells
lines along the x- and y-axes along x-axis
• FSXINC - defines the increment between • YINC - increment between 2-grid cells
2-grid cells along the x- and y-axes along y-axis
• NCOL - defines the number of grid lines
along the x-axis
• NROW - defines the number of grid lines
along the x-axis
Note All keywords (except for FSASCI) in this
format should be non-CPS3 keywords.

Here is an example file that shows the common keyword format.
! Comments must start with an exclamation point in column one.

FSASCI 0 1 "Computed" 0 1E30 0
FSATTR 4 2 2 0
FSLIMI 1272825.0 1290105.0 230707.00 262067.00 1260.5129 1470.5430
FSROW 197 109
FSXINC 160.00000 160.00000
.
.
.
->Grid of TimeInterpretation
0.11272825E+04 0.2307070E+04 0.2664000E+04 0.11235625E+04
0.11272825E+04 0.2311172E+04 0.2656000E+04 0.13452825E+04
0.11272825E+04 0.2315224E+04 0.2500000E+02 0.36572825E+04
.
.
.
Here is an example file that shows the individual parameters format
! Comments must start with an exclamation point in column one.

FSASCI 0 1 "Computed" 0 1E30 0
!Grod :attoce" Gemeroc Bomset
!VOI B0X XMIN 421850.00000
! XMAX 441250.00000
! YMIN 6797250.0000
! YMAX 6283650.0000
.
.
.
->Default
0.11272825E+04 0.2307070E+04 0.2664000E+04 0.11235625E+04
0.11272825E+04 0.2311172E+04 0.2656000E+04 0.13452825E+04
0.11272825E+04 0.2315224E+04 0.2500000E+02 0.36572825E+04
.
.
.
CPS3 Binary Data

The converter can import a CPS3 binary Fortran-formatted file. This file should contain
control-point data that the converter will use to create a PointsSet or Curve object or X, Y
grid data and Z property data that the converter will use to create a 2D-Grid object.
CPS3 .svd format The converter expects an .svd file to contain X, Y, Z data.
CPS3 .svs format The converter expects an .svs file to contain X and Y grid data and Z property data.

A.5 ECLIPSE Formats
The ECLIPSE converters include ASCII, properties, binary, and RSM.
• "ECLIPSE ASCII format," page A-12
• "ECLIPSE properties," page A-13
• "ECLIPSE binary format," page A-13
ECLIPSE ASCII format The ECLIPSE ASCII Grid converter expects to read an ASCII file that contains header data
followed by a series of keyword-defined data columns.
The converter expects the file to describe a Cartesian grid with corner point geometry.
The converter does not recognize radial grid and block centered geometry. Comments
may appear anywhere in the file.
The following ECLIPSE keywords are listed, by section, according to where they should
appear in the file. Within the section, the keywords can appear in any sequence.
Section Keyword Definition

GRID MAPUNITS Units used for MAPAXES data
MAPAXES Input of pre-processor map origin
GRIDUNIT Grid data units
COORD Coordinate lines
ZCORN Depths of grid block corners
TOPS Depth of the top face of each grid block
DX Block size along direction X
DY Block size along direction Y
DZ Block size along direction Z
PORO Porosity
DZNET Net thickness
NTG Net-to-gross thickness ratios
ACTNUM The nature of the SGrid cells (active or inactive).
Inactive cells are not included in any computation.
PERMX Absolute permeabilities along direction X
PERMY Absolute permeabilities along direction Y
PERMZ Absolute permeabilities along direction Z
MULTX Direction transmissibility multipliers along X
MULTY Direction transmissibility multipliers along Y
MULTZ Direction transmissibility multipliers along Z
EDIT PORV Grid pore volume
REGION Note The converter loads Region keywords (those with an NUM
suffix) as properties and regions.
FIPNUM Fluid-in-place region number
SATNUM Saturation function region number
EQLNUM Equilibration region number
PVTNUM PVT region number
SOLUTION SWAT Water saturation in every grid block
SGAS Gas saturation in every grid block
SGL Scaled connate gas saturations
SCHEDULE BOX Redefine the current input box
(Continued 1 of 2)

Section Keyword Definition

ENDBOX Reset input box to encompass the entire grid
COPY Copy data from one array to another
EQUALS Set array to a constant in current box
ADD Add specified constants to specified arrays in the current box
MULTIPLY Multiply specified arrays by specified constants within the current
box
MAXVALUE Apply a maximum value to specified arrays within the current box
MINVALUE Apply a minimum value to specified arrays within the current box
Required Keywords:
SPECGRID or Specification of grid dimensions
DIMENS
COORD Coordinate lines
ZCORN Point depths of grid block corner
(Continued 2 of 2)
Here is an example file that shows an ECLIPSE ASCII 3D grid format.
Grid 3D Grid MAPAXES 559077.827586

6788493 237725 559077 827586 6787493 237725
560077 827586 6787493 237725 /GRIDUNIT ’METERS’ ’MAP’
/ SPECGRID 73 166 7 1 F / COORDSVS 1 7 ’incomp ’ /
COORD 561291.562500 6789790.500000 9212.705186
561056.312500 6789891.000000 9212.705186 561291.00000
6789789.500000 9212.705186 561055.687500 6789890.500000
.
.
.
ECLIPSE properties The converter will import ECLIPSE properties and add them to an existing SGrid object.
• The converter imports the REGION (see the keywords table) keywords values as
properties and regions for the SGrid object.
• The converter sets all inactive cells as not visible and such cells are not included in any
computations. The ACTNUM keyword defines the SGrid cells as active or inactive.
ECLIPSE binary format The converter expects to read a binary file that contains ECLIPSE keywords.
The file containing the grid geometry data should have the .grid or .egrid extension. All
other relevant data files (for example, .init for initial reservoir data and .unrst for unified
restart data) should be in binary format. They should have the same file name as the GRID
file but a different extension, and they should be located in the same folder.
User Guide A.5 ECLIPSE Formats A-13

A.6 FastEdit Formats
The FastEdit converter can read the following FastEdit file formats and create different
objects, based on the type of data in the file being imported.
• Fault polygon
• Scattered data
• Horizon contours
• 2D grid
FastEdit fault polygon The FastEdit fault polygons converter expects to read an ASCII file that contains header
format and data in the following format.
Header A comment line, denoted by $$, that specifies the type of file.
The converter ignores all other data in the header.
Data Each line should begin with a Segment ID number followed by a series of X, Y data
points, all separated by one or more spaces.
Note If there is more than one Segment in the file, the converter imports all data and creates a
Curve object for each Segment ID. The name of the new object will include the Segment ID. For
example, Segment 1 in a file called FaultPolyFastedit is imported as a curve named
“FaultPolyFastedit_1”.
Here is an example file that shows FastEdit fault data.
$$ FastEdit Faults
(A10,X,G15.7,X,G15.7,X,G15.7,X,G15.7)
1 4355.3798828 6467.2402344 4355.2900391 6648.2597656
1 4355.2900391 6648.2597656 4359.1098633 6827.8701172
1 4359.1098633 6827.8701172 4367.2999805 7004.8999023
1 4367.2299895 7004.8999023 4379.9399414 7178.0200195
1 4379.9399414 7178.0200195 4397.6601563 7507.7299805
1 4420.6601563 7345.0898438 4420.6601563 7346.0898438
.
.
.
FastEdit scattered The FastEdit scattered data converter expects to read an ASCII file that contains header
data format and data in the following format. The converter creates a PointsSet object with the same
name as the import file, without the file name extension.
Data Columns of X, Y, and Z data points. Each column is separated by one or more
spaces.
Here is an example file that shows FastEdit scattered data.

$$ Scattered Data
(G15.7,X,G15.7,X,G15.7)
0.0000000 0.0000000 0.0000000
0.0000000 1000.0000000 0.0000000
0.0000000 2000.0000000 0.0000000
.
.
.
1000.000000 0.000000 0.0000000
1000.000000 1000.00000 500.0000000
1000.000000 2000.00000 500.0000000
.
.
.

FastEdit horizon The FastEdit horizon contours converter expects to read an ASCII file that contains header
contours format and data in the following format.
Data Columns of X, Y, and Z data points. Each column is separated by one or more
spaces.
Here is an example file that shows FastEdit contours data.
$$ FastEdit Contours
(G15.7,X,G15.7,X,G15.7)
-1.0000000 -1.0000000 -1.0000000
12303.0166016 8103.0097656 11000.0000000
.
.
.
-1.0000000 -1.0000000 -1.0000000
12303.3906520 8040.6127930 -10800.0000000
.
.
.
FastEdit 2D Grid The FastEdit 2D Grid converter expects to read an ASCII file that contains header and data
format in the following format.
Data Columns of X, Y, and Z (W property) coordinates for the 2D grid defined in the
header. Each coordinate gives the location of a particular grid node. The nodes are
in column-major order, column by column, row by row, starting in the upper-left
corner of the grid and moving down along the y-axis (V).
Each column is separated by one or more spaces.
Here is an example file that shows FastEdit 2D grid data.
$$ FastEdit 2D Grid
151 151
(F12.3,X,F12.3
1364.340 19052.400
(F7.3)
270.000
F12.3,X.F12.3)
100.565 200.144
24781.1562500 18650.1386719 -99.9999
24981.3007813 18650.1386710 -99.9999
25581.7324219 18659.1386719 -99.9999
.
.
.
User Guide A.6 FastEdit Formats A-15

A.7 Irap RMS Formats
There are five Irap RMS converters:
• Fault polygons or lines
• Triangle surface
• 2D-grid mapping
• 2D-grid classic
• Well
Irap RMS fault The Irap RMS fault polygons or lines converter expects to read an ASCII file that contains
polygons or lines header data followed by a series of X, Y, and Z coordinates separated by one or more
format spaces. The converter can read the classic or mapping format, and imports one object per
file.
Header Classic format: The header contains of a series of keywords, in a required sequence,
that define the grid.
Mapping format: The header contains a series of keywords, in any sequence, that
define the grid.
Data The data portion should contain the X, Y, and Z coordinates separated by one or
more spaces.
The converter reads each line of data as a single node on the Curve object.
Here is an example file that shows Irap RMS fault polygons format.
Begin GEOMATIC file header

type =lines
name =faultpolygon1
category =lines
date (1) =2003.11.1
xmin =-2500.000000
.
.
.
End GEOMATIC file header
4355.379883 6467.240234 0.000000
4367.229980 7004.899902 0.000000
.
.
.

Irap RMS triangle The Irap RMS triangle surface converter expects to read an ASCII file that contains header
surface format data followed by a series of X, Y, and Z coordinates separated by one or more spaces.
Header The header should contain a series of keywords that define the data.
more spaces and triangulation atoms for the triangulated surface defined in the
header.
Here is an example file that shows the Irap RMS triangle surface format.

type =Lines
name =Faultpolygon1
category =Lines
date(1) =2004.01.20
.
.
.
xmin = -2500.000000
ymin =1000.000000
.
.
End header
4355.379883 6467.240234 0.000000
4355.290039 6648.259766 0.000000
.
.
.
10 140 0
200 198 197
6 5 62
.
.
.
Irap RMS 2D grid The converter expects to read an ASCII file with header data that contains grid parameters
classic format in a specific sequence, followed by the X, Y, and Z coordinates.
Header Classic format: The converter expects to read a series of grid parameters in the
following sequence:
• Number of rows
• X increment
• Y increment
• minimum X (unrotated)
• maximum X (unrotated) – expected to be in the file but are not read during import
• minimum Y (unrotated)
• maximum Y (unrotated) – expected to be in the file but are not read during import
• Number of columns
• angle of rotation
more spaces. The converter reads each line of data as a single node on the Curve
object.
Here is an example file that shows the classic format:

-996 151 100.565407 200.143738
1364.339966 16449 150391 19052.400391 49073.960938
151 270.000000 1364.339966 19052.400391
0 0 0 0 0 0
9999900.00
9999900.00
9999900.00
User Guide A.7 Irap RMS Formats A-17

-8357.719727
-8347.599609
-8326.809570
.
.
.
Legend:
# of rows = 151
x = 100.565407
y = 200.143738
min x = 1364.339966
max x = 16449.150391
min y = 19502.400391
max y = 49073.960938
# of columns = 151
angle of rotation = 270.000000
Irap RMS 2D grid The converter expects to read an ASCII file that contains header data followed by
mapping format z-coordinates for the 2D grid defined in the header, and expects each coordinate to give
the z-location of a particular grid node. The nodes are laid out in column-major order,
column by column, row by row, starting in the upper-left corner of the grid and moving
down along the y-axis.
Header Mapping format: The converter expects to read keywords that define grid
parameters. The keywords can occur in any sequence.
Data The data portion should contain the xyz-coordinates separated by one or more
spaces.
Here is an example file that shows Irap RMS 2D grid mapping format.

type =RegularGrid
name =V
category =DepthSurface
data(1) =2004.01.20
.
.
.
xmin = 1564.483765
ymin = -4068.155273
.
.
.
End header
1.e+29
1.e+28
.
.
.
-0322.389648
-0315.009768
.
.
.

Irap RMS well format The Irap RMS Well converter expects to read an ASCII file that contains header data
followed by location coordinates. Property and marker data can be in the same file.
Header The header section should contain a series of keywords that define the data.
Data The data section should contain the X, Y, TVDSS, and MD coordinates separated by
one or more spaces.
Each line of data should contain location data for a single point on the Well.
Property and marker data, if any, should follow at the end of each line.
Here is an example file that shows the Irap RMS well data format:
1.0
Oil_and_Gas
wll7 -25.000000 -92.000000
3
Facies none linear
Porosity none linear
marker disc 0 ANGstructural 1 BATstructural
prop_horizons_morph_0 3 prop_horizons_morph_1
-25.000000 -92.000000 21.000000 -999 -999 -999
-25.000000 -92.000000 21.000000 -999 -999 -999
-25.000000 -92.000000 21.000000 -999 -999 -999
-25.000000 -92.000000 21.000000 -999 -999 -999
60.000000 668.000000 -1307.000000 -999 -999 -999
62.285698 672.507694 -1313.000000 -999 -999 -999
64.571404 677.143005 -1319.000000 -999 -999 -999
66.857101 681.713989 -1325.000000 -999 -999 -999
.
.
.
User Guide A.7 Irap RMS Formats A-19

A.8 LAS Format
The LAS converter expects to read an ASCII file that contains header and data in the
following format.
Important LAS files can vary considerably in content and format. The converter requires specific
data to be present in the import file.
If several wells are described in the same file, the converter loads them all.
LAS format Each keyword the converter recognizes should be preceded by a tilde (~) followed by a
single uppercase letter, which may or may not be part of a longer word. For example, the
converter reads the phrase “~Version Information” as the keyword ~V.
Header The Header section can contain a series of standard LAS keywords that provide
information about the well’s name, location, logs (if any), picks (if any), and
deviation survey (if any).
Required keywords: ~W, ~C. If these keywords do not appear in the header
portion of the LAS file, the converter will not work.
~W
Well Information: Provides general information about the well, such as: name,
location, service company, and so on. The converter creates a Well object or adds
data to an existing well object by using the name it finds in this section next to the
word WELL, or WN, or UWI.
~C
Curve (Log) Information: The converter uses the data in this section to name and
order the imported logs.
Optional keyword: ~T
Tops information (not shown in the example). If the file contains well picks
(markers), these should be included in the Header portion of the file with this
keyword.
Data Required keyword: ~A
The data portion of the file should contain the property and deviation data values of
the properties defined by the ~C keyword in the header. The converter reads the
values in the same order as the properties listed in ~C.
Here is an example file that shows an LAS ASCII file with ~W, ~C, and ~A keywords:
~Version Information Block
VERS . 5.00: CWLS LOG ASCII STANDARD - VERSION 5.00
WRAP . NO: One line per depth step
~Well Information Block
#MNEM.UNIT Data Type Information
#---------- ---------------- -----------
STRT .F 703: START DEPTH
STOP .F 1262: STOP DEPTH
STEP .F 0.5: STEP
NULL . -999.25: NULL VALUE
COMP . : COMPANY
WELL . W_1: WELL
.
.
.
~Curve Information Block
#MNEM.UNIT API CODE Curve Description
#---------- ---------------- -----------------
DEPTH.F :
CALI .IN : Loaded from X.GEOASCII
CT .MH/M : True formation conductivity
CXO .MH/M : Flushed zone conductivity
DRHO .G/C3 : Loaded from X.GEOASCII

.
.
.
~Parameter Information Block
#MNEM.UNIT Value Description
#---------- ---------------- -----------
PROJECT. Y.ras:
SET . MMWORK:
~A DEPTH CALI CT CXO DRHO
FPRESS FTEMP GR HMC HMC
PHIT RGRD RHOB RMC RMF
RM RXO SWT
703.0000 8.6303 0.0044 0.0049 0.1130
335.7760 60.8508 38.8602 0.0000 0.0000
0.0043 228.5933 2.7125 3.1620
.
.
.
User Guide A.8 LAS Format A-21

A.9 MPath Formats
The MPath converter expects to read MPath .act, .fid, .par, and .raw files created by the
Permedia Consortium Project. For more information, see www.permedia.ca.
MPath .act format The converter expects to read an .act file that contains simulation results output by
Migration, Dynamic Migration, Connections, Intrusion, or Analysis. The .act files can be
ASCII or binary.
The converter expects to read an ASCII header, followed by a 4-byte sequence to detect
the byte order of the file.
Header The file should have an ASCII header that contains a series of keywords defining the
data. The converter ignores blank lines and lines starting with #.
.act required keywords:
• fid
• par
• extents
• origin
• cellsize
• rotation
• fields
• gridcells
• fields
• data (the converter expects to start reading data immediately following this
keyword)
Data The converter expects to read data for the grid cells in binary format.
Here is an example file that shows an .act format.
# act
description: n/a
fid: model.fid
par: model.par
fabric: none
extents: 171 171 141
origin: 0 0 0
cellsize: 1 1 1
rotation: 0
time: 0.000
stocktank_bp: 0.001899
stocktank_dp: 0.998998
stocktank_rhov: 1.292138
stocktank_rhol: 897.150952
fields: index pet_presence invasion_sequence path_index pore_saturation
bulk_saturation moveable_pore_saturation moveable_bulk_saturation
gridcells: 412298
data: binary 15140

MPath .fid format The converter expects to read grid data files consisting of a regular grid containing a
single value for each grid cell.
(data data. The converter ignores blank lines and lines starting with #.
requirements are .fid required keywords:
the same, • origin
whether the file • cellsize
is in ASCII or
binary format)
• rotation
• cycling_order
• extents
• data
Here is an example file that shows an .fid format.
# .fid version
origin: 0 0 0
cellsize: 1 1 1
rotation: 0
cycling_order: xzy
extents: 500 1 200
data
MPath .fid format The converter expects to read a 3D regular grid format .fid file that contains flow unit ID
data. The first lines contain ASCII header information relating to the dimensions of the
model (number of grid cells in each direction), its position, and the grid cell sizes.
(data data. The converter ignores blank lines and lines starting with #.
requirements are .fid required keywords:
the same, • origin
whether the file • cellsize
is in ASCII or
binary format)
• rotation
• extents
• data
Here is an example file that shows an .fid format.
## .fid version 0.700

origin: 0 0 0
cellsize: 1 1 1
rotation: 0
cycling_order: xzy
extents: 500 1 200
data
User Guide A.9 MPath Formats A-23

MPath .par format The converter expects to read a .par file that contains petrophysical parameters for each
flow unit ID contained in the .fid file.
.par required keywords:
• Fid
• Red
• Green
• Blue
Data The converter expects to read ASCII data for the grid cells.
Here is an example file that shows a .par format:

Pth_x Poro
Fid Red Green Blue Auto_Descr. User_Descr
2 20000.0000
1000.0000 2 .2000 .0100 1 257 215 121 445_214_192 fault 3
2 8700.0000 100.0000 2 .2000 .0100 2
293 229 0 237_237_0 z=4
2 14001.0000 100.0000 2 2000 0100
3 165 107 33 165_33_247 z=09
.
.
.
MPath .raw format The converter expects to read raw grid data files consisting of a regular grid containing a
single value for each grid cell. The following keywords are required:
.raw required keywords:
• origin
• cellsize
• rotation
• extents
• data
Data The converter expects to read ASCII data for the grid cells.
• The first noncomment line defines the number of data cells. The first number is the x-
dimension, the second y, and the third z. Your raw data grids should have the same x-
, y-, and z-values as the .fid file you selected.
• All lines appearing after the data keyword are data values, cycled through in the xzy-
order.
• Values may be undefined and are specified as "NaN" values.

Here is an example of a RAW file:

# .raw version
origin: 100000 200000 0
cellsize: 100 100 10
rotation: 0
cycling_order: xzy
extents: 30 40 585
data
3.000
4.000
1.000
2.000
NaN
NaN
NaN
NaN
2.000
3.000
4.000
4.000
4.000
5.000
5.000
3.000
3.000
3.000
The example shows extent: 30 40 585. This means 30 grid cells in the x-dimension, 40 in
the y-dimension, and 585 in the z-dimension are defined in the data block.
User Guide A.9 MPath Formats A-25

A.10 SEG-Y Formats
2D SEG-Y format The 2D SEG-Y converter expects to read a two-dimensional SEG-Y file that contains
header data and trace and shotpoint location data.
You can use this converter to import data and create three different objects:
• If you select the 2D SEG-Y as CrossSection import option, the converter imports your
file and creates two objects: a Voxet that contains the seismic data and a Voxet that
contains the geometry (area and vertical) of the line.
• If you select the 2D SEG-Y as SGrid import option, the converter imports your file and
creates an SGrid object.
Header Navigation Data or Trace Geometry

The converter can read the geometrical trace header information either from a
separate navigation file or from the SEG-Y file.
Trace and Shotpoint Information
If you are using a separate navigation file, you can either provide the following
information or use the converter default settings:
• First shotpoint of the first trace in the file (default is 0)
• Number of traces per shotpoint (default is 1)
• Whether the shotpoint number decreases with the trace number (default is no)
• Line name (if there are multiple lines in the navigation file)
Minimum and Maximum Time/Depth
You can specify the Minimum Time/Depth (minzt) and Maximum Time/Depth (maxzt)
yourself, or you can instruct the converter to compute these values from the SEG-Y
header.
Shot Location or geophone Location
If you are not using a navigation file, you can instruct the converter to get the line
geometry using either the shot location or the geophone location in the SEG-Y trace
header.
Data The converter expects to read seismic data in the single-line standard SEG-Y binary
format. For details, see the Society of Exploration Geophysicists Web site at
www.seg.org.
Here is an example of a 2D SEG-Y navigation file format:

Line Name SP (Shot Point) X Y
XSection 1 1 451346 1390689
XSection 1 2 451304 1390653
XSection 1 3 451262 1390617
.
.
.

3D SEG-Y format The 3D SEG-Y converter expects to read a three-dimensional SEG-Y file that contains
header data and seismic data.
The converter imports only post-stack data and reads a binary format, if the file adheres
to the standards defined on the Society of Exploration Geophysicists Web site at
www.seg.org. Files, examples of files, and keyword requirements for each file are fully
explained on this Web site. The converter can usually determine the correct format;
however, if you want to specify the file format, you can do so during the import
procedure.
The following table gives a brief description of the general contents expected to be in the
different 3D SEG-Y file types.
Header Content
Binary A standard 400-byte header that contains 2-byte and 4-byte integer values that apply to
the whole file.
Trace A standard 240-byte header that contains 2-byte and 4-byte integer values that apply to
the associated trace. A SEG-Y file generally contains multiple traces (seismic amplitude
samples), with a separate 240-byte trace header describing the information contained in
each one.
For the converter to work properly, the 3D SEG-Y file being imported should be evenly
sampled and all traces should have the same length.
User Guide A.10 SEG-Y Formats A-27

A.11 SEP Format
The SEP converter expects to read two files that contain a data cube in SEP format. One
file contains the header data, one file contains the data.
Header The converter expects a separate ASCII header file that has the same file name as the
data file, but with H added as the file name extension. The converter expects the file
to contain the following data:
# indicates a comment line.
• Number of samples along each cube axis–for example: n1=81, n=41, n3 =81
• Voxet origin–for example 01=500, 02=300, 03=2100
• Increment between samples–for example d1=110, d2=140, d3=10
Data The data file contains the data values, described in the header file, as one long array
of numbers in binary form.
#SEP#
in="D:/giod/DATA2/voxet/newsurveySEP"
n1-81 01=500 d1=110
n2=41 02=300 d2=140
n3=81 03=2100 d3=10
esize=4
U step, V step, W step
voxet origin
number of nodes along UVW

A.12 Velf Format

Velf format The converter expects to read two keywords that define the location and velocity values
for the Curve object:
• SPNT This keyword defines the X, and Y location of one vertical line. The fourth
column defines X and the fifth column defines Y. For each line starting with SPNT, the
converter creates a vertical line.
• IVEF This keyword defines for each vertical line the couple’s time_or_depth/velocity.
The converter can read up to five couples per “IVEF” line. For each line starting with
IVEF, the converter starts reading from the twentieth character and reads the velocity
value for each time or depth.
You can have many IVEF lines for one SPNT line.
User Guide A.12 Velf Format A-29

A.13 XYZ Format
The XYZ converter expects to read a three-column ASCII file that contains only data
values, and the data values should be separated by one or more spaces.
An X, Y, Z file consists of data lines only–no header lines, no end (marker) lines. The
converter expects the first column to be East, the second column to be North, and the
third column to be TVDSS, or time (or any other direction) and ignores any data beyond
the third column.
The converter creates a single-part PointsSet object with each data point imported
becoming a valid line in the object.
The new object name is the name of the input file without the extension.
X, Y, Z ASCII format XYZ coordinates for TypSurf East <-converter ignores this line
761451.5 1031947.875 -7434.87695312
761139.8751031643.75 -7437.42773438 <-converter ignores this line
761503.9375 1031670.1875 -7435.35888672
1 <-converter ignores this line
761164 1031362.1875 -7438.75878906
760918.125 1031110.875 -7446.625
761430.625 1031350.25 -7434.51503906
761133.93752 1031083.625 -7442.04785150 76113.9357

.
.
.

A.14 Z-MAP Formats

The Z-MAP converter can read the following Z-MAP file formats and create different
objects, based on the type of data in the file being imported.
• Fault polygon data
• 2D grid data
• 2D grid data properties
Z-MAP fault polygon The Z-MAP fault polygon converter expects to read an ASCII file that contains header data
format followed by a series of fault polygon location coordinates and associated segment IDs in
the following format.
Header The header section should contain the following:

• An @ symbol at the beginning and at the end of the header data
• The keyword FALT or CARTOGRAPHIC
The converter ignores all other data in the header.
Data The converter looks for three columns of data and reads columns one and two as the
X and Y coordinates and column three as the segment ID
The converter creates a Curve part for each new segment ID.
@Faultpoloygon2 HEADER FALT

X (EASTING) , 1, 1, 1, 1, 15, 7, 0.1000000E+31.
Y (NORTHING) , 2, 2, 1, 16, 30, 7, 0.1000000E+31.
SEG I.D. , 3, 35, 1, 31, 40, 1, 0.1000000E+31.
@
X Y Segment ID
4355.29 6467.24 1.0
4355.29 6648.26 1.0
4359.11 6827.87 1.0
6367.23 7004.90 1.0
4379.94 7178.02 1.0
4397.66 7346.09 1.0
4420.66 7507.73 1.0
4455.74 7667.89 2.0
.
.
.
User Guide A.14 Z-MAP Formats A-31

Z-MAP 2D Grid The Z-MAP 2D Grid converter and the Z-MAP 2D Grid Properties converter expects to read
format an ASCII file that contains header data followed by a series of Z coordinates separated by
one or more spaces. The converter requires the following format.
The header section should contain the following:
Header
• An @ symbol at the beginning and at the end of the header data
• The name of the grid to be imported
• The no-data-value for the z-coordinates
• The number of nodes along each axis (Nu and Nv)
• The xy-locations of the u-extremity and v-extremity
The data should be sequenced as follows:
@
GRID
Unused - No-data-value
nu nv umin umax vmin vmax
@
Data The data portion should contain the z-coordinates (w-property) for the 2D Grid
defined in the header. Each coordinate gives the z-location of a particular grid node.
The nodes are laid out in order, column by column, row by row, starting in the
upper-left corner of the grid and moving down along the y-axis (v).
In the following example:

• -9999.99 identifies the no-data value, and the converter ignores any coordinate with
this value.
• 151 and 151 are the Nu and Nv values—the number of nodes along each axis.
• The other values (1364.34 31385.9 3967.59 19052.4) appearing on

the same line with the Nu and Nv values are the UV extremities (xmin, xmax, ymin,
ymax)—the X, Y locations.
• Data values appearing after the end-of-header indicator (@) are the z/w-coordinates
for the 2D grid.
@BaseSand geometry Header grid 5

15 -9999.99
151 151 1364.34 31385.9 3967.59 19052.4
@
-9999.00 -9999.00 -9999.00 -9999.00 -9999.00
-8315.01 -8307.63 -8301.10 -8300.49 8299.87
-8269.02 -8260.09 -8251.16 -8241.76 -8241.14

A.15 VIP Formats

The VIP converter can read VIP file formats and create an SGrid object or add property
data to an existing SGrid object.
VIP SGrid format The VIP SGrid converter expects to read an ASCII file that contains header and data in the
following format.
Header The converter ignores all data in the header except the following two lines of text:
• NX NY NZ (indicating that the data starts on the next line).
• nn nn nn (where nn is the number of cells in the u/i-direction, v/j-direction, and
w/k-direction, respectively).
Note If your grid file does not contain data values for the NX NY NZ keywords,
you need to supply the values in the Import an SGrid from VIP ASCII file dialog
box. See"Importing a VIP ASCII Grid File" on page 1-56.
Data A series of 8-point cells.
Each block of data should contain the cell location in the SGrid, followed by eight
sets of xyz-coordinates (24 numbers in total) identifying the eight corner points of
the cell.
The converter reads the grid data from the upper-left corner downward, cell-by-cell
and layer-by-layer. All eight point values are read for each cell.
Property data Property data is not required. However if property data is included, it should be at
the end of the file. If property data is present in the same file, you can import it at
the same time that you create the SGrid.
C File name: sgrid1.cor

C
NX NY NZ NCOMP
30 20 1 0 Grid size
ARRAYS
CORP VALUE
Required
C LAYER 1
ZONE 1 SPLIT 1.00000000 LAYER 1
C GRID BLOCK: I = 1, J = 1, K = 1
31223.06 41427.86 9589.03 31800.62 41427.86 9589.23
31800.62 40780.29 9591.69 31223.06 40780.29 9589.00 One grid block
31223.06 41427.86 9659.38 31800.62 41427.86 9659.71
31800.62 40780.29 9664.03 31223.06 40780.29 9660.13 with cell location
C GRID BLOCK I = 2, J = 1, K = 1 and eight sets of
31800.62 41427.86 9589.23 32378.19 41427.86 9591.28 X, Y, coordinates
.
.
.
User Guide A.15 VIP Formats A-33

VIP SGrid property The VIP SGrid properties converter expects to read an ASCII file that contains data in the
data format following format:
• The text line defining each property should be in this format: property_name VALUE.
• The converter reads property values cell by cell downward.
This example shows the beginning of data for the property “Porosity1.”
0 0 0 0 0 0
0 0 0 0 1 1
1 1 0 1 1 1
Porosity1 VALUE
0.166836 0.161804 0.150371 0.141576 0.13394 0.137214
0.128452 0.124265 0.127039 0.134051 0.132983 0.127658
0.119557 0.112348 0.104378 0.10151 0.101245 0.100864
0.0945651 0.00964849 0.00899982 0.00929927 0.0942273 0.00899488
.
.
.
• VIP property keywords

The converter recognizes these VIP property keywords:
Keyword Definition
POR Porosity
KX Direction of permeability along X
KY Direction of permeability along Y
KZ Direction of permeability along Z
NETGRS Net-to-gross ratio (sand content)
SWR Irreducible water saturation
SWRO Water saturation at residual oil
SGR Irreducible gas saturation
SGRO Gas saturation at residual oil
SO Oil saturation
SG Gas saturation
SW Water saturation
VIP LGR keywords The VIP local grid refinement (LGR) converter requires an ASCII file that contains the
following keywords:
Note The data in the file should be Cartesian values only. The converter does not support the OMIT
or INGRID keywords.
Keyword Definition
CARTREF Marks the beginning of Cartesian grid refinement
name Name of the grid being defined
i1,i2,j1,j2,k1,k2 The indices defining the portion of the coarse grid to be refined
nx1,nx2 Number of X direction fine grid blocks for each of the
corresponding coarse grid blocks
ny1,ny2 Number of Y direction fine grid blocks for each of the
nz1, nz2 Number of Z direction fine grid blocks for each of the
ENDREF Marks the end of data defining a refined grid

Index
Symbols importing FastEdit 2D-Grid creating using IRAP RMS ASCII

files 1-40 2D-Grid converter 1-40
.act files
.gvw files exporting 2-28
importing 1-18
importing 1-40 exporting properties to an Excel
.avf files
.las files file 2-7
exporting velocity data to 2-17
exporting wells to 2-65 exporting to a FastEdit file 2-29
importing 1-74
importing 1-79 exporting to a Medica file 2-16
.bin files
.ply files exporting to a Z-MAP file 2-30
importing 1-32
importing 1-29 exporting to an IRAP file 2-29
.cgm files
.t4d files exporting to CPS3 files 2-28
exporting 3D Viewer images
importing 1-16 3D SEG-Y files
to 2-68
.vrml files importing as voxets 1-62
exporting views to 2-68
exporting 3D Viewer images 3D Viewer
.cmg files
to 2-71 exporting as an image 2-68
exporting an SGrid object
to 2-38 .xls files exporting images to CGM
exporting object properties files 2-68
.dat files
to 2-7 exporting images to VRML
importing 1-24, 1-35
files 2-71
importing CPS3 ASCII data
files 1-37, 1-76 Numerics
.dxf files 2D SEG-Y files A
exporting an object to 2-7 importing 1-68 Add Log From Ascii File dialog
importing 1-22 box 1-88
2D view
.flt files Adobe contours files
exporting as an image 2-68
importing 1-27 importing 1-37
2D voxet
.grd files Advanced Connect Parameters
importing 1-44
exporting s grids to ECLIPSE dialog box 2-14
2D-Grid objects
ASCII files 2-43 ArcView files
creating from horizon surface
importing 1-31 importing 1-21
data files 1-39
importing CPS3 ASCII 2D-Grid ASCII file
creating using FastEdit scattered
files 1-39 data converter 1-35 exporting an object to a custom
ASCII file 2-5
Index-1
exporting an SGrid object column-based files creating Curve objects from
to 2-43 importing 1-35, 1-37, 1-76, CPS3 ASCII fault trace
exporting well curves to 2-67 1-86 file 1-27
exporting well markers to 2-66 importing location data 1-87 creating Curve objects from fault
interpretations data
AVF file importing well marker data
files 1-23
exporting velocity data to 2-17 from 1-86
creating from a Velf ASCII
importing wizard 1-8
file 1-74
contour data
B creating from column-based-file
importing to create a Cure data 1-76, 1-86
basic concept for importing 1-6 object 1-37
basin modeling CPS3 data files 1-39
importing MPath .act files 1-18 import file format creating from location data from
importing MPath .fid files 1-19 requirements A-6 column-based files 1-87
importing MPath .par color map CPS3 binary converter 1-25 creating using FastEdit scattered
files 1-19 CPS3 fault traces data converter 1-35
importing MPath .raw importing 1-27 exporting 2-20
files 1-18
CPS3 files exporting properties to an Excel
importing PetroMod 1-19 file 2-7
exporting 2D-Grid objects
importing Temis 3D .t4d to 2-28 exporting to a FastEdit fault
files 1-16 polygon file 2-20
importing 1-35
importing Temis 3D color exporting to a Medica file 2-16
importing CPS3 ASCII 2D-Grid
map 1-17
files 1-31, 1-39 exporting to a Z-MAP contours
binary files file 2-23
exporting an SGrid object files 1-37, 1-76 exporting to a Z-MAP faults
to 2-51 file 2-22
importing CPS3 ASCII polygon
files 1-29 exporting to an IRAP file 2-21
C importing CPS3 binary exporting well curves to an ASCII
files 1-25, 1-31, 1-35 file 2-67
CGM files
Create Well from IRAP File dialog importing Z-MAP contour files
box 1-78 as 1-38
to 2-68
Create Well from WITSML File custom ASCII file
exporting views to 2-68
dialog box 1-85 exporting an object to 2-5
channels
cross section
exporting properties to an Excel
exporting as an image 2-68
file 2-7 D
CUBIT facet files
Charisma files, importing DDS files
exporting a surface to 2-24
fault interpretations files 1-26 exporting voxets to 2-31
cultural data
fault polygon files 1-29 DXF files
importing .dxf files 1-22
horizon points 1-34 exporting to 2-7
importing ArcView files 1-21
CMG files
curves
exporting SGrid objects to 2-38
Column as Production Data -
creating Curve objects from a E
column-based file 1-37
ECLIPSE format wizard 1-98 ECLIPSE
creating Curve objects from a
Column as Production Data - import file format
SeisWorks fault sticks
General Format wizard 1-91 requirements A-12
file 1-28
column-based file import wizard ECLIPSE binary file 1-101
creating Curve objects from
import file format Charisma fault polygon ASCII ECLIPSE files
requirements A-4 files 1-29 export well data of s grids
to 2-46
Index-2 SKUA® and GOCAD® – Paradigm™ 2011

exporting SGrid objects to Export SGrid to CMG File dialog 2D-Grid objects to a Z-MAP
ECLIPSE ASCII files 2-43 box 2-39, 2-41, 2-42 file 2-30
exporting SGrid objects to Export SGrid to ECL File dialog 2D-Grid objects to an IRAP
ECLIPSE binary files 2-51 box 2-44 file 2-29
format 2-38 Export SGrid to ECLIPSE Binary 3D Viewer image to CGM
importing ASCII grids 1-46 dialog box 2-51 files 2-68
importing binary grid files 1-47 Export SGrid to RESCUE dialog 3D Viewer images to VRML
box 2-54 files 2-71
importing faults 1-61
Export SGrid to VIP File dialog basic procedures 2-4
importing properties 1-58
box 2-55 curves 2-20
ECLIPSE keyword 2-43
Export Surface To CUBIT Facet curves to a FastEdit fault polygon
Excel files ASCII file dialog box 2-24 file 2-20
exporting object properties Export Surface to FastEdit curves to a Medica file 2-16
to 2-7 Contours dialog box 2-25
curves to a SeisWorks fault sticks
importing 1-77 Export Surface To IRMS as Triangle file 2-21
Export 2D-Geometry or Properties Surface file dialog box 2-26
curves to a Z-MAP contours
to Z-MAP dialog box 2-30 Export Surfaces to MohrFracs file 2-23
Export 2D-Grid Geometry or dialog box 2-26
curves to an IRAP file 2-21
Properties to CPS3 dialog Export to DXF format dialog
box 2-28 curves to Z-MAP faults
box 2-7
files 2-22
Export 2D-Grid Geometry or Export to Generic ASCII File dialog
Properties to FastEdit dialog object properties to Excel
box 2-5
box 2-29 files 2-7
Export unit to Isatis dialog
Export 2D-Grid Geometry or objects to a custom ASCII
box 2-75
Properties to Irap RMS dialog file 2-5
Export Voxet to DDS dialog
box 2-29 points sets to a FastEdit
box 2-31
Export 2D-Grid to Medica dialog file 2-19
Export Voxet to SEG-Y dialog
box 2-16 SGrid objects 2-36
box 2-32
Export 3D Grid Property to AVF SGrid objects and data to an
Export Voxet to SEP dialog
dialog box 2-17 Isatis file 2-73
box 2-33
Export 3D Grid Property to Velf SGrid objects to a CMG
Export Voxet To VoxelGeo dialog
dialog box 2-18 file 2-38
box 2-34
Export Curve to FastEdit Fault SGrid objects to a RESCUE
Export VSet to Isatis dialog
Polygon dialog box 2-20 file 2-53
box 2-14
Export Curve to IRMS dialog SGrid objects to an ECLIPSE
Export Well Curves as a Column
box 2-21 ASCII file 2-43
File dialog box 2-67
Export Curves as contours to Z- SGrid objects to an ECLIPSE
Export Well Markers to ASCII file
MAP dialog box 2-23 binary file 2-51
dialog box 2-66
Export Fault polygons to SeisWorks SGrid objects to Temis 3D
Export Wells To Irap RMS dialog
dialog box 2-21 files 2-59
box 2-64
Export Fault polygons to Z-MAP SGrid objects to VIP files 2-54
Export Wells To LAS dialog
dialog box 2-22 shot lines 2-35
box 2-65
Export PointsSet to FastEdit surface data 2-24
exporting
Scattered Data Format dialog
2D-Grid data 2-28 surfaces to a CUBIT facet
box 2-19
file 2-24
Export Properties to Excel dialog 2D-Grid objects to a CPS3
file 2-28 surfaces to a FastEdit file 2-25
box 2-8
2D-Grid objects to a FastEdit surfaces to a GMI WellCheck
Export Seismic Line to 2D SEG-Y
file 2-29 MohrFracs file 2-26
dialog box 2-35
2D-Grid objects to a Medica surfaces to an IRAP file 2-26
Export SeismicLine to 2D SEG-Y
dialog box 2-35 file 2-16 to an Isatis file 2-12
to DFX files 2-7
User Guide Index-3

velocity data to a Velf file 2-18 importing CPS3 binary Irap RMS A-16
velocity data to an AVF files 1-25 LAS A-20
file 2-17 importing data 1-23 MPath A-22
view as an image 2-68 importing FastEdit fault polygon VIP A-33
views 2-70 files 1-30
XYZ A-30
views to CGM files 2-68 importing FastEdit scattered
Z-MAP A-31
data 1-25
voxets 2-31
importing Irap RMS fault
voxets to a DDS file 2-31
polygons or lines 1-30 G
voxets to a SEG-Y file 2-32
importing Petrel Pillar files as Geoprobe 2D-Grid files
voxets to a VoxelGeo file 2-34 curves 1-28
importing 1-40
voxets to an SEP file 2-33 importing Petrel Pillar files as
GMI WellCheck MohrFracs files
well curves to an ASCII surfaces 1-32
file 2-67 exporting surfaces to 2-26
importing SeisWorks fault
well markers to an ASCII polygon files 1-30 GSLib 2D Map file
file 2-66 importing SeisWorks fault stick importing as surface 1-40
wells 2-64 files 1-28 GSLib 2D Map files
wells to an IRAP file 2-64 importing X Y Z files 1-26 importing 1-35
wells to LAS files 2-65 importing Z-MAP fault or
contour files 1-28
H
importing.flt files 1-27
F horizon contours
fault polygon files
FastEdit importing Z-MAP horizon
exporting curves to 2-20
import file format contour files 1-38
importing FastEdit fault polygons
requirements A-14 horizon interpretations
files 1-30
FastEdit files importing Adobe
fault sticks files
exporting 2D-Grid objects contours 1-37
exporting a curve to 2-21
to 2-29 importing Charisma horizon
fault surfaces points 1-34
exporting curves to 2-20
importing CPS3 ASCII 2D-Grid importing column-based
exporting points sets to 2-19
files 1-31 files 1-35, 1-37
exporting surfaces to 2-25
importing FastEdit 2D-Grid importing CPS3 .dat files 1-35
importing 1-30 files 1-31
importing 2D grid files 1-40 importing Irap RMS Triangle files 1-37
importing 2D-Grids 1-31 Surface files 1-32
importing FastEdit horizon
importing FastEdit scattered data importing RC2 2D-Grid contours 1-37
files 1-35 files 1-32
importing FastEdit scattered
importing horizon contour importing RESCUE model data 1-35
files 1-37 files 1-32
importing GSLib 2D Map
importing scattered data 1-25 importing Z-MAP 2D-Grid files 1-35
fault interpretations files 1-33
importing SeisWorks Inline Xline
importing Charisma fault faults XYZ files 1-36
interpretations files 1-26 importing ECLIPSE ASCII fault importing X Y Z files 1-36
importing Charisma fault files 1-61
importing Z-MAP horizon
polygon files 1-29 file format requirements for contours 1-38
importing column-based importing
horizon surface
files 1-8, 1-25 column-based file A-4
importing data 1-39
importing CPS3 .dat files 1-24 CPS3 A-6
importing GSLib 2D map as
importing CPS3 ASCII polygon ECLIPSE A-12 surface 1-40
files 1-29 FastEdit A-14 horizon surfaces

importing .gvw files 1-40 VIP import file format Import production data from
importing CPS3 .grd files 1-39 requirements A-33 ECLIPSE RSM file dialog
XYZ import file format box 1-102
importing FastEdit 2D-Grid
files 1-40 requirements A-30 Import Properties from VIP ASCII
Z-MAP import file format File dialog box 1-60
importing Irap RMS 2D-Grid
files 1-40 requirements A-31 Import RESCUE as SGrid dialog
Import 2D SEG-Y dialog box 1-69 box 1-33
importing Irap RMS ASCII 2D-
Grid property files 1-41 Import a Z-MAP file as a Property Import Temis3d t4d File dialog
of the Grid dialog box 1-42 box 1-16
importing Norsar horizons 1-41
Import an SGrid from VIP ASCII file Import Termis3D Colormap dialog
importing RC2 2D-Grid
dialog box 1-56 box 1-17
files 1-41
Import ASCII Charisma Fault Import VIP ASCII LGR dialog
importing RESCUE model
Polygon To Curve dialog box 1-57
files 1-42
box 1-29 Import Well from excel file dialog
importing Z-MAP ASCII 2D-Grid
Import CMG Grid and Production box 1-77
properties 1-42
Data dialog box 1-54 Import Well Image Log dialog
Import DXF file dialog box 1-22 box 1-43, 1-44
I Import ECLIPSE ASCII as SGrid Import Well Log from LAS File
I J K properties Properties dialog box 1-58 dialog box 1-83
importing 1-59 Import ECLIPSE ASCII LGR as SGrid Import Well Symbols dialog
dialog box 1-57 box 1-89
images
Import ECLIPSE Binary Files dialog Import X Y Z ASCII File dialog
exporting 3D Viewer images to
box 1-48 box 1-36
CGM files 2-68
Import ECLIPSE Binary Production Import Z-MAP ASCII as 2D-Grid
exporting 3D Viewer images to
Data dialog box 1-101 Property dialog box 1-41
VRML files 2-71
Import ECLIPSE Well Completions importing
exporting from 3D and 2D
views 2-70 dialog box 1-90 .avf files 1-74
exporting views to CGM Import Faults from ECLIPSE ASCII .dxf files 1-22
files 2-68 File dialog box 1-61 .flt files 1-27
importing 1-43 import file format requirements 2D SEG-Y files 1-68
import SEG-Y A-26 2D voxet 1-44
column-based import file format SEP A-28 Adobe contours files 1-37
requirements A-4 VIP A-33 basic concept 1-6
CPS3 import file format XYZ A-30 Charisma fault interpretations
requirements A-6 Z-MAP A-31 files 1-26
ECLIPSE import file format Import I J K Property-Value File as Charisma fault polygon
requirements A-12 Grid Property dialog box 1-60 files 1-29
FastEdit file import Import Image as Voxet dialog Charisma horizon points 1-34
requirements A-14 box 1-44 column-based files 1-8, 1-35,
file format table A-2 Import LAS Data Files dialog 1-37, 1-76, 1-86
Irap RMS import file format box 1-79 CPS3 .dat files 1-76
requirements A-16 Import Medica 2D Grid dialog CPS3 ASCII 2D-Grid files 1-31,
LAS import file format box 1-15 1-39
requirements A-20 Import Norsar 2.1 Object into CPS3 ASCII data files 1-24,
MPath import file format Gocad dialog box 1-71 1-35
requirements A-22 Import Permedia ACT File dialog CPS3 ASCII polygon files 1-29
SEG-Y import file format box 1-18
CPS3 binary files 1-25, 1-31,
requirements A-26 Import PetroMod ACT dialog 1-35
SEP import file format box 1-19
requirements A-28
User Guide Index-5

CPS3 files ProMAX files 1-73 importing RMS ASCII 2D-Grid
importing CPS3 ASCII data RC2 2D-Grid files 1-32, 1-41 property files 1-41
files 1-37 RC2 files as wells 1-84 importing RMS fault polygons or
cultural data 1-21 lines 1-30
RESCUE model files 1-32, 1-42
ECLIPSE ASCII grid file 1-46 importing RMS Triangle Surface
RESCUE model files (grids,
files 1-32
ECLIPSE ASCII properties horizons, faults) 1-56
files 1-58 importing RMS well files 1-78
reservoir grid data 1-45
ECLIPSE binary grid files 1-47 Irap RMS
SEG-Y 3D files as voxets 1-62
ECLIPSE faults 1-61 import file format
seismic data 1-62
requirements A-16
Excel files 1-77 SeisWorks fault polygon
Isatis files
FastEdit 2D-Grid files 1-31, files 1-30
1-40 exporting stratigraphic grid data
SeisWorks fault sticks files 1-28
to 2-73
FastEdit fault polygon SeisWorks Inline Xline XYZ
files 1-30 exporting to 2-12
files 1-36
FastEdit horizon contour SEP files 1-71
files 1-37
TDQs 1-74 J
FastEdit scattered data 1-25
Temis 3D .t4d files 1-16 Jason traces
FastEdit scattered data
Temis 3D files as wells 1-84 importing 1-73
files 1-35
Velf files 1-74
fault interpretations data 1-23
velocity data 1-73
Geoprobe 2D-Grid files 1-40 L
VIP ASCII grid files 1-56
GSLib 2D map as surface 1-40 LAS
VIP LGR data 1-57
GSLib 2D Map files 1-35 import file format
VIP properties 1-60
horizon surface data 1-39 requirements A-20
VoxelGeo files 1-68
I J K property files 1-59 LAS file
voxet 1-44
image files 1-43 exporting wells to 2-65
well data 1-76
Irap RMS ASCII 2D-Grid LAS well data
files 1-40 well marker data from column-
importing 1-79
based files 1-86
Irap RMS ASCII 2D-Grid property log data
files 1-41 well symbol data 1-89
importing from column-based
Irap RMS fault polygons or WITSML files 1-85
files 1-87
lines 1-30 X Y Z fault data 1-26
Irap RMS Triangle Surface X Y Z files as wells 1-86
files 1-32 X Y Z horizon data 1-36 M
Irap RMS well files 1-78 Z-MAP 2D-Grid files 1-33 map
Jason traces 1-73 Z-MAP ASCII 2D-Grid property exporting as an image 2-68
LAS well data 1-79 files 1-42 Medica file
MPath .act files 1-18 Z-MAP contour files 1-38 exporting 2D-Grid objects
MPath .fid 1-19 Z-MAP fault or contour to 2-16
MPath .par color map files 1-28 exporting curves to 2-16
files 1-19 IRAP files MPath
MPath .raw files 1-18 exporting 2D-Grid objects import file format
Norsar depth cube files 1-71 to 2-29 requirements A-22
Norsar horizons files 1-41 exporting a curve to 2-21 importing .fid files 1-19
Petrel Pillar files as exporting surfaces to 2-26 importing .par color map
surfaces 1-32 exporting wells to 2-64 files 1-19
Petrel Pillars files as curves 1-28 Irap files importing .raw files 1-18
PetroMod 1-19 importing RMS 2D-Grid MPath .act files
files 1-40 importing 1-18

N R importing SEG-Y 3D files as

voxets 1-62
Norsar Depth Cube RC2 files
converter 1-71 importing SEP files 1-71
importing as wells 1-84
Norsar depth cubes importing VoxelGeo files 1-68
importing RC2 2D-Grid
importing 1-71 files 1-32, 1-41 SeisWorks files
Norsar horizons files RESCUE file exporting curves to SeisWorks
fault sticks files 2-21
importing 1-41 exporting SGrid objects to 2-53
importing fault polygons 1-30
Norsar Trend Map 1-71 RESCUE model files
importing fault sticks files 1-28
importing 1-32, 1-42
Inline Xline XYZ files 1-36
importing grids, horizons,
O SEP file
faults 1-56
objects exporting voxets to 2-33
reservoir grid data
exporting to a custom ASCII SEP files
importing 1-45
file 2-5 importing 1-71
importing ECLIPSE ASCII
exporting to an Isatis file 2-12 SEP import file format
grids 1-46
exporting to DXF files 2-7 requirements A-28
importing ECLIPSE binary
grids 1-47 SGrid objects
P importing ECLIPSE faults 1-61 exporting 2-36
Petrel Pillars importing ECLIPSE exporting properties to an Excel
properties 1-58 file 2-7
importing Petrel Pillars files as
curves 1-28 importing I J K properties 1-59 exporting to a RESCUE
importing RESCUE model (grids, file 2-53
importing Petrel Pillars files as
surfaces 1-32 horizons, faults) 1-56 exporting to an ECLIPSE ASCII
importing VIP grids 1-56 file 2-43
PetroMod
importing VIP LGR files 1-57 exporting to an ECLIPSE binary
importing 1-19 file 2-51
points sets importing VIP properties 1-60
exporting to an Isatis file 2-73
creating from column-based-file exporting to Temis3D files 2-59
data 1-76, 1-86 S exporting to VIP files 2-54
S Grid object shot lines
data files 1-39
creating from velocity exporting 2-35
creating from location data from
data 1-73 SIF 1-44
column-based files 1-87
Save SGrid Geometry and SmartRaster Interchange
creating PointsSet object from
Properties as Temis3D Format Format 1-44
Charisma ASCII file 1-34
dialog box 2-59
creating PointsSet objects from Snapshot dialog box 2-70
SEG-Y 3D files
fault interpretations data solids
files 1-23 importing as voxets 1-62
exporting properties to an Excel
creating using FastEdit scattered SEGY 3D to Voxet dialog file 2-7
data converter 1-35 box 1-63
stratigraphic grid data
exporting properties to an Excel SEG-Y files
exporting to an Isatis file 2-73
file 2-7 exporting voxets to 2-32
surface
exporting to a FastEdit file 2-19 SEG-Y import file format
requirements A-26 importing GSLib 2D map
Print Window to a CGM File dialog as 1-40
box 2-68 seismic data
surfaces
Print Window to VRML dialog importing 1-62
box 2-71 importing 2D SEG-Y files 1-68 data files 1-39
ProMAX files importing Norsar depth creating from velocity
importing 1-73 cubes 1-71 data 1-73
User Guide Index-7

exporting data 2-24 VIP import file format well markers
exporting properties to an Excel requirements A-33 exporting to an ASCII file 2-66
file 2-7 VIP properties files well section
exporting to a CUBIT facet importing 1-60 exporting as an image 2-68
file 2-24 VoxelGeo files well symbol data
exporting to a FastEdit file 2-25 exporting voxets to 2-34 importing 1-89
exporting to a GMI WellCheck importing 1-68 wells
MohrFracs file 2-26 creating from column-based-file
voxets
exporting to an IRAP file 2-26 data 1-76, 1-86
creating from a Norsar interface
creating from location data from
and Norsar trend map 1-71
column-based files 1-87
T creating using existing
creating using RC2
images 1-43
TDQ .avf files converter 1-84
creating using Norsar exporting 2-64
importing 1-74
converter 1-41
Temis 3D color map exporting properties to an Excel
exporting 2-31 file 2-7
importing 1-17
exporting properties to an Excel exporting to an IRAP file 2-64
Temis 3D files file 2-7 exporting to LAS files 2-65
importing as s grids 1-16 exporting to a DDS file 2-31 importing Irap RMS files 1-78
importing as wells 1-84 exporting to a SEG-Y file 2-32 importing using the X Y Z
Temis3D files exporting to an SEP file 2-33 converter 1-86
exporting SGrid objects to 2-59 exporting to VoxelGeo WITSML files
triangulated surfaces files 2-34 importing 1-85
importing 1-32 VRML files
X
to 2-71
V X Y Z files
Velf file, exporting velocity data importing as points set 1-26
to 2-18 W importing as wells 1-86
Velf files well curves importing horizon data 1-36
importing 1-74 exporting to an ASCII file 2-67 XYZ import file format
velocity data well data requirements A-30
exporting to a Velf file 2-18 importing 1-76
exporting to an AVF file 2-17 importing column-based Z
importing 1-73 files 1-76, 1-86 Z-MAP files
importing Jason traces 1-73 importing CPS3 .dat files 1-76 exporting 2D-Grid objects
importing ProMAX files 1-73 importing Excel files 1-77 to 2-30
importing TDQ .avf files 1-74 importing Irap RMS files 1-78 exporting curves to contours
importing LAS files 1-79 files 2-23
importing Velf files 1-74
importing location data from exporting curves to faults
view
column-based files 1-87 files 2-22
exporting images to CGM importing 2D-Grid object
files 2-68 importing Temis 3D files 1-84
to 1-33
views importing Velf files 1-74
importing ASCII 2D-Grid
exporting images 2-70 importing WITSML files 1-85 properties 1-42
VIP files well marker data importing Z-MAP contour
exporting SGrid objects to 2-54 importing from column-based files 1-38
files 1-86 importing Z-MAP fault or
importing grids 1-56
well marker data importing contour files 1-28
importing VIP LGR files 1-57
column-based file 1-86 Z-MAP import file format
requirements A-31


Scua Gocad Import Exportpdf Compress

Uploaded by

Copyright:

Available Formats

Scua Gocad Import Exportpdf Compress

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Scua Gocad Import Exportpdf Compress

Uploaded by

Copyright:

Available Formats

SKUA® and GOCAD® User Guide

Part II: Data Import and Export

Published October 10, 2012

Part II: Data Import and Export

iv Contents SKUA® and GOCAD® – Paradigm™ 2011

1.10 Importing Image Files...................................................................................1-43

User Guide Contents v

Chapter 2 Exporting Data ......................................................................................... 2-1

vi Contents SKUA® and GOCAD® – Paradigm™ 2011

2.5.3 Exporting a Surface to an IRAP File ..................................................2-26

Appendix A Import File Formats .................................................................................. A-1

User Guide Contents vii

viii Contents SKUA® and GOCAD® – Paradigm™ 2011

In this chapter • "Converters and Supported Formats," • "Importing Horizon Interpretations

• "Importing Fault Surfaces Data," • "Importing Cross Section Data,"

1.1 Converters and Supported Formats

Table 1–1 Converters and

1-2 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

User Guide 1.1 Converters and Supported Formats 1-3

1-4 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

Locations from column-based file Well

User Guide 1.1 Converters and Supported Formats 1-5

1-6 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

User Guide 1.2 Basic Concept for Importing Data 1-7

1-8 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

Figure 1–1 Wizard for importing fault interpretations as a point set

1-10 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

Figure 1–2 Column

For this data type Do this

Figure 1–3 Miscellaneous information for fault interpretation data

1-12 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

Figure 1–4 Column assignment for fault interpretation data

1-14 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

1.4 Importing Basin Modeling Files

1.4.1 Import Temis/Medica Files

1. Medica and Temis3D are software products available from Beicip-Franlab.

User Guide 1.4 Importing Basin Modeling Files 1-15

1-16 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

• Variables. List of Temis3D properties.

• Vectors. List of Temis3D vectors.

5 Click one or more entries in the Vectors column.

User Guide 1.4 Importing Basin Modeling Files 1-17

1-18 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

1.4.3 Importing a PetroMod File

1. PetroMod is a multi-dimensional modeling software system available from Integrated Exploration

User Guide 1.4 Importing Basin Modeling Files 1-19

1-20 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

1.5 Importing Cultural Data

1.5.1 Importing an ArcView File

User Guide 1.5 Importing Cultural Data 1-21

1.5.3 Importing a SeisWorks Cultural Data File

1. A .dxf file is produced by AutoCAD, a software product available from Autodesk.

1-22 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

1.6 Importing Fault Interpretations Data

User Guide 1.6 Importing Fault Interpretations Data 1-23

Either choice opens the same dialog box.

• To create a Curve object, click Curve.

• To create a Well object, click Well.

1-24 Importing Data SKUA® and GOCAD® – Paradigm™ 2011

1.6.2 Importing a CPS3 Binary File