02 Import Export

GOCAD® 2009.
1 User Guide
Part II Data Import and Export

© 1997–2009 Paradigm B.V. and/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 B.V. and/or its affiliates or subsidiaries (collectively, "Paradigm"). Paradigm assumes no responsibility for any
errors that may appear 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 B.V. and/or its affiliates or subsidiaries (collectively,
"Paradigm") in the United States or in other countries: Paradigm, Paradigm logo, Alea, Coherence Cube, Director,
DirectorGeo, EarthStudy 360, Echos, Epos, FastVel, FracMV, GeoDepth, Geolog, GeoScene, GeoSec, GeoSteer,
GOCAD, Interpret, Jacta, Kine3D, OpenGeo, OpsLink, Probe, Pump-It, Rock & Fluid Canvas, SeisEarth, SeisFacies,
SeisX, SKUA, SolidGeo, StratEarth, Stratimagic, Sysdrill, UVT Transform, Vanguard, VoxelGeo, and/or other Paradigm
products referenced herein. 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; 6,092,026; 6,430,508; 6,819,628; 6,859,734; 6,873,913; 7,095,677; 7,123,258;
7,295,929; and 7,295,930. In addition, there may be patent protection in other foreign jurisdictions for these and other
Paradigm products.
All rights not expressly granted are reserved.
Published June 22, 2009

Contents
Part II Data Import and Export

Chapter 1 Importing Data.......................................................................................... 1-1
1.1 Converters ................................................................................................... 1-2
1.2 Basic Concept for Importing Data .................................................................. 1-6
1.3 Importing Basin Modeling Files ...................................................................... 1-8
1.3.1 Import Temis/Medica Files ................................................................. 1-8
1.3.2 Importing MPath Files .....................................................................1-11
1.3.3 Importing a PetroMod File ...............................................................1-13
1.4 Importing Cultural Data ...............................................................................1-14
1.4.1 Importing an ArcView File ...............................................................1-14
1.4.2 Importing a DXF File ........................................................................1-15
1.4.3 Importing a SeisWorks Cultural Data File ..........................................1-15
1.5 Importing Fault Interpretations Data .............................................................1-16
1.5.1 Importing a CPS3 ASCII Data (.dat) File ...........................................1-16
1.5.2 Importing a CPS3 Binary File ............................................................1-18
1.5.3 Importing a Column-Based File ........................................................1-18
1.5.4 Importing a FastEdit Scattered Data File ...........................................1-23
1.5.5 Importing an XYZ File ......................................................................1-24
1.5.6 Importing a Charisma Fault Interpretations File .................................1-24
1.5.7 Importing a CPS3 ASCII Data (.dat) File ............................................1-25
1.5.8 Importing a CPS3 ASCII Polygons (.ply) File.......................................1-25
1.5.9 Importing a CPS3 ASCII Fault Traces (.flt) File ....................................1-25
1.5.10 Importing a CPS3 Binary File ............................................................1-25
1.5.12 Importing a Petrel Pillars File ............................................................1-26
1.5.13 Importing a SeisWorks Fault Sticks File .............................................1-26
Contents iii
Paradigm™
1.5.14 Importing a Z-MAP Fault or Contour File ........................................ 1-26

1.5.15 Importing a Charisma Fault Polygons File ........................................ 1-27
1.5.16 Importing a CPS3 ASCII Polygons (.ply) File ...................................... 1-27
1.5.17 Importing a FastEdit Fault Polygons File ........................................... 1-28
1.5.18 Importing an Irap RMS Fault Polygons or Lines File ........................... 1-28
1.5.19 Importing a SeisWorks Fault Polygon File ......................................... 1-28
1.6 Importing Fault Surfaces Data...................................................................... 1-29
1.6.1 Importing a CPS3 ASCII 2D-Grid (.grd) File ...................................... 1-29
1.6.2 Importing a CPS3 Binary File ........................................................... 1-29
1.6.3 Importing a FastEdit 2D-Grid File ..................................................... 1-30
1.6.4 Importing an Irap RMS TriangleSurface File ...................................... 1-30
1.6.5 Importing a Petrel Pillars File ........................................................... 1-30
1.6.6 Importing a RC2 2D-Grid File .......................................................... 1-30
1.6.7 Importing a StrataModel 2D-Grid File .............................................. 1-32
1.6.8 Importing a Z-MAP ASCII 2D-Grid File ............................................. 1-32
1.7 Importing Horizon Interpretations Data ........................................................ 1-33
1.7.1 Importing a Charisma Horizon Points File......................................... 1-33
1.7.2 Importing a CPS3 ASCII Data (.dat) File............................................ 1-33
1.7.4 Importing a Column-Based File ....................................................... 1-34
1.7.5 Importing a FastEdit Scattered Data File........................................... 1-34
1.7.6 Importing a GSLib 2D Map File........................................................ 1-34
1.7.7 Importing a SeisWorks Inline Xline X Y Z File.................................... 1-35
1.7.8 Importing an X, Y, Z File ................................................................. 1-35
1.7.9 Importing an Adobe Contours File................................................... 1-36
1.7.10 Importing a CPS3 ASCII Data (.dat) File............................................ 1-36
1.7.13 Importing a FastEdit Horizon Contour File........................................ 1-37
1.7.14 Importing a Z-MAP Contour File ...................................................... 1-37
1.8 Importing Horizon Surfaces Data ................................................................. 1-38
1.8.1 Importing a CPS3 ASCII 2D-Grid (.grd) File....................................... 1-38
1.8.3 Importing a FastEdit 2D-Grid File ..................................................... 1-39
1.8.4 Importing a Geoprobe 2D Grid (.gvw) File ...................................... 1-39
1.8.5 Importing a GSLib 2D Map as Surface File ...................................... 1-39
1.8.6 Importing an Irap RMS ASCII 2D-Grid File ....................................... 1-39
1.8.7 Importing an Irap RMS ASCII 2D-Grid Property File ........................... 1-40
1.8.8 Importing a Norsar Horizons File ..................................................... 1-40
1.8.9 Importing an RC2 2D-Grid File ........................................................ 1-40
1.8.10 Importing a RESCUE Model File ....................................................... 1-41
1.8.11 Importing a StrataModel 2D-Grid File .............................................. 1-41
iv Contents GOCAD® 2009.1 User Guide

Part
II
and Export
Data Import
1.8.12 Importing a StrataModel 2D-Grid Property File .................................1-41
1.8.13 Importing a Z-MAP ASCII 2D-Grid File ..............................................1-41
1.8.14 Importing a Z-MAP ASCII 2D-Grid Property File .................................1-42
1.9 Importing Image Files...................................................................................1-43
1.10 Importing Reservoir Grid Data ......................................................................1-44
1.10.1 Importing an ECLIPSE ASCII Grid File ................................................1-45
1.10.2 Importing an ECLIPSE Binary Grid File ...............................................1-46
1.10.3 Importing a RESCUE Model (Grids, Horizons, Faults) File ...................1-53
1.10.4 Importing a VIP ASCII Grid File .........................................................1-53
1.10.5 Importing a VIP or ECLIPSE LGR File .................................................1-54
1.10.6 Importing ECLIPSE ASCII Properties File ............................................1-55
1.10.7 Importing an I J K Property File ........................................................1-56
1.10.8 Importing a VIP ASCII Properties File ................................................1-57
1.10.9 Importing an ECLIPSE ASCII Faults File ..............................................1-57
1.11 Importing Seismic Data ................................................................................1-58
1.11.1 Importing a SEG-Y 3D File as Voxet ..................................................1-58
1.11.2 Importing a VoxelGeo File................................................................1-62
1.11.3 Importing a 2D SEG-Y File ...............................................................1-63
1.11.4 Importing an SEP File.......................................................................1-65
1.11.5 Importing a Norsar Depth Cube File .................................................1-66
1.11.6 Importing a 2D SEG-Y File as Surface ...............................................1-66
1.11.7 Importing a 2D SEG-Y File as SGrid ..................................................1-66
1.11.8 Importing a SeisWorks Colormap .....................................................1-67
1.12 Importing Velocity Data ...............................................................................1-68
1.12.1 Importing a Jason ASCII Traces File...................................................1-68
1.12.2 Importing a ProMAX File .................................................................1-68
1.12.3 Importing a TDQ (.avf) File ...............................................................1-69
1.12.4 Importing a Velf File .......................................................................1-69
1.12.5 Importing a SEG-Y 3D as Voxet File ..................................................1-69
1.12.6 Importing a SEP File ........................................................................1-69
1.12.7 Importing a VoxelGeo File................................................................1-69
1.12.8 Importing a SEG-Y 2D as Surface File ...............................................1-69
1.12.9 Importing a SEG-Y 2D as SGrid File ..................................................1-70
1.13 Importing Well Data ....................................................................................1-71
1.13.2 Importing a CPS3 ASCII Data (.dat) File ............................................1-72
1.13.3 Importing an Excel File ...................................................................1-72
1.13.4 Importing an Irap RMS File ..............................................................1-73
1.13.5 Importing an LAS File ......................................................................1-74
Importing an LAS File as a New Well Object......................................1-74
Importing Data from LAS to Update an Existing Well ........................1-78
1.13.6 Importing an RC2 File......................................................................1-78
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 Contents v

Paradigm™
1.13.7 Importing a Temis3D File................................................................. 1-79

1.13.8 Importing a WITSML File ................................................................. 1-79
1.13.10 Importing an X Y Z File ................................................................... 1-80
1.13.11 Importing an Octopus File ............................................................... 1-80
1.13.12 Importing Locations from Column-Based File ................................... 1-81
1.13.13 Importing Well Marker Data from a Column-Based File .................... 1-82
1.13.14 Importing Log Data from Column-Based File .................................... 1-82
1.13.15 Importing Log Data from an LAS File ............................................... 1-82
1.13.16 Importing Log Data from ASCII File with Header .............................. 1-83
1.13.17 Importing Completion Data from Column-Based File ........................ 1-83
1.13.18 Importing Well Production Data from ECLIPSE Binary file .................. 1-84
1.14 Importing Cross Section Data ...................................................................... 1-85
1.14.1 Importing a DXF File ....................................................................... 1-85
1.14.2 Importing a GeoSec Cross Section File ............................................. 1-85
1.14.3 Importing a Locace File ................................................................... 1-85
1.14.4 Importing Well Symbol Data ........................................................... 1-86
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-16
2.2.7 Exporting Velocity Data to a Velf File ............................................... 2-17
2.3 Exporting PointsSet Data ............................................................................. 2-18
2.4 Exporting Curve Data .................................................................................. 2-19
2.4.1 Exporting a Curve to a FastEdit Fault Polygon File ............................ 2-19
2.4.2 Exporting a Curve to an IRAP File .................................................... 2-20
2.4.3 Exporting a Curve to a SeisWorks Fault Sticks File ............................ 2-20
2.4.4 Exporting a Curve to a Z-MAP Faults File ......................................... 2-21
2.4.5 Exporting a Curve to a Z-MAP Contours File .................................... 2-22
2.5 Exporting Surface Data ............................................................................... 2-23
2.5.1 Exporting a Surface to a CUBIT Facet File......................................... 2-23
2.5.2 Exporting a Surface to a FastEdit File ............................................... 2-24
2.5.3 Exporting a Surface to an IRAP File .................................................. 2-24
2.5.4 Exporting a Surface to a GMI WellCheck MohrFracs File ................... 2-25
2.6 Exporting 2D-Grid Data ............................................................................... 2-26
2.6.1 Exporting a 2D-Grid to a CPS3 File .................................................. 2-26
vi Contents GOCAD® 2009.1 User Guide

Part
II
and Export
Data Import
2.6.2 Exporting a 2D-Grid to a FastEdit File ...............................................2-27
2.6.3 Exporting 2D-Grid Data to an IRAP File.............................................2-27
2.6.4 Exporting 2D-Grid Data to a Z-MAP File ...........................................2-28
2.7 Exporting Voxet Data ...................................................................................2-29
2.7.1 Exporting a Voxet to a DDS File........................................................2-29
2.7.2 Exporting a Voxet to a SEG-Y File .....................................................2-30
2.7.3 Exporting a Voxet to an SEP File .......................................................2-31
2.7.4 Exporting a Voxet to a VoxelGeo File ................................................2-32
2.8 Exporting SGrid Data ...................................................................................2-33
2.8.1 About the Grid Origin .....................................................................2-34
2.8.2 Exporting an SGrid to a CMG File ....................................................2-35
2.8.3 Exporting an SGrid to an ECLIPSE ASCII File ......................................2-39
2.8.4 Exporting an SGrid to an ECLIPSE Binary File.....................................2-46
2.8.5 Exporting an SGrid to a RESCUE File ................................................2-48
2.8.6 Exporting an SGrid to a VIP File........................................................2-50
2.8.7 Exporting an SGrid to a Temis3D (libnf) File ......................................2-55
2.8.8 Exporting LGR Data from an SGrid to a Flow Simulator .....................2-55
2.9 Exporting Well Data .....................................................................................2-60
2.9.1 Exporting a Well to an IRAP File .......................................................2-60
2.9.2 Exporting a Well to an LAS File ........................................................2-61
2.9.3 Exporting Well Markers to an ASCII File............................................2-62
2.9.4 Exporting Well Logs to an ASCII File .................................................2-63
2.9.5 Exporting Well Targets to an Octopus File .........................................2-64
2.10 Exporting a View as an Image ......................................................................2-65
2.10.1 Exporting a View to a CGM File .......................................................2-65
2.10.2 Exporting a View to an Image File ....................................................2-66
2.10.3 Exporting a 3D Viewer Image to a VRML File ....................................2-68
2.11 Exporting an SGrid and Data to an Isatis File .................................................2-69
Appendix A Import File Formats .................................................................................. A-1

A.1 Import File Formats ....................................................................................... A-2
A.2 Column-based Formats ................................................................................. A-4
A.3 CPS3 Formats ............................................................................................... A-5
A.4 Eclipse Formats ........................................................................................... A-11
A.5 FastEdit Formats ......................................................................................... A-13
A.6 Irap RMS Formats ....................................................................................... A-15
A.7 LAS Format ................................................................................................ A-20
A.8 MPath Formats ........................................................................................... A-22
A.9 SEG-Y Formats ........................................................................................... A-26
A.10 SEP Format ................................................................................................. A-28
A.11 Velf Format ................................................................................................ A-29
A.12 XYZ Format ................................................................................................ A-30
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 Contents vii

Paradigm™
A.13 Z-MAP Formats ........................................................................................... A-31

A.14 VIP Formats ................................................................................................ A-33
Index .................................................................................................. Index-1
viii Contents GOCAD® 2009.1 User Guide

1
Importing Data
In this chapter • "Converters," page 1-2 • "Importing Horizon Surfaces Data,"

page 1-38
• "Basic Concept for Importing Data,"
page 1-6 • "Importing Image Files," page 1-43
• "Importing Basin Modeling Files," • "Importing Reservoir Grid Data,"

page 1-8 page 1-44
• "Importing Cultural Data," page 1-14 • "Importing Seismic Data," page 1-58
• "Importing Fault Interpretations • "Importing Velocity Data," page 1-68
Data," page 1-16
• "Importing Well Data," page 1-71
• "Importing Fault Surfaces Data,"
page 1-29 • "Importing Cross Section Data,"
page 1-85
• "Importing Horizon Interpretations
Data," page 1-33
Overview In Paradigm™ GOCAD ® 2009, 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 format, and many additional formats from other software products.
With the GOCAD data converters, 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 programs
or data types for which GOCAD includes an import converter.
These topics explain how to import the related files and identify the objects GOCAD
creates based on the imported files.
Note You will notice that some programs or data types are listed more than once on the
Import submenus. When GOCAD includes data converters for importing multiple kinds of
data associated with a specific program or data type, the import option appears under
each applicable category.
1-1
Paradigm™
Paradigm adds support for new formats based on client need. To inquire about new
options, contact us at: pdgm.com/support.
Before you begin The validity and accuracy of the data in your file determines the success of what you want
to 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 GOCAD supports
and describes how the converter reads the file.
1.1 Converters
Table 1–1 identifies the kind of data you can import, the programs or data types, the file
name extensions, and objects the GOCAD converter creates from the imported data.
Table 1–1 Supported

converters and resulting If you want to
In this data format (or from With this common GOCAD can create
GOCAD objects 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
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 1
ER Mapper
DEM binary 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 PointsSet
FastEdit scattered data .dat PointsSet
XYZ PointsSet
(Continued 1 of 4)
1-2 Importing Data GOCAD® 2009.1 User Guide

Part
II
and Export
Data Import
If you want to
import this
type of data
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 Curve
Petrel pillars .dat Curve
Seisworks fault sticks .dat Curve
Z-MAP fault or contour Curve
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 PointsSet
Horizon Adobe contours .esp Curve
interpretation - CPS3 ASCII data .dat Curve
contours
CPS3 binary .svf, .svp Curve
Column-based file Curve
FastEdit horizon contours .dat Curve
Z-MAP contour .zmap Curve
(Continued 2 of 4)
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.1 Converters 1-3
Paradigm™
If you want to
import this
type of data
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
Reservoir grid - ECLIPSE ASCII grid .grdecl SGrid
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
Seismic data - SEG-Y 3D as Voxet .sgy, .segy Voxet
cubes VoxelGeo .vol Voxet
SEP .h Voxet
Norsar depth cube Voxet
Seismic data - SEG-Y 2D as surface .sgy, .segy Surface
lines
SEG-Y 2D as SGrid .sgy, .segy SGrid
Seismic data - SeisWorks .clr
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 SEG-Y 2D as surface .sgy, .segy Surface
SEG-Y 2D as SGrid .sgy, .segy SGrid
(Continued 3 of 4)

Part
II
and Export
Data Import
If you want to
import this
type of data
Well data - Column-based file 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
WITSML .gz, .xml Well
Well data - path Columns-based file Well
X Y Z file Well
Octopus Well
Locations from column-based file Well
Well data - Column-based file Well
markers
Well data - logs Column-based file Well
LAS .las Well
ASCII file with header Well
Completion Well
Well data - ECLIPSE .DATA file .data Well
Completion data Column-based file Well
Well data - ECLIPSE binary file Well
Production data Column-based file Well
Well data - Well Status Symbols Well
Symbols
Cross sections DXF .dxf
Geosec .ihf
Locace .ext
Dip data Dip ASCII file with header Dip 2
Dip column-based file Dip
(Continued 4 of 4)
1. Importing a DEM as a DEM object requires the Advanced Structural Analysis (Kine3D-1) module. For
more information about importing a DEM, see Part VII: Geologic Interpretation, "Importing a DEM" on
page 3-13.
2. Importing dip data as a Dip object requires the Advanced Structural Analysis (Kine3D-1) module. For
more information about importing dip data, see Part VII: Geologic Interpretation , "Importing Dip Data"
on page 3-31.
Paradigm™
1.2 Basic Concept for Importing Data

Each dialog box in the import process requires you to enter various options that the
converter needs to quickly and accurately import your data files. Some converters 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 import procedure and the remaining sections in this
chapter explains detailed procedures for specific converters.
Important When you import any 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
the converters honor the GOCAD naming conventions. If you import a file that does
not follow the naming conventions, GOCAD will rename the file. For example, an
asterisk (*) is not allowed as a part of the file name. If your file is named W1*1,
GOCAD will rename the file as W1_1. For information about naming conventions, see
"Naming Objects" on page 3-7.
Basic procedure for 1 On the File menu, point to Import, point to the data type, and then click the
importing appropriate command. The dialog box for the specific command opens. The example
shows the dialog box that displays when you want to import an X, Y, Z ASCII file to
create a Well object.
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. The program enters the selected file
name in the File name box.
– or –
In the File name box, type the full path and file name.

Part
II
and Export
Data Import
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 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 GOCAD Project" on page 1-12.
4 Click OK to carry out the command and close the dialog box, or click Apply to carry
out the command and leave the dialog box open.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.2 Basic Concept for Importing Data 1-7
Paradigm™
1.3 Importing Basin Modeling Files

GOCAD includes converters for importing various 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-8
• "Importing MPath Files," page 1-11
• "Importing a PetroMod File," page 1-13
1.3.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
♦ On the File menu, point to Import, point to Basin Modeling, click Medica Fault
Polygons under Temis, 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.
♦ On the File menu, point to Import, point to Basin Modeling, click Medica
Topographic Surface under Temis, 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 On the File menu, point to Import, point to Basin Modeling, click Medica
Topographic Surface (Advanced) under Temis to open the dialog 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.

Part
II
and Export
Data Import
4 To select which object type you want the converter to create when importing the file,
click one of the following:
• Create PointsSet
• Create 2D Grid
• 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:
On the menu bar, click the File menu, and then click 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 On the File menu, point to Import, point to Basin Modeling, click Temis 3D Grid
(.t4d) under Temis to open the dialog box.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.3 Importing Basin Modeling Files 1-9
Paradigm™
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. Press and hold 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 On the File menu, point to Import, point to Basin Modeling, click Temis 3D Grid
Colormap under Temis to open the dialog box.
3 In the Colormap name box, type the name you want to use for the map. The default
name is Temis_Colormap.

Part
II
and Export
Data Import
1.3.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.
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 On the File menu, point to Import, point to Basin Modeling, and then click MPath
ACT to open the 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.
Paradigm™
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
♦ On the File menu, point to Import, point to Basin Modeling, click 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
♦ On the File menu, point to Import, point to Basin Modeling, click 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 ♦ On the File menu, point to Import, point to Basin Modeling, click MPath PAR
(Colormap), and then select the file or type the full path and file name in the dialog
box.

Part
II
and Export
Data Import
1.3.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 On the File menu, point to Import, point to Basin Modeling, and then click
IES file as an SGrid PetroMod to open the dialog box.
3 If you want to create a corner-point grid, click load overlays. By default the
converter imports this file and creates a cell-centered SGrid (load facies.).
1. PetroMod is a multi-dimensional modeling software system available from Integrated Exploration

Systems (IES).
Paradigm™
1.4 Importing Cultural Data

GOCAD includes converters for importing 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-14
• "Importing a DXF File," page 1-15
• "Importing a SeisWorks Cultural Data File," page 1-15
1.4.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
must 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 ♦ On the File menu, point to Import, point to Cultural Data, click Arcview, and then
file select the file or type the full path and file name in the dialog box.
1. ArcView is a geographic information system available from the Environmental Systems Research
Institute (ESRI).

Part
II
and Export
Data Import
1.4.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 On the File menu, point to Import, point to Cultural Data, and then click DXF to
open the 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.4.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 ♦ On the File menu, point to Import, point to Cultural Data, click SeisWorks
file Cultural Data (ASC), and then 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.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.4 Importing Cultural Data 1-15
Paradigm™
1.5 Importing Fault Interpretations Data

GOCAD includes converters for importing various 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-16
• "Importing a CPS3 Binary File," page 1-18
• "Importing a Column-Based File," page 1-18
• "Importing a FastEdit Scattered Data File," page 1-23
• "Importing an XYZ File," page 1-24
For information about fault sticks (Curves), see:
• "Importing a Charisma Fault Interpretations File," page 1-24
• "Importing a CPS3 ASCII Polygons (.ply) File," page 1-25
• "Importing a CPS3 ASCII Fault Traces (.flt) File," page 1-25
• "Importing a SeisWorks Fault Sticks File," page 1-26
• "Importing a Z-MAP Fault or Contour File," page 1-26
For information about fault polygons or traces (Curves), see:
• "Importing a Charisma Fault Polygons File," page 1-27
• "Importing a CPS3 ASCII Polygons (.ply) File," page 1-27
• "Importing a FastEdit Fault Polygons File," page 1-28
• "Importing an Irap RMS Fault Polygons or Lines File," page 1-28
• "Importing a SeisWorks Fault Polygon File," page 1-28
1.5.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.
1. CPS3 (a mapping system) is a part of the GeoFrame software product available from Schlumberger.

Part
II
and Export
Data Import
To import a .dat file 1 On the File menu, point to Import, and then do one of the following to open the
as a PointsSet, a dialog box.
Curve, or a Well
If you want to import this To create this
Do this
type of data type of object
Fault interpretations PointsSet Point to Fault Interpretations, and then
click CPS3 ASCII Data (.dat) under
PointsSet
Horizon interpretations PointsSet Point to Horizon Interpretations, and
then click CPS3 ASCII Data (.dat) under
PointsSet
Fault interpretations, fault sticks Curve Point to Fault Interpretations, and then
click CPS3 ASCII Data (.dat) under Fault
Sticks.
Horizon interpretations, Curve Point to Horizon Interpretations, and
contours then click CPS3 ASCII Data (.dat) under
Contours
Well data (X, Y, TVDSS) Well Point to Well Data and then click CPS3
ASCII Data (.dat) under Path and Logs.
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.

Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.5 Importing Fault Interpretations Data 1-17
Paradigm™
1.5.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 import file.
To import a CPS3 ♦ On the File menu, point to Import, point to Fault Interpretations, under
binary .svd file as a PointsSet, click CPS3 Binary (.svd, .svs, .svf, and .svp), and then select the file or
PointsSet type the full path and file name in the dialog box.
1.5.3 Importing a Column-Based File

Note You use the column-based import wizard to import different ASCII file types containing
different types of data (and therefore, creating different objects). The procedure for using this
wizard is explained here and you are referenced to this procedure from the other import options that
use this wizard
The column-based-file converter is an import wizard that guides you through the import
procedure and shows you (in a window in each dialog box) the direct result of the
decisions you make. The converter lets you do the following:
• Import all or only a portion of a file
• Load property data besides X, Y, and Z
• Name the new object (rather than the converter automatically assigning a name or
looking for the name inside the file)
You can create the following objects, depending on the type of data in the file.
If your data file contains You can create this object

Fault interpretations PointsSet
Horizon interpretations
Fault interpretations, fault sticks Curve
Horizon interpretations, contours
Well paths, markers, positions, and/or logs Well
Dip data Dip 1
1. Importing dip data as a Dip object requires the Advanced Structural Analysis
(Kine3D-1) module. For more information about importing dip data, see
Part VII: Geologic Interpretation, "Importing Dip Data" on page 3-31.
For PointsSet or Curve data, the converter creates an object from each file that you
import. For Well data, the converter creates a Well object for each well identified in the
file.
Note The import procedure is similar whether you are importing PointsSet, Curve, or Well data; the
dialog boxes are slightly different when you are importing well data.

Part
II
and Export
Data Import
To import a column- 1 On the File menu, point to Import, and then do one of the following to open the
based file as a dialog box.
PointsSet, Curve, or
Well If you want to import this type To create this
Do this
of data type of object
Fault interpretations PointsSet Point to Fault Interpretations, and then
click Column-based file under PointsSet
Horizon interpretations PointsSet Point to Horizon Interpretations, and
then click Column-based file under
PointsSet
Fault interpretations, fault sticks Curve Point to Fault Interpretations, and then
click Column-based file under Fault
Sticks.
Horizon interpretations, contours Curve Point to Horizon Interpretations, and
then click Column-based file under
Contours
Well data (X, Y, MD, TVDSS) Well Point to Well Data, and then click
Column-based file under Path and
Logs, Path, Markers, Logs, or
Completion Data (depending upon the
type of data in the file).
2 The File type dialog box is the first of four dialog boxes you need to complete before
you can import the file. Click to open the Open dialog box, browse for the file or
files you want to import, and then double-click the file name. The converter enters
the selected file name in the Current file box.
Note In this step, you can select as many files as you want; always ensure that the file name for
the file you intend to work with is showing in the Current file box.
Paradigm™
3 The first 400 lines of the file are quickly preloaded into the viewing window. If you
want to see more than 400 lines, click Preload all to load the entire file.
Note If the data is not what you wanted or expected, click Cancel. You can edit the file in a
text editor, such as Notepad, or select a different file and then begin the import procedure
again.
4 Do one of the following to specify how the columns in the file are separated:
• If each column is a fixed length, click Fixed width, click Next, and then go to
step 6.
– or –
• If the columns are not fixed, leave Delimited selected and click Next to open the
Column Separation dialog box.
5 The Column Separation dialog box shows the column structure of your file and lets
you specify column delimiters. Specify the column delimiters in your file by selecting
the Tab, Semicolon, Comma, Space, and/or Other check boxes. If you select Other,
type the delimiter in the box.
Note The defaults are Tab and Space. You can select as many delimiters as you need. To help
you better read the data, yellow highlighting appears in alternate columns.
6 Click Next to open the Miscellaneous Information dialog box.

Part
II
and Export
Data Import
7 In the Miscellaneous Information dialog box, you are asked a series of four
questions, one at a time, and you must answer each question before the next
question will appear. Click Yes or No (whichever is appropriate) to all the questions.
Paradigm™
8 Click Next to open the Column Assignment dialog box. You are asked a series of
questions, one at a time, and you must answer each question before the next
question will appear. The question vary depending on the type of data you are
importing and the type of object being created.
Note If you click No for X, Y, and/or Z, the converter automatically assigns a value of zero for
that coordinate.
9 If the file you are importing does not have a file name identified in the header
section, type a name for the new object in the Object name box. If you clicked No in
response to the question Do you have a column containing the Name of the object?
in the previous dialog box, you must type a name in this box.
10 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.)
11 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.
12 To add an additional property, click Add, type the name (any name you want) in the
New Property Name, box and then click OK. Then enter the column location
number in the Column number box. The converter will add the property in your file
to the existing object.
13 To remove a property, highlight the name in the Property List and parameters box
and then click Remove.

Part
II
and Export
Data Import
14 Select the Use nodata value check box, if you want the converter to honor a no-
data-value (a number the converter always reads as null).
15 Click Time or Depth to identify how your data values are represented.
Note The default value for this option is whatever unit was selected for the project you are
working in.
16 Review the file to ensure that all additions or changes you made are correct.
17 Click Apply on current file to carry out the command on the file name showing in
the window. If you use this option, GOCAD imports the file, the dialog box remains
open, and the file name remains displayed in the Current file box.
18 If you are importing more than one file, return to step 2, select another file in the
Current file box and repeat the import procedure for that file. Repeat the process
until you complete the import procedure for all files you selected. Then click OK to
import all the selected files.
– or –
Click OK to import all the selected files and close the dialog box.
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click FastEdit
Scattered Data file as Scattered data, and then select the file or type the full path and file name in the
a PointsSet dialog box.
Paradigm™
1.5.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 On the File menu, point to Import, point to Fault Interpretations, and then click X
ASCII file as a Y Z under PointsSets to open the 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.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click Charisma
file as a Curve Fault Interpretations under Fault Sticks, 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.

Part
II
and Export
Data Import
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-16.
If your file contains fault sticks data, the converter creates a Curve object from each file
that you import.
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click CPS3 ASCII
a PointsSet Polygons (.ply) under PointsSet, and then select the file or type the full path and
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click CPS3 ASCII
a Curve Polygons (.flt) under Fault Sticks, and then select the file or type the full path and

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 ♦ On the File menu, point to Import, point to Fault Interpretations, under Fault
binary .svf or .svp file Sticks click CPS3 Binary (.svd, .svs, .svf, and .svp), and then select the file or type
as a Curve the full path and file name in the dialog box.
Paradigm™

You will use the Column-based-file import 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 for using the wizard is similar whether you are importing Well, PointsSet,
or Curve data and therefore is explained only once. For information, see "Importing a
Column-Based File" on page 1-18.
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click Petrel
Pillars file as a Curve Pillars under Fault Sticks, and then select the file or type the full path and file name
in the dialog box.
1.5.13 Importing a SeisWorks Fault Sticks File

Use the Seisworks2 fault sticks converter to create a Curve object from a SeisWorks fault
sticks file.
To import a SeisWorks ♦ On the File menu, point to Import, point to Fault Interpretations, click SeisWorks
fault sticks file as a Fault Sticks under Fault Sticks, and then select the file or type the full path and file
Curve name in the dialog box.
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click
fault traces or Z-MAP Fault or Contour Files under Fault Sticks, and then select the file or type
contour file as a the full path and file name in the dialog box.
Curve
1. Petrel is a software product available from Schlumberger.

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

Part
II
and Export
Data Import
1.5.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 On the File menu, point to Import, point to Fault Interpretations, and then click
Fault Polygon file as a Charisma Fault Polygons under Fault Polygons or Traces to open the dialog box.
Curve
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.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click CPS3 ASCII
Polygons file as a Polygons (.ply) under Fault Polygons or Traces, and then select the file or type the
Curve full path and file name in the dialog box.
Paradigm™
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click Fastedit
fault polygons file as Fault Polygons under Fault Polygons or Traces, and then select the file or type the
a Curve full path and file name in the dialog box.
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click Irap RMS
file as a Curve Fault Polygons or Lines under Fault Polygons or Traces, and then select the file or
type the full path and file name in the dialog box.
1.5.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 ♦ On the File menu, point to Import, point to Fault Interpretations, click SeisWorks
Fault Polygon file as a Fault Polygons under Fault Polygons or Traces, and then select the file or type the
Curve full path and file name in the dialog box.
1. IRAP RMS is a software product available from ROXAR.


Part
II
and Export
Data Import
1.6 Importing Fault Surfaces Data
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-29
• "Importing a FastEdit 2D-Grid File," page 1-30
• "Importing an Irap RMS TriangleSurface File," page 1-30
• "Importing a Petrel Pillars File," page 1-30
• "Importing a RC2 2D-Grid File," page 1-30
• "Importing a RESCUE Model File," page 1-31
• "Importing a StrataModel 2D-Grid File," page 1-32
• "Importing a Z-MAP ASCII 2D-Grid File," page 1-32
1.6.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 ♦ On the File menu, point to Import, point to Fault Surfaces, click CPS3 ASCII 2D-
file as a 2D-Grid Grid (.grd), 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 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.
To import a CPS3 ♦ On the File menu, point to Import, point to Fault Surfaces, click CPS3 Binary
binary .svs file as a (.svd, .svs, .svf, and .svp), and then select the file or type the full path and file
2D Grid name in the dialog box.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.6 Importing Fault Surfaces Data 1-29
Paradigm™
1.6.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 ♦ On the File menu, point to Import, point to Fault Surfaces, click Fastedit 2D-Grid,
2D grid file as a 2D- and then select the file or type the full path and file name in the dialog box.
Grid
1.6.4 Importing an Irap RMS TriangleSurface File

Use the Irap RMS Triangle Surface converter to create a Surface (triangulated surface)
object from an Irap RMS TriangleSurface file.
To import an Irap RMS ♦ On the File menu, point to Import, point to Fault Surfaces, click Irap RMS
TriangleSurface file as TriangleSurface, and then select the file or type the full path and file name in the
a Surface dialog box.
1.6.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 ♦ On the File menu, point to Import, point to Fault Surfaces, click Petrel Pillars, and
Pillars file as a Surface then select the file or type the full path and file name in the dialog box.
1.6.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 ♦ On the File menu, point to Import, point to Fault Surfaces, click RC2 2D-Grid, and
2DGrid file as a 2D then select the file or type the full path and file name in the dialog box.
Grid
1. Petrel is a software product available from Schlumberger.

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

Part
II
and Export
Data Import
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 35.
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.
To import a RESCUE 1 On the File menu, point to Import, point to Reservoir Grid, and then click RESCUE
file as an SGrid or Model (Grids, Horizons, Faults).
Surface (2D Grid)
name in the file name box.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.6 Importing Fault Surfaces Data 1-31
Paradigm™
3 If you want to accept the defaults, you can go to step 4. If you want to review or
change the defaults click Advanced to expand the dialog box.
1.6.7 Importing a StrataModel 2D-Grid File

Use the StrataModel 1 converter to create a 2D-Grid object from an .smg StrataModel file.
To import a 1 On the File menu, point to Import, point to Fault Surfaces, and then click
StrataModel file as a StrataModel 2D-Grid to open the dialog box.
2D Grid
3 Clear the Column Oriented check box, if your file is row oriented. By default, the
converter expects to read a column-oriented file.
1.6.8 Importing a Z-MAP ASCII 2D-Grid File

Use the Z-MAP2 2D Grid converter to create a 2D-Grid object from a Z-MAP.
To import a Z-MAP 2D ♦ On the File menu, point to Import, point to Fault Surfaces, click Z-MAP ASCII 2D-
grid file as a 2D Grid Grid, and then select the file or type the full path and file name in the dialog box.
1. Stratamodel is a software product available from Landmark Graphics.

2. Z-MAP is a software product available from Landmark Graphics.

Part
II
and Export
Data Import
1.7 Importing Horizon Interpretations Data
GOCAD includes converters for importing various files that contain horizon interpretation
data in the form of points, contours, or grids. You can create PointsSets, 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-33
• "Importing a FastEdit Scattered Data File," page 1-34
• "Importing a GSLib 2D Map File," page 1-34
• "Importing a SeisWorks Inline Xline X Y Z File," page 1-35
• "Importing an X, Y, Z File," page 1-35
For information about contours (Curves), see:
• "Importing an Adobe Contours File," page 1-36
• "Importing a FastEdit Horizon Contour File," page 1-37
• "Importing a Z-MAP Contour File," page 1-37
1.7.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 On the File menu, point to Import, point to Horizon Interpretations, click Charisma
file as a PointsSet Horizon Points under PointsSet, and then select the file or type the full path and file
name in the dialog box.

If your file contains horizon data, the converter creates a PointsSet object from each file
that you import.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.7 Importing Horizon Interpretations Data 1-33
Paradigm™

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.
To import a CPS3 ♦ On the File menu, point to Import, point to Horizon Interpretations, click CPS3
binary .svd file as a Binary (.svd, .svs, .svf, and .svp), and then select the file or type the full path and
PointsSet file name in the dialog box.

You will use the Column-based file import 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 "Importing a Column-Based File" on page 1-18.
1.7.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 ♦ On the File menu, point to Import, point to Horizon Interpretations, click FastEdit
scattered data file as Scattered Data, and then select the file or type the full path and file name in the
a PointsSet dialog box.
1.7.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 ♦ On the File menu, point to Import, point to Horizon Interpretations, click GSLib
Map as a PointsSet 2D Map under PointsSets, and then select the file or type the full path and file name
in the dialog box.

Part
II
and Export
Data Import
1.7.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 ♦ On the File menu, point to Import, point to Horizon Interpretations, click
Inline file as a SeisWorks Inline Xline X Y Z under PointsSets, and then select the file or type the
PointsSet full path and file name in the dialog box.
1.7.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 On the File menu, point to Import, point to Horizon Interpretations, and then click
file as a PointsSet XYZ under PointsSet to open the 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.
Paradigm™
1.7.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 ♦ On the File menu, point to Import, point to Horizon Interpretations, click Adobe
Contours as a Curve Contours under Contours, 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.
To import a CPS3 ♦ On the File menu, point to Import, point to Horizon Interpretations, under
binary .svf or .svp file Contours, click CPS3 Binary (.svd, .svs, .svf, and .svp), and then select the file or
as a Curve type the full path and file name in the dialog box.

If your file contains contours, the converter creates a Curve object.
You will use the Column-based file import wizard to import contour 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.

Part
II
and Export
Data Import
1.7.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 ♦ On the File menu, point to Import, point to Horizon Interpretations, click Fastedit
horizon contour file Horizon contours, and then select the file or type the full path and file name in the
as a Curve dialog box.
1.7.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 ♦ On the File menu, point to Import, point to Horizon Interpretations, click Z-MAP
Contour file as a Contour Files, and then select the file or type the full path and file name in the
Curve dialog box.
Paradigm™
1.8 Importing Horizon Surfaces Data

GOCAD includes converters for importing various files that contain horizon surface data
in the form of 2D grid 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-38
• "Importing a FastEdit 2D-Grid File," page 1-39
• "Importing a Geoprobe 2D Grid (.gvw) File," page 1-39
• "Importing a GSLib 2D Map as Surface File," page 1-39
• "Importing an Irap RMS ASCII 2D-Grid File," page 1-39
• "Importing an Irap RMS ASCII 2D-Grid Property File," page 1-40
• "Importing a Norsar Horizons File," page 1-40
• "Importing an RC2 2D-Grid File," page 1-40
• "Importing a RESCUE Model File," page 1-41
• "Importing a StrataModel 2D-Grid File," page 1-41
• "Importing a StrataModel 2D-Grid Property File," page 1-41
• "Importing a Z-MAP ASCII 2D-Grid File," page 1-41
• "Importing a Z-MAP ASCII 2D-Grid Property File," page 1-42
1.8.1 Importing a CPS3 ASCII 2D-Grid (.grd) File

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 ♦ On the File menu, point to Import, point to Horizon Surfaces, click CPS3 ASCII 2D-
as a 2D-Grid Grid (.grd), and then select the 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.
To import a CPS3 ♦ On the File menu, point to Import, point to Horizon Surfaces, click CPS3 Binary
binary .svs file as a 2D (.svd, .svs, .svf, and .svp), and then select the file or type the full path and file
Grid name in the dialog box.

Part
II
and Export
Data Import
1.8.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 ♦ On the File menu, point to Import, point to Horizon Surfaces, click FastEdit 2D-
2D-Grid file as a 2D Grid, and then select the file or type the full path and file name in the dialog box.
Grid
1.8.4 Importing a Geoprobe 2D Grid (.gvw) File

Use the Geoprobe 2D-Grid converter to create a 2D Grid object from Geoprobe .gvw file.
To import a Geoprobe ♦ On the File menu, point to Import, point to Horizon Surfaces, click Geoprobe 2D-
.gvw file as a 2D Grid Grid (.gvw), and then select the file or type the full path and file name in the dialog
box.
1.8.5 Importing a GSLib 2D Map as Surface File

Use the GSLib 2D Map converter to create a Surface object from GSLib 2D Map file.
To import a GSLib 2D ♦ On the File menu, point to Import, point to Horizon Surfaces, click GSLib 2D Map
Map as a Surface as Surface, and then select the file or type the full path and file name in the dialog
box.
1.8.6 Importing an Irap RMS ASCII 2D-Grid File

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 ♦ On the File menu, point to Import, point to Horizon Surfaces, click Irap RMS ASCII
RMS ASCII grid file as 2D-Grid, and then select the file or type the full path and file name in the dialog box.
a 2D-Grid object
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.8 Importing Horizon Surfaces Data 1-39
Paradigm™
1.8.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 On the File menu, point to Import, point to Horizon Surfaces, click Irap RMS ASCII
ASCII grid file as 2D- 2D-Grid Property.
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 IRAP file 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.8.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-66.
NORSAR-2D and NORSAR-3D are software products available from NORSAR.
1.8.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 ♦ On the File menu, point to Import, point to Horizon Surfaces, click RC2 2D-Grid,
2DGrid file as a 2D and then select the file or type the full path and file name in the dialog box.
Grid

Part
II
and Export
Data Import
1.8.10 Importing a RESCUE Model File
If your file contains surface data, the converter creates a Surface object.
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 information about how to import this
type of file, see "Importing a RESCUE Model File" on page 1-31.
1.8.11 Importing a StrataModel 2D-Grid File

You can use the StrataModel converter to create a 2D-Grid object from a .smg
StrataModel file. For information about how to import this type of file, see "Importing a
StrataModel 2D-Grid File" on page 1-32.
1.8.12 Importing a StrataModel 2D-Grid Property

File
Use the StrataModel Property converter to import StrataModel 2D-Grid properties to an
existing 2D Grid.
To import a 1 On the File menu, point to Import, point to Horizon Surfaces, and then click
StrataModel property StrataModel 2D-Grid Property to open the dialog box.
file to an existing 2D
Grid
2 In the 2D-Grid box, enter the name of the existing 2D-Grid object.
1.8.13 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 ♦ On the File menu, point to Import, point to Horizon Surfaces, click Z-MAP ASCII
grid file as a 2D-Grid 2D-Grid, and then select the file or type the full path and file name in the dialog box.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.8 Importing Horizon Surfaces Data 1-41
Paradigm™
1.8.14 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 On the File menu, point to Import, point to Horizon Surfaces, and then click Z-
MAP ASCII 2D-Grid Property to open the 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 Click , browse for the file you want to import, and then double-click the file
name. The program enters the selected file name in the Z-MAP file box.
5 In the Property name box, type the name of the property you want to import.

Part
II
and Export
Data Import
1.9 Importing Image Files
GOCAD includes converters for importing existing images. You can create a Voxet object
from these data files.
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 On the File menu, point to Import, point to Images, and then click 2D Voxet to
3 If you want the converter to convert characters into float values, select the convert
to float value check box.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.9 Importing Image Files 1-43
Paradigm™
1.10 Importing Reservoir Grid Data

GOCAD includes converters for importing various files that contain 3D reservoir grid data
from standard commercial flow simulators such as ECLIPSE (Schlumberger) or VIP
(Halliburton) or through the reservoir grid exchange format RESCUE. You can create a
stratigraphic grid (SGrid object) from these data files or you can import the property data
and assign them to existing SGrids.
section.
The following topics provide information about the supported import sources for specific
object types and how to import the files.
For information about importing SGrids, see:
• "Importing an ECLIPSE ASCII Grid File," page 1-45
• "Importing an ECLIPSE Binary Grid File," page 1-46
• "Importing a RESCUE Model (Grids, Horizons, Faults) File," page 1-53
• "Importing a VIP ASCII Grid File," page 1-53
• "Importing a VIP or ECLIPSE LGR File," page 1-54
For information about object properties, see:
• "Importing ECLIPSE ASCII Properties File," page 1-55
• "Importing an I J K Property File," page 1-56
• "Importing a VIP ASCII Properties File," page 1-57
For information about importing faults, see:
• "Importing an ECLIPSE ASCII Faults File," page 1-57

Part
II
and Export
Data Import
1.10.1 Importing an ECLIPSE ASCII Grid File
Use the ECLIPSE ASCII Grid converter to create an SGrid object from an ECLIPSE ASCII file.
If the file contains property values, you can import the properties at the same time. For
information about how to import ECLIPSE property data, see "Importing ECLIPSE ASCII
Properties File" on page 1-55.
ECLIPSE (a reservoir simulation software) is a part of the Schlumberger Information Solutions
(formerly GeoQuest) suite of simulators.
To import an ECLIPSE 1 On the File menu, point to Import, point to Reservoir Grid, and then click ECLIPSE
ASCII file as an SGrid ASCII Grid under SGrid.
2 In the File name box, enter the path and file name of the file that you want to
import.
3 To modify the grid origin, import well completions or local grid refinements (LGRs), or
specify the units, click Advanced, and then do the following as necessary:
a To import the well completions along with the grid and properties, select the
Import Well Completions check box.
b 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.
c To modify the origin of the grid, select the Modify Grid Origin relative to
SGrid Axis check box, and then in the X, Y, and/or Z boxes, select max
(maximum). The default for the coordinates is min (minimum).
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.10 Importing Reservoir Grid Data 1-45
Paradigm™
d 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
Note GOCAD automatically selects units based on the default Z-axis setting (in the New
e 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 select the appropriate units.
For information about setting units for your project, see "Setting Units for a
GOCAD Project" on page 1-12.
Notes
• The imported grid and properties appear in the Object Tree under SGrid, object.
• If you imported well completions, the completions appear as SGrid properties and the date
is included in the name (for example, completions_1998_01_01). The wells appear in the
Object Tree under Group, groupname, wells.
1.10.2 Importing an ECLIPSE Binary Grid File

You can use the ECLIPSE binary grid converter to create an SGrid object from an ECLIPSE
binary file. You can also import the .INIT file (containing initial properties) and .UNRST file
(containing time dependant properties) at the same time.
Note The binary ECLIPSE file (.GRID or .EGRID), the initial reservoir data file (.INIT), and the unified
restart data file (.UNRST) must have the same file name: name.GRID, name.INIT, and name.UNRST.
All files must be binary and must be located in the same directory.
Exception If you are importing more than one restart file, the extensions must be .X0000, .X0001
and so on.
You can also import LGR data (local grid refinements) with this converter. When you
import a grid from an ECLIPSE binary file that contains LGRs, the converter automatically
imports all of the 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 them, see Part X: Reservoir Production and Simulation, "What Is Upscaling and
Downscaling?" on page 2-2.

Part
II
and Export
Data Import
To import an ECLIPSE 1 On the File menu, point to Import, point to Reservoir Grid, and then click ECLIPSE
binary file as an SGrid Binary Grid to open the dialog box.
2 In the Grid file box, enter the path and file name of the file containing the grid that
you want to import.
Note You can only select files with the .GRID or .EGRID extension.
When you select the grid file, if the .INIT and .UNRST files are in the same folder, the
converter automatically selects them for you.
3 If the imported grid does not include some of the required information, complete
these steps in the General Information panel.
a If the grid origin is not defined, type the X, Y, and Z coordinates in the boxes to
define the grid origin.
b If the map rotation is not defined, type the angle in the Angle (degrees,
clockwise) box.
Paradigm™
c If the areal and vertical units of measurement are not defined, click Feet or
Meters under Map units and Grid units.
4 If you want to import all of the data contained in the binary file (all initial properties
and time-dependant properties using all report dates) and you don’t want to make
any adjustments to the grid, you can complete this procedure by clicking OK to
import the file and create the SGrid object. Otherwise, you can selectively choose
what properties to import and adjust the grid by completing the remaining steps in
this procedure.

Part
II
and Export
Data Import
5 To select the initial properties to import:
a In the General Information panel, 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.
6 To the select the 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.
Paradigm™
d In the Properties box, select the time-dependent properties.
7 To select the report dates for the time-dependent properties:

a Click the General Information tab and select the Select individual report
dates in the time-dependent properties panel check box.
b Click the Time-Dependent Properties tab.
c Under Report dates, do one of the following:
• To individually select report dates, click Select individual report dates in
the list below and select the dates in the list.
• To automatically select the dates according to frequency and start and end
dates, click Select one every number report dates, and then select the
frequency number. In the From and To boxes, select the start and end dates.

Part
II
and Export
Data Import
Important If you have only one restart file, the extension must be .UNRST (meaning
unified restart). If you are importing more than one restart file, the extensions must
be .X0000, .X0001 and so on.
Paradigm™
8 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-34.
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.
The imported grid and properties appear in the Object Tree under the name of the SGrid
object.

Part
II
and Export
Data Import
1.10.3 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-31.
1.10.4 Importing a VIP ASCII Grid File

Use the VIP 1 ASCII Grid converter to create an SGrid object from a VIP ASCII file. If the file
contains property values, you can import the properties at the same time. For procedures
to load property data, see "Importing a VIP ASCII Properties File" on page 1-57.
To import a VIP file as 1 On the File menu, point to Import, point to Reservoir Grid, and then click VIP
an SGrid ASCII Grid under SGrid to open the 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
import file.
1. VIP is a software product available from Landmark Graphics.
Paradigm™
1.10.5 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, do one of the following:

ECLIPSE LGR file
• From the menu bar, click the File menu, point to Import, point to Reservoir
Grid, and then click VIP LGR or ECLIPSE LGR.
• In the Object Tree, right-click the name of the SGrid object that you want to
contain the LGRs, and then point to Import LGR From and click VIP LGR File or
ECLIPSE LGR File.
import.
3 In the Stratigraphic grid box, enter the name of the existing SGrid object that you
want to contain the local refinement data.
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 Upscaler 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-113.
1. VIP is a software product available from Landmark Graphics.

2. ECLIPSE is a software product available from Schlumberger.

Part
II
and Export
Data Import
1.10.6 Importing ECLIPSE ASCII Properties File
Use the ECLIPSE ASCII Properties converter to import properties, from an ECLIPSE ASCII
file, to existing SGrid objects. You can import properties to 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 On the File menu, point to Import, point to Reservoir Grid, and then click ECLIPSE
properties into an ASCII Properties under Properties to open the dialog box.
SGrid
2 In the Stratigraphic Grid box, select the file 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 existing grid.
Paradigm™
1.10.7 Importing an I J K Property File

Use the I J K Property converter to import data that the converter will use to modify values
of a property in an existing SGrid or Voxet object. You can apply the data in this 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 SGrid.
The mapping of the property data is done by using the U, V and W information. The file
being imported must be an ASCII file that contains four columns: U, V, W and Property
Value.
To import an I J K 1 On the File menu, point to Import, point to Reservoir Grid, and then click IJK
property file to an Property under Properties to open the 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 you want the converter to start the grid
indices at one. By default the converter starts the grid indices at zero.

Part
II
and Export
Data Import
1.10.8 Importing a VIP ASCII Properties File
Use the VIP ASCII Properties converter to 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 SGrid.
To import VIP 1 On the File menu, point to Import, point to Reservoir Grid, click VIP ASCII Grid to
properties into an open the dialog box.
existing SGrid
2 In the Stratigraphic Grid box, select the file 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.
1.10.9 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
SGrid.
To import ECLIPSE 1 On the File menu, point to Import, point to Reservoir Grid, and then click ECLIPSE
fault data into an ASCII Fault to open the 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.
Paradigm™
1.11 Importing Seismic Data

GOCAD includes converters for importing various files that contain seismic data. You can
create Voxet, Surface, or SGrid objects from these data files.
These topics provide information about supported import sources and how to import the
files.
For information about importing seismic cubes, see:
• "Importing a SEG-Y 3D File as Voxet," page 1-58
• "Importing a VoxelGeo File," page 1-62
• "Importing an SEP File," page 1-65
• "Importing a Norsar Depth Cube File," page 1-66
For information about importing seismic lines, see:
• "Importing a 2D SEG-Y File as Surface," page 1-66
• "Importing a 2D SEG-Y File as SGrid," page 1-66
For information about importing color maps, see:
• "Importing a SeisWorks Colormap," page 1-67
To import a VoxelGeo ♦ On the File menu, point to Import, point to Seismic Data, click VoxelGeo, and then
file as a 2D-Grid select the file or type the full path and file name in the dialog box.
1.11.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 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.

Part
II
and Export
Data Import
To import a 3D SEG-Y 1 On the File menu, point to Import, point to Seismic Data, and then click SEG-Y 3D
file as a Voxet as Voxet under Seismic Cubes to open the 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.
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:
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.11 Importing Seismic Data 1-59
Paradigm™
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).

Part
II
and Export
Data Import
6 If you want to edit values, other than dimensions or geometry, click the Advanced
tab to open the 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 (’trwf’) 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 (’scalco’)
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 there are missing traces in the file, select the Some Traces are missing check
box.
g 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.
Paradigm™
7 If you want to see the different headers that are in the file, click the SEG-Y Headers
tab to open the dialog box.
EBCDIC
Header
a 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, click OK
to carry out the command and close the dialog box, or click Apply to carry out the
command and leave the dialog box open.
1.11.2 Importing a VoxelGeo File

Use the VoxelGeo converter to create a Voxet object from a VoxelGeo file (8 bytes only).
GOCAD 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.

Part
II
and Export
Data Import
1.11.3 Importing a 2D SEG-Y File
GOCAD includes two converters for importing data from a 2D SEG-Y file.
• A converter that imports 2D SEG-Y data and creates a Voxet object (contains the
seismic data), and a Surface object (contains the data that defines the geometry (areal
and vertical) of the line).
• A converter that imports 2D SEG-Y data and creates an SGrid object.
The converter determines which object or objects you want to create based on the import
action you select from the Import Option menu. You will use the same dialog box to
provide data for the converter to use.
Note To display the 2D SEG-Y object, you must display the Surface object in the 3D Viewer. GOCAD
automatically displays the seismic data on the Surface.
Paradigm™
To import a 2D SEG-Y 1 On the File menu, point to Import, point to Seismic Data, and then do one of the
file as a Voxet and following:
Cross Section or as an
• If you want to create a Voxet object and a Surface object, click 2D SEG-Y as
SGrid
Voxet under Seismic Cubes to open the dialog box.
• If you want to create an SGrid object click 2D SEG-Y as SGrid under Seismic
Lines to open the dialog box.
2 In the Segy file box, enter the path and file name of the file that you want to import.
• If the trace geometry data for your SEG-Y file is contained in a separate file and
you want the converter to use the data in that file (this is the default), leave the
use navigation data check box selected and go to step 4.
• If the data is not contained in a separate file, clear the use navigation data
check box and go to step 7.
4 In the Navigation file box, enter the path and file name of the file that you want to
import.

Part
II
and Export
Data Import
5 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.
6 The navigation file contains shot-point data that tells the converter how to read the
SEG-Y trace data. Because the SEG-Y data is ordered by trace, which is rarely the
same as shot point, you must specify the relationship between the trace number in
the SEG-Y file and the shot point number in the navigation file.
a In the first shot point box, type the shot-point number of the first trace in the
navigation file. The default is 0.
b In the number of trace per sp box, type the number of traces per shot point
(delta between two shot points). The default is 1.
c If the shot point number decreases with the trace number, select the sp decrease
with trace number check box.
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.
Tip With the previous 8 If you want to manually specify the maximum depth or time, select the specify
informations and this maxzt check box. If you do not select this check box, the converter computes the
maximum distance, the
value from the SEG-Y header.
converter creates a Surface
and the Voxet object 9 Select the use segy shot geometry check box if you want the converter to read the
properties are automatically line geometry from the shot location. If you are not using a separate navigation file,
texture-mapped onto this
you must specify how the converter should define the line geometry. By default the
surface.
converter reads the line geometry from the geophone location in the SEG-Y trace
header. If you are using a separate navigation file, the check box is unavailable.
1.11.4 Importing an SEP File

Use the SEP 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.
The Stanford Exploration Project (SEP) is an industry-funded academic consortium devoted to seismic
imaging. SEPlib is a complete and freely distributed seismic data processing software product
developed by SEP.
To import an SEP file ♦ On the File menu, point to Import, point to Seismic Data, click SEP and then select
as a Voxet the file or type the full path and file name in the dialog box.
Paradigm™
1.11.5 Importing a Norsar Depth Cube File

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 X, Y, T (time) Voxet with X depth, Y depth and
Z depth as extra properties, which GOCAD uses during the time-to-depth conversion.
To import Norsar file 1 On the File menu, point to Import, point to Seismic Data, and then click Norsar
as a Voxet Depth Cube to open the dialog box.
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.11.6 Importing a 2D SEG-Y File as Surface

Use the 2D SEG-Y converter to import a 2D SEG-Y file and create a vertical Surface object
(carrying the geometry data) and a Voxet object (carrying the property data). For
information about how to import a 2D SEG-Y file, see "Importing a 2D SEG-Y File" on
page 1-63.
1.11.7 Importing a 2D SEG-Y File as SGrid

Use the 2D SEG-Y as SGrid converter to create an SGrid object from a 2D SEG-Y file. In
contrast to the 2D SEG-Y-as Surface converter, which creates a vertical Surface object
(carrying the geometry data) and a Voxet object (carrying the property data) this converter
creates one SGrid object that contains geometry and property data.
For information about how to import a 2D SEG-Y file, see "Importing a 2D SEG-Y File" on
page 1-63.

Part
II
and Export
Data Import
1.11.8 Importing a SeisWorks Colormap
You can use the SeisWorks converter to create a color map from a SeisWorks Colormap
file.
To import a SeisWorks ♦ On the File menu, point to Import, point to Seismic Data, click SeisWorks under
Colormap Colormaps, and then select the file or type the full path and file name in the dialog
box.
Paradigm™
1.12 Importing Velocity Data

GOCAD includes 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-68
• "Importing a ProMAX File," page 1-68
• "Importing a TDQ (.avf) File," page 1-69
• "Importing a Velf File," page 1-69
For information about importing velocity cubes, see:
• "Importing a SEG-Y 3D as Voxet File," page 1-69
• "Importing a SEP File," page 1-69
• "Importing a VoxelGeo File," page 1-69
For information about importing velocity lines, see:
• "Importing a SEG-Y 2D as Surface File," page 1-69
• "Importing a SEG-Y 2D as SGrid File," page 1-70
1.12.1 Importing a Jason ASCII Traces File

Use the Jason ASCII import file to create a Curve object from Jason ASCII Traces file. The
traces in this file are converted into a Curve that has velocity data as properties.
To import a Jason ♦ On the File menu, point to Import, point to Velocity Data, click Jason ASCII Traces
trace file under Velocity Functions, and then select the file or type the full path and file name
in the dialog box.
1.12.2 Importing a ProMAX File

Use the ProMAX converter to import velocity data from a ProMAX file and create an
object.
To import a Promax ♦ On the File menu, point to Import, point to Velocity Data, click Promax under
file Velocity Functions, and then select the file or type the full path and file name in the
dialog box.

Part
II
and Export
Data Import
1.12.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 ♦ On the File menu, point to Import, point to Velocity Data, click TDQ (.avf) under
as a Curve Velocity Functions, and then select the file or type the full path and file name in the
dialog box.
1.12.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 On the File menu, point to Import, point to Velocity Data, click Velf, and then select
as a Well the file or type the full path and file name in the dialog box.
1.12.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-58.
1.12.6 Importing a 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-65.
1.12.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 "To import a VoxelGeo file as a
2D-Grid" on page 1-58.
1.12.8 Importing a SEG-Y 2D 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.
1. TDQ is a software product available from Landmark Graphics.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.12 Importing Velocity Data 1-69
Paradigm™
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-63.
1.12.9 Importing a SEG-Y 2D 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-63.

Part
II
and Export
Data Import
1.13 Importing Well Data
GOCAD includes converters for importing several types or categories of well data,
including paths, logs, markers, deviations, and picks.
Note You will find that some of the converters are listed more than once in this section. That is
because you can use that converter to import files that contain different kinds of data. For example,
you can use the column-based import wizard to import column-based files that contain path and log
data, just path data, or just log data; therefore, you see this converter listed under all three
categories.
section.
Path and Logs
• "Importing an Excel File," page 1-72
• "Importing an Irap RMS File," page 1-73
• "Importing an LAS File," page 1-74
• "Importing an RC2 File," page 1-78
• "Importing a Temis3D File," page 1-79
• "Importing a WITSML File," page 1-79
Path
• "Importing an X Y Z File," page 1-80
• "Importing an Octopus File," page 1-80
• "Importing Locations from Column-Based File," page 1-81
Markers
"Importing Well Marker Data from a Column-Based File," page 1-82
Logs
• "Importing Log Data from Column-Based File," page 1-82
• "Importing Log Data from an LAS File," page 1-82
• "Importing Log Data from ASCII File with Header," page 1-83
Symbols
"Importing Well Symbol Data," page 1-86
Completion data
• "Importing Completion Data from Column-Based File," page 1-83
Production data
• "Importing Well Production Data from ECLIPSE Binary file," page 1-84

You will use the Column-based-file import 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.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.13 Importing Well Data 1-71
Paradigm™

If your file contains well path and log data, the converter creates an object for each well
identified in the file.
1.13.3 Importing an Excel File

Use the Excel converter to create a Well object from well data in an Excel spreadsheet.
Excel is a software product offered by Microsoft® Corporation.
To import an Excel 1 On the File menu, point to Import, point to Well Data, and then click Excel under
spreadsheet as a Well Path and Logs to open the 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

Part
II
and Export
Data Import
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.
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.
1.13.4 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.
To import an Irap well 1 On the File menu, point to Import, point to Well Data, and then click Irap RMS
file as a Well under Path and Logs.
3 In the Null Value box, type the no data value. The default is -999.0.
Paradigm™
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.
1.13.5 Importing an LAS File

Use the LAS converter to create a Well object from an LAS (up to version 2.0) ASCII file or
to add data to an existing Well object.
About LAS The Log ASCII Standard (LAS) was first proposed in 1990 by the Canadian Well Logging
Society to facilitate simple and easy exchange of digital well log data between logging
service companies and clients. It has since become a de facto industry standard.
Specifying units If the LAS file does not contain units, you can specify them in the dialog during the
during import import. If the LAS file does contain units, they will automatically be used, regardless of
the units that you specify during import.
For more information about importing an LAS file, see:
• "Importing an LAS File as a New Well Object," page 1-74
• "Importing Data from LAS to Update an Existing Well," page 1-78
Importing an LAS File as a New Well Object

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 On the File menu, point to Import, point to Well Data, and then, under Path and
object from an LAS Logs, click LAS to open the dialog box.
file

Part
II
and Export
Data Import
2 Click to open the Open dialog box, browse for and select the files you want to
import, and then click Open.
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 open the Open dialog box, 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 to open the dialog box. If the file does
not contain deviation data, go to step 6.
Paradigm™
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.

Part
II
and Export
Data Import
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
Note GOCAD automatically selects units based on the default z-axis setting (in the New
• 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.
Paradigm™
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 must 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 On the File menu, point to Import, point to Well Data, and then, under Logs, click
an LAS file to update LAS to open the dialog box.
an existing well
2 Click to open the Select Text File dialog box, browse for and select the files you
want to import, and then click Open.
3 To specify how to import the name of the well, click Options for the name of the
well, and then 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.
1.13.6 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 ♦ On the File menu, point to Import, point to Well Data, click RC2 under Path and
a Well Logs, and then select the file or type the full path and file name in the dialog box.

Part
II
and Export
Data Import
1.13.7 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 ♦ On the File menu, point to Import, pint to Well Data, click Temis3D under Path
file as a Well and Logs, and then select the file or type the full path and file name in the dialog
box.
1.13.8 Importing a WITSML File

Use the WITSML converter to create a Well object from a WITSML file.
The converter creates one Well object for each file.
WITSML is an acronym for Wellsite Information Transfer Standard Markup Language and is an
industry standard for transferring data between businesses.
To import a WITSML 1 On the File menu, point to Import, point to Well Data, and then click WITSML
file as a Well under Path and Logs to open the dialog box.
Paradigm™
2 Click to open the Select Text File dialog box, browse for the files you want to
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.

You will use the Column-based-file import 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.
1.13.10 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 ♦ On the File menu, point to Import, point to Well Data, click X Y Z file under Path,
as a Well and then select the file or type the full path and file name in the dialog box.
1.13.11 Importing an Octopus File

Use the Octopus1 converter to create a Well object from an Octopus ASCII file.
Important To use this import converter, you must have Octopus software and GOCAD 2009
installed on the same computer. Creating a Well object from this file requires data exchange
interaction between the two software products. Octopus is a software product that provides well
data in a format that supports data exchange between businesses for the purposes of analysis and
optimization for field development and drilling operations.
Note When you first import this file, the converter will create a PointsSet object. After you
complete the steps in this procedure, the converter then creates a Well object that contains the well
path data.
1. Octopus is a software product available from Techdrill International.

Part
II
and Export
Data Import
To import an Octopus 1 On the File menu, point to Import, point to Well Data, and then click Octopus
file as a Well under Path to open the Well Planner dialog box.
2 Click to open the Select Text File dialog box, browse for the files you want to
import, and then double-click the file names. The program enters the selected file
names in the Octopus project file box.
3 In the Well Planning Categories box select Target (the other options are
unavailable).
4 Click Time or Depth to specify how the data in your file is represented.
5 If you want to change any of the X, Y, or Z coordinate values for a Target Name,
enter the new value in the appropriate box. The target name values represent well
marker locations.
6 If you want to change any of the X, Y, or Z coordinate values for a Vector Name,
enter the new value in the appropriate box. The vector name values represent well
marker locations.
7 Click N to add a new Target Name and its coordinate locations to your file. When you
initially load the file, the converter displays as many lines of data in your file as will fit
in the dialog box window. Clicking N adds a new line at the end of the file. You can
add only one new target name with its coordinates at a time.
8 If you want to delete a target name from the displayed file, highlight the Target Name
you want to delete and then click D.
9 When you finish reviewing the file, click Send to Octopus to send the data file to the
Octopus software product.
• Octopus will calculate the well path (casing and uncertainty values). You can
monitor this activity in the Octopus software.
• Ensure that the calculations are complete and are successful.
Note There is no notification in GOCAD when this calculation is complete.
10 When the calculation is complete in Octopus, click Update.

The converter imports the file again (with the newly calculated well paths) into GOCAD
and creates a new Well object
1.13.12 Importing Locations from Column-Based File

You can use the Column-based-file converter to import an ASCII file and create a
PointsSet, Curve, or Well object. For information about how to import this type of file, see
"Importing a Column-Based File" on page 1-18.
Paradigm™
1.13.13 Importing Well Marker Data from a Column-

Based File
You can use the column-based wizard to import and add well marker data (from an ASCII
file) to an existing Well object.
1.13.14 Importing Log Data from Column-Based File

You will use the Column-based-file import 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.
1.13.15 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-74.

Part
II
and Export
Data Import
1.13.16 Importing Log Data from ASCII File with
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 On the File menu, point to Import, point to Well Data, and then click ASCII File
a Well with Header under Logs to open the dialog box.
2 In the Well Well box, enter the name of the existing Well object.
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.13.17 Importing Completion Data from Column-

Based File
You can use the Column-based-file converter to import an ASCII file and add completion
data to an existing Well object. For information about how to import this type of file, see
"Importing a Column-Based File" on page 1-18.
Paradigm™
1.13.18 Importing Well Production Data from ECLIPSE

Binary file
You can use the Production Data converter to import an ECLIPSE binary data file and add
production data to an existing Well object.
To import Production ♦ On the File menu, point to Import, point to Well Data, click ECLIPSE binary file
data for an existing under Production data, and then select the file or type the full path and file name in
Well the dialog box.

Part
II
and Export
Data Import
1.14 Importing Cross Section Data
When you import a file that contains cross section data, GOCAD stores that data as a
series of PointsSet, Curve, or Surface objects, depending upon the type of data in your
file.
• "Importing a DXF File," page 1-85
• "Importing a GeoSec Cross Section File," page 1-85
• "Importing a Locace File," page 1-85
1.14.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-15.
1.14.2 Importing a GeoSec Cross Section File

Use the GeoSec converter to create an object from an .ihf file. If the file contains
geometry data for more than one object, the converter creates a new Curve or PointsSet
object for each set of geometry data.
The converter expects to read an ASCII .ihf file.
To import a Geosec ♦ On the File menu, point to Import, point to CrossSections, click Geosec, and then
file as a Curve select the file or type the full path and file name in the dialog box.
1.14.3 Importing a Locace File

Use the Locace converter to import a Locace file. By default the converter creates a Curve
object from the data in this file.
To import a Locace ♦ On the File menu, point to Import, point to CrossSections, click Locace, and then
file as a Curve select the file or type the full path and file name in the dialog box.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 1.14 Importing Cross Section Data 1-85
Paradigm™
1.14.4 Importing Well Symbol Data

Use the Well Status Symbols converter to import well symbol data to an existing Well
object.
1 On the File menu, point to Import, point to Well Data, click Well Status Symbols
under Symbols to open the dialog box.
3 In the Well Name Column box, type the column number where you want the
converter to start reading the name of the existing Well object.
4 In the Symbol Name Column box, type the column number where you want the
converter to reading 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.

2
Exporting Data
In this chapter • "Converters," page 2-2 • "Exporting Voxet Data," page 2-29
• "Basic Procedures for Exporting • "Exporting SGrid Data," page 2-33

Data," page 2-4
• "Exporting Well Data," page 2-60
• "Exporting PointsSet Data,"
page 2-18 • "Exporting a View as an Image,"
page 2-65
• "Exporting Curve Data," page 2-19
• "Exporting an SGrid and Data to an
• "Exporting Surface Data," page 2-23 Isatis File," page 2-69
• "Exporting 2D-Grid Data," page 2-26
Overview Paradigm™ GOCAD ® 2009 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 the file
formats for which GOCAD provides an export converter.
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 GOCAD provides 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 pdgm.com/support.
2-1
Paradigm™
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

objects in GOCAD 2009 You can export this To these programs or data With these common
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 GOCAD® 2009.1 User Guide

Part
II
and Export
Data Import
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
Octopus
Viewer images CGM
Picture .jpeg, .bmp, .pbm, .pgm, .png,
.ppm, .rgb, .tiff, .xbm, .xpm
VRML .vrml
SGrid + data Isatis
(Continued 2 of 2)
Paradigm™
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-16
• "Exporting Velocity Data to a Velf File," page 2-17

Part
II
and Export
Data Import
2.2.1 Exporting an Object to a Custom ASCII File
Use this procedure to 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 On the File menu, point to Export, point to the object you are exporting (PointsSet,
a custom ASCII file Curve, or Surface) and then click Custom ASCII to open the 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.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.2 Basic Procedures for Exporting Data 2-5
Paradigm™
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 the Add, Insert, and Remove buttons. You can
arrange the sequence by clicking the Up and Down buttons.
• 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.

Part
II
and Export
Data Import
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 On the File menu, point to Export, point to the objects you are exporting (PointsSet,
a DFX file Curve, or Surface) and then click DFX to open the 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 GOCAD to Excel. You can export
properties of the following object types to Excel:
• PointsSet • Curve
• Surface • 2D-Grid
• Voxet • SGrid
• Well • Solid
• Channel
Paradigm™
To export object 1 On the File menu, point to Export, point to the object you are exporting (PointsSet,
properties to Excel Curve, Surface, 2D-Grid, Voxet, SGrid, or Well) and then click Export Properties
to Excel to open the 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.

Part
II
and Export
Data Import
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.
Paradigm™
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 must specify which object you want to compute
the distribution for. The source name is composed by 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.

Part
II
and Export
Data Import
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 must 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.
Paradigm™
2.2.4 Exporting an Object to an Isatis File

Use this procedure to export an object to Isatis. For details about the Isatis program, visit
the Geovariances Inc. Web site at www.geovariances.com.
GOCAD connection GOCAD must connect to the Isatis database using the GTXserver, a program provided by
with Isatis Geovariances. This program is installed with Isatis. If you have Isatis installed on the same
machine as GOCAD 2009, 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. This program is available for several
platforms:
• Microsoft Windows
• Red Hat - Linux
• Sun - Solaris
• Silicon Graphics - Irix
To access to the database, GOCAD first opens a connection with the database and then
uses the GTXserver for loading or saving data. The connection is closed once the load or
save are 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.
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.

Part
II
and Export
Data Import
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
About.
The structure of each study is:
Isatis objects Isatis contains a set of files corresponding to GOCAD object types. This table shows the
relationship between the object types and the corresponding Isatis file types.
GOCAD object type 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. The different types of
database properties are:
• Character variables (string).
• 1-bit variable, defining subsets of object (a subset is equivalent to region in GOCAD).

• Scalar variable.
• Macro variable for multi-realization property representation.
This table shows the relationship between the GOCAD properties and the corresponding
Isatis variables.
GOCAD property Isatis variable

Region flag Selection variable/1-bit variable
1-dimension float property Float variable
Multidimensional variable Macro variable
Paradigm™
To export an object to 1 On the File menu, point to Export, point to the object you are exporting (PointsSet,
an Isatis file Curve, Surface, 2D-Grid, Voxet, SGrid, or Well) and then click Export Isatis to open
the dialog box.
2 To set the advanced connect parameters, click Advanced to open the Advanced
Connect Parameters dialog.
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.

Part
II
and Export
Data Import
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.
• If you are a Linux user, if necessary, you may need to define the GTX_HOME
environment variable and then restart GOCAD 2009.
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.
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 GOCAD properties.
11 In the Regions box, enter the object regions to export to Isatis.
Paradigm™
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 On the File menu, point to Export, point to the object you are exporting (Curve or
a Medica file 2D-Grid) and then click Medica to open the 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.
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 On the File menu, point to Export, point to the object you are exporting (Voxet or
an AVF file SGrid) and then click AVF to open the dialog box.
2 In the Grid Object box, select the objects (Voxet or SGrid) to export.
1. Medica is a mapping product embedded in the Temis3D program developed by IFP, Inc., and sold
by Beicip, Inc. For more information, visit www.beicip-inc.com.

Part
II
and Export
Data Import
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 On the File menu, point to Export, point to the object you are exporting (Voxet or
a Velf file SGrid) and then click Velf to open the 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.
Paradigm™
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 On the File menu, point to Export, point to PointsSet, and then click FastEdit to
2 In the PointsSet box, enter the point sets to export.

existing one.
1. For information about the FastEdit program, visit CGG Inc. at www.cgg.com.

Part
II
and Export
Data Import
2.4 Exporting Curve Data
GOCAD includes converters for exporting Curve data to various programs and data types.
Supported export sources and how to export the specific files are described in this section.
• "Exporting a Curve to a FastEdit Fault Polygon File," page 2-19
• "Exporting a Curve to an IRAP File," page 2-20
• "Exporting a Curve to a SeisWorks Fault Sticks File," page 2-20
• "Exporting a Curve to a Z-MAP Faults File," page 2-21
• "Exporting a Curve to a Z-MAP Contours File," page 2-22
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
Curve object 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 On the File menu, point to Export, point to Curve, and then click FastEdit to open
FastEdit polygon file the dialog box.
2 In the Curve box, enter the curves to export.

existing one.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.4 Exporting Curve Data 2-19
Paradigm™
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 On the File menu, point to Export, point to Curve, and then click IRAP to open the
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
Use this procedure to export Curve object date to a SeisWorks Fault Sticks file. For details
about the SeisWorks program, visit Landmark Graphics Corporation at
www.halliburton.com.
To export a Curve to a 1 On the File menu, point to Export, point to Curve, and then click SeisWorks Fault
SeisWorks Fault Sticks Sticks to open the 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.
1. For information about the Irap RMS program, visit Roxar Inc. at www.roxar.com.

Part
II
and Export
Data Import
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.
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
must 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 On the File menu, point to Export, point to Curve, and then click Z–MAP Faults to
Z–MAP Faults file open the dialog box.
2 In the Curve Fault Polygons box, enter the curves to export.

existing one.
1. For formation about the Z-Map program, visit Landmark Graphics at www.halliburton.com.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.4 Exporting Curve Data 2-21
Paradigm™
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 On the File menu, point to Export, point to Curve, and then click Z–MAP Contours
Z–MAP Contours file to open the dialog box.
2 In the Curve Contours box, enter the curves to export.

existing one.
1. For information about the Z-Map program, visit Landmark Graphics at www.halliburton.com.

Part
II
and Export
Data Import
2.5 Exporting Surface Data
GOCAD includes converters for exporting Surface data to various programs and data
types. Supported export sources and how to export the specific files are described in this
section.
• "Exporting a Surface to a CUBIT Facet File," page 2-23
• "Exporting a Surface to a FastEdit File," page 2-24
• "Exporting a Surface to an IRAP File," page 2-24
• "Exporting a Surface to a GMI WellCheck MohrFracs File," page 2-25
Surface object 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 On the File menu, point to Export, point to Surface, and then click FastEdit to open
a CUBIT Facet file the dialog box.
2 In the Surface box, enter the Surface objects to export.

existing one.
1. For information about the CUBIT program, visit Sandia Corporation at http://cubit.sandia.gov/.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.5 Exporting Surface Data 2-23
Paradigm™
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 On the File menu, point to Export, point to Surface, and then click FastEdit to open
a FastEdit file the 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 Attributes dialog box.
existing one.
2.5.3 Exporting a Surface to an IRAP File

Use this procedure to export the geometry of a Surface to an IRAP2 file.
To export a Surface to 1 On the File menu, point to Export, point to Surface, and then click IRAP to open
an IRAP file the dialog box.
1. For details about the FastEdit program, visit CGG Inc. at www.cgg.com.
2. For details about the Irap RMS program, visit Roxar Inc. at www.roxar.com.

Part
II
and Export
Data Import
2 In the Surface box, enter the Surfaces to export.
existing one.
2.5.4 Exporting a Surface to a GMI WellCheck

MohrFracs File
Use this procedure to export a Surface object to a GMI WellCheck MohrFracs1 file.
To export a Surface to 1 On the File menu, point to Export, point to Surface, and then click GMI WellCheck
a GMI WellCheck MohrFracs to open the dialog box.
MohrFracs file
2 In the Surface box, enter the Surface objects to export.

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.
1. For details about the GMI WellCheck program, visit Geomechanics at www.geomi.com.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.5 Exporting Surface Data 2-25
Paradigm™
2.6 Exporting 2D-Grid Data

GOCAD includes converters for exporting 2D-Grid data to various programs and data
types. Supported export sources and how to export the specific files are described in this
section.
• "Exporting a 2D-Grid to a CPS3 File," page 2-26
• "Exporting a 2D-Grid to a FastEdit File," page 2-27
• "Exporting 2D-Grid Data to an IRAP File," page 2-27
• "Exporting 2D-Grid Data to a Z-MAP File," page 2-28
2D-Grid object 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 On the File menu, point to Export, point to 2D-Grid, and then click CPS3 to open
object to a CPS3 file the 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 details about CPS3, visit Schlumberger at www.slb.com.

Part
II
and Export
Data Import
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 On the File menu, point to Export, point to 2D-Grid, and then click FastEdit to
object to a FastEdit open the 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 On the File menu, point to Export, point to 2D-Grid, and then click IRAP to open
an IRAP file the dialog box.

3 In the Property box, enter the property to export with the 2D-Grid geometric data.
existing one.
1. For details about the FastEdit program, visit CGG Inc. at www.cgg.com.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.6 Exporting 2D-Grid Data 2-27
Paradigm™
5 To choose the IRAP format, click one of these options:

• IRAP Classic format
• IRAP Mapping format
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 On the File menu, point to Export, point to 2D-Grid, and then click Z-MAP to open
a Z–Map file the 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 details about the Z-Map program, visit Landmark Graphics at www.halliburton.com.

Part
II
and Export
Data Import
2.7 Exporting Voxet Data
GOCAD includes converters for exporting Voxet data to various programs and data types.
• "Exporting a Voxet to a DDS File," page 2-29
• "Exporting a Voxet to a SEG-Y File," page 2-30
• "Exporting a Voxet to an SEP File," page 2-31
• "Exporting a Voxet to a VoxelGeo File," page 2-32
Voxet object data to the programs in this table:

AVF "Exporting Velocity Data to an AVF File," page 2-16
Velf "Exporting Velocity Data to a Velf File," page 2-17
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 On the File menu, point to Export, point to Voxet, and then click DDS to open the
DDS file dialog box.
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 more information about DDS, visit this Web site www.freeusp.org/DDS/.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.7 Exporting Voxet Data 2-29
Paradigm™
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 must 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 On the File menu, point to Voxet, and then click SEGY to open the dialog box.
SEGY file
2 In the Voxet box, enter the Voxet objects to export.

3 In the Property box, enter the Voxet property to export.
existing one.
5 To format the numbers in the IEEE format, clear the lbm format check box.
6 To enter advanced SEGY export parameters, click Advanced to display the advanced
options.
7 In the Min inline box, type the inline number that corresponds to the first inline
section of the voxet.
8 In the Delta inline box, type the number of inlines that are between two voxet
sections, plus one.
9 In the Min crossline box, type the crossline number that corresponds to the first
crossline section of the voxet.
10 In the Delta crossline box, type the number of inlines that are between two voxet
sections, plus one.
1. For details about the SEG-Y program, visit the Society of Exploration Physicists at www.seg.org.

Part
II
and Export
Data Import
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 On the File menu, point to Export, point to Voxet, and then click SEP.
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 must 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.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.7 Exporting Voxet Data 2-31
Paradigm™
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 On the File menu, point to Voxet, and then click VoxelGeo.
VoxelGeo file
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.

Part
II
and Export
Data Import
2.8 Exporting SGrid Data
GOCAD includes converters for exporting SGrid object data to various programs and data
formats. You can access these commands from the File menu (Export, SGrid submenu).
For information about the types of files that you can export and how to export SGrids as
these types, see:
• "About the Grid Origin," page 2-34
• "Exporting an SGrid to a CMG File," page 2-35
• "Exporting an SGrid to an ECLIPSE ASCII File," page 2-39
• "Exporting an SGrid to an ECLIPSE Binary File," page 2-46
• "Exporting an SGrid to a RESCUE File," page 2-48
• "Exporting an SGrid to a VIP File," page 2-50
• "Exporting an SGrid to a Temis3D (libnf) File," page 2-55
• "Exporting LGR Data from an SGrid to a Flow Simulator," page 2-55
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-16
Velf "Exporting Velocity Data to a Velf File," page 2-17
Note You can also access shortcut commands for many common export converters from the
Object Tree by right-clicking the name of the SGrid that you want to export.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.8 Exporting SGrid Data 2-33
Paradigm™
2.8.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)

I Target origin: point 2 (max, min)
1 (min, min) 4 (min, max)
In the figure, imagine that the origin of the SGrid is 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). By changing the settings, you redefine the areal
orientation of the ECLIPSE grid relative to the SGrid in GOCAD.

Part
II
and Export
Data Import
2.8.2 Exporting an SGrid to a CMG File
By using the SGrid CMG converter, you can export a stratigraphic grid to a CMG ASCII
data file. With this converter, 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.
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.
Note For exported files that contain well path data, the converter uses the ECLIPSE format, which
CMG can read.
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-36
• "To export well data from an SGrid to a CMG file," page 2-38
• "To set the advanced options for exporting to a CMG file," page 2-38
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-55.
Paradigm™
To export grid data 1 On the File menu, point to Export, point to SGrid, and then click CMG to open the
from an SGrid to a dialog 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).

Part
II
and Export
Data Import
5 If you want to change the units to express the grid geometry, click Feet. Otherwise,
the grid geometry will be 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 GOCAD 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 GOCAD properties, see Table 2–3 on page 2-37.
• 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 GOCAD property CMG keyword 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.
Paradigm™
To export well data 1 On the File menu, point to Export, point to SGrid, click CMG to open the dialog
from an SGrid to a box, and then click the Well Data tab.
CMG file
2 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).
To set the advanced 1 On the File menu, point to Export, point to SGrid, click CMG, and then click the
options for exporting Advanced tab.
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.

Part
II
and Export
Data Import
2 If you want to change the orientation of the grid relative to the SGrid, 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-34.
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.8.3 Exporting an SGrid to an ECLIPSE ASCII File

You can use the ECLIPSE ASCII grid converter to export a stratigraphic grid as an ECLIPSE
ASCII data file. The converter can create a single file containing both geometric and
property information, or it can create two or more separate geometry and property files. It
can also create files containing well connection and completion data for any Well objects
intersecting the SGrid. The converter can export multiple properties and multiple wells.
For details about the ECLIPSE program, visit the Schlumberger Corporation Web site at
www.slb.com.
For information about how to specify data in the ECLIPSE converter, see:
• "ECLIPSE keywords," page 2-39
• "To export grid data from an SGrid to an ECLIPSE ASCII file," page 2-40
• "To export well data from an SGrid to an ECLIPSE ASCII file," page 2-41
• "To export fault data from an SGrid to an ECLIPSE ASCII file," page 2-42
• "To export region data from an SGrid to an ECLIPSE ASCII file," page 2-43
• "To set the advanced options for exporting an SGrid to an ECLIPSE ASCII file,"
page 2-44
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-55.
ECLIPSE keywords Because ECLIPSE requires special keywords for properties, you need to specify the
mapping between the ECLIPSE keyword and the GOCAD properties that you want to
export. For information about how to specify the keywords, see step 7 on page 2-41.
Paradigm™
To export grid data 1 On the File menu, point to Export, point to SGrid, point to ECLIPSE, and then click
from an SGrid to an ASCII.
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.

Part
II
and Export
Data Import
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 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
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 On the File menu, point to Export, point to SGrid, point to ECLIPSE, click ASCII,
from an SGrid to an and then click the Well Data tab.
ECLIPSE ASCII file
Paradigm™
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 must have a log that indicates the perforation of the reservoir (and the log must be
equal to zero when not perforated).
To export fault data 1 On the File menu, point to Export, point to SGrid, point to ECLIPSE, click ASCII,
from an SGrid to an and then 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 file, clear the Include it with Grid Data
Output check box.
4 In the Fault 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.

Part
II
and Export
Data Import
To export region data 1 On the File menu, point to Export, point to SGrid, point to ECLIPSE, click ASCII,
from an SGrid to an and then 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 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 must know the name of the corresponding
ECLIPSE keyword to do this.
Paradigm™
To set the advanced 1 On the File menu, point to Export, point to SGrid, point to ECLIPSE, click ASCII,
options for exporting and then 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-34.

Part
II
and Export
Data Import
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
GOCAD and SKUA rather than translating them to ECLIPSE-compatible null
values.
Paradigm™
2.8.4 Exporting an SGrid to an ECLIPSE Binary File

You can export an SGrid object to an ECLIPSE 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 details about the ECLIPSE program, visit the Schlumberger Corporation Web site at
www.slb.com.
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-55.
To export an SGrid to 1 On the File menu, point to Export, point to SGrid, point to ECLIPSE, and then click
an ECLIPSE binary file Binary to display the dialog box.
2 In the Stratigraphic grid box, enter the SGrid object to export.

Part
II
and Export
Data Import
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-34.
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 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 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
GOCAD property 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
Paradigm™
2.8.5 Exporting an SGrid to a RESCUE File

Use this procedure to 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.
Because older RESCUE versions (up to 26) do not allow you to export to a single grid, one
RESCUE grid is exported for each grid layer.
Export tips During the construction of the SGrid, all horizon and fault surfaces should be present in
the project. If the SGrid was constructed by using the SKUA Flow Simulation Grid
Workflow or the GOCAD 3D Reservoir Grid Builder Workflow, most of the information
needed by the converter is automatically provided by the workflow. For information about
creating SGrids with the 3D Reservoir Grid Builder Workflow, see Part VIII: 3D Grid
Building , Chapter 3, "Building a 3D Reservoir Grid." For information about creating
SGrids with the SKUA Flow Simulation Grids Workflow, see the SKUA 2009.1 User Guide.
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 Attribute Manager dialog box and opening the Advanced panel.
If no FaceSets are listed in the Attribute Manager, 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 Rename/merge faults command. For instructions, see Part VIII:
3D Grid Building, "Editing Faults" on page 3-117.
To export an SGrid to 1 On the File menu, point to Export, point to SGrid, and then click RESCUE.
a RESCUE file
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.
1. For details about the RESCUE program, visit the Petrotechnical Open Standards Consortium at
www.posc.org/rescue.

Part
II
and Export
Data Import
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 To generate one unique grid for all of the layers, select the Global grid check box
(available only on version 28 and beyond).
7 To specify advanced RESCUE export options, click Advanced to display the advanced
options.
8 If you want to indicate that the grid contains information about the faults and
horizons, click Horizons and faults extracted from grid.
For example, if you imported the grid from RESCUE, it should contain information
about the surfaces from which it was built.
9 If you want to specify the horizons and faults from Surface objects in the project, click
Horizons and faults saved from surfaces, and then do the following:
a Select the check boxes for the types of surfaces (top, base, or faults) that you
want to save with the grid, and then enter the names of the surfaces that you
want to save.
b Indicate the order in which you want to save the surfaces by clicking Top to Base
or Base to Top.
Paradigm™
2.8.6 Exporting an SGrid to a VIP File

Use this procedure to export a SGrid object to an VIP 1 file.
For information about how to specify data in the VIP converter, see:
• "To export grid data to a VIP file," page 2-50
• "To export wells data to a VIP file," page 2-52
• "To export fault data to a VIP file," page 2-52
• "To export region data to a VIP file," page 2-53
• "To set the advanced options for exporting data to a VIP file," page 2-54
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-55.
To export grid data to 1 On the File menu, point to Export, point to SGrid, and then click VIP.
a VIP file
2 In the Reservoir grid box, enter the SGrid to export.
1. For details about the VIP program, visit Landmark Graphics at www.halliburton.com.

Part
II
and Export
Data Import
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 ReservoirName indicates the name of the
SGrid and PropertyName 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 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.
Paradigm™
To export wells data 1 On the File menu, point to Export, point to SGrid, click VIP to open the dialog box,
to a VIP file and then click the Well 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 On the File menu, point to Export, point to SGrid, click VIP, and then click the Fault
to a VIP file Data tab.
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.

Part
II
and Export
Data Import
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 + d 2
- , where ki = permeability in the cell.
Transmissibility = area/length × -----------------------------
⎛ -----1-⎞ + ⎛ d
d
-----2-⎞
⎝ k 1⎠ ⎝ k 2 ⎠
5 If you do not want to export the transmissibility, clear the Compute transmissibility
check box.
To export region data 1 On the File menu, point to Export, point to SGrid, click VIP to open the dialog box,
to a VIP file and then click the Region Data tab.
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.
Paradigm™
To set the advanced 1 On the File menu, point to Export, point to SGrid, click VIP, 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-34.
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.

Part
II
and Export
Data Import
2.8.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 On the File menu, point to Export, point to SGrid, and then click Temis3D to open
a Temis3D file the 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.8.8 Exporting LGR Data from an SGrid to a Flow

Simulator
With the LGR and Upscaler 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 details about the Temis3D program, visit the Beicip Inc. Web site at www.beicip-inc.com.
Paradigm™
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–3). 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-57
• "To export local grid refinements (LGRs) to an ECL, VIP, or CMG ASCII file," page 2-57
Figure 2–3 LGR export options

Part
II
and Export
Data Import
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 Upscaler Part I: Getting Started, "Choosing Modules for a Project" on page 1-8
module
Import or create LGRs within Part II: Data Import and Export, "Importing an ECLIPSE ASCII Grid File"
an SGrid object* on page 1-45 or "Importing a VIP or ECLIPSE LGR File" on page 1-54
– or –
*ECLIPSE requires LGR names Part X: Reservoir Production and Simulation, "Creating Local Grid
to be eight characters or less. Refinements (LGRs)" on page 2-84
Define an LGR export Part X: Reservoir Production and Simulation, "Defining LGR Export
scenario 1 Scenarios for Flow Simulation" on page 2-106
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 On the File menu, point to Export, point to SGrid, and then, depending on the
an ECL, VIP, or CMG simulator that you selected in the export scenario, click either CMG or VIP or point to
ASCII file ECLIPSE and click ASCII.
Note You can also open the export converter from:
• The shortcut menu for the SGrid object in the Object Tree (right-click the name of the grid
to access the menu).
• The LGR and Upscaler Workflow in the Defining LGR Export Scenarios task (Define
Scenarios and Export step).
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.
Paradigm™
5 In the LGR export scenario box, select the name of the scenario (that you created in
the LGR and Upscaler 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
Upscaler Workflow, see Part X: Reservoir Production and Simulation, "Defining
LGR Export Scenarios for Flow Simulation" on page 2-106.
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 Upscaler 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
Upscaler Workflow, see Part X: Reservoir Production and Simulation, "Defining LGR
Export Scenarios for Flow Simulation" on page 2-106.

Part
II
and Export
Data Import
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-39
• "Exporting an SGrid to a VIP File" on page 2-50
• "Exporting an SGrid to a CMG File" on page 2-35
Carrying out the command converts the LGR data to ASCII format and saves the file in the
folder that you specified.
Paradigm™
2.9 Exporting Well Data

GOCAD includes converters for exporting Well data to various programs and data types.
• "Exporting a Well to an IRAP File," page 2-60
• "Exporting a Well to an LAS File," page 2-61
• "Exporting Well Markers to an ASCII File," page 2-62
• "Exporting Well Logs to an ASCII File," page 2-63
• "Exporting Well Targets to an Octopus File," page 2-64
Well object data to Excel. For information, see "Exporting Object Properties to Excel" on
page 2-7.
2.9.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 On the File menu, point to Export, point to Wells, and then click IRAP to open the
IRAP file dialog box.
2 In the Curve box, enter the Wells 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 a new file, or overwrites an existing
one.

Part
II
and Export
Data Import
2.9.2 Exporting a Well to an LAS File
Use this procedure to export Well objects to an LAS1 file.
To export a Well to an 1 On the File menu, point to Export, point to Well, and then click LAS to open the
LAS file dialog box.
2 In the Wells box, enter the Well objects to export.

3 In the Files prefix box, enter the path and file name of the file to which you are
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 details about the LAS program, visit the Canadian Well Logging Society at cwls.org/.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.9 Exporting Well Data 2-61
Paradigm™
2.9.3 Exporting Well Markers to an ASCII File

Use this procedure to export a well markers to an ASCII file.
To export well 1 On the File menu, point to Export, point to Well, and then click Well Markers to
markers to an ASCII ASCII to open the 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.

Part
II
and Export
Data Import
2.9.4 Exporting Well Logs to an ASCII File
You can use the converter to export well log curve data for one or more wells to an ASCII
file.
To export well logs to 1 On the File menu, point to Export, point to Well, and then click Well Path and
an ASCII file Logs to ASCII to open the 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.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.9 Exporting Well Data 2-63
Paradigm™
2.9.5 Exporting Well Targets to an Octopus File

Use the Octopus converter to export a Well object to an Octopus1 ASCII file.
Octopus is a software product that provides well data in a format that supports data
exchange between businesses. The purpose is for the analysis and optimization of field
development and drilling operations.
To export a Well to an 1 On the File menu, point to Export, point to Well, and then click Octopus.
ASCII file
2 In the Octopus project file box, enter the path and file name of the file to which you
are exporting the object, and then click OK. The converter either creates a new file,
or overwrites an existing one.
3 In the Well Planning Categories box, select Target (the other options are
unavailable).
4 Enter the target data by completing these steps:
a In the Target name box, type the name of the target.
b In the X, Y, and Z boxes, enter numeric values to define the coordinates of the
target.
Note The target name values represent well marker locations.
5 Enter the vector data by completing these steps:

a In the Vector name box, type the name of the target.
b In the X, Y, and Z boxes, enter numeric values to define the coordinates of the
vector.
Note The vector name values represent well marker locations.
6 Click Send to carry out the command and close the dialog box, or click Update to
carry out the command and leave the dialog box open.
1. For more information about the Octopus program, visit Techdrill International at
www.techdrill.com.

Part
II
and Export
Data Import
2.10 Exporting a View as an Image
GOCAD includes converters for exporting the display in the view as various image
formats.
For information about how to export the contents of a view, see:
• "Exporting a View to a CGM File," page 2-65
• "Exporting a View to an Image File," page 2-66
• "Exporting a 3D Viewer Image to a VRML File," page 2-68
2.10.1 Exporting a View to a CGM File

You can export the display in a 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 On the File menu, point to Export, point to Camera, and then click CGM to open
3D Viewer image to a the dialog box.
CGM file
2 In the Camera box, enter the name of the viewer that contains the image that you
want to export. By default, the converter selects the main viewer. If other viewer
windows are open, select the one to export.
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 must specify a height number. This
number corresponds to the plot’s height in centimeters.
• Use scale. If you select this option, you must define a scale factor. This number,
which is in real world units, corresponds to one plot centimeter.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.10 Exporting a View as an Image 2-65
Paradigm™
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.
2.10.2 Exporting a View to an Image File

You can export the display in a view to an image file. The format can be one of these file
types:
• BMP • JPEG
• PBM • PGM
• PNG • PPM
• RGB • TIFF
• XBM • XPM
The converter captures the image directly on the screen, and any dialog boxes located
within the view are also captured. Therefore, you should clear the view from any
overlapping windows to get a clean image.

Part
II
and Export
Data Import
To export a view to With the view open and set up how you want it to appear in the screen capture, do the
an image file following:
1 On the File menu, point to Export, point to Camera, and then click Picture to open
the dialog box.
– or –
From a 2D view, on the File toolbar, click Save Snapshot As .
2 In the Camera box, enter the name of the view that contains the image that you
want to save.
The converter preselects the main view. If other views are open, select the one to
save.
3 In the Snapshot file box, enter the path and file name where you want to save the
image.
The converter either creates a new file, or overwrites an existing one.
4 In the Image format box, select the file format that you want to use to save the
image.
5 To select the size (width and height) of the saved image, select the Resize snapshot
check box, and then type numeric values in the Width and Height boxes to specify
the size in pixels.
Note Due to hardware limitations, the maximum size you can set is 2000 by 2000 pixels.
6 Ensure that no other windows overlap the view that you want to save.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.10 Exporting a View as an Image 2-67
Paradigm™
2.10.3 Exporting a 3D Viewer Image to a VRML File

Use this converter to 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 On the File menu, point to Export, point to Camera, and then click VRML to open
3D Viewer image to a the dialog box.
VRML file
2 In the Camera box, enter the name of the viewer that contains the image that you
want to export. The converter preselects the main viewer. If other viewer windows are
open, select the one to export.
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.
1. For more information about the VRML format, visit the Web 3D Consortium at www.vrml.org.

Part
II
and Export
Data Import
2.11 Exporting an SGrid and Data to an Isatis
File
You can export an SGrid with other GOCAD objects (usually, point sets or wells), creating
a regular 3D Isatis1 grid from the SGrid. The converter exports the additional object with
the coordinates modified to maintain the correlation between the object and the SGrid
cells that it crosses.
GOCAD connection GOCAD must connect to the Isatis database using the GTXserver, a program provided by
with Isatis Geovariances. This program is installed with Isatis. So if you have Isatis installed on the
same machine as GOCAD 2009, 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. This program is available for several
platforms:
• Microsoft - Windows
• Red Hat - Linux
• Sun - Solaris
• Silicon Graphics - Irix
To access to the database, GOCAD first opens a connection with the database and then
uses the GTXserver for loading or saving data. The connection is closed once the load or
save are 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.
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.
1. For details about the Isatis program, visit Geovariances, Inc. at www.geovariances.com.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.11 Exporting an SGrid and Data to an Isatis File 2-69
Paradigm™
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 the GOCAD objects. This table shows the
relationship between the object types and the corresponding Isatis file types.
GOCAD object type 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. The different types of
database properties are:
• Character variables (string).
• 1-bit variable, defining subsets of object (a subset is equivalent to GOCAD region)
• Scalar variable.
• Macro variable for multi-realization property representation.
This table shows the relationship between the GOCAD properties and the corresponding
Isatis variables.
GOCAD property Isatis variable

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

Part
II
and Export
Data Import
To export an SGrid 1 On the File menu, point to Export, point to SGrid + Data, and then click Isatis to
and data to an Isatis open the dialog box.
file
2 To set the advanced connect parameters, click Advanced to open the Advanced
Connect Parameters dialog.
Note Steps 2 and 3 are necessary only if you need to maintain these parameters. Once set, you
will not have to complete these steps.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 2.11 Exporting an SGrid and Data to an Isatis File 2-71
Paradigm™
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.
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.
• If you are a Linux user, if necessary, you may need to define the GTX_HOME
environment variable and restart GOCAD 2009.
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.
4 In the DX, DY, and DZ boxes, type numeric values to set the direction block size
parameters.
5 To export the grid properties, select the Export grid properties check box.
6 To export the original data coordinates, select the Export original data coordinates
check box.
7 In the Study box, select the corresponding Isatis study.
8 In the Directory box, select the directory you are exporting to.
9 In the Gocad Grid object box, enter the SGrid to export.
10 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
• "CPS3 Formats," page A-5 • "SEP Format," page A-28
• "Eclipse Formats," page A-11 • "Velf Format," page A-29
• "FastEdit Formats," page A-13 • "VIP Formats," page A-33
• "Irap RMS Formats," page A-15 • "Z-MAP Formats," page A-31
• "LAS Format," page A-20 • "XYZ Format," page A-30
Overview In Paradigm™ GOCAD ® 2009, when possible, the import converters provide a high
degree of flexibility and can identify and import data files without requiring rigid file
formats. 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
Paradigm™
A.1 Import File Formats

The following is a summary of the import file formats GOCAD supports:
Table A–1 Import file formats
Imported from this With this common Imported from this With this common
program or data type extension program or data type extension
Adobe® contours .esp Locations from column-based file
ArcView® .dbf, .shp, and .shx Medica Fault Polygons .fau
ASCII file with header Medica Topographic Surface .g
AutoCAD® .dxf Medica Topographic Surface .g
Advanced
Charisma fault interpretations MPath .act, .fid, .raw, .par
Charisma fault polygons Norsar depth cube
Charisma horizon points .gridexp Norsar horizons
Column-based file Octopus
CPS3 ASCII 2D grid .grd Petrel pillars .dat
CPS3 ASCII data .dat PetroMod® .pmb
CPS3 ASCII fault traces .flt Promax®
CPS3 ASCII polygon .ply RC2 .gz, .asc, .out
CPS3 binary .svd RC2 2D grid .gz
CPS3 binary .svd, .svs, .svf, .svp RESCUE .bin
CPS3 binary .svf, .svp RESCUE (grids, horizons, faults) .bin
CPS3 binary .svd, .svs, .svf, .svp SEG-Y 2D as SGrid .sgy, .segy
DEM binary SEG-Y 2D as surface .sgy, .segy
Digital Elevation Model (DEM) .ers SEG-Y 3D as voxet .sgy, .segy
ER Mapper
Dip ASCII file with header SeisWorks .clr
Dip column-based file SeisWorks fault polygons
DXF .dxf Seisworks fault sticks .dat
ECLIPSE .DATA file .data Seisworks Inline Xline X Y Z .asc
ECLIPSE ASCII faults Seisworks® cultural data .asc
ECLIPSE ASCII properties .grdecl SEP .h
ECLIPSE binary file StrataModel 2D grid .smg
ECLIPSE binary grid .grid, .egrid, .init, StrataModel 2D grid property .smg
.unrst
ECLIPSE® ASCII grid .grdecl TDQ™ .avf
Excel .xls Temis3D
FastEdit 2D grid .dat Temis3D Colormap
FastEdit fault polygons Temis3D Grid .td4
FastEdit horizon contours .dat Velf .velf
FastEdit scattered data .dat VIP ASCII properties .cor
Geoprobe 2D grid .gvw VIP LGR .lgr
Geosec® .ihf VIP™ ASCII grid .cor
GSLib 2D map VoxelGeo .vol
I J K property VoxelGeo .vol
Images Well Status Symbols
(Continued 1 of 2)
A-2 Import File Formats GOCAD® 2009.1 User Guide

Part
II
Started
Getting
Imported from this With this common Imported from this With this common
program or data type extension program or data type extension
Irap RMS .log, .decode WITSML .gz, .xml
Irap RMS ASCII 2D-grid property X Y Z file
Irap RMS fault polygons or lines Z-MAP ASCII 2D grid
Irap RMS triangle surface .dat Z-MAP ASCII 2D grid property
Jason ASCII traces Z-MAP fault or contour
(Jason Geoscience Workbench®)
LAS .las Z-MAP™ contour .zmap
Locace® .ext
(Continued 2 of 2)
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.1 Import File Formats A-3
Paradigm™
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 must 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

Part
II
Started
Getting
A.3 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 must contain X, Y, and Z 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
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.3 CPS3 Formats A-5
Paradigm™
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 must contain X, Y, coordinates in columns one and two, and
TVDSS values in column three. If MD values are included, they must be in column
four. Each column must be separated by one or more spaces.
• The name of the well must immediately follow the arrow symbol (->); if the file
contains data for more than one well, a new arrow symbol and a new well name
must 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 Property Script on an Object" on page 11-27.
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
.
.
.

Part
II
Started
Getting
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 X, Y 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 must contain two columns of X and Y coordinates, with each
column separated by one or more spaces.
If the imported Curve object has several separate segments (parts), each part must
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
.
.
.
Paradigm™
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 must 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 must
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

Part
II
Started
Getting
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 must
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 must 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 Y axis
Note All keywords (except for FSASCI) in this
format must be non-CPS3 keywords.
Paradigm™
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.

Part
II
Started
Getting
A.4 Eclipse Formats
There are three Eclipse converters: ASCII, properties, and binary.
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
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
(Continued 1 of 2)
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.4 Eclipse Formats A-11
Paradigm™
Section Keyword Definition

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 must have a .grid or .egrid extension. All other
relevant data files (for example, .init for initial reservoir data and .unrst for unified restart
data) must be in binary format. They must have the same file name as the .grid file but a
different extension, and they must be located in the same directory.

Part
II
Started
Getting
A.5 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 must 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
.
.
1000.000000 0.000000 0.0000000
1000.000000 1000.00000 500.0000000
.
.
.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.5 FastEdit Formats A-13
Paradigm™
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 (V) axis.
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
.
.
.

Part
II
Started
Getting
A.6 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
.
.
.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.6 Irap RMS Formats A-15
Paradigm™
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
.
.
.

Part
II
Started
Getting
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
Legend:
9999900.00 # of rows = 151
9999900.00 x = 100.565407
9999900.00 y = 200.143738
-8357.719727 min x = 1364.339966
-8347.599609 max x = 16449.150391
-8326.809570 min y = 19502.400391
. max y = 49073.960938
. # of columns = 151
. angle of rotation = 270.000000
Paradigm™
Irap RMS 2D grid The converter expects to read an ASCII file that contains header data followed by Z
mapping format 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.
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
.
.
.

Part
II
Started
Getting
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 must 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, must 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
.
.
.
Paradigm™
A.7 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 must 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 must be included in the Header portion of the file with this
keyword.
Data Required keyword: ~A
The data portion of the file must 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.

Part
II
Started
Getting
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
.
.
.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.7 LAS Format A-21
Paradigm™
A.8 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 must 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

Part
II
Started
Getting
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
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.8 MPath Formats A-23
Paradigm™
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
.
.
.

Part
II
Started
Getting
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 must 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 X, Z,
and Y order.
• Values may be undefined and are specified as "NaN" values.
Here is an example of a .raw file. The example shows extent: 30 40 585. This means 30
grid cells in the X dimension, 40 in the Y and 585 in the Z are defined in the data block.
# .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
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.8 MPath Formats A-25
Paradigm™
A.9 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
.
.
.

Part
II
Started
Getting
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 must be evenly
sampled and all traces must have the same length.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.9 SEG-Y Formats A-27
Paradigm™
A.10 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

Part
II
Started
Getting
A.11 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.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.11 Velf Format A-29
Paradigm™
A.12 XYZ Format

The XYZ converter expects to read a three-column ASCII file that contains only data
values, and the data values must 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

.
.
.

Part
II
Started
Getting
A.13 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 must 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
.
.
.
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.13 Z-MAP Formats A-31
Paradigm™
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 must 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 X Y locations of the U extremity and V extremity
The data must be sequenced as follows:
@
GRID
Unused - No-data-value
nu nv umin umax vmin vmax
@
Data The data portion must 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 (V) axis.
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

Part
II
Started
Getting
A.14 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 must supply the values in the Import an SGrid from VIP ASCII file dialog
box. See"Importing a VIP ASCII Grid File" on page 1-53.
Data A series of 8-point cells.
Each block of data should contain the cell’s location on the SGrid, followed by eight
sets of X,Y, and Z coordinates (24 numbers in total) identifying the cell’s eight corner
points.
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 must be at the
end of the file. If property data is present in the same file, you can import it at the
same time 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 One grid block with
31800.62 40780.29 9591.69 31223.06 40780.29 9589.00 cell location and
31223.06 41427.86 9659.38 31800.62 41427.86 9659.71
31800.62 40780.29 9664.03 31223.06 40780.29 9660.13 eight sets of X, Y,
C GRID BLOCK I = 2, J = 1, K = 1 coordinates
31800.62 41427.86 9589.23 32378.19 41427.86 9591.28
.
.
.
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 must 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
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 A.14 VIP Formats A-33
Paradigm™
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 expects to read an ASCII file that contains
the following keywords:
Note The data in the file must 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 The indices defining the portion of
,k1,k2 the coarse grid to be refined
nx1,nx2 Number of X direction fine grid
blocks for each of the corresponding
coarse gridblocks
ny1,ny2 Number of Y direction fine grid
coarse gridblocks
nz1, nz2 Number of Z direction fine grid
coarse grid blocks
ENDREF Marks the end of data defining a
refined grid

Index
Symbols importing CPS3 ASCII creating from horizon

2D-Grid files 1-38 surface data
.act files
importing FastEdit 2D- files 1-38
importing 1-11
Grid files 1-39 creating using FastEdit
.avf files scattered data
.gvw files
exporting velocity data converter 1-34
importing 1-39
to 2-16 creating using IRAP
.las files
importing 1-69 RMS ASCII 2D-Grid
exporting wells converter 1-39
.bin files
to 2-61
importing 1-31 creating using
importing 1-74 StrataModel
.cgm files
.ply files converter 1-41
exporting 3D Viewer
importing 1-27 exporting 2-26
images to 2-65
.t4d files exporting properties to
.cmg files
importing 1-9 an Excel file 2-7
exporting an SGrid
object to 2-35 .vrml files exporting to a FastEdit
exporting 3D Viewer file 2-27
.dat files
images to 2-68 exporting to a Medica
importing 1-16, 1-33
.xls files file 2-16
importing CPS3 ASCII
exporting object exporting to a Z-MAP
data files 1-36,
properties to 2-7 file 2-28
1-72
exporting to an IRAP
.dxf files
file 2-27
exporting an object Numerics exporting to CPS3
to 2-7
2D SEG-Y files files 2-26
importing 1-15
importing 1-63 3D SEG-Y files
.flt files
2D view importing as
importing 1-25 voxets 1-58
exporting as an
.grd files image 2-65 3D Viewer
exporting s grids to 2D voxet exporting as an
Eclipse ASCII image 2-65
importing 1-43
files 2-39
2D-Grid objects exporting images to
importing 1-29 CGM files 2-65
Index-1
Paradigm™
exporting images to C importing CPS3 ASCII

picture files 2-66 polygon files 1-27
CGM files
exporting images to importing CPS3 binary
exporting 3D Viewer
VRML files 2-68 files 1-18, 1-29,
images to 2-65
1-34
channels
cross section
A exporting properties to
exporting as an
Adobe contours files an Excel file 2-7
image 2-65
importing 1-36 Charisma files, importing
CUBIT facet files
ArcView files fault interpretations
exporting a surface
files 1-24
importing 1-14 to 2-23
fault polygon
ASCII file cultural data
files 1-27
exporting an object to importing .dxf
horizon points 1-33
a custom ASCII files 1-15
file 2-5 CMG files
importing ArcView
exporting an SGrid exporting SGrid objects files 1-14
object to 2-39 to 2-35
curves
exporting well curves column-based file import
creating Curve objects
to 2-63 wizard
from a column-based
exporting well markers import file format file 1-36
to 2-62 requirements A-4
creating Curve objects
exporting well targets column-based files from a SeisWorks
to an Octopus ASCII importing 1-34, 1-36, fault sticks file 1-26
file 2-64 1-71, 1-80 creating Curve objects
AVF file importing location from Charisma fault
exporting velocity data data 1-82 polygon ASCII
to 2-16 importing well marker files 1-27
data from 1-82 creating Curve objects
importing from CPS3 ASCII
B wizard 1-18 fault trace file 1-25
basic concept for contour data creating Curve objects
importing 1-6 importing to create a from fault
basin modeling Cure object 1-36 interpretations data
files 1-16
importing MPath .act CPS3
files 1-11 creating from a Velf
import file format
ASCII file 1-69
importing MPath .fid requirements A-5
files 1-12 creating from column-
CPS3 binary
based-file
importing MPath .par converter 1-18
data 1-71, 1-80
colormap files 1-12 CPS3 fault traces
creating from horizon
importing MPath .raw importing 1-25 surface data
files 1-12
CPS3 files files 1-38
importing
exporting 2D-Grid creating from location
PetroMod 1-13
objects to 2-26 data from column-
importing Temis 3D based files 1-82
importing 1-33
.t4d files 1-9
importing CPS3 ASCII creating using FastEdit
importing Temis 3D scattered data
2D-Grid files 1-29,
colormaps 1-10 converter 1-34
1-38
binary files exporting 2-19
importing CPS3 ASCII
exporting an SGrid data files 1-36, exporting properties to
object to 2-46 1-72 an Excel file 2-7
Index-2 GOCAD® 2009.1 User Guide

Part
II
and Export
Data Import
exporting to a FastEdit Eclipse keyword 2-39 SGrid objects to a CMG
fault polygon Excel files file 2-35
file 2-19 SGrid objects to a
exporting object
exporting to a Medica properties to 2-7 RESCUE file 2-48
file 2-16 SGrid objects to an
importing 1-72
exporting to a Z-MAP Eclipse ASCII
exporting
contours file 2-22 file 2-39
2D-Grid data 2-26
exporting to a Z-MAP SGrid objects to an
faults file 2-21 2D-Grid objects to a Eclipse binary
CPS3 file 2-26 file 2-46
exporting to an IRAP
file 2-20 2D-Grid objects to a SGrid objects to Temis
FastEdit file 2-27 3D files 2-55
exporting well curves
to an ASCII 2D-Grid objects to a SGrid objects to VIP
file 2-63 Medica file 2-16 files 2-50
importing Z-MAP 2D-Grid objects to a Z- surface data 2-23
contour files MAP file 2-28
surfaces to a CUBIT
as 1-37 2D-Grid objects to an facet file 2-23
custom ASCII file IRAP file 2-27
surfaces to a FastEdit
exporting an object 3D Viewer image to file 2-24
to 2-5 CGM files 2-65
surfaces to a GMI
3D Viewer images to WellCheck
picture files 2-66 MohrFracs file 2-25
D 3D Viewer images to surfaces to an IRAP
DDS files VRML files 2-68 file 2-24
exporting voxets basic procedures 2-4 to an Isatis file 2-12
to 2-29 curves 2-19 to DFX files 2-7
DXF files curves to a FastEdit velocity data to a Velf
exporting to 2-7 fault polygon file 2-17
file 2-19
velocity data to an AVF
curves to a Medica file 2-16
E file 2-16
voxets 2-29
Eclipse curves to a SeisWorks
voxets to a DDS
import file format fault sticks file 2-20
file 2-29
requirements A-11 curves to a Z-MAP
voxets to a SEG-Y
Eclipse files contours file 2-22
file 2-30
export well data of s curves to an IRAP
voxets to a VoxelGeo
grids to 2-41 file 2-20
file 2-32
exporting s grids to curves to Z-MAP faults
voxets to an SEP
Eclipse ASCII files 2-21
file 2-31
files 2-39 display as an
well curves to an ASCII
exporting SGrid objects image 2-65
file 2-63
to Eclipse binary object properties to
files 2-46 well markers to an
Excel files 2-7
ASCII file 2-62
format 2-35 objects to a custom
well targets to an
importing ASCII ASCII file 2-5
Octopus ASCII
grids 1-45 points sets to a FastEdit file 2-64
importing binary grid file 2-18
wells 2-60
files 1-46 SGrid objects 2-33
wells to an IRAP
importing faults 1-57 SGrid objects and data file 2-60
importing to an Isatis file 2-69
wells to LAS
properties 1-55
files 2-61
Rock & Fluid Canvas™ 2009 | Epos™ 4.0 Index-3

Paradigm™
F importing Petrel Pillar LAS A-20

files as MPath A-22
FastEdit
surfaces 1-30
import file format VIP A-33
importing SeisWorks
requirements A-13 XYZ A-30
fault polygon
FastEdit files filess 1-28 Z-MAP A-31
exporting 2D-Grid importing SeisWorks
objects to 2-27 fault stick files 1-26 G
exporting curves importing X Y Z
to 2-19 Geoprobe 2D-Grid files
files 1-24
exporting points sets importing 1-39
importing Z-MAP fault
to 2-18 or contour GMI WellCheck
exporting surfaces files 1-26 MohrFracs files
to 2-24 importing.flt exporting surfaces
importing 1-28 files 1-25 to 2-25
importing 2D grid fault polygon files GSLib 2D Map files
files 1-39 exporting curves importing 1-34
importing 2D- to 2-19 importing as
Grids 1-30 importing FastEdit fault surfaces 1-39
importing FastEdit polygons files 1-28
scattered data fault sticks files
files 1-34 H
exporting a curve
importing horizon horizon contours
to 2-20
contour files 1-37 importing Z-MAP
fault surfaces
importing scattered horizon contour
importing CPS3 ASCII files 1-37
data 1-23
2D-Grid files 1-29
fault interpretations horizon interpretations
importing FastEdit 2D-
importing Charisma importing Adobe
Grid files 1-30
fault interpretations contours 1-36
importing Irap RMS
files 1-24 importing Charisma
TriangleSurface
importing Charisma horizon points 1-33
files 1-30
fault polygon importing column-
importing RC2 2D-Grid
files 1-27 based files 1-34,
files 1-30
importing column- 1-36
importing RESCUE
based files 1-18 importing CPS3 .dat
model files 1-31
importing CPS3 .dat files 1-33
importing StrataModel
files 1-16 importing CPS3 ASCII
2D-Grid files 1-32
importing CPS3 ASCII data files 1-36
importing Z-MAP 2D-
polygon files 1-27 importing FastEdit
Grid files 1-32
importing CPS3 binary horizon
faults contours 1-37
files 1-18
importing Eclipse ASCII importing FastEdit
importing data 1-16
fault files 1-57 scattered data 1-34
importing FastEdit fault
file format requirements importing GSLib 2D
polygon files 1-28
for importing Map files 1-34
importing FastEdit
column-based importing SeisWorks
scattered data 1-23
file A-4 Inline Xline XYZ
importing Irap RMS
CPS3 A-5 files 1-35
fault polygons or
lines 1-28 Eclipse A-11 importing X Y Z
FastEdit A-13 files 1-35
importing Petrel Pillar
files as curves 1-26 Irap RMS A-15

Part
II
and Export
Data Import
importing Z-MAP CPS3 import file format Charisma horizon
horizon requirements A-5 points 1-33
contours 1-37 Eclipse import file column-based
horizon surfaces format files 1-18, 1-34,
importing 1-38 requirements A-11 1-36, 1-71, 1-80
importing .gvw FastEdit file import CPS3 .dat files 1-72
files 1-39 requirements A-13 CPS3 ASCII 2D-Grid
importing CPS3 .grd file format table A-2 files 1-29, 1-38
files 1-38 Irap RMS import file CPS3 ASCII data
importing data 1-38 format files 1-16, 1-33
requirements A-15 CPS3 ASCII polygon
importing FastEdit 2D-
Grid files 1-39 LAS import file format files 1-27
requirements A-20 CPS3 binary
importing GSLib 2D
maps as MPath import file files 1-18, 1-29,
surfaces 1-39 format 1-34
requirements A-22 CPS3 files
importing Irap RMS 2D-
Grid files 1-39 SEG-Y import file importing CPS3
format ASCII data
importing Irap RMS
requirements A-26 files 1-36
ASCII 2D-Grid
property files 1-40 SEP import file format cultural data 1-14
requirements A-28
importing Norsar Eclipse ASCII grid
horizons 1-40 VIP import file format file 1-45
requirements A-33
importing RC2 2D-Grid Eclipse ASCII properties
files 1-40 XYZ import file format files 1-55
requirements A-30
importing RESCUE Eclipse binary grid
model files 1-41 Z-MAP import file files 1-46
format
importing StrataModel Eclipse faults 1-57
requirements A-31
2D-Grid files 1-41 Excel files 1-72
import file format
importing Z-MAP ASCII FastEdit 2D-Grid
requirements
2D-Grid files 1-30, 1-39
properties 1-42 SEG-Y A-26
FastEdit fault polygon
SEP A-28
files 1-28
VIP A-33
I FastEdit horizon
XYZ A-30 contour files 1-37
I J K properties
Z-MAP A-31 FastEdit scattered
importing 1-56
importing data 1-23
images
.avf files 1-69 FastEdit scattered data
exporting 3D Viewer files 1-34
.dxf files 1-15
images to CGM
.flt files 1-25 fault interpretations
files 2-65
data 1-16
exporting 3D Viewer 2D SEG-Y files 1-63
Geoprobe 2D-Grid
images to picture 2D voxet 1-43
files 1-39
files 2-66 Adobe contours
GSLib 2D Map
exporting 3D Viewer files 1-36
files 1-34
images to VRML basic concept 1-6
files 2-68 GSLib 2D maps as
Charisma fault surfaces 1-39
importing 1-43 interpretations
horizon surface
import files 1-24
data 1-38
column-based import Charisma fault polygon
horizon surfaces
file format files 1-27
data 1-38
requirements A-4

Paradigm™
I J K property SeisWorks fault sticks Irap files

files 1-56 files 1-26 importing RMS 2D-Grid
image files 1-43 SeisWorks Inline Xline files 1-39
Irap RMS ASCII 2D-Grid XYZ files 1-35 importing RMS ASCII
files 1-39 SEP files 1-65 2D-Grid property
Irap RMS ASCII 2D-Grid StrataModel 2D- 1-41 files 1-40
property files 1-40 StrataModel 2D-Grid importing RMS fault
Irap RMS fault files 1-32, 1-41 polygons or
polygons or lines 1-28
TDQs 1-69
lines 1-28 importing RMS
Temis 3D .t4d
Irap RMS TriangleSurface
files 1-9
TriangleSurface files 1-30
Temis 3D files as
files 1-30 importing RMS well
wells 1-79
Irap RMS well files 1-73
Velf files 1-69
files 1-73 Irap RMS
velocity data 1-68
Jason traces 1-68 import file format
VIP ASCII grid requirements A-15
LAS well data 1-74
files 1-53
MPath .act files 1-11 Isatis files
VIP LGR data 1-54
MPath .fid 1-12 exporting stratigraphic
VIP properties 1-57 grid data to 2-69
MPath .par colormap
VoxelGeo files 1-62 exporting to 2-12
files 1-12
voxet 1-43
MPath .raw files 1-12
well data 1-71
Norsar depth cube J
files 1-66 well marker data from
column-based Jason traces
Norsar horizons
files 1-82 importing 1-68
files 1-40
well symbol
Octopus files 1-80
data 1-86
Petrel Pillar files as
WITSML files 1-79
L
surfaces 1-30 LAS
X Y Z fault data 1-24
Petrel Pillars files as import file format
curves 1-26 X Y Z files as
wells 1-80 requirements A-20
PetroMod 1-13 LAS file
X Y Z horizon
ProMAX files 1-68 exporting wells
data 1-35
RC2 2D-Grid to 2-61
Z-MAP 2D-Grid
files 1-30, 1-40 LAS well data
files 1-32
RC2 files as importing 1-74
Z-MAP ASCII 2D-Grid
wells 1-78
property files 1-42 log data
RESCUE model
Z-MAP contour importing from
files 1-31, 1-41
files 1-37 column-based
RESCUE model files files 1-82
Z-MAP fault or contour
(grids, horizons,
files 1-26 log display
faults) 1-53
IRAP files exporting as an
reservoir grid
exporting 2D-Grid image 2-65
data 1-44
objects to 2-27
SEG-Y 3D files as
voxets 1-58 exporting a curve
to 2-20
M
seismic data 1-58 map
exporting surfaces
SeisWorks fault exporting as an
to 2-24
polygon files 1-28 image 2-65
exporting wells
to 2-60 Medica file

Part
II
and Export
Data Import
exporting 2D-Grid exporting 3D Viewer importing Eclipse
objects to 2-16 images to 2-66 faults 1-57
exporting curves points sets importing Eclipse
to 2-16 creating from column- properties 1-55
MPath based-file importing I J K
import file format data 1-71, 1-80 properties 1-56
requirements A-22 creating from horizon importing RESCUE
importing .fid surface data model (grids,
files 1-12 files 1-38 horizons,
creating from location faults) 1-53
importing .par
colormap files 1-12 data from column- importing VIP
based files 1-82 grids 1-53
importing .raw
files 1-12 creating PointsSet importing VIP LGR
object from files 1-54
MPath .act files
Charisma ASCII importing VIP
importing 1-11 file 1-33 properties 1-57
creating PointsSet
N objects from fault
interpretations data S
Norsar Depth Cube files 1-16 S Grid object
converter 1-66
creating using FastEdit creating from velocity
Norsar depth cubes scattered data data 1-68
importing 1-66 converter 1-34
SEG-Y 3D files
Norsar horizons files exporting properties to
importing as
importing 1-40 an Excel file 2-7
voxets 1-58
Norsar Trend Map 1-66 exporting to a FastEdit
SEG-Y files
file 2-18
exporting voxets
ProMAX files
O to 2-30
importing 1-68
SEG-Y import file format
objects
requirements A-26
exporting to a custom
R seismic data
ASCII file 2-5
RC2 files importing 1-58
exporting to an Isatis
file 2-12 importing as importing 2D SEG-Y
wells 1-78 files 1-63
exporting to DXF
files 2-7 importing RC2 2D-Grid importing Norsar depth
files 1-30, 1-40 cubes 1-66
Octopus files
RESCUE file importing SEG-Y 3D
importing 1-80
files as voxets 1-58
exporting SGrid objects
to 2-48 importing SEP
P RESCUE model files
files 1-65
Petrel Pillars importing VoxelGeo
importing 1-31, 1-41
files 1-62
importing Petrel Pillars importing grids,
files as curves 1-26 SeisWorks files
horizons,
importing Petrel Pillars faults 1-53 exporting curves to
files as SeisWorks fault sticks
reservoir grid data
surfaces 1-30 files 2-20
importing 1-44
PetroMod importing fault
importing Eclipse ASCII polygons 1-28
importing 1-13 grids 1-45
importing fault sticks
picture files importing Eclipse files 1-26
binary grids 1-46

Paradigm™
Inline Xline XYZ exporting to an IRAP importing VIP LGR

files 1-35 file 2-24 files 1-54
SEP file importing GSLib 2D VIP import file format
exporting voxets maps as 1-39 requirements A-33
to 2-31 VIP properties files
SEP files importing 1-57
T
importing 1-65 VoxelGeo files
targets
SEP import file format exporting voxets
exporting well targets
requirements A-28 to 2-32
to an Octopus ASCII
SGrid objects file 2-64 importing 1-62
exporting 2-33 TDQ .avf files voxets
exporting properties to importing 1-69 creating from a Norsar
an Excel file 2-7 interface and Norsar
Temis 3D colormap
exporting to a RESCUE trend map 1-66
importing 1-10
file 2-48 creating using existing
Temis 3D files images 1-43
exporting to an Eclipse
ASCII file 2-39 importing as s creating using Norsar
grids 1-9 converter 1-40
exporting to an Eclipse
binary file 2-46 importing as exporting 2-29
wells 1-79
exporting to an Isatis exporting properties to
file 2-69 Temis3D files an Excel file 2-7
exporting to Temis3D exporting SGrid objects exporting to a DDS
files 2-55 to 2-55 file 2-29
exporting to VIP triangulated surfaces exporting to a SEG-Y
files 2-50 importing 1-30 file 2-30
solids exporting to an SEP
exporting properties to file 2-31
V
an Excel file 2-7 exporting to VoxelGeo
Velf file, exporting files 2-32
StrataModel files
velocity data to 2-17
importing 2D-Grid VRML files
Velf files
files 1-32, 1-41 exporting 3D Viewer
importing 1-69 images to 2-68
stratigraphic grid data
velocity data
exporting to an Isatis
file 2-69 exporting to a Velf
file 2-17 W
surfaces
exporting to an AVF well curves
creating from horizon
file 2-16 exporting to an ASCII
surface data
importing 1-68 file 2-63
files 1-38
importing Jason well data
creating from velocity
data 1-68 traces 1-68 importing 1-71
exporting data 2-23 importing ProMAX importing column-
files 1-68 based files 1-71,
exporting properties to
importing TDQ .avf 1-80
an Excel file 2-7
files 1-69 importing CPS3 .dat
exporting to a CUBIT
importing Velf files 1-72
facet file 2-23
files 1-69 importing Excel
exporting to a FastEdit
VIP files files 1-72
file 2-24
exporting SGrid objects importing Irap RMS
exporting to a GMI
to 2-50 files 1-73
WellCheck
MohrFracs file 2-25 importing grids 1-53

Part
II
and Export
Data Import
importing LAS creating from column- importing as
files 1-74 based-file wells 1-80
importing location data data 1-71, 1-80 importing horizon
from column-based creating from location data 1-35
files 1-82 data from column- XYZ import file format
importing Octopus based files 1-82 requirements A-30
files 1-80 creating using RC2
importing Temis 3D converter 1-78
files 1-79 exporting 2-60 Z
importing Velf exporting properties to Z-MAP files
files 1-69 an Excel file 2-7 exporting 2D-Grid
importing WITSML exporting to an IRAP objects to 2-28
files 1-79 file 2-60 exporting curves to
well marker data exporting to LAS contours files 2-22
importing from files 2-61 exporting curves to
column-based importing Irap RMS faults files 2-21
files 1-82 files 1-73 importing 2D-Grid
well markers importing using the X object to 1-32
exporting to an ASCII Y Z converter 1-80 importing ASCII 2D-
file 2-62 WITSML files Grid
properties 1-42
well symbol data importing 1-79
importing Z-MAP
importing 1-86
contour files 1-37
well targets
X importing Z-MAP fault
exporting to an or contour
X Y Z files
Octopus ASCII files 1-26
file 2-64 importing as points
set 1-24 Z-MAP import file format
wells requirements A-31

Paradigm™

02 Import Export

Uploaded by

Copyright:

Available Formats

You might also like

02 Import Export

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

02 Import Export

Uploaded by

Copyright:

Available Formats

GOCAD® 2009.

Part II Data Import and Export

Published June 22, 2009

Part II Data Import and Export

1.5.14 Importing a Z-MAP Fault or Contour File ........................................ 1-26

iv Contents GOCAD® 2009.1 User Guide

Rock & Fluid Canvas™ 2009 | Epos™ 4.0 Contents v

1.13.7 Importing a Temis3D File................................................................. 1-79

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

vi Contents GOCAD® 2009.1 User Guide

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

Rock & Fluid Canvas™ 2009 | Epos™ 4.0 Contents vii

A.13 Z-MAP Formats ........................................................................................... A-31

Index .................................................................................................. Index-1

viii Contents GOCAD® 2009.1 User Guide

In this chapter • "Converters," page 1-2 • "Importing Horizon Surfaces Data,"

• "Importing Basin Modeling Files," • "Importing Reservoir Grid Data,"

Table 1–1 Supported

1-2 Importing Data GOCAD® 2009.1 User Guide

1-4 Importing Data GOCAD® 2009.1 User Guide

1.2 Basic Concept for Importing Data

1-6 Importing Data GOCAD® 2009.1 User Guide

1.3 Importing Basin Modeling Files

1.3.1 Import Temis/Medica Files

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

1-8 Importing Data GOCAD® 2009.1 User Guide

5 Click one or more entries in the Vectors column.

1-10 Importing Data GOCAD® 2009.1 User Guide

GOCAD includes converters for importing four MPath file types:

1-12 Importing Data GOCAD® 2009.1 User Guide

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

1.4 Importing Cultural Data

1.4.1 Importing an ArcView File

1-14 Importing Data GOCAD® 2009.1 User Guide

1.4.3 Importing a SeisWorks Cultural Data File

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

1.5 Importing Fault Interpretations Data

1.5.1 Importing a CPS3 ASCII Data (.dat) File

1-16 Importing Data GOCAD® 2009.1 User Guide

Either choice opens the same dialog box.

• To create a Well object, click Well.

1.5.2 Importing a CPS3 Binary File

1.5.3 Importing a Column-Based File

If your data file contains You can create this object

1-18 Importing Data GOCAD® 2009.1 User Guide

6 Click Next to open the Miscellaneous Information dialog box.

1-20 Importing Data GOCAD® 2009.1 User Guide

1-22 Importing Data GOCAD® 2009.1 User Guide

1.5.4 Importing a FastEdit Scattered Data File

1.5.5 Importing an XYZ File

1.5.6 Importing a Charisma Fault Interpretations

1. Charisma is a part of the GeoFrame software product available from Schlumberger.

1-24 Importing Data GOCAD® 2009.1 User Guide

1.5.8 Importing a CPS3 ASCII Polygons (.ply) File

1.5.9 Importing a CPS3 ASCII Fault Traces (.flt) File

1.5.10 Importing a CPS3 Binary File

1.5.11 Importing a Column-Based File

1.5.12 Importing a Petrel Pillars File

1.5.13 Importing a SeisWorks Fault Sticks File