Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
19972012 Paradigm Ltd. or its affiliates and subsidiaries. All rights reserved.
The information in this document is subject to change without notice and should not be construed as a commitment by
Paradigm Ltd. or its affiliates and subsidiaries (collectively, "Paradigm"). Paradigm assumes no responsibility for any
errors that mayappear in this document.
The Copyright Act of the United States, Title 17 of the United States Code, Section 501 prohibits the reproduction or
transmission of Paradigms 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 Paradigms actual damages
and any additional profits of the infringer, or statutory damages in the amount of up to $150,000 per infringement.
Paradigm will also seek all costs and attorney fees. In addition, any person who infringes this copyright willfully and for the
purpose of commercial advantage or private financial gain, or by the reproduction or distribution of one or more copies of
a copyrighted work with a total retail value of over $1,000 shall be punished under the criminal laws of the United States of
America, including fines and possible imprisonment.
The following are trademarks or registered trademarks of Paradigm Ltd. or its affiliates and subsidiaries
(collectively,"Paradigm") in the United States or in other countries: Paradigm, Paradigm logo, and/or other Paradigm
products referenced herein. For a complete list of Paradigm trademarks, visit our Web site at www.pdgm.com. All other
company or product names are the trademarks or registered trademarks of their respective holders.
Alea and Jacta software under license from TOTAL. All rights reserved.
Some components or processes may be licensed under one or more of U.S. Patent Numbers 5,570,106; 5,615,171;
6,765,570; and 6,690,820.
Some components or processes are patented by Paradigm and/or one or more of its affiliates under U.S. Patent Numbers
5,563,949; 5,629,904; 5,838,564; 5,892,732; 5,930,730; 6,055,482; 6,092,026; 6,430,508; 6,819,628; 6,820,043;
6,859,734; 6,873,913; 7,095,677; 7,123,258; 7,295,929; 7,295,930; 7,328,139; 7,561,922; 7,584,056; 7,711,532; and
7,844,402. In addition, there may be patent protection in other foreign jurisdictions for these and other Paradigm products.
All rights not expressly granted are reserved.
Third-party software notices are located at www.pdgm.com/thirdparty/.
Contents
1.2
1.3
1.4
1.5
1.6
1.4.1
1.4.2
1.4.3
1.5.2
1.5.3
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
Contents
iii
1.8
1.7.2
1.7.3
1.7.4
1.7.5
1.7.6
1.7.7
1.8.2
1.8.3
1.8.4
1.8.5
1.8.6
1.8.7
1.8.8
1.8.9
1.9.2
1.9.3
1.9.4
1.9.5
1.9.6
1.9.7
1.9.8
1.9.9
iv
Contents
1.10
1.11
1.12
1.13
1.14
User Guide
Contents
Chapter 2
Converters.................................................................................................... 2-2
2.2
Contents
2.2.2
2.2.3
2.2.4
2.2.5
2.2.6
2.2.7
2.3
2.4
2.5
vi
2.2.1
2.4.1
2.4.2
2.4.3
2.4.4
2.4.5
2.5.2
2.6
2.7
2.5.3
2.5.4
2.6.2
2.6.3
2.6.4
2.7.2
2.7.3
2.7.4
2.8
2.9
2.10
2.9.1
2.9.2
2.9.3
2.9.4
2.9.5
2.9.6
2.9.7
2.9.8
2.11
2.12
Appendix A
User Guide
A.2
A.3
A.4
A.5
A.6
A.7
A.8
Contents
vii
viii
Contents
A.9
A.10
A.11
A.12
A.13
A.14
A.15
1
Importing Data
In this chapter
Overview
In Paradigm SKUA and Paradigm GOCAD , you can import many types of data
from numerous external sources. For example, you can import data in the form of industry
standard formats, raw data, and many formats from other software products. When you
import data, you can:
You can find the importing commands from the File menu on the Import submenu. This
submenu is organized first by the categories of data you can import and then by the
supported programs or data types.
These topics explain how to import the related files and identify the objects that you can
create from the imported files.
Paradigm adds support for new formats based on client need. To inquire about new
options, contact us at: www.pdgm.com/support.
1-1
The validity and accuracy of the data in your file determines the success of what you
import. Therefore, ensure that all files you want to import contain valid data and are in
the correct format. Reviewing ASCII files in an editor, like Notepad, before importing is a
good idea.
Appendix A, "Import File Formats," identifies the import formats that SKUA and GOCAD
support and describes how the converters read the files.
1.1
If you want to
import this
type of data
Basin Modeling
.fau
Curve
.g
Surface
.g
PointsSet, 2D Grid,
Surface, Voxet, SGrid
Temis3D Grid
.td4
SGrid
Temis3D Colormap
Cultural data
Colormap
MPath
PetroMod
.pmb
ArcView
AutoCAD
.dxf
.asc
Curve
.ers
DEM
Fault
interpretation fault sticks
PointsSet, Curve
DEM
DEM binary1
Fault
interpretation points
PointsSet, Voxet
.dat
PointsSet
.ply
PointsSet
.flt
PointsSet
CPS3 binary
.svd
PointsSet
Column-based file
User defined
PointsSet
.dat
PointsSet
XYZ
User defined
PointsSet
Curve
.dat
Curve
.ply
Curve
.flt
Curve
CPS3 binary
.svd
Curve
Column-based file
User defined
Curve
Petrel pillars
.dat
Curve
.dat
Curve
Curve
(Continued 1 of 4)
1-2
Importing Data
If you want to
import this
type of data
Fault
interpretation fault polygons or
traces
Fault surfaces
Curve
.ply
Curve
Curve
.grd
CPS3 binary
Surface
FastEdit 2D grid
.dat
Surface
.dat
Surface
Petrel pillars
.dat
Surface
RC2 2D grid
.gz
Surface
.bin
Surface
StrataModel 2D grid
.smg
Surface
Surface
.gridexp
PointsSet
.dat
PointsSet
CPS3 binary
.svd
.dat
PointsSet
.asc
PointsSet
XYZ
User defined
PointsSet
PointsSet
Adobe contours
.esp
Curve
.dat
Curve
CPS3 binary
.svf, .svp
Curve
Column-based file
User defined
Curve
.dat
Curve
Curve
Z-MAP contour
.zmap
.grd
2D Grid
CPS3 binary
2D Grid
FastEdit 2D grid
.dat
Geoprobe 2D grid
.gvw
2D Grid
GSLib 2D map
Surface
2D Grid properties
Norsar horizons
Voxet
RC2 2D grid
.gz
2D Grid
RESCUE
.bin
Surface
StrataModel 2D grid
.smg
2D Grid
.smg
2D Grid properties
PointsSet
PointsSet
GSLib 2D map
Horizon surfaces
Surface
RESCUE
Column-based file
Horizon
interpretation contours
Curve
Curve
2D Grid
2D Grid properties
Images
2D Grid
(Continued 2 of 4)
User Guide
1-3
If you want to
import this
type of data
Reservoir grid
.grdecl
SGrid
SGrid
.bin
SGrid
.cor
SGrid
VIP LGR
.lgr
SGrid
.grdecl
I J K property
VIP ASCII properties
.cor
SGrid properties
SGrid
.irf, .IRF
.rsm
.GRID, .grid,
.EGRID, .egrid,
.GRD
SGrid properties
SGrid properties
Column-based file
User defined
SEG-Y 3D as voxet
.sgy, .segy
Voxet
VoxelGeo
.vol
Voxet
SEP
.h
Voxet
Voxet
2D SEG-Y as SeismicLine
.sgy, .segy
SeismicLine
SeisWorks
.clr
Colormap
Velocity functions
Promax
Velocity cubes
TDQ
.avf
Velf
.velf
Curve
SEG-Y 3D as voxet
.sgy, .segy
Voxet
SEP
.h
Voxet
VoxelGeo
.vol
2D Grid
Velocity lines
2D SEG-Y as SeismicLine
.sgy, .segy
SeismicLine
Column-based file
User defined
Well
.dat
Well
Excel
.xls
Well
Irap RMS
.log, .decode
Well
LAS
.las
Well
RC2
Well
.gz, .xml
Well
Temis3D
WITSML
Well
(Continued 3 of 4)
1-4
Importing Data
If you want to
import this
type of data
Columns-based file
User defined
Well
X Y Z file
User defined
Well
User defined
Well
Column-based file
Well
Column-based file
User defined
Well
LAS
.las
Well
Well
Completion
Well
Well
.DATA, .data
Well
Column-based file
User defined
Well
Well properties
Well properties
Dip data1
Well properties
Column-based file
User defined
Well properties
DXF
.dxf
PointsSet, Curve, or
Surface
Paradigm Geosec
.ihf
Curve or PointsSet
Locace
.ext
Curve
Dip
Dip
(Continued 4 of 4)
1. Importing a DEM or Dip data requires the Structural Analysis (Kine3D-1) module. For more information
about importing a DEM or Dip, see Part VII: Geologic Interpretation, "Importing a DEM" on page 4-13
or "Importing Dip Data" on page 4-30.
User Guide
1-5
1.2
Important When you import a file to create an object, the name of the new object is the
same name as the import file, without the extension. With the exception that the
commands comply with the SKUA and GOCAD naming conventions. If you import a file
that does not follow the naming conventions, the import command renames the file. For
example, an asterisk (*) is not allowed as a part of the file name. If your file is named
W1*1, the command renames the file as W1_1. For more information about naming
conventions, see Part I: Getting Started, "Naming Objects and Other Items" on page 3-9.
Basic procedure for
importing
Select File > Import, point to the data type, and then click the appropriate
command. The dialog box for the specific command opens.
For example:
Click
to open the Select Text File dialog box, browse for the file you want to
import, and then double-click the file name.
or
In the File name box, type the full path and file name.
1-6
Importing Data
To set the units indicating how the file is to be imported, click Advanced, and then
do any of the following:
a
If the z-axis value in the file you are importing differs from the default z-axis set
for your project, change the domain for this new object. To change the z-axis
value from depth to time, or time to depth click the appropriate option.
Note SKUA or GOCAD automatically selects units based on the default z-axis setting (in
the New Project dialog box) chosen when the project was created.
If the units in the file differ from the default units set for your project, select the
Specify Units of Selected File check box, and then click the appropriate units.
For information about setting units for your project, see Part I: Getting Started,
"Setting Units for a Project" on page 1-19.
User Guide
Click OK or Apply.
1-7
1.3
For point set or curve data, the import wizards create an object from each file that you
import. However, for well data, the wizard creates a Well object for each well identified in
the file.
The importing process is similar for most of the column-based importing wizards. The
following describes the general procedure. Where you encounter differences from this
procedure, follow the instructions in the wizard.
Note You can import certain types of data only if you load specific modules with SKUA or GOCAD.
For information about data that you can import with a particular module, see the topics that
describe the module.
For more information about common settings in column-based import wizards, see:
For information about specifying additional settings for well production data and timedependent grid properties, see:
1-8
Importing Data
"Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97
"Importing Well Production Data from a General Format User File or VOL File,"
page 1-91
Select File > Import, and then do one of the following to access the wizard.
To import this data
And create
this object
Fault interpretations
PointsSet
Horizon interpretations
PointsSet
Curve
Horizon interpretations,
contours
Curve
Select
And create
this object
Well
Well Data > Path > Path and Logs > Markers,
Logs, or Completion Data (depending upon the
type of data in the file) > Column-based file.
Wells
Select
In column-based importing wizards, File type is the first page in most wizards. Select the
data file and specify the data type as follows:
1
User Guide
The wizard automatically previews the first 400 lines of the file. If you want to see
more than 400 lines, click Preload all to preview the entire file.
If the width of each column in the file is a fixed number of characters, click Fixed
width.
Otherwise, if the data is separated by specific characters such as commas, spaces,
tabs, semi-colons, or other characters, leave the Delimited setting.
1-9
For more information, see "Tips for specifying the data type for a column-based file"
on page 1-10.
4
Click Next.
When you import ASCII data by using a column-based import wizard, ensure that you
specify the correct data type, either Delimited (the preselected setting) or Fixed width.
You can find this setting on the File type page (first page in most column-based wizards).
You can check for the following scenarios to help determine which setting to select:
With the Delimited setting, if there are empty lines in the column headings, the
wizard will misalign the headings. For example:
Original data:
DATE
1/1/1988
1/1/1989
1/1/1990
FPRH
barsa
FIELD
397.802
307.55
233.713
FWPRH
sm^3/d
FIELD
0.0000
0.0000
0.0000
FGPRH
sm^3/d
FIELD
0.0
1356750.0
1217807.5
FOPRH
sm^3/d
FIELD
0.00
9000.00
9000.00
Misaligned data:
In this data, lines 2 and 3 in the "Date" column heading are empty, and the wizard
aligns the data as follows:
DATE
barsa
FIELD
1/1/1988
1/1/1989
1/1/1990
FPRH
sm^3/d
FIELD
397.802
307.55
233.713
FWPRH
sm^3/d
FIELD
0.0000
0.0000
0.0000
FGPRH
sm^3/d
FIELD
0.0
1356750.0
1217807.5
FOPRH
0.00
9000.00
9000.00
With the Delimited setting, when you advance to the next page of the wizard
(Column Separation) and select delimiters, the columns should be highlighted with
alternate colors. For example:
If the columns are not selected as shown, return to the previous page and select
Fixed width instead.
If you select Fixed width, when you advance to the next page in the wizard, you can
delineate the columns based on fixed field width.
1-10
Importing Data
In column-based import wizards, the Column Separation page previews the column
structure of the file. Yellow highlighting appears in alternate columns.
Figure 12 Column
separation for delimited
fault interpretation data
Specify the column separation by doing one of the following depending on the data
type:
For this data type
Do this
Delimited
2
3
Fixed width
Specify column breaks by clicking within the preview pane to add a column
break or double-clicking a break to remove it.
Click Next.
Note In the production data importing wizards, the next pages are specific to production data. For
information about these pages, see:
User Guide
"Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97
"Importing Well Production Data from a General Format User File or VOL File," page 1-91
1-11
To specify
miscellaneous
information for a
column-based file
To answer a question click Yes, No, or another option if a question has other options.
The area to the left of the questions presents additional information to help you
answer the questions.
If there is no x-, y-, or z-column in the file, the wizard automatically assigns a value of zero for
that coordinate.
If there is an x-, y-, or z-column, on the next page of the wizard, you need to specify the
location of this data in the file.
In the column-based importing wizards, if items (such as x-, y-, or z-coordinates or the
object name) are given in specific columns in the file, on the Column assignment page
(see example, Figure 14), you need to specify the location of the items in the file.
Note This page is not exactly the same in all column-based import wizards, and not all wizards
include this page. Where you encounter differences, follow the instructions in the wizard.
1-12
Importing Data
User Guide
Depending on the option selected on the previous page (under To name the
objects), you may type a name for the new object in the Object name box, select a
column, or use the file name.
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.
1-13
Click Add, type the name (any name you want) in the New Property Name box,
and then click OK.
Select the property or parameter in the list, and then enter the column location
number in the Column number box.
The wizard will add the property in your file to the existing object.
5
To remove a property, select the name in the Property List and parameters box and
then click Remove.
If you want the wizard to read a specific value as a no-data value (a number always
read as null), select the Use no-data value check box, and then type the number in
the box.
Tip For well production data, use -99999 as the no-data value to prevent null data from
appearing as zeros in production plots. For more information about importing production data,
see "Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97.
If you want to specify the time or depth domain or the units of measurement for the
data, click Advanced, and then do the following as necessary:
To specify units, click the Specify units of selected files check box, and then
click options for the area, depth, and depth axis units.
To complete the
importing process
1-14
Importing Data
In a column-based importing wizard, when you finish adjusting the configuration settings,
do the following to complete the importing process:
1
Review the file to ensure that all additions or changes you made are correct.
Import the data or adjust the settings for additional files as follows:
To do this
Do this
Click OK.
The wizard imports the data from all of the files and closes the
wizard.
The wizard creates objects and any object properties from the imported data. You can
find the new objects and properties in the Objects browser.
1.4
1.4.1
To import a Fault
Polygon Medica file
as a Curve
Use the Medica converter to create a Curve object from fault polygon data in a Medica
fault polygon file. The converter creates a Curve object for each import file.
Select File > Import > Basin Modeling > Temis > Medica Fault Polygons, and
then select the file or type the full path and file name in the dialog box.
For more information about how to complete the importing process, see "Basic procedure
for importing" on page 1-6.
To import a
Topographic Surface
Medica file
Use the Medica converter to import Medica Surface Topographic files. These files have
a .g or .top file name extension. A Medica Topographic file is a binary file that can
contains a regular map or a tartan map (Scottish map). The converter creates a Surface
object from each import file.
Select File > Import > Basin Modeling > Temis >Medica Topographic Surface,
and then select the file or type the full path and file name in the dialog box.
For more information about how to complete the importing process, see "Basic procedure
for importing" on page 1-6.
To import a Medica
2D Grid file
Use the Medica converter to import a Temis 2D Grid file and create a PointsSet, 2D Grid,
Surface, Voxet, or SGrid object.
1
Select File > Import > Basin Modeling > Temis > Medica Topographic Surface
(Advanced) to open the Import Medica 2D Grid dialog box.
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.
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.
User Guide
1-15
To select which object type you want the converter to create when importing the file,
click one of the following:
Create PointsSet
Create Surface. In the Decimation Level box, select how you want the
converter to use the data in the file.
None. Keep all points.
Level 1. Take into account all data points when creating the Surface.
Level 2. Take into account four out of nine points when creating the Surface.
In the Maximum error box, type the value for maximum distance you want the
converter to use when computing errors.
Note Values are measured in the units you set for the project. To check the project units:
select File > Project Properties.
To import a Temis3D
Grid file
Create Voxet. In the Property name box, type a name you want the converter
to use when storing the data values.
Create SGrid
In the Output no data value box, type the value that you want the converter to
recognize as a no-data value.
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.
Click OK or Apply.
You can use the Medica converter to import a Temis3D Grid file as an SGrid object. The
converter can create one or more objects from each import file. The name of the resulting
SGrid object will be the name of the Temis3D file plus the Roamer age.
1
Select File > Import > Basin Modeling > Temis > Temis 3D Grid (.t4d) to open the
Import Temis3d t4d File dialog box.
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 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:
1-16
Importing Data
Roamer (or Age). List of model ages (age of a layer deposition) in the selected
file.
Click one or more entries in the Roamer column. You can create an SGrid for each
entry in the list. Hold down the CTRL key to select more than one entry.
To import a Temis3D
Colormap
User Guide
Click OK or Apply.
You can use the Medica converter to import a Temis3D Colormap. The converter will
create a Colormap for each import file.
1
Select File > Import > Basin Modeling > Temis > Temis 3D Grid Colormap to
open the Import Termis3D Colormap dialog box.
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.
In the Colormap name box, type the name you want to use for the map. The default
name is Temis_Colormap.
Click OK or Apply.
1-17
1.4.2
.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
Use the MPath ACT converter to import an .act file that contains basin modeling data.
The .act file can contain ASCII and binary formatted data.
The converter creates a Voxet or PointsSet object from each file that you import.
To import an
MPath .raw file as a
Voxet
1-18
Importing Data
Select File > Import > Basin Modeling > MPath ACT to open the Import Permedia
ACT File dialog box.
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 converter enters the selected file
name in the ACT file box.
If you want the converter to create a PointsSet object click PointsSet. By default, the
converter imports this file and creates a Voxet object.
If you want to also import the related .fid and .par files, select the Import
Related .fid and .par File check box.
Click OK or Apply.
Use the import MPath Raw file converter to create a Voxet object from a combined ASCII
and binary MPath .raw file.
Select File > Import > Basin Modeling > MPath RAW, 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 an
MPath .fid file as a
Voxet
Use the import MPath FID converter to create a Voxet object from a combined ASCII and
binary MPath flow unit identification (.fid) file.
Select File > Import > Basin Modeling > MPath FID, 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 an
MPath .par
(Colormap) file
Use the import MPath PAR converter to create a color map from an ASCII MPath .par file.
Select File > Import > Basin Modeling > MPath PAR (Colormap), and then select
the file or type the full path and file name in the dialog box.
For more information about how to complete the importing process, see "Basic procedure
for importing" on page 1-6.
1.4.3
To import a PetroMod
IES file as an SGrid
Select File > Import > Basin Modeling > PetroMod to open the Import PetroMod
ACT File dialog box.
User Guide
1-19
Click
name.
Specify whether you want to import facies or overlays and create a cell-centered or
corner-point grid by clicking one of these:
1-20
Importing Data
If you want to specify the domain or units of measurements for data in the selected
files, click Advanced and then do the following as necessary:
to browse for the file you want to import, and then double-click the file
Click OK or Apply.
1.5
Supported import sources and how to import the specific files are described in this
section.
1.5.1
To import an ArcView
file
Select File > Import > Cultural Data > Arcview, 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.
1. ArcView is a geographic information system available from the Environmental Systems Research
Institute (ESRI).
User Guide
1-21
1.5.2
Select File > Import > Cultural Data > DXF to open the Import DXF file dialog box.
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 converter enters the selected file
names in the File name box.
Select the Import text check box, if you want to include text as a part of the object.
Note Including text with the object significantly increases processing time.
1.5.3
Click OK or Apply.
To import a SeisWorks
file
Select File > Import > Cultural Data > SeisWorks Cultural Data (ASC), 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.
1. A .dxf file is produced by AutoCAD, a software product available from Autodesk.
2. SeisWorks is a software product available from Landmark Graphics.
1-22
Importing Data
1.6
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
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
a
a
a
a
a
a
a
a
User Guide
"Importing
"Importing
"Importing
"Importing
"Importing
1-23
1.6.1
Select File > Import >, and then do one of the following to open the dialog box.
If you want to import this
type of data
To create this
type of object
Fault interpretations
PointsSet
Horizon interpretations
PointsSet
Curve
Horizon interpretations,
contours
Curve
Well
Do this
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.
Click OK or Apply.
1. CPS3 (a mapping system) is a part of the GeoFrame software product available from Schlumberger.
1-24
Importing Data
1.6.2
To import a CPS3
binary .svd file as a
PointsSet
Select File > Import > Fault Interpretations > PointsSet > CPS3 Binary
(.svd, .svs, .svf, and .svp), 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.
1.6.3
1.6.4
To import a FastEdit
Scattered Data file as
a PointsSet
User Guide
Select File > Import > Fault Interpretations > FastEdit Scattered data, 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.
1-25
1.6.5
To import an X, Y, Z
ASCII file as a
PointsSet
1.6.6
Select File > Import > Fault Interpretations > PointsSets > X Y Z to open the
Import X Y Z ASCII File dialog box.
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.
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-datavalue is -9999. The no-data-value option is unavailable unless you select the ignore
points with no data value check box.
Click OK or Apply.
To import a Charisma
file as a Curve
Select File > Import > Fault Interpretations > Fault Sticks > Charisma Fault
Interpretations, and then select the file or type the full path and file name in the
dialog box.
For more information about how to complete the importing process, see "Basic Concept
for Importing Data" on page 1-6.
1-26
Importing Data
1.6.7
1.6.8
Select File > Import > Fault Interpretations > PointsSet > CPS3 ASCII Polygons
(.ply), 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.
1.6.9
Select File > Import > Fault Interpretations > Fault Sticks > CPS3 ASCII Polygons
(.flt), 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.
1.6.10
To import a CPS3
binary .svf or .svp file
as a Curve
Select File > Import > Fault Interpretations > Fault Sticks > CPS3 Binary
(.svd, .svs, .svf, and .svp), 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.
User Guide
1-27
1.6.11
1.6.12
To import a Petrel
Pillars file as a Curve
Select File > Import > Fault Interpretations > Fault Sticks > Petrel Pillars, 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.
1.6.13
To import a SeisWorks
fault sticks file as a
Curve
1.6.14
Select File > Import > Fault Interpretations > Faults Sticks > SeisWorks 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 procedure
for importing" on page 1-6.
To import a Zmap
fault traces or
contour file as a
Curve
Select File > Import > Fault Interpretations > Fault Sticks > Z-MAP Fault or
Contour Files, 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.
1-28
Importing Data
1.6.15
To import a Charisma
Fault Polygon file as a
Curve
1.6.16
Select File > Import > Fault Interpretations > Fault Polygons (Curves) >
Charisma Fault Polygons to open the Import ASCII Charisma Fault Polygon To Curve
dialog box.
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.
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.
Type the no-data-value in the value when undefined box. The default is 0.
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).
If you chose to use a prefix, type the prefix you want in the Fault prefix box.
Click OK or Apply.
To import a CPS3
Polygons file as a
Curve
Select File > Import > Fault Interpretations > Fault Polygons or Traces > CPS3
ASCII Polygons (.ply), 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.
User Guide
1-29
1.6.17
To import a FastEdit
fault polygons file as
a Curve
Select File > Import > Fault Interpretations > Fault Polygons or Traces >
Fastedit Fault Polygons, and then select the file or type the full path and file name
in the dialog box.
For more information about how to complete the importing process, see "Basic procedure
for importing" on page 1-6.
1.6.18
Select File > Import > Fault Interpretations > Fault Polygons or Traces > Irap
RMS Fault Polygons or Lines, 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.
1.6.19
To import a SeisWorks
Fault Polygon file as a
Curve
Select File > Import > Fault Interpretations > Fault Polygons or Traces >
SeisWorks Fault Polygons, and then select the file or type the full path and file
name in the dialog box.
For more information about how to complete the importing process, see "Basic procedure
for importing" on page 1-6.
1-30
Importing Data
1.7
1.7.1
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
Select File > Import > Fault Surfaces > CPS3 ASCII 2D-Grid (.grd), 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.7.2
To import a CPS3
binary .svs file as a
2D-Grid
1.7.3
Select File > Import > Fault Surfaces > CPS3 Binary (.svd, .svs, .svf, and .svp),
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 FastEdit
2D grid file as a 2DGrid
User Guide
Select File > Import > Fault Surfaces > Fastedit 2D-Grid, 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.
1-31
1.7.4
1.7.5
Select File > Import > Fault Surfaces > Irap RMS Triangle Surface, 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 Petrel
Pillars file as a Surface
Select File > Import > Fault Surfaces > Petrel Pillars, 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.
1.7.6
To import an RC2
2DGrid file as a 2D
Grid
Importing a RESCUE
Model File
Select File > Import > Fault Surfaces > RC2 2D-Grid, 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.
Use the RESCUE Model converter to import a .bin file. Depending on the type of data in
your file, you can:
The converter imports grid data as an SGrid object and horizon or fault data as a girded
Surface object (2D Grid).
RESCUE, a Joint Industry Project managed by the Petrotechnical Open Software Corporation (POSC),
is an acronym for REServoir Characterization Using Epicentre.
A RESCUE file is typically composed of multiple file types. The converter reads only files
with a .bin file extension, and only files produced up to and including RESCUE Version 37.
Output from a RESCUE project typically contains different types of data: surfaces, grids
and properties. The converter can import grids, horizons, faults and properties.
Note The converter can read only horizons or faults that are represented by a regular I, J grid. This
converter cannot import Well data.
1. Petrel is a software product available from Schlumberger.
2. RC(2) Geostatistics for Stratamodel is a software product available from Landmark Graphics.
1-32
Importing Data
To import a RESCUE
file as an SGrid or
Surface (2D Grid)
Select File > Import > Reservoir Grid > RESCUE Model (Grids, Horizons, Faults)
to open the Import RESCUE as SGrid dialog box.
Click
If the data includes stratigraphic units and the logical order for those units, the
command creates a stratigraphic column resource from the data in the file. In the
New stratigraphic column name box, type a name for this new resource. (After the
import, you can find it in the Resources browser.)
1.7.7
Load reservoir grid. Imports the grid and creates and SGrid object.
Load properties. Imports property data as object properties.
Load horizon and fault surfaces. Imports horizons and faults as triangulated
surfaces, gridded surfaces, point sets, and curves. If you deselect this option, the
command imports all horizon and fault data as 2D-Grid Surface objects.
If you want to extract fault block information from imported grid, in the Advanced
area, select the Recreate fault blocks check box.
Click OK or Apply.
To import a Z-MAP 2D
grid file as a 2D Grid
Select File > Import > Fault Surfaces > Z-MAP ASCII 2D-Grid, 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.
1. Z-MAP is a software product available from Landmark Graphics.
User Guide
1-33
1.8
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
1.8.1
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
To import a Charisma
file as a PointsSet
Select File > Import > Horizon Interpretations > PointsSet > Charisma Horizon
Points, 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-34
Importing Data
1.8.2
1.8.3
To import a CPS3
binary .svd file as a
PointsSet
Select File > Import > Horizon Interpretations > CPS3 Binary (.svd, .svs, .svf,
and .svp), 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.
1.8.4
1.8.5
To import a FastEdit
scattered data file as
a PointsSet
1.8.6
Select File > Import > Horizon Interpretations > FastEdit Scattered Data, 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 GSLib 2D
Map as a PointsSet
Select File > Import > Horizon Interpretations > PointsSet > GSLib 2D Map, 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.
User Guide
1-35
1.8.7
To import a SeisWorks
Inline file as a
PointsSet
Select File > Import > Horizon Interpretations > PointsSets > SeisWorks Inline
Xline X Y Z, 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.
1.8.8
Importing an X, Y, Z File
Use the X, Y, Z converter to import a raw data ASCII file to create a PointsSet object. The
converter reads only the first three data fields in the file. Each line in the input file
becomes a point in the newly created object, with the X value as the first point, the Y
value as the second point, and the Z value as the third point.
To import an X, Y, Z
file as a PointsSet
1-36
Importing Data
Select File > Import > Horizon Interpretations > PointsSets > XYZ to open the
Import X Y Z ASCII File dialog box.
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.
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.
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.
Click OK or Apply.
1.8.9
To import an Adobe
Contours as a Curve
Select File > Import > Horizon Interpretations > Contours > Adobe Contours,
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.
1.8.10
1.8.11
To import a CPS3
binary .svf or .svp file
as a Curve
Select File > Import > Horizon Interpretations > Contours > CPS3 Binary
(.svd, .svs, .svf, and .svp), 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.
1.8.12
1.8.13
To import a FastEdit
horizon contour file
as a Curve
User Guide
Select File > Import > Horizon Interpretations > Fastedit Horizon contours, 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.
1-37
1.8.14
To import a Z-MAP
Contour file as a
Curve
1-38
Importing Data
Select File > Import > Horizon Interpretations > Z-MAP Contour Files, 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.
1.9
1.9.1
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
Select File > Import > Horizon Surfaces > CPS3 ASCII 2D-Grid, 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.
1.9.2
To import a CPS3
binary .svs file as a
2D-Grid
Select File > Import > Horizon Surfaces > CPS3 Binary, and then select the file or
type the full path and file name in the dialog box.
User Guide
1-39
1.9.3
To import a FastEdit
2D-Grid file as a 2D
Grid
1.9.4
Select File > Import > Horizon Surfaces > FastEdit 2D-Grid, 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 Geoprobe
.gvw file as a 2D Grid
Select File > Import > Horizon Surfaces > Geoprobe 2D-Grid (.gvw), 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.
1.9.5
To import a GSLib 2D
Map as a Surface
Select File > Import > Horizon Surfaces > GSLib 2D Map as Surface, 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.
1.9.6
To import an IRAP
RMS ASCII grid file as
a 2D-Grid object
1-40
Importing Data
Select File > Import > Horizon Surfaces > Irap RMS ASCII 2D-Grid, 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.
1.9.7
1.9.8
Select File > Import > Horizon Surfaces > Irap RMS ASCII 2D-Grid Property to
open the Import Z-MAP ASCII as 2D-Grid Property dialog box.
In the 2D-Grid box, specify the file name of the existing 2D-Grid object (for which
you want to import the properties).
In the File name box, specify the file you want to import. Click
file you want to import, and then double-click the file name.
In the Property name box, type the name of the property you want to import.
Click OK or Apply.
1.9.9
To import an RC2
2DGrid file as a 2D
Grid
User Guide
Select File > Import > Horizon Surfaces > RC2 2D-Grid, 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.
1-41
1.9.10
1.9.11
To import a Z-MAP 2D
grid file as a 2D-Grid
Select File > Import > Horizon Surfaces > Z-MAP ASCII 2D-Grid, 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.
1.9.12
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-42
Importing Data
Load an existing 2D-Grid object into your project or create a 2D-Grid object.
Select File > Import > Horizon Surfaces > Z-MAP ASCII 2D-Grid Property to open
the Import a Z-MAP file as a Property of the Grid dialog box.
In the 2D-Grid box, enter the file name of the existing 2D-Grid object for which you
want to import the properties.
In the Property name box, type the name of the property you want to import.
Click OK or Apply.
1.10
To import an image
log
You can import an image log to use in a track in a well section or cross section view.
1
Select File > Import > Well Data > Logs > Image Log to open the Import Well
Image Log dialog box.
In the Well box, select the well for which you want to import the image log.
In the Image Top Measured Depth box, enter the top depth at which you want the
image to appear.
In the Sampling box, enter a value that is used to multiply the image height in pixels
to determine the height of the image. For example, if your image is 120 pixels in
height, and the sampling is 2 meters, the log image will be 240 meters in height.
Note The sampling unit is the measured depth unit, which can vary depending on the well.
User Guide
Click OK or Apply.
1-43
To import an image
log with SIF
You can import an image log in SmartRaster Interchange Format (SIF) to use as an image
track in a well section or cross section view. This format allows for a proper calibration
between the picture and the measured depth. For example, it corrects deformations
caused by scanning paper logs. A2D Technologies licenses SIF.
1
Select File > Import > Well Data > Logs > Image Log with SIF to open the Import
Well Image Log dialog box.
Click OK or Apply.
After you import the image log, you can attach the picture to the appropriate well. You
can determine which well to attach the image log by using the well API, which you can
check and edit in the well constant table. For more information about well constants, see
Part I: Getting Started, "Opening Well Constants from Epos" on page 4-17.
To import a 2D image
file as a Voxet
1-44
Importing Data
Use the 2D Voxet converter to create a Voxet object from a 2D image file.
1
Select File > Import > Images > As 2D Voxet to open the Import Image as Voxet
dialog box.
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.
Click OK or Apply.
1.11
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
For information about importing faults, see "Importing an ECLIPSE ASCII Faults File,"
page 1-61.
For information about importing well completions as SGrid object properties, see
"Importing Well Completion Data," page 1-90.
User Guide
1-45
1.11.1
To import an ECLIPSE
ASCII file as an SGrid
Select File > Import > Reservoir Grid > SGrid > ECLIPSE ASCII Grid to open the
Import ECLIPSE ASCII as SGrid dialog box.
In the File name box, enter the path and file name of the file that you want to
import.
To specify the advanced importing options, click Advanced, and then do the
following as necessary:
To import the well completions along with the grid and properties, select the
Import well completions check box and enter a name for the production
scenario in the Completion scenario name box.
1. ECLIPSE (a reservoir simulation software) is a part of the Schlumberger Information Solutions suite
of simulators.
1-46
Importing Data
To import local grid refinements (LGRs), select the Import LGR check box.
For information about LGRs, see Part X: Reservoir Production and Simulation,
"Local grid refinement (LGR)" on page 2-5.
To change the origin of the grid, select Switch I, Switch J, and Switch K check
boxes as necessary.
For example, Switch I sets the origin of the grid to Imax instead of Imin.
Depending on the options selected, you can set the origin of the grid to any
corner.
If the units in the file differ from the default units set for your project, select the
Specify units of selected files check box, and then select the appropriate units.
For information about setting units for the project, see "Setting Units for a
Project" on page 1-19.
If you want to extend dying faults, select the Propagate vertical cuts check box.
If selected, the command extends fault cuts from the top to the bottom of the
grid.
If you want to automatically build faults, select the Automatically detect faults
check box. For example, this is useful if faults are not defined in the file by using
the FAULTS keyword.
Note If there is no FAULTS keyword in the file, you might want to turn off the automatic
detection of faults, and instead use the ECLIPSE ASCII Faults converter (File > Import >
Reservoir Grid > ECLIPSE ASCII Fault) to add fault data to the imported grid. For
information, see "Importing an ECLIPSE ASCII Faults File," page 1-61.
You can find the imported grid and properties in the Objects browser by expanding the
Flow Models category.
If you imported well completions, the completions appear as grid properties and the date
is included in the name (for example, completions_1998_01_01). The wells appear in the
Objects browser.
1.11.2
User Guide
1-47
Important The binary ECLIPSE file (*.GRID or *.EGRID), the initial reservoir data file
(*.INIT), and the unified restart data file (*.UNRST) should have the same root file
name, such as: name .GRID, name .INIT, and name .UNRST. In addition, all files should
be binary and should be located in the same folder.
Exception If you are importing more than one restart file, the extensions should
be .X0000, .X0001, and so on.
Note When you import dual-porosity data, matrix properties are prefixed with "M" (for example,
MPORO for matrix porosity) and fracture properties with "F" (for example, FPORO for fracture
porosity).
For more information, see the following procedure.
To import an ECLIPSE
binary file as an SGrid
1-48
Importing Data
Select File > Import > Reservoir Grid > ECLIPSE Binary Grid to open the Import
ECLIPSE Binary Files dialog box.
In the Grid file box, enter the path and file name for the grid that you want to
import. Supported formats include: GRID and EGRID files.
When you select the grid file, if the INIT and UNRST files are in the same folder and
have the same root file name, the converter automatically selects them for you.
3
If you plan to work with the data in the Production Data Analysis Workflow or, later,
export the grid to a flow simulation program, in the Scenario box, type a name to
specify the simulation scenario.
For more information about Production Data Analysis, see Part X: Reservoir
Production and Simulation, Chapter 5, "Analyzing Production Data."
User Guide
If the imported grid does not include some of the required information, complete
these steps on the General Information tab:
If the grid origin is not defined in the file, type the coordinates in the X, Y, and Z
boxes to define the grid origin.
If the map rotation is not defined in the file, type the angle in the Angle
(degrees, clockwise) box.
If the areal and vertical units of measurement are not defined, click Feet or
Meters under Map units and Grid units.
If you want to import all the data contained in the binary file (all initial properties and
time-dependant properties from all report dates) and you do not want to make any
adjustments to the grid position, complete this procedure by clicking OK to import
the file and create the SGrid object.
1-49
Otherwise, choose which properties to import and adjust the grid if necessary by
completing the remaining steps in this procedure.
1-50
Importing Data
User Guide
In the Properties box, select the initial properties that you want to import.
1-51
Click the General Information tab, and then select the Select individual
report dates in the time-dependent properties panel check box.
Click the Time-Dependent Properties tab, and then under Report dates, do
one of the following:
To automatically select the dates according to frequency and start and end
dates, click Select one every n report dates, and then select the frequency
number. In the From and To boxes, select the start and end dates.
Important If you have only one restart file, the extension should be .UNRST
(meaning unified restart ). If you are importing more than one restart file, the
extensions should be .X0000, .X0001, and so on.
1-52
Importing Data
To change the grid origin or use INSPEC and RSSPEC files, click the Advanced tab.
To change the origin of the imported grid, click one of the options for the Areal
origin of cells and for the Vertical origin of cells.
For information, see "About the Grid Origin" on page 2-37.
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.
To automatically build faults, select the Automatically detect faults check box.
For example, you might want to do this if faults are not defined in the file with
the FAULTS keyword.
Note If faults are not defined in the file with the FAULTS keyword, you might want to turn
off the automatic detection of faults, and instead use the ECLIPSE ASCII Faults converter
(File > Import > Reservoir Grid > ECLIPSE ASCII Fault) to add fault data to the imported
grid. For more information, see "Importing an ECLIPSE ASCII Faults File," page 1-61.
10 Click OK or Apply.
You can find the imported grid and properties in the Objects browser in the Flow
Models category. Time-dependent properties appear under Property Groups.
User Guide
1-53
1.11.3
To import CMG
simulation results
Select File > Import > Reservoir Grid > CMG Grid to open the Import CMG Grid
and Production Data dialog box.
Do this
File name
Type the path and file name of the CMG .irf or .IRF data file that you want
to import, or click
Scenario
If you plan to work with the data in the Production Data Analysis Workflow
or, later, export the grid to a flow simulation program, type a name to
specify the simulation scenario.
For more information about Production Data Analysis, see Part X: Reservoir
Production and Simulation, Chapter 5, "Analyzing Production Data."
Realization
Unit system
Specify the unit system for the CMG simulation run by typing in the box.
Valid entries include Metric and Field.
Import properties
Select the check box to import any initial and time-dependent properties
(for example, permeability and pressure over time).
Or, clear the check box to import only the grid, excluding any grid
properties.
1-54
Importing Data
Do this
Import
productions
Select the check box to import any well production data along with the grid,
or clear the check box to exclude any production data.
Import
completions
Select the check box to import any completion data along with the grid, or
clear the check box to exclude any completion data.
The command imports the CMG grid, creating an SGrid object (and Wells, if any) and
adding any properties and production or injection results as object properties.
Additionally, if you are working in the Production Data Analysis Workflow, you can find
the new data by accessing the Specify Scenarios task in the workflow. In the list of
scenarios, the data location for the named scenario appears as "Session," and the
associated grid is given the name of the .irf or .IRF file. Additionally, you can skip the next
two tasks in the workflow, Load Grid Properties and Load Production Results, for any
CMG scenarios for which you imported grid properties and production or injection results.
For information about specifying scenarios in the workflow, see Part X: Reservoir
Production and Simulation, "Specifying Scenarios and Importing Historical Data" on
page 5-24.
User Guide
1-55
1.11.4
1.11.5
Select File > Import > Reservoir Grid > SGrid > VIP ASCII Grid to open the Import
an SGrid from VIP ASCII file dialog box.
In the File name box, enter the path and file name for the file that you want to
import.
In the SGrid name box, type a name for the new grid.
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
Type the number of cells for the I, J, and K directions in the appropriate Number
of cells box.
If you do not specify the size, the converter expects to read the values from the file.
1-56
Importing Data
1.11.6
If you want to specify the domain or the units for the data in the selected files, click
Advanced to expand the dialog box, and then do the following:
To specify the units, select the Specify units of selected files check box, and
then click either Feet, Meters, or Kilometers for the Area units and Depth
unit as necessary.
Click OK or Apply.
To import a VIP or
ECLIPSE LGR file
To open the import converter, select File > Import > Reservoir Grid:
VIP LGR. Opens the Import VIP ASCII LGR dialog box.
ECLIPSE LGR. Opens the Import ECLIPSE ASCII LGR as SGrid dialog box.
In the File name box, enter the path and file name of the file that you want to
import.
In the Stratigraphic grid box, enter the name of the existing SGrid object associated
with the local refinement data.
1. VIP is a software product available from Landmark Graphics.
2. ECLIPSE is a software product available from Schlumberger.
User Guide
1-57
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.
If you plan to work with the LGRs in the LGR and Upscaling Workflow, or later, export
the LGRs to a flow simulation program, type a name to identify the LGRs in the LGR
scenario box (for VIP) or Scenario box (for ECLIPSE).
For more information about LGR scenarios, see Part X: Reservoir Production and
Simulation, "Defining LGR Scenarios and Starting the Export Process" on page 2-118.
1.11.7
To import ECLIPSE
properties into an
SGrid
Select File > Import > Reservoir Grid > Properties > ECLIPSE ASCII Properties to
open the Import ECLIPSE ASCII as SGrid Properties dialog box.
In the Stratigraphic Grid box, select the names of the existing SGrid objects for
which you want to import the properties. If you have only one SGrid object loaded,
the correct name automatically appears in this box.
In the File name box, enter the path and file name of the file that you want to
import.
Important If you import a property value that already exists in the grid, the
converter overwrites the existing property values with the new (imported)
property values. If you import a property value that does not exist in the grid, the
converter adds that property value to the grid.
1-58
Importing Data
1.11.8
Meaning
Values
or
1 to i
2
or
1 to i
3
or
1 to i
4
Value of the
property
NA
Notes
Not all indices are required. If one is missing, the imported value is assigned the no-data value.
If there is more than one column describing the property, the property will be vectorial, with
each field described by a column.
The total number of lines in the text file corresponds to the sum of I J K .
If an index is out of range, the line is discarded.
You can easily create an I J K Property file by running a property script on an SGrid. For
example:
print > "File Path" I, J, K, Property Name;
where, File Path is the path where you want to save the file, and Property Name is the
name of the property you want to export.
User Guide
1-59
To import an I J K
property file to an
existing SGrid
1.11.9
Select File > Import > Reservoir Grid > Properties > IJK Property to open the
Import I J K Property-Value File as Grid Property dialog box.
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.
In the Property box, type or select the name of the property you are going to update.
In the File name box, enter the path and file name of the file that you want to
import.
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).
Select the indices start at 1 check box if the grid indices in the file start at one. By
default the converter starts the grid indices at zero.
Click OK or Apply.
To import VIP
properties into an
existing SGrid
1-60
Importing Data
Select File > Import > Reservoir Grid > VIP ASCII Properties to open the Import
VIP ASCII as SGrid Properties dialog box.
1.11.10
In the Stratigraphic Grid box, select the existing SGrid objects for which you want to
import the properties. If you have only one SGrid object in the project, the correct
name automatically appears in this box.
In the File name box, enter the path and file name of the file that you want to
import.
Click OK or Apply.
To import ECLIPSE
fault data into an
SGrid
User Guide
Select File > Import > Reservoir Grid > Fault > ECLIPSE ASCII to open the Import
Faults from ECLIPSE ASCII File dialog box.
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.
In the File name box, enter the path and file name of the file that you want to
import.
If the grid already contains faults and you want to overwrite them, select the Replace
all existing faults check box.
Click OK or Apply.
1-61
1.12
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
For information about importing seismic lines, see "Importing a 2D SEG-Y File as Seismic
Lines," page 1-72.
For information about importing color maps, see "Importing a SeisWorks Colormap,"
page 1-72.
1.12.1
Important By default SKUA and GOCAD saves only the link to the file you import
the data is not copied into your project. You can request that the data be saved in
your project; see step 6.
1-62
Importing Data
To import a 3D SEG-Y
file as a Voxet
Select File > Import > Seismic Data > Seismic Cubes > SEG-Y 3D as Voxet to
open the SEGY 3D to Voxet dialog box.
This example shows a 3D SEG-Y file already selected in the SEG-Y file box so that you
can see what is displayed in the dialog box window.
User Guide
In the SEG-Y file box, enter the path and file name of the file that you want to
import.
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.
1-63
If you want to edit the dimensions in the file, click Settings to edit the SEGY import
settings, and then do any of the following:
Important After you complete your edits (all tabs), you can click Rescan and the
converter will recalculate all the values in the file. Click Close to close the dialog box
and return to the 3D-Seg-Y as Voxet dialog box. Depending on the size of the file,
this process could take a significant amount of time.
To change the line and trace byte locations, on the Edit Dimensions tab, select
the Override Line and Trace byte location check box and type the correct byte
locations in the boxes.
Note The converter uses trace header keywords to determine where the line and trace
data is located and these values are displayed in the dimmed boxes.
1-64
Importing Data
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.
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).
User Guide
1-65
If you want to edit values, other than dimensions or geometry, click the Advanced
tab to open the SEGY 3D import settings dialog box.
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).
Select the Use Trace Weighting Factor check box, if you want the converter to
use the rescaling factor.
Note You can elect to use the rescaling factor at any time, however, it is most effective
when you select an 8-bit format as the Override sample format.
To override the scaling factor, select the Override Coordinate Scaling check box
and then type the value you want to use in the box. By default, all coordinate
values are unscaled (that is, all coordinates are scaled by a factor of one).
To change the name of the property, type the new name in the Property Name
box. The default is amplitude.
If you want to specify whether the property is signed, select the Property is
Signed check box. A signed value can be negative, 0 or positive, while an
unsigned value can be only 0 or positive.
Note This option is applicable only for 8 or 16 bit data.
If there are missing traces in the file, select the Some Traces are missing check box.
If the format of the raw data has the most significant digits stored on the right
(the little end), select the File is a little endian check box. Otherwise, leave the
check box cleared to indicate the order is big endian; that is, an order in which
the "big end" (the most significant digits) are stored first.
Little endian is the format commonly used in the Windows and Linux operating
environments. Big endian is the format commonly used in the UNIX environment.
1-66
Importing Data
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.
To add a property to an existing Voxet in your project, select the Add property
to an existing Voxet check box, and then select the Voxet.
Note You can add a property only to an existing voxet that has the same number of
samples as the SEGY data. In addition, make sure the orientation of the data is the same
(the three axis directions in the voxet match the directions in the SEGY data).
The typical workflow for that is that you have many properties for several objects
then you export them to one object that you can work with together in one
voxet.
If you want to see the different headers that are in the file, click the SEG-Y Headers
tab to open the SEGY 3D import settings dialog box.
EBCDIC
header
User Guide
In the SEGY HEADERS box, the EBCDIC header contains information about the
general content of the file, such as company name, the Voxet object name, the
instruments and processing methods used, and so on. This data is optional, the
converter does not need to read it to import the file.
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.
1-67
1.12.2
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.
When you are sure that all the data appearing in the dialog boxes is correct, in the
SEGY 3D to Voxet dialog box, click OK or Apply.
1.12.3
Important By default the command saves only the link to the file you importthe
data is not copied into your project. You can request that the data be saved in your
project; see step 4.
1-68
Importing Data
To import a 2D SEG-Y
file as seismic lines
Select File > Import > Seismic Data > Seismic Lines > 2D SEG-Y as Seismic Lines
to open the Import 2D SEG-Y dialog box.
In the File name box, enter the path and file name of the 2D SEG-Y file that you
want to import.
In the Survey name box, type the name of the survey to associate with the seismic
lines.
A survey carries several seismic lines from a specific seismic acquisition. You group
seismic lines into a survey for easier manipulation.
User Guide
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.
1-69
To change the coordinate byte locations (index numbers) or the common depth point
location (CDP) that are read from the file, type them in the X byte location, Y byte
location, or CDP byte location boxes.
Note The X byte and Y byte coordinates represent the shot line anchor point of the vertical
trace as specified by its (X, Y) origin location.
If necessary, change the geometry data format used to represent floating numbers:
Integer
IBM Float
IEEE Float
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.
If you want to manually specify the maximum depth or time, select the specify
maxzt check box. If you do not select this check box, the converter computes the
value from the SEG-Y header.
If your SEG-Y file does not contain geometry information, select the Use
navigation data check box and go to step 10.
In the Navigation file box, enter the path and file name of the file that you
want to import.
Note The navigation file contains seismic line data that tells the converter how to read the
SEG-Y trace data. You need to specify which columns in the navigation file represent the
The navigation data files should be space delimited and formatted into columns. It should
contain the name of the seismic line, the shotpoint number, and the coordinates, as shown
in the following example:
bh34_112_14_11
bh34_112_14_11
bh34_112_14_11
bh34_112_14_11
bh34_112_14_11
1
2
3
4
5
451346
451304
451262
451220
451178
1390689
1390653
1390617
1390580
1390544
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.
1-70
Importing Data
Because the SEG-Y data is ordered by trace, which is rarely the same as a seismic
line, you need to specify the relationship between the trace number in the SEG-Y
file and the seismic line number in the navigation file:
In the first shot point box, type the seismic line number of the first trace in
the navigation file. The default is 0.
In the number of trace per sp box, type the number of traces per seismic
line (delta between two seismic lines). The default is 1.
If the seismic line number decreases with the trace number, select the sp
decrease with trace number check box.
11 If necessary, change the domain and the units used in the imported SEG-Y file by
selecting the Time or Depth option and by selecting the Specify units of selected
files check box, and selecting the units.
12 Click OK or Apply.
To improve performance, seismic lines are not displayed in the 3D Viewer when you
import them. To display them, select the imported seismic lines in the Objects browser. In
addition, the property is not loaded in memory until you display it and apply commands
on it.
1.12.4
Select File > Import > Seismic Data > SEP, 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.
1.12.5
Select File > Import > Seismic Data > Seismic Cubes > Norsar Depth Cube to
open the Import Norsar 2.1 Object into Gocad dialog box.
User Guide
1-71
1.12.6
In the Norsar project root box, enter the path and file name of the file you want to
import.
In the Norsar object box, enter the path and file name of the file you want to
import.
In the object type box, select the type of object being imported. The default is
Interface.
Click OK or Apply.
1.12.7
To import a SeisWorks
Colormap
Select File > Import > Seismic Data > Colormaps > SeisWorks, 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.
1-72
Importing Data
1.13
"Importing
"Importing
"Importing
"Importing
a
a
a
a
1.13.1
To import a Jason
trace file
Select File > Import > Velocity Data > Velocity Functions > Jason ASCII Traces,
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.
1.13.2
To import a Promax
file
Select File > Import > Velocity Data > Velocity Functions > Promax, 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.
User Guide
1-73
1.13.3
Select File > Import > Velocity Data > Velocity Functions > TDQ (.avf), 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.
1.13.4
Select File > Import > Velocity Data > Velf, 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.
1.13.5
1.13.6
1.13.7
1.13.8
1-74
Importing Data
1.13.9
User Guide
1-75
1.14
1.14.1
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
Well
Well
Well
Well
Well
Well
Well
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
"Importing
1-76
Importing Data
To import an Excel
spreadsheet as a Well
User Guide
Select File > Import > Well Data > Path and Logs > Excel to open the Import Well
from excel file dialog box.
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.
The default is to import only one sheet from the Excel file. Click all sheets if you
want to import more than one.
If you selected
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.
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.
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.
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.
1-77
If you want to import an additional property, select the import other properties
check box, and then do the following:
10 Click OK or Apply.
1-78
Importing Data
Select File > Import > Well Data > Path and Logs > Irap RMS to open the Import
Irap RMS as Wells dialog box.
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.
In the Null Value box, type the no data value. The default is -999.0.
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.
Click OK or Apply.
Based on data contained in the LAS file, the converter creates a Well object with surface
location, logs, picks, and deviation data, or it creates a Well object with incomplete
information (you can update the Well object at a later time.)
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.
Select File > Import > Well Data > Path and Logs > LAS to open the Import LAS
Data Files dialog box.
Click
to browse for and select the files you want to import, and then click Open.
1. The Log ASCII Standard (LAS) was first proposed in 1990 by the Canadian Well Logging Society to
facilitate exchange of digital well log data between logging service companies and clients. It has
since become an industry standard.
User Guide
1-79
Choose one of the following options for specifying well location information:
If the LAS file does not contain well location data (or you do not want to use the
well location data), click Input well location and then do one of the following:
If you do not want to specify the well location data, leave the default values
in the boxes for the X, Y, and Z coordinates.
To specify the well location, select the coordinates from the 3D Viewer.
Click
and then click (with the resulting crosshair) on the coordinate
locations in the 3D Viewer. The x-, y-, and z-coordinates of the points you
click appear automatically in the X, Y, and Z boxes.
To use the well location data that is specified in the LAS file, click Well location
in LAS file. Then instruct the converter to search for the location coordinates
within the LAS file you are importing by using keywords that you supply (the
default keywords are XCOORD, YCOORD, and ELEV).
To use a well location that is specified in a different external file, click Well
location in external file, click
to browse for the external file, and then
double-click the file name to enter it in the Well location file box.
To load deviation survey data, select the Deviation survey information is in the
LAS file(s) or in external files(s) check box. Another dialog box opens.
Or, if the file does not contain deviation data, skip to step 6.
Important If the LAS file contains deviation survey data and you do not select the
Deviation survey information is in the LAS file(s) or in external file(s) check
box, the converter loads the deviation data as properties and the well path will
appear as a straight line.
1-80
Importing Data
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.
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.
Specify how the converter should interpret the deviation data by clicking the
appropriate option:
User Guide
Click Close to close this dialog box and return to Import LAS Data File dialog box.
1-81
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.
If the z-axis value in the file you are importing differs from the default z-axis set
for your project, change the domain for this new object. To change the z-axis
value from depth to time, or time to depth click the appropriate option.
Note The converter automatically selects units based on the default z-axis setting (in the
New Project dialog box) chosen when the project was created.
To specify how to import the name of the well, choose one of the following options:
Select the Specify units of selected files check box, and then click the
appropriate area units and depth unit for deviation data.
Click OK or Apply.
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-82
Importing Data
Select File > Import > Well Data > Logs > LAS to open the Import Well Log from
LAS File dialog box.
Click
To specify the measured depth unit or how to import the name of the well, click
Options for the name of the well, and then do the following as necesary:
to browse for and select the files you want to import, and then click Open.
Click OK or Apply.
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.
User Guide
1-83
Select File > Import > Well Data > Path and Logs > RC2, 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 Temis3D
file as a Well
Select File > Import > Well Data > Path and Logs > Temis3D, 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.
1-84
Importing Data
To import a WITSML
file as a Well
Select File > Import > Well Data > Path and Logs > WITSML to open the Create
Well from WITSML File dialog box.
Click
to browse for the files, and then double-click the file name. The command
automatically enters the selected file names in the File name box.
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.
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.
Click OK or Apply.
1. WITSML is an acronym for Wellsite Information Transfer Standard Markup Language and is an
industry standard for transferring data.
User Guide
1-85
1.14.2
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
as a Well
Select File > Import > Well Data > Path > X Y Z file, 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.
1.14.3
1-86
Importing Data
1.14.4
For information about importing image logs, see "Importing Image Files" on page 1-43.
User Guide
1-87
1-88
Importing Data
Select File > Import > Well Data > Logs > ASCII File with Header to open the Add
Log From Ascii File dialog box.
In the Well box, enter the name of the existing Well object.
Click
to browse for the file you want to import, and then double-click the file
name. The command enters the selected file names in the File name box.
Clear the True z check box, if the data value in your file represents measured depth.
In the Property Interpolation Method box, select the method you want the
converter to use when estimating a value between two known values.
Click OK or Apply.
1.14.5
If you experience difficulty importing statuses that include spaces, add quotation marks
surrounding the text in your file.
You can also edit the well status (change the symbol) for an existing well. For information, see
Part IV: Foundation Modeling, "Setting the Well Status" on page 9-10.
For users running SKUA from the Paradigm Session Manager, the well status that you can set
with this command includes the same list of well symbols that you can assign from the
Paradigm Well Data Manager. For information about sharing well data with other Paradigm
applications or setting well status in an Epos project, see:
Part I: Getting Started, Chapter 4, "Sharing Data with Paradigm Applications."
Paradigm 2011 Help > Data Management and Import/Export > Well Data Manager >
Assigning Well Symbols.
Select File > Import > Well Data > Constants > Well Status Symbols to open the
Import Well Symbols dialog box.
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 converter enters the selected file
name in the File name box.
In the Well Name Column box, type the number for the column that includes the
well names (matching the names of existing wells in the project).
In the Symbol Name Column box, type the number for the column that includes the
symbol data.
In the Start at Line box, type the line number where you want the converter to start
reading the import file.
The command issues an error message if wells listed in the file are not present in the
project or a symbol listed in the file is an unrecognized type. (To see messages or errors,
select View > Terminal to access the session history.)
User Guide
1-89
1.14.6
To import well
completions from an
ECLIPSE file
You can also import completion data along with CMG? or ECLIPSE production data. For
information, see:
"Importing an ECLIPSE ASCII Grid File," page 1-46
"Importing a CMG Grid and Simulation Results," page 1-54
"Importing Well Production Data from an ECLIPSE Binary File," page 1-101
You can import completion data as well logs by using the column-based file wizard for
importing well paths and logs (File > Import > Well Data > Paths and Logs > Column-Based
File). For more information, see "Common Process for Importing a Column-Based File" on
page 1-8.
Select File > Import > Well Data > Completions > ECLIPSE Data File to open the
Import ECLIPSE Well Completions dialog box.
In the Stratigraphic grid box, enter the name of the SGrid object associated with
the well completion data.
In the Scenario name box, enter a unique name for the simulation scenario.
The scenario name is useful if you plan to use the data in the Reservoir Simulation
Link Workflow or the Production Data Analysis Workflow.
Indicate whether you also want to create properties in the associated grid to store the
completion data by selecting or clearing the Create completion properties check
box. (Initially preselected.)
If selected, the command adds the completion data to both the wells and the grid.
If cleared, the command adds the completion data only to the wells.
After you import completions, you can find them in an object browser.
1-90
Importing Data
1.14.7
"Importing
page 1-91
"Importing
"Importing
"Importing
Well Production Data from a General Format User File or VOL File,"
Well Production Data from an ECLIPSE Column-Based File," page 1-97
Well Production Data from an ECLIPSE Binary File," page 1-101
Well Production Data from an ECLIPSE RSM File," page 1-102
For information about displaying and working with production data after you import it,
see Part IV: Foundation Modeling, "Working with Engineering and Production Data" on
page 9-29.
This wizard includes many settings that are common to other column-based import
wizards. This topic describes only the steps that are specific to importing production data.
For information about how to configure the common settings, see "Common Process for
Importing a Column-Based File" on page 1-8.
Tip For production data, specifying a no-data value of -99999 prevents null data from appearing as
zeros in production plots. For information about how to specify a no-data value in the wizard, see
step 6 in "To specify the column assignment for a column-based file" on page 1-12.
"To
"To
"To
"To
"To
Select File > Import > Well Data > Production Data > General Format User File
to open the Column as Production Data - General Format wizard.
access the import wizard for column-based production data," page 1-91
specify the production data type and scenario," page 1-92
specify the date format," page 1-93
specify the phase units," page 1-95
specify line and column assignments," page 1-96
1. VOL is an output format for production data from Schlumbergers Schedule software.
User Guide
1-91
To specify the
production data type
and scenario
After you access the Column as Production Data importing wizard and complete the
common settings on the first pages (see "Common Process for Importing a Column-Based
File" on page 1-8), specify the type of production data that you are importing and the
scenario as follows:
1
Ensure that the file you want to configure is selected in the Current file box.
Specify whether you are importing historical data by selecting or clearing the
Historical production data check box, and then do the following as necessary:
If you specified historical data, you do not need to define a scenario for this data,
because the command imports historical data into the Project (root) scenario.
If the production data is not historical, specify the scenario by doing one of the
following:
To use the file name to identify the scenario, click Use filename.
To provide a name, click Select or type it, and then enter a unique scenario
name in the box.
To specify a line in the file that identifies the scenario, click Select line, and
then type the line number in the box, or click
preview pane.
1-92
Importing Data
The scenario name is useful, for example, to help you differentiate between
multiple sets of production data.
3
Click Next.
For the question What is the type of your dates?, click either:
User Guide
1-93
Depending on the date format selected, specify additional information about the data
as necessary:
Setting
Description
Date format
Click either One column (if the date or time is given in a single column) or
Multiple columns (if the date or time is given in multiple columns), and then
select the date format for the time or the start date.
If you select multiple columns, later in the wizard, on the Line and Column
Assignment page, you can specify what each column represents.
Start date
1-94
Importing Data
Specify the type of production data, unit system, and object type as follows:
Setting
Description
Data type
Units system
Producing object
The data includes well data, data from a group of wells, or the entire field.
If you want to import production data only for existing wells, ignoring any additional
production data for other wells, select the Load only on existing objects check
box.
Click Next.
User Guide
On the Selection of the phase units page, the units for each value are preselected
based on the Units system selected on the prevous page in the wizard. Change the
units for any production value as necessary (following the instructions in the wizard),
and then click Next.
1-95
On the Line and Column Assignment page, assign each type of data to the
appropriate column in the file (following the instructions in the wizard), and clear the
check box for any data that is not included in the file.
Notes
1-96
Importing Data
If you indicated that date or time values are given in multiple columns, this page has
additional options for indicating which columns represent each part of the date or time
value (For example, Day column, Month column, and Year column).
If you are importing a VOL file, Well or Group name column is not available (appears
dimmed). In VOL files, well names are on rows by themselves (not in columns), and the
converter finds the well names automatically.
The Days produced column should specify the number of days of actual well production
during the specified period. If you indicate that you want to compute missing production
data (see step 2), this number affects the daily production rate calculation. For example, if
production is not a full month, you need to specify the number of actual producing days.
If you want to calculate any missing production data, select the Compute missing
production data check box.
Depending on the type of production data (cumulative volumes, production rates, or
interval volumes), the command can calculate:
When you finish specify the column assignments, complete the steps in "To complete
the importing process" on page 1-14.
You can easily import ASCII historical data by using the column-based importing wizard as
follows:
Identify the columns that contain standard ECLIPSE data keywords followed by "H."
For example, historical field oil-production data becomes FOPRH; similarly, historical
well water-cut data becomes WWCTH. For a list of the most common ECLIPSE
keywords, see Part X: Reservoir Production and Simulation, "Primary ECLIPSE
FrontSim production data" on page 5-13.
Identify the units in the historical data by using these unit identifiers:
The following is an excerpt from a comma-separated values (CSV) file containing historical
field data:
DATE,FPRH,FWPRH,FGPRH,FOPRH
,barsa,sm^3/d,sm^3/d,sm^3/d
,FIELD,FIELD,FIELD,FIELD
1/1/1988,397.8,0.0000,0.0,0.00
1/1/1989,307.6,0.0000,1356750.0,9000.00
1/1/1990,233.7,0.0000,1217807.5,9000.00
4/1/1990,221.9,0.0000,1183632.1,9000.00
User Guide
1-97
In this example, the first line identifies the ECLIPSE data types with an "H" to indicate
historical data. The second line identifies the units for each data type, and the third line
indicates the object, FIELD. The data is delimited by commas, with the date in the first
column followed by pressure, water production rate, gas production rate, and oil
production rate.
Select File > Import > Well Data > Production Data > ECLIPSE User File to open
the Column as Production Data - ECLIPSE format wizard.
After you access the Column as Production Data importing wizard and complete the
common settings on the first pages (see "Common Process for Importing a Column-Based
File" on page 1-8), specify the type of production data that you are importing and the
date format as follows:
1
Ensure that the file you want to configure is selected in the Current file box.
For the question What is the type of your production data?, click one of the
options: Historical or ECLIPSE name convention.
Note If the production data names have an "H" at the end of the string (FWPTH, for example)
indicating historical data, you can select either option.
1-98
Importing Data
For the question What is the format of your dates?, click either:
Depending on the date format, specify additional information about the data as
necessary:
Setting
Description
Date format
Start date
To specify the
production scenario
In the Column as Production Data import wizard, specify the scenario as follows:
Note This page appears only if the file does not contain historical data. If the file contains historical
data, the command automatically imports the data into the Project (root) scenario. You cannot
specify a production scenario for historical data.
User Guide
Click Next.
Ensure that the file that you want to configure is selected in the Current file box.
1-99
To use the file name to identify the scenario, click Use filename.
To provide a name, click Select or type it, and then enter a unique scenario
name in the box.
To specify a line in the file that identifies the scenario, click Select line, and then
type the line number in the box, or click
pane.
The scenario name is useful, for example, to help you differentiate between multiple
sets of production data.
3
Completing the
importing process
The scenario name is useful, for example, to help you differentiate between multiple
sets of production data.Click Next.
For more information about configuring the remaining settings in the wizard and how to
complete the importing process, see "Common Process for Importing a Column-Based
File" on page 1-8.
To import Production
data for an existing
Well
Select File > Import > Well Data > Production Data > ECLIPSE Binary File to open
the Import ECLIPSE Binary Production Data dialog box.
In the File name box, type the full path and file name or click
file.
If you want to associate the well production data with simulation results that were
previously imported from ECLIPSE as an SGrid object, select the Use grid check box,
and then enter the grid in the Stratigraphic grid box.
If the wells associated with the production data do not already exist, with this option
selected, the command creates the wells by approximating the well paths from the
grid data and associates the new wells and production data with the selected grid.
If cleared, the command creates the wells without well paths and without associating
them with any existing data.
4
To specify advanced importing options, click Advanced, and then do the following as
necessary.
User Guide
Import Completions. Imports any completion data included in the file along
with the production data.
If cleared, the command ignores any completion data in the file.
The command imports the data, creating Well objects (if necessary) and adding the
production data and completions (if any) to the wells. You can find the new production
data and any completions in the Objects browser by expanding the productions or
completions category for the wells.
To import production
data from an ECLIPSE
RSM file
Select File > Import > Well Data > Production Data > ECLIPSE RSM file to open
the Import Production Data from ECLIPSE RSM File dialog box.
In the File name box, type the file names. Or, click
and then double-click the selected files.
In the Scenario name box, select an existing scenario or type a name a new
production scenario.
The scenario name is useful if you plan to use the data in the Production Data
Analysis Workflow. For information about the workflow, see Part X: Reservoir
Production and Simulation, Chapter 5, "Analyzing Production Data."
The command automatically checks for existing well properties and does not
overwrite them. If you want to overwrite properties, clear the Check existing
properties check box.
If you want to calculate any missing production data, select the Compute missing
production data check box.
Depending on the type of production data (cumulative production volumes or
production rates), the command can calculate:
The command imports the data, creating wells (if necessary) and adding the production
data and properties (if any) to the wells. You can find the new production data and any
new well properties in the Objects browser by expanding the productions, properties,
or property groups category for the wells.
Note If the wells do not already exist, the command creates the wells without well paths.
User Guide
1.15
1.15.1
1.15.2
To import a Geosec
file as a Curve
Select File > Import > CrossSections > Geosec, 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.
1.15.3
To import a Locace
file as a Curve
Select File > Import > CrossSections > Locace, 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.
2
Exporting Data
In this chapter
Overview
Paradigm SKUA and Paradigm GOCAD includes several converters that you can
use to export objects and viewer images to numerous file formats.
You can find the exporting commands from the File menu on the Export submenu. This
submenu is organized first by the object types that you can export and then by file
formats.
These topics explain how to use the data converters to export modeling objects.
You will notice that some file format types are listed more than once on the Export
menus. When SKUA and GOCAD provide support for exporting multiple objects types to
the same file format type, the export option appears under each object type.
Paradigm adds support for new formats based on customer needs. To inquire about new
options, contact us at www.pdgm.com/support.
2-1
2.1
Converters
This table identifies the software programs to which you can export, the object types that
you can export to each software program, and the common extension for the exported
file (where applicable).
Table 21 Exportable
objects
PointsSet
Custom ASCII
.dat, .txt
DXF (AutoCAD)
.dxf
FastEdit
Excel
.xls
Isatis
Curve
Custom ASCII
.dat, .txt
DXF
.dxf
.dat
IRAP
Medica
.fau
.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
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
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
SGrid + data
.xls
CGM
Picture
VRML
.vrml
Isatis
(Continued 2 of 2)
User Guide
2.1 Converters
2-3
2.2
2-4
Exporting Data
"Exporting
"Exporting
"Exporting
"Exporting
"Exporting
"Exporting
"Exporting
2.2.1
To export an object to
a custom ASCII file
Select File > Export > Object Type (PointsSet, Curve, or Surface) > Custom ASCII
to open the Export to Generic ASCII File dialog box.
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.
To export each object in a separate file, select the Output each object in a separate
file check box.
User Guide
2-5
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.
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.
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.
Other existing properties. You can select any additional properties existing on
the object.
Notes
You can add or remove fields by clicking Add, Insert, and Remove. You can arrange the
sequence by clicking Up and Down.
The options available here depend on what object you choose above in the Object box.
Each field contains the name, part ID, and the union of all the properties that exist on the
selected objects.
10 Click OK or Apply.
2-6
Exporting Data
2.2.2
To export an object to
a DFX file
Select File > Export > Object Type (PointsSet, Curve, or Surface) > DFX to open
the Export to DXF format dialog box.
In the File name 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.
2.2.3
Click OK or Apply.
PointsSet
Surface
Voxet
Well
Channel
Curve
2D-Grid
SGrid
Solid
User Guide
2-7
To export object
properties to Excel
Select File > Export > Object Type (PointsSet, Curve, Surface, 2D-Grid, Voxet,
SGrid, or Well) > Export Properties to Excel to open the Export Properties to Excel
dialog box.
Note If you are exporting a well, then you should click Logs to Excel, not Export Properties
to Excel.
In the Properties box, enter the properties to export. You can export any number of
properties.
In the Regions box, enter the regions from which the properties will be exported.
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.
Click OK or Apply.
After you complete the Export Properties to Excel dialog box, the converter automatically
launches an Excel spreadsheet, which populates with the exported data.
2-8
Exporting Data
Notes
To compute the
statistics in Excel
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.
In the Nb class box, select a numeric value to set the number of bins that display on
a histogram.
User Guide
In the Select property box, click the property to use to compute the statistics.
Click Compute Statistics. Excel computes a histogram that presents the property
distribution.
2-9
2D cross plots
A 2D cross-plot provides:
2-10
Exporting Data
To compute a cross
plot in Excel
In the Select source box, click the object source that contains the two properties to
analyze.
Note If you are exporting several objects, you need to specify which object you want to
analyze. The source name is composed by the name of the object, a space, and then region.
User Guide
In the Select property X box, select the property to plot as the X-axis.
In the Select property Y box, select the property to plot as the Y-axis.
2-11
2.2.4
Click Compute Cross Plot. Excel computes a 2D cross-plot that presents the
correlation between the properties.
Connection with
Isatis
SKUA or GOCAD connects to the Isatis database by using the GTXserver, a program
provided by Geovariances. This program is installed with Isatis. If you have Isatis installed
on the same machine as SKUA or GOCAD, there is no need to separately download and
install them.
However, if Isatis is not installed, you can download GTXserver, free of charge, directly
from the Geovariances Web site (www.geovariances.com). This program is available for
several platforms.
To access the database, you need to first open a connection with the database and then
use the GTXserver for loading or saving data. The connection closes once the load or save
is done.
2-12
Exporting Data
Typically, a new GTXserver runs from a location on your machine that is designated during
the Isatis installation. Therefore, the default option in the Advanced parameters is Run
GTXserver and the Force GTXserver check box is cleared.
Your particular situation may require you to set different parameters. For example:
If you do not have Isatis installed, but you have an Isatis database available, you can
extract the GTXserver package from Geovariances Web site, select the Force
GTXserver check box, and then type the path location of the executable file in the
GTXserver box.
If you need to access a database stored on another machine, you may need to run
GTXserver on that machine. You would click the Use already running GTX server
and then type the entries for the Host Name and Port boxes.
If the Run GTXserver option is not working, the reason may be that it cannot be
found due to a registry problem or an environment variable. To fix this, you can select
the Force GTXserver check box and reset the location, or click the Use already
running GTX server to run GTXserver manually.
The default values for the advanced parameters are set when you initially use the Export
to Isatis dialog box. The parameters remain set, unless you change them. This prevents
you from having to re-enter the same parameters multiple times.
Architecture of the
Isatis database
In Isatis, the GTX_INIT directory contains all of the available studies (this directory is also
known as $HOME/.isatis for Linux and %APP_DATA%\Geovariances\Isatis for Windows).
You can reference the location of this directory from the Isatis Help menu by clicking
About.
The structure of each study is:
Isatis objects
Isatis contains a set of files corresponding to SKUA and GOCAD object types. This table
shows the relationship between SKUA and GOCAD objects and the corresponding Isatis
file types.
SKUA and GOCAD object
User Guide
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
2-13
This table shows the relationship between SKUA and GOCAD properties and the
corresponding Isatis variables.
To export an object to
an Isatis file
Isatis variable
Region flag
Float variable
Multidimensional variable
Macro variable
Select File > Export > Object Type (PointsSet, Curve, Surface, 2D-Grid, Voxet,
SGrid, or Well) > Export Isatis to open the Export VSet to Isatis dialog box.
To set the advanced connect parameters, click Advanced to open the Advanced
Connect Parameters dialog box.
Note step 2 and step 3 are necessary only if you need to edit these settings. Typically, you will
not need to change the preselected settings.
2-14
Exporting Data
Do the following:
a
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.
If you clicked the Run GTX server option, and selected the Force GTXserver
check box, enter the GTXServer path in the GTXServer path box.
Notes
This path corresponds to the full GTXserver executable path. Normally, this path is in
the bin directory of the Isatis installation path.
You only have to force the GTXserver executable when you do not have Isatis
installed. If Isatis is installed, GTXserver is automatically installed under Windows.
For Linux users, you may need to define the GTX_HOME environment variable and
then restart SKUA or GOCAD.
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.
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.
User Guide
In the DATA path box, enter the full data path. This path corresponds to the
Isatis database directory.
2-15
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.
In the Directory box, select the directory of the selected study where you want to
save the object.
In the Gocad Object box, enter the object name to be exported to Isatis.
To attach faults to the Isatis file, select the Store Faults check box.
10 In the Float variables box, enter the float variables to export. Variables are the
equivalent of SKUA and GOCAD properties.
11 In the Regions box, enter the object regions to export to Isatis.
12 Click OK or Apply.
2.2.5
To export an object to
a Medica file
Select File > Export > Object Type (Curve or 2D-Grid) > Medica to open the Export
2D-Grid to Medica dialog box.
Note The image below is an example of the Export 2D-Grid to Medica dialog box. The Export
Fault Polygons to Medica (used for exporting curves) is virtually identical (the only difference, aside
from the name of the dialog box, is the name of the object box).
For a 2D-Grid, enter the name of the grid in the 2D-Grid object box.
For curves, enter the name of the Curve objects in the Curves box.
In the File name 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.
Click OK or Apply.
1. Medica is a mapping product embedded in the Temis3D program developed by IFP, and sold by
Beicip. For more information, visit www.beicip.com.
2-16
Exporting Data
2.2.6
To export an object to
an AVF file
Select File > Export > Object Type (Voxet or SGrid) > AVF to open the Export 3D
Grid Property to AVF dialog box.
In the Grid Object box, select the objects (Voxet or SGrid) to export.
In the Property box, select the property name that represents the velocity.
In the File name 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.
In the Function Type box, select the type of velocity function to export:
Meters
Feet
Click OK or Apply.
Caution If the object you are exporting is large, the export will take longer and the
exported file will require increased disk space.
User Guide
2-17
2.2.7
To export an object to
a Velf file
2-18
Exporting Data
Select File > Export > Object Type (Voxet or SGrid) > Velf to open the Export 3D
Grid Property to Velf dialog box.
In the Grid Object box, enter the objects (Voxet or SGrid) to export.
In the Property box, select the property name that represents the velocity.
In the File name 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.
Click OK or Apply.
2.3
To export a PointsSet
to a FastEdit file
ASCII
DXF
Excel
Isatis
Select File > Export > PointsSet > FastEdit to open the Export PointsSet to FastEdit
Scattered Data Format dialog box.
In the File name 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.
Click OK or Apply.
User Guide
2-19
2.4
"Exporting
"Exporting
"Exporting
"Exporting
"Exporting
a
a
a
a
a
Curve
Curve
Curve
Curve
Curve
to
to
to
to
to
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
curve data to the programs in this table.
2.4.1
ASCII
DXF
Medica
Excel
Isatis
What is a FastEdit
polygon file?
To export Curves to a
FastEdit polygon file
2-20
Exporting Data
A FastEdit fault polygon file is a simple ASCII file containing a series of X and Y data
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.
1
Select File > Export > Curve > FastEdit to open the Export Curve to FastEdit Fault
Polygon dialog box.
In the File name 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.
2.4.2
To export a Curve to
an IRAP file
2.4.3
Select File > Export > Curve > IRAP to open the Export Curve to Irap Classic Format
dialog box.
In the File name 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.
To export a Curve to a
SeisWorks Fault Sticks
file
Select File > Export > Curve > SeisWorks Fault Sticks to open the Export Fault
polygons to SeisWorks dialog box.
In the Curve Fault Sticks box, enter the Curve objects that you want to export to a
SeisWorks Fault Sticks file.
In the File name 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.
In the Interpreter Name box, type the interpreter name. This is the user name.
User Guide
2-21
2.4.4
Z-Map headers
Curve data
To export a Curve to a
ZMAP Faults file
The Z-Map header is set off by an @ symbol at the beginning and the end. The header
should contain the keyword "FAULT" or "CARTOGRAPHIC." It can also contain other
information, such as the name of the curve you are importing. However, the converter
ignores most of this data.
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.)
Select File > Export > Curve > ZMAP Faults to open the Export Fault polygons to
Z-MAP dialog box.
In the File name 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.
2-22
Exporting Data
2.4.5
Curve data
To export a Curve to a
ZMAP Contours file
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.)
Select File > Export > Curve > ZMAP Contours to open the Export Curves as
contours to Z-MAP dialog box.
In the File name 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.
User Guide
2-23
2.5
"Exporting
"Exporting
"Exporting
"Exporting
a
a
a
a
Surface
Surface
Surface
Surface
to
to
to
to
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
surface data to the programs in this table.
2.5.1
ASCII
DXF
Excel
To export a Surface to
a CUBIT Facet file
Select File > Export > Surface > CUBIT Facet to open the Export Surface To CUBIT
Facet ASCII file dialog box.
In the File name 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.
2-24
Exporting Data
2.5.2
To export a Surface to
a FastEdit file
Select File > Export > Surface > FastEdit to open the Export Surface to FastEdit
Contours dialog box.
In the Surface box, enter the Surface objects, one by one, to export.
In the Step box, type a numeric value to specify the interval spacing for the contour
lines created in the FastEdit file.
In the Alignment box, type a numeric value to specify the reference value from
which the contour lines are computed. By default, this value is 0.
Note This parameter corresponds to the Contour shift setting in the Style dialog box.
In the File name 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.
User Guide
2-25
2.5.3
To export a Surface to
an IRAP file
Select File > Export > Surface > IRAP to open the Export Surface To IRMS as Triangle
Surface file dialog box.
In the Files prefix box, enter the path and file name of the file to which you are
exporting the object.
The converter either creates new files or overwrites existing ones. It creates one file for
each surface. The name of the exported file surface is the prefix defined in the dialog box
concatenated with the surface name.
2.5.4
To export a Surface to
a GMI WellCheck
MohrFracs file
Select File > Export > Surface > GMI WellCheck MohrFracs to open the Export
Surfaces to MohrFracs dialog box.
2-26
Exporting Data
User Guide
In the File name prefix 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.
2-27
2.6
"Exporting
"Exporting
"Exporting
"Exporting
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
2D grid data to the programs in this table.
2.6.1
Medica
Excel
Isatis
To export a 2D-Grid
object to a CPS3 file
Select File > Export > 2D-Grid > CPS3 to open the Export 2D-Grid Geometry or
Properties to CPS3 dialog box.
In the File name 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.
2-28
Exporting Data
2.6.2
To export a 2D-Grid
object to a FastEdit
file
2.6.3
Select File > Export > 2D-Grid > FastEdit to open the Export 2D-Grid Geometry or
Properties to FastEdit dialog box.
In the Property box, select the property to export along with the 2D-Grid object
geometric data.
In the File name 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.
To export a 2D-Grid to
an IRAP file
Select File > Export > 2D-Grid > IRAP to open the Export 2D-Grid Geometry or
Properties to Irap RMS dialog box.
In the Property box, enter the property to export with the 2D-Grid geometric data.
In the File name 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.
User Guide
2-29
2.6.4
To export a 2D-Grid to
a Z-Map file
Select File > Export > 2D-Grid > Z-MAP to open the Export 2D-Geometry or
Properties to Z-MAP dialog box.
In the Property box, enter the property carried by the 2D-Grid to export.
In the File name box, enter the path and file name of the file to which you are
exporting the object. The converter with either create a new file or overwrite an
existing one.
2-30
Exporting Data
2.7
"Exporting
"Exporting
"Exporting
"Exporting
a
a
a
a
Voxet
Voxet
Voxet
Voxet
to
to
to
to
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
Voxet data to the programs in this table:
2.7.1
AVF
Velf
Excel
Isatis
To export a Voxet to a
DDS file
Select File > Export > Voxet > DDS to open the Export Voxet to DDS dialog box.
In the Property box, enter the property carried by the voxet to export.
In the File name box, enter the path and file name of the file to which you are
exporting the object. The converter with either create a new file or overwrite an
existing one.
User Guide
2-31
2.7.2
To export a voxet to a
SEGY file
Select File > Export > Voxet > SEGY to open the Export Voxet to SEG-Y dialog box.
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.
In the Axis Name boxes, enter the mapping between the Voxet and the crossline,
inline axes, and vertical axis. For example, indicate if U is time, crossline, or inline, and
then do the same for V and W.
In the Start and End boxes, verify the line numbers that correspond to the first and
last inline section, crossline section, and vertical section.
To specify where in the SEGY file to store the line, trace, X, and Y information, enter
the byte location (index number) for each value.
Note X and Y represent the coordinates of the location of the vertical trace, Line represents
inline in SEGY, and Trace represents crossline in SEGY.
To format the numbers in the IEEE format, clear the Save in IBM format check box.
1. For information about SEG-Y, visit the Society of Exploration Physicists at www.seg.org.
2-32
Exporting Data
2.7.3
To export a Voxet to
an SEP file
Select File > Export > Voxet > SEP to open the Export Voxet to SEP dialog box.
In the Property box, enter the property carried by the voxet to export.
In the File name 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.
In the Time axis, Crossline axis, and Inline axis boxes, enter U, V, or W.
Note You need to set the mapping between the Voxet and the time, crossline, and
inline axes. Indicate if U is time, crossline, or inline, and then do the same for V and
W.
User Guide
2-33
2.7.4
To export a voxet to a
VoxelGeo file
Select File > Export > Voxet > VoxelGeo to open the Export Voxet To VoxelGeo
dialog box.
In the Property box, select the property to export along with the Voxet object
geometric data.
In the File name 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.
To export the property as an 8-bit property, select the Export in 8-bit check box.
Note If you clear this check box, the converter exports the property as a 32-bit property.
2-34
Exporting Data
2.8
To export seismic
lines to a 2D SEG-Y
file
Select File > Export > Seismic Lines > SEGY to open the Export Seismic Line to 2D
SEG-Y dialog box.
In the Seismic Line Lines box, enter the seismic lines to export.
In the Property box, select the property to export along with the seismic line
geometric data.
In the File name 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.
Note If you select several seismic lines to export, the program saves them as multiple files; it
names each file by appending the shot line name to the file name that you provide
( filename_linename.sgy).
User Guide
To format the numbers in the IEEE format, clear the Save in IBM format check box.
2-35
2.9
Important Exporting and reimporting an SGrid created by using the SKUA Flow
Simulation Grid Workflow breaks the link between the SGrid and the workflow,
removing the ability to use important functionality with the SGrid (for example,
property upscaling from a Geologic Grid object).
For more information, see:
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:
2-36
Exporting Data
AVF
Velf
Excel
Isatis
2.9.1
2 (max, min)
3 (max, max)
Original origin: point 1 (min, min)
Target origin: point 2 (max, min)
1 (min, min)
4 (min, max)
If the origin of the SGrid in this figure were at point 1 in the bottom-left corner, to change
the origin to point 2 in the upper-left corner, you would specify the new origin at
I = maximum and J = minimum (zero).
User Guide
2-37
2.9.2
For exported files that contain well path data, the converter uses the ECLIPSE format, which
CMG can read.
If you export an SGrid that was created by using the SKUA Flow Simulation Grid Workflow and
the SGrid includes mixed or reverse faults, CMG might not be able to read all the connections
between the cells. This capability requires the CMG keyword SCONNECT, which the converter
does not currently export.
For information about how to specify data in the CMG converter, see:
"To export grid data from an SGrid to a CMG file," page 2-39
"To export well data from an SGrid to a CMG file," page 2-41
"To set the advanced options for exporting to a CMG file," page 2-42
For information about exporting local grid refinement (LGR) data from an SGrid to a CMG
ASCII file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on page 2-59.
2-38
Exporting Data
Select File > Export > SGrid > CMG to open the Export SGrid to CMG File dialog
box.
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 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).
User Guide
If you want to change the units to express the grid geometry, click Feet. Otherwise,
the grid geometry is expressed in meters in the file.
2-39
To generate a grid property file that does not include geometric information, clear the
Export geometry check box.
To specify the CMG keyword for each of the properties that you want to export, do
either of the following as necessary:
For a property that has an equivalent CMG keyword in the list, select the name of
the property in the Gocad Property box.
For a list of the CMG keywords (Flow Simulator Keyword column) that
correspond to SKUA or GOCAD properties, see Table 23 on page 2-40.
For properties that correspond to custom CMG keywords, add them by using the
blank row at the bottom of the list. You also need to import the corresponding
CMG keyword.
The converter automatically adds an empty row at the end so that you can add
multiple keywords.
2-40
CMG keyword
CMG keyword
POR
Porosity.
TRANSLI
PERMI
TRANSLJ
PERMJ
TRANSLK
PERMK
S0
Oil saturation.
Initial water saturations.
NETGROSS
SW
TRANSI
RTYPE
TRANSJ
PTYPE
TRANSK
NULL
Null blocks/cells.
Exporting Data
User Guide
Select File > Export > SGrid > CMG to open the Export SGrid to CMG File dialog
box.
From the Well Data tab, select the Export Well Data check box to enable the
options for exporting well data.
To select the wells to export, enter the well names in the Wells box.
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).
In the Well completion file box, enter the full path and file name of the file where
you want to save any exported well completion data.
2-41
Select File > Export > SGrid > CMG to open the Export SGrid to CMG File dialog
box.
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.
If you want to change the orientation of the grid relative to the SGrid, on the
Advanced tab, click one of the options for the Areal Origin of Cells and the
Vertical Origin of Cells.
Note CMG requires that the grid origin is in the upper-left corner.
For more information, see "About the Grid Origin" on page 2-37.
2-42
Exporting Data
If you want to restore the preselected settings for the areal and vertical origin, click
Restore Defaults.
To reverse the I- and J-axes in the output file, select the Switch I and J axis check
box.
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.
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.)
To exclude the inactive cells when writing out the NULL keyword (NULL: Null cells),
clear the Include dead cells for NULL keyword check box.
2.9.3
Create a single file containing both geometric and property information, or create
two or more separate geometry and property files.
Create files containing well connection and completion data for any Well objects
intersecting the grid.
Export fault information, if the grid is a SKUA flow simulation grid created with the
SKUA Flow Simulation Grid Workflow.
You can choose to define faults by using nonneighbor connections (NNCs) or the
MULTNUM keyword. If you choose these methods to define faults, you need to
compute the NNCs or the MULTNUM keyword values before you export the grid. For
information, see Part VIII: 3D Grid Building, "Using NNCs or the MULTNUM Keyword
to Define Faults" on page 2-132.
All you need to do to quickly export grid geometry is to select the grid that you want to
export and specify the path name to save the file. The remaining items are optional. You
only need to enter information for the specific types of data that you want to export.
For more information, see:
For information about exporting local grid refinement (LGR) data from an SGrid to an
ECLIPSE ASCII file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on
page 2-59.
ECLIPSE keywords
Because ECLIPSE requires keywords to define properties, you need to specify the mapping
between the ECLIPSE keyword and the SKUA or GOCAD properties that you want to
export. For information about how to specify the keywords, see step 7 on page 2-45.
User Guide
2-43
2-44
Exporting Data
Select File > Export > SGrid > ECLIPSE > ASCII to open the Export SGrid to ECL File
dialog box.
In the Reservoir Grid box, enter the name of the SGrid that you want to export.
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.
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.
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.
If you want to change the units of the grid in the exported file, click Feet. Otherwise
the grid units will be meters.
To generate an ASCII property file that contains no geometric information, clear the
Export geometry check box.
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
PORO
Porosity
PERMX
PERMY
PERMZ
NTG
ACTNUM
Active cell
PORV
MULTX
MULTY
MULTZ
MULTNUM
SGAS
SWAT
SWL
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.
User Guide
2-45
Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
click the Well Data tab.
Select the Export Well Data check box to enable the exporting options.
In the Wells box, enter the names of the wells that you want to export.
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).
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).
To limit the export to only the perforated intervals, select the well property in the
Perforation Log list.
Note You need a log that indicates the perforation of the reservoir (and the log should be
equal to zero when not perforated).
2-46
Exporting Data
Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
click the Fault Data tab.
Select the Export Fault Data check box to enable the exporting options.
To export the fault data in a separate .FAULTS file, clear the Include it with Grid
Data Output check box.
If you are exporting faults for a SKUA flow simulation grid, the command generates
the following additional files:
.NNC file. Contains the indexes of the nonneighbor cells (NNCs) and the
transmissibility values. For more information, see Part VIII: 3D Grid Building,
"Using NNCs or the MULTNUM Keyword to Define Faults" on page 2-132.
.EDITNNC file. Contains the indexes of the nonneighbor cells and the
transmissibility multiplier values. For more information, see Part VIII: 3D Grid
Building, "Computing the MULTNUM Keyword to Describe Faults" on
page 2-133.
To view a sample file that shows the content of these files, see Figure 23 on
page 2-47.
User Guide
2-47
Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
click the Region Data tab.
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.
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.
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
EQLNUM
FIPNUM
PVTNUM
SATNUM
Note If your SGrid has any properties that are not listed in this dialog box, add them by using
the blank rows at the bottom of the list. You need to know the name of the corresponding
ECLIPSE keyword to do this.
2-48
Exporting Data
Select File > Export > SGrid > ECLIPSE > ASCII to open the dialog box, and then
click the Advanced tab.
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.
To specify a local coordinate system for the grid (that is defined by the bottom left of
the SGrid cage), do the following:
a
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.
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.
User Guide
2-49
To change the origin of the ECLIPSE grid relative to the SGrid, click one of the options
for the Areal Origin of Cells and for the Vertical Origin of Cells.
Note For information, see "About the Grid Origin" on page 2-37.
If you want to restore the preselected settings for the areal and vertical origin, click
Restore Defaults.
To reverse the I- and J-axes in the output file, select the Switch I and J axis check
box.
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.
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.)
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.
2-50
Exporting Data
Include dead cells for ACTNUM keyword. Indicates which cells are inactive in
the output property when writing out the ACTNUM keyword (ACTNUM: Active
cells).
Keep GOCAD no-data value. Exports null values that are compatible with SKUA
and GOCAD rather than translating them to ECLIPSE-compatible null values.
2.9.4
To export an SGrid to
an ECLIPSE binary file
Select File > Export > SGrid > ECLIPSE > Binary to open the Export SGrid to
ECLIPSE Binary dialog box.
User Guide
2-51
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.
In the Origin Relative to SGrid area, select min or max as the coordinate of the
grid origin for the X, Y, and Z boxes.
Note For information to help you decide which option to choose, see "About the Grid Origin"
on page 2-37.
To switch the orientation of U for V, select the Switch U and V check box.
To indicate the number that the converter uses to multiply the X and Y coordinates of
the SGrid, type a numeric value in the Convert areal by a factor of box.
Note Use this option when you want to transform the SKUA or GOCAD coordinates in feet
into ECLIPSE coordinates in meters and vice versa.
To indicate the number that the converter uses to multiply the Z coordinate of the
SGrid, type a numeric value in the Convert vertically by a factor of box.
Note Use this option when you want to transform SKUA or GOCAD coordinates in feet into
ECLIPSE coordinates in meters and vice versa.
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
keyword
ECLIPSE
keyword
PORO
Porosity
FIPNUM
PERMX
PVTNUM
PERMY
SATNUM
PERMZ
SGAS
NTG
SWAT
ACTNUM
Active cells
SWL
MULTX
TOPS
MULTY
DX
MULTZ
DY
PORV
DZ
EQLNUM
DZNET
Net thicknesses
11 Click OK or Apply.
2-52
Exporting Data
2.9.5
Export tips
Ensure that all horizon and fault surfaces used to construct the SGrid are present in the
project. If you constructed the SGrid using the SKUA Flow Simulation Grid Workflow or
the GOCAD 3D Reservoir Grid Building Workflow, most of the information needed by the
converter is automatically provided.
For information about creating SGrids with:
SKUA Flow Simulation Grid Workflow, see Part VIII: 3D Grid Building, Chapter 3,
"Building a Flow Simulation Grid in SKUA."
GOCAD 3D Reservoir Grid Building Workflow, see Part VIII: 3D Grid Building,
Chapter 6, "Building a 3D Reservoir Grid in GOCAD."
Each of the SGrid FaceSets links to a set of grid faces attached to a fault of the same
name. If the SGrid has no FaceSets, or if you have not assigned the FaceSets to specific
faults, the converter only exports the grid, not the fault surfaces.
Before exporting an SGrid to RESCUE, verify that all the fault surfaces are loaded into the
project and that all the FaceSets are assigned to faults. You can do this by selecting the
SGrid in the Style dialog box and opening the Advanced page.
If no FaceSets are listed in the Style dialog box, the export converter cannot retrieve any
fault data. If any FaceSets are listed as "lost faces," assign each of these lost faces to a
real fault by using the following commands:
In GOCAD, use the Rename/Merge Faults command (see Part VIII: 3D Grid Building,
"Editing Faults," page 6-115).
In SKUA, use the Rename Grid Fault command (SGrid commands > Tools).
1. For information about RESCUE, visit the Petrotechnical Open Standards Consortium at
www.posc.org/rescue.
User Guide
2-53
To export an SGrid to
a RESCUE file
2.9.6
Select File > Export > SGrid > RESCUE to open the Export SGrid to RESCUE dialog
box.
In the File name box, enter the RESCUE output path and file name.
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.
In the Version number box, type the numeric value to indicate the RESCUE version
that you are exporting to.
If you want to export layers, horizons, and fault surfaces, select the Export
structural model check box.
Click OK or Apply.
"To
"To
"To
"To
"To
For information about exporting local grid refinement (LGR) data from an SGrid to a VIP
file, see "Exporting LGR Data from an SGrid to a Flow Simulator" on page 2-59.
2-54
Exporting Data
Select File > Export > SGrid > VIP to open the Export SGrid to VIP File dialog box.
To separate the output into two files (one contains geometric information, the other
contains property information), click Separate files.
Note If you click Separate files, the dialog box displays two boxes, Output directory and
Prefix.
If you are generating a single file, enter the file and location to which you want
to generate the output in the Output file box.
If you are generating separate files, enter the location to which you want to
generate the output in the Output directory box, and then type the prefix that
the geometry and property files will share in the Prefix box.
Note When you run the converter, it creates two or more data files. The geometry file has
the name prefix_ Reservoir Grid Name.COR added to it. Each property file has the
prefix_Property Name.COR added to it (where Reservoir Grid Name indicates the name of
the SGrid and Property Name indicates the VIP keyword for that particular Property).
User Guide
In the Export grid in the following unit area, click Feet if you want to export the
grid in feet.
To generate an ASCII grid property file that contains no geometric information, clear
the Export geometry check box.
2-55
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
NETGRS
Net to gross
POR
Porosity
KX
Permeability in X
KY
Permeability in Y
KZ
Permeability in Z
SWR
SWRO
SGR
SGRO
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.
2-56
Exporting Data
Select File > Export > SGrid > VIP to open the dialog box, and then click the Well
Data tab.
Select the Export Well Data check box to enable the exporting options.
To select the wells to export, enter the well names in the Wells box.
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.
Select File > Export > SGrid > VIP to open the dialog box, and then click the Fault
Data tab.
Select the Export Fault Data check box to enable the exporting options.
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.
d1 + d2
, where k i = permeability in the cell.
----------------------------d
d
-----1- + -----2-
k1
User Guide
k2
If you do not want to export the transmissibility, clear the Compute transmissibility
check box.
Select File > Export > SGrid > VIP to open the dialog box, and then click the Region
Data tab.
Select the Export Regions check box, to enable the exporting options.
2-57
In the Region 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.
In the Regions box, enter the names of the regions that you want to export.
Click OK or Apply.
Select File > Export > SGrid > VIP to open the dialog box, and then click the
Advanced tab.
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.
To change the orientation of the VIP grid relative to the SGrid, click one of the options
for the Areal Origin of Cells and for the Vertical Origin of Cells.
Note VIP requires that the grid origin is in the upper-left corner.
For more information, see "About the Grid Origin" on page 2-37.
2-58
Exporting Data
If you want to restore the preselected settings for the areal and vertical origin, click
Restore Defaults.
To reverse the I and J-axes in the output file, select the Switch I and J axis check
box.
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.
To change the horizontal scale in the output file to a negative, select -1 in the
Horizontal Scale box.
2.9.7
To export an SGrid to
a Temis3D file
2.9.8
Select File > Export > SGrid > Temis3D to open the Save SGrid Geometry and
Properties as Temis3D Format dialog box.
In the SGrid box, enter the SGrid object that you want to export.
In the Lithology box, select the discrete property that represents the lithology.
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.
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.
User Guide
2-59
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 24). 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:
2-60
Exporting Data
Prerequisites for
exporting LGRs
Before you can export LGRs, you will need to do the following.
For information about this
Part II: Data Import and Export, "Importing an ECLIPSE ASCII Grid File,"
page 1-46 or "Importing a VIP or ECLIPSE LGR File," page 1-57
or
Part X: Reservoir Production and Simulation, "Creating Local Grid
Refinements (LGRs)," page 2-90
1. The ECLIPSE binary converter does not support LGR export scenarios. This converter automatically
exports all LGRs within the grid.
After you define an LGR export scenario for the LGRs in your grid, do the following:
1
Select File > Export > SGrid, and then, depending on the simulator that you selected
in the export scenario, click either CMG or VIP or point to ECLIPSE and click ASCII.
Note You can also open the export converter from:
User Guide
The context menu for the SGrid object in the Objects browser (right-click the name of the
grid to access the menu).
The LGR and Upscaling Workflow in the Defining LGR Export Scenarios > Define Scenarios
and Export task).
If necessary enter the name of the stratigraphic grid (SGrid object) that contains the
LGRs in the Reservoir Grid box.
Click the LGR tab, and then select the Export LGR check box to enable the export
options.
In the LGR file box, enter a path and file name (including the file name extension,
.lgr) for the exported file.
2-61
In the LGR export scenario box, select the name of the scenario (that you created in
the LGR and Upscaling Workflow), which contains the list of LGRs that you want to
export from the selected grid.
If you want to export property data along with each LGR, select the Export
properties check box.
If you want to include any AMALGAM keyword data that you specified in the LGR
export scenario, select the Export AMALGAM keyword check box.
For information about how to specify the data for the keyword in the LGR and
Upscaling Workflow, see Part X: Reservoir Production and Simulation, "Defining
LGR Export Scenarios for Flow Simulation" on page 2-111.
b
Click Check LGR names to determine if the names of the LGRs are compatible
with the ECLIPSE requirement (that is, eight characters or less).
The converter displays a message if you need to rename any of the LGRs.
Caution If you rename any of the LGRs, you will need to resave the LGR export
scenario from the LGR and Upscaling Workflow, and then reselect the scenario in
the converter.
8
In the VIP converter, if you want to include any OMIT or INGRID keyword data that
you specified in the LGR export scenario, select the Export OMIT and INGRID
keywords check box.
For information about how to specify the data for the keyword in the LGR and
Upscaling Workflow, see Part X: Reservoir Production and Simulation, "Defining LGR
Export Scenarios for Flow Simulation" on page 2-111.
2-62
Exporting Data
To export additional data from the selected SGrid, click another tab in the converter
and enter information as necessary. For information, see:
Carrying out the command converts the LGR data to ASCII format and saves the file in the
folder that you specified.
User Guide
2-63
2.10
"Exporting
"Exporting
"Exporting
"Exporting
As described in "Basic Procedures for Exporting Data" on page 2-4, you can also export
Well object data to Excel. For information, see "Exporting Object Properties to Excel" on
page 2-7.
2.10.1
To export a Well to an
IRAP file
Select File > Export > Wells > IRAP to open the Export Wells To Irap RMS dialog
box.
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.
2-64
Exporting Data
2.10.2
To export a Well to an
LAS file
Select File > Export > Well > LAS to open the Export Wells To LAS dialog box.
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.
Note The converter adds the well name to the file prefix.
To export the X,Y, and TVDSS data, select the Include deviation check box.
In the Sampling interval box, type a numeric value to indicate the distance
between each sample.
1. For information about LAS, visit the Canadian Well Logging Society at http://cwls.org.
User Guide
2-65
2.10.3
To export well
markers to an ASCII
file
Select File > Export > Well > Well Markers to ASCII to open the Export Well
Markers to ASCII file dialog box.
In the File name 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.
To export Dip and Azimuth data, select the Export Dip and Azimuth check box.
Note When you select this check box, two columns are added to the file, Dip and Azimuth
(from North), in a clockwise direction. The angle is in degrees.
2-66
Exporting Data
2.10.4
User Guide
Select File > Export > Well > Well Path and Logs to ASCII to open the Export Well
Curves as a Column File dialog box.
In the File name 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.
In the Region box, select the region for which you want to export the curve data.
2-67
2.11
2.11.1
To export a
3D Viewer image to a
CGM file
Select File > Export > View > CGM from 3D Viewer to open the Print Window to a
CGM File dialog box.
In the Camera box, enter the name of the view that you want to export.
The view name appears on the title bar for the view window. (Or, if the view is
maximized, the view name appears on the title bar of the SKUA or GOCAD window).
In the CGM file 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.
2-68
Exporting Data
Use height. If you select this option, you need to specify a height. This number
corresponds to the plot height in centimeters.
Use scale. If you select this option, you need to define a scale factor. This
number, which is in real world units, corresponds to one plot centimeter.
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.
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.
In the CGM encoding box, select one of these options to determine how the
converter encodes the exported CGM file:
binary
clear text
Note Binary is quicker and more compact than clear text but cannot be edited.
User Guide
2-69
2.11.2
BMP
JPEG
PNG
TIF
XBM
ICO
JPG
PPM
TIFF
XPM
The command takes a screen capture of the image at the same size and scale as it appears
on screen. Any dialog boxes obscuring the view are also captured. Before you carry out
the command, you should clear the view of any overlapping windows.
To export a view to
an image file
With the view open and set up how you want it to appear in the image, do one of the
following to open the Snapshot dialog box:
In the View box or Camera box (as applicable), enter the name of the view that you
want to export.
The view name appears on the title bar for the view window. (Or, if the view is
maximized, the view name appears on the title bar of the SKUA or GOCAD window).
Specify where you want to save the file by doing one of the following:
Click Save in project. Save the image file in the project folder (*.prj). With this
option, the image will be available for review in the Images browser, on the
Results tab.
Click External file, and then in the Snapshot file box, enter the path and file
name where you want to save the image.
With this option, the command either creates a file or overwrites an existing one.
2-70
Exporting Data
In the User comment box, type any text that you want to associate with the image.
If you save the image in the project, this text appears below the image in the Images
browser.
5
In the Image format box, select the file format that you want to use to save the
image.
If you want to specify the size of the image, select the Resize snapshot check box,
and then type numeric values (in pixels) in the Width and Height boxes. (In the
3D Viewer, the maximum is 2000 by 2000 pixels.)
If cleared, the command takes a screen capture of the view at the same size and scale
as it appears on screen.
Note If you are working with a remote connection with limited graphics support or with an
early version of OpenGL, such as OpenGL 1.1, resizing is not supported.
You can find the new image file by using a file management program to browse to the
folder you specified. And, if you saved the file to the project folder, you can also view the
file by using the Images browser on the Results tab (for more information, see Part IV:
Foundation Modeling, "Reviewing and Comparing Images" on page 17-14).
2.11.3
VRML export
limitations
The converter does not support 2D and 3D textures. All Voxet sections and 2D images
appear as white in the VRML file.
The Predefine Viewpoint function may not work in some VRML viewers.
To export a
3D Viewer image to a
VRML file
Select File > Export > Camera > VRML to open the Print Window to VRML dialog
box.
In the Camera box, enter the name of the view that you want to export.
The view name appears on the title bar for the view window. (Or, if the view is
maximized, the view name appears on the title bar of the SKUA or GOCAD window).
1. For information about VRML format, visit the Web 3D Consortium at www.web3d.org/x3d/vrml.
User Guide
2-71
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.
To save data (such as geometry and shading) from the hidden parts of objects, select
the Add back face information check box.
Notes
2-72
Exporting Data
Select this option to overcome the effects of backface culling that occur with some VRML
viewers.
If you select back face culling (not selecting and drawing what is not in front of the 3D
view), any object or part of an object (such as triangles, nodes, or other objects) that face
away from your point of view is eliminated.
2.12
Connection with
Isatis
SKUA or GOCAD connects to the Isatis database by using the GTXserver, a program
provided by Geovariances. This program is installed with Isatis. So if you have Isatis
installed on the same machine as SKUA or GOCAD, there is no need to do a separate
download and install.
However, if you do not have Isatis installed, you can download this program, free of
charge, directly from the Geovariances Web site (www.geovariances.com). This program is
available for several platforms.
To access to the database, you need to first open a connection with the database and
then use the GTXserver for loading or saving data. The connection is closes once the load
or save is done.
Typically, a new GTXserver runs from a location on your machine that is designated during
the Isatis installation. Therefore, the default option in the Advanced parameters is Run
GTXserver and the Force GTXserver check box is cleared.
Depending on your situation, you may need to set different parameters. For example:
If you do not have Isatis installed, but you have an Isatis database available, you can
extract the GTXserver package from Geovariances Web site, select the Force
GTXserver check box, and then type the path location of the executable file in the
GTXserver box.
If you need to access a database stored on another machine, you may need to run
GTXserver on that machine. You would click the Use already running GTX server
and then type the entries for the Host Name and Port boxes.
If the Run GTXserver option is not working, the reason may be that it cannot be
found due to a registry problem or an environment variable. To fix this, you can select
the Force GTXserver check box and reset the location, or click the Use already
running GTX server to run GTXserver manually.
The preselected values for the advanced parameters are set when you initially use the
Export to Isatis command. The parameters remain set, unless you change them.
User Guide
2-73
Architecture of the
Isatis database
In Isatis, the GTX_INIT directory contains all of the available studies (this directory is also
known as $HOME/.isatis for UNIX and %APP_DATA%\Geovariances\Isatis for Windows).
You can reference the location of this directory from the Isatis Help menu by clicking
clicking About.
The structure of each study is:
Isatis objects
Isatis contains a set of files corresponding to SKUA and GOCAD objects. This table shows
the relationship between the object types and the corresponding Isatis file types.
SKUA and GOCAD object
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
This table shows the relationship between the SKUA and GOCAD properties and the
corresponding Isatis variables.
2-74
Exporting Data
Isatis variable
Region flag
Float variable
Multidimensional variable
Macro variable
To export an SGrid
and data to an Isatis
file
Select File > Export > SGrid + Data > Isatis to open the Export unit to Isatis dialog
box.
To set the advanced connect parameters, click Advanced to open the Advanced
Connect Parameters dialog box, and then do the following:
Note Steps 2 is necessary only if you need to maintain these parameters. Once set, you will not
have to complete these steps.
User Guide
Use already running GTX server box. Uses the GTXserver that is currently
running.
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.
2-75
If you clicked the Run GTX server option, and selected the Force GTXserver
check box, enter the GTXServer path in the GTXServer path box.
Notes
This path corresponds to the full GTXserver executable path. Normally, this path is in
the bin directory of the Isatis installation path.
You only have to force the GTXserver executable when you do not have Isatis
installed. If Isatis is installed, GTXserver is automatically installed under Windows.
For Linux users, if necessary, you may need to define the GTX_HOME environment
variable and restart SKUA or GOCAD.
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.
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.
In the DATA path box, enter the full data path. This path corresponds to the
Isatis database directory.
In the DX, DY, and DZ boxes, type numeric values to set the direction block size
parameters.
To export the grid properties, select the Export grid properties check box.
To export the original data coordinates, select the Export original data coordinates
check box.
In the Directory box, select the directory you are exporting to.
In the Gocad Data object box, enter the data object to export.
10 Click OK or Apply.
2-76
Exporting Data
A
Appendix A Import File
Formats
In this appendix
Overview
In Paradigm SKUA and Paradigm GOCAD , where possible, the import converters
provide a high degree of flexibility and can identify and import data files without requiring
rigid file formats. However, some converters, because of the specific data being imported,
require explicit formatting and precise data to import a file. This appendix describes the
converters and file format requirements.
Table A1 on page A-2 is a summary of the file formats that you can import.
A-1
A.1
Adobe contours
.esp
LAS
.las
ArcView
Locace
.ext
.fau
.g
.g
MPath
.dxf
.gridexp
Column-based file
Completion
Norsar horizons
.grd
Octopus
.dat
Petrel pillars
.dat
.flt
PetroMod
.pmb
.ply
Promax
CPS3 binary
.bin
SEG-Y 2D as SGrid
.sgy, .segy
SEG-Y 2D as Surface
.sgy, .segy
DEM ER Mapper1
.ers
RC2
RC2 2D grid
DXF
.dxf
SEG-Y 3D as Voxet
.sgy, .segy
.data
SeisWorks
.clr
.asc
.grdecl
.grdecl
.dat
.asc
SEP
.h
StrataModel 2D grid
.smg
.smg
.avf
Excel
.xls
TDQ
FastEdit 2D grid
.dat
Temis3D
Temis3D Colormap
.dat
Temis3D Grid
.td4
.dat
Velf
.velf
.cor
Geoprobe 2D grid
.gvw
.cor
Paradigm Geosec
.ihf
VIP LGR
.lgr
.vol
GSLib 2D map
Paradigm VoxelGeo
I J K property
Images
WITSML
.gz, .xml
(Continued 1 of 2)
A-2
Irap RMS
.log, .decode
XYZ
Z-MAP contour
.zmap
1. You can import DEM and Dip data with the Structural Analysis (Kine3D-1) module. For more information about importing
DEMs and Dips, see Part VII: Geologic Interpretation, "Importing a DEM" on page 4-13 and "Importing Dip Data" on
page 4-30.
User Guide
A-3
A.2
Column-Based Formats
The converter for column-based files lets you import the following types of data:
The converter expects to read a set of points from an ASCII file that contains columns of
data. The file should contain a column of X data, a column of Y data, a column of Z data,
and (optionally) additional columns for different properties. The file does not have to be
structured.
Free-form or fixedwidth columns
The file format can be either free-form (fields are separated by blanks and/or
tabs) or fixed-width columns (each column can be of a different width).
Column position
Properties
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
(delimited), used for
PointsSet objects
89
90
91
92
.
.
.
0.22135 2
0.2 2
0.209244 2
0.176622 2
Free-format
(delimited) used for
Curve objects
A-4
A.3
CMG Formats
Each run of the CMG IMEX black oil simulator creates an Output file (OUT), Index Results
File (IRF), and Main Results File (MRF). The IRF and MRF work together. Thus, an IRF is not
useful without an MRF and vice versa. The IRF contains an index of the MRFthat is, the
IRF is a user-readable ASCII file that provides details about the contents of the binary MRF.
Important If you plan to use IMEX data in the Production Data Analysis Workflow, you
need, at least, the IRF and the MRF files.
User Guide
A-5
A.4
CPS3 Formats
The converter for CPS3 ASCII files lets you import the following types of data to create a
PointsSet, Curve, Well, or 2D-Grid object.
Data in the ASCII file
X, Y, Z
PointsSet or Curve
X, Y, TVDSS, MD
Well
X, Y
Curve
Fault trace
CPS3 X, Y, Z format
X,
X,
X,
X,
Curve
Y,
Y, Z
Y, Object name
Y, X, Object name
2D-Grid
.svd
PointsSet
.svf or .svp
Curve
.svs
2D-Grid
You choose whether to create a PointsSet, a Curve, or a Well object from an X, Y, Z ASCII
data file, depending upon the type of data in your file. The converter expects to read a file
that contains header data followed by a series of coordinates and data values (depending
upon which object you want to create).
Header
The converter ignores all data in the header, except for the FFASCI or FDASCI
keywords. If either of these keywords are present, the converter reads the number
following the keyword as the no-data-value.
Data
The converter expects to start reading data immediately following an arrow symbol (>).
The data portion should contain xyz-coordinates in columns separated by one or
more spaces.
This sample file contains X, Y, and Z coordinates that you can import as a PointsSet or
Curve object.
FDASCI 0 1 "Computed" 0 1E30 0
FDATTR 4 2 2 0
FDATNM 1 "TimeInterpretation real"
! Coordinate System:
! Secondary Horizontal : Units: m Per/Meter: 1.0000000000
!
Geodetic Datum : NAD27 Ellipsoid CL66
(3E15.7)
-> Grid: AA, red, 1, TimeInterpretaion, [ms]
0.11272825E+07 0.2307070E+06 0.2664000E+04
0.11272825E+07 0.2311172E+06 0.2656000E+04
0.11272825E+07 0.2315224E+06 0.2612000E+04
A-6
CPS3 X, Y, TVDSS, MD
format
The converter imports an ASCII file that contains X, Y, TVDSS, and MD data as a Well
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.
Data
The converter expects to start reading data immediately following an arrow symbol (>).
The data portion should contain xy-coordinates in columns one and two, and
TVDSS values in column three. If MD values are included, they should be in
column four. Each column should be separated by one or more spaces.
The name of the well should immediately follow the arrow symbol (->); if the file
contains data for more than one well, a new arrow symbol and a new well name
should appear at the start of each.
Note The converter assumes TVDSS coordinates are elevation values (negative
subsea values). If your data represents depth (positive subsea values), you can
run a script (Z = -Z;) that will correct the problem by inverting the well data. For
information, see "Applying a Script on an Object Property" on page 12-33.
Here is an example file that contains X, Y, TVDSS, and MD data for a well named 30/6-1.
FDASCI 0 1 "Computed" 0 1E30 0
FDATTR 4 2 2 0
FDATNM 1 "TimeInterpretation real"
! Coordinate System:
! Secondary Horizontal : Units: m Per/Meter: 1.0000000000
.
.
.
!
Geodetic Datum : NAD27 Ellipsoid CL66
(3E15.7)
-> 30/6-1
0.11272825E+07 0.2307070E+06 0.2664000E+04 0.0000000E+03
0.11272825E+07 0.2311172E+06 0.2656000E+04 0.0188000E+03
0.11272825E+07 0.2315224E+06 0.2500000E+02 0.2722000E+04
.
.
.
User Guide
A-7
CPS3 X, Y polygons
format
The converter imports a CPS3 ASCII polygons (.ply) as a Curve object. The converter
expects an ASCII file that contains header data followed by a series of xy-coordinates.
Header
The converter ignores all header data. This file usually contains a single line of text,
in parentheses, that describes the format of the data.
Data
The converter expects to start reading data immediately following an arrow symbol (>).
The data portion should contain two columns of xy-coordinates, with each column
separated by one or more spaces.
If the imported Curve object has several separate segments (parts), each part should
be designated by a new arrow symbol and segment ID.
Here is an example file that contains X, Y coordinates for two polygons: (2E15.7) and
(P-2a). The converter will create one Curve object with two parts, from the data in this
file.
(2E15.7)
->
0.1280157E+07 0.2583688E+06
0.1287104E+07 0.2458821E+06
0.5128826E+07 0.2419755E+06
->
.
.
.
(P-2a)
0.12875781E+07 0.2563888E+06
0.12857812E+07 0.2452881E+06
0.51284826E+07 0.2419556E+06
.
.
.
A-8
The converter imports CPS3 ASCII fault trace data (.flt) as a Curve object. The converter
expects an ASCII file that contains header data followed by a series of coordinates.
Header
Data
The converter starts reading data immediately following an arrow symbol (->)
The data portion can contain up to four (but should have at least two columns)
of coordinates (or values), with each column separated by one or more spaces. The
converter expects coordinates or data as follows:
2 columns: X, Y
3 columns: X, Y, Z (if the third column is a number) or X, Y, object name (if the third
column is a word)
4 columns: X, Y, Z, object name
If the imported Curve object has several separate segments (parts), each part should
be designated by a new arrow symbol and segment ID, and the segment ID becomes
a part of the Curve object name.
User Guide
A-9
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
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
A-10
The converter expects an .svs file to contain X and Y grid data and Z property data.
User Guide
A-11
A.5
ECLIPSE Formats
The ECLIPSE converters include ASCII, properties, binary, and RSM.
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
GRID
MAPUNITS
MAPAXES
GRIDUNIT
COORD
Coordinate lines
ZCORN
TOPS
DX
DY
EDIT
DZ
PORO
Porosity
DZNET
Net thickness
NTG
ACTNUM
PERMX
PERMY
PERMZ
MULTX
MULTY
MULTZ
PORV
REGION
SOLUTION
SCHEDULE
Definition
FIPNUM
SATNUM
EQLNUM
PVTNUM
SWAT
SGAS
SGL
BOX
A-12
Section
Keyword
Definition
ENDBOX
COPY
EQUALS
ADD
MULTIPLY
MAXVALUE
MINVALUE
Required Keywords:
SPECGRID or
DIMENS
COORD
Coordinate lines
ZCORN
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.
The converter expects to read a binary file that contains ECLIPSE keywords.
The file containing the grid geometry data should have the .grid or .egrid extension. All
other relevant data files (for example, .init for initial reservoir data and .unrst for unified
restart data) should be in binary format. They should have the same file name as the GRID
file but a different extension, and they should be located in the same folder.
User Guide
A-13
A.6
FastEdit Formats
The FastEdit converter can read the following FastEdit file formats and create different
objects, based on the type of data in the file being imported.
Fault polygon
Scattered data
Horizon contours
2D grid
The FastEdit fault polygons converter expects to read an ASCII file that contains header
and data in the following format.
Header
Data
Each line should begin with a Segment ID number followed by a series of X, Y data
points, all separated by one or more spaces.
Note If there is more than one Segment in the file, the converter imports all data and creates a
Curve object for each Segment ID. The name of the new object will include the Segment ID. For
example, Segment 1 in a file called FaultPolyFastedit is imported as a curve named
FaultPolyFastedit_1.
FastEdit scattered
data format
4355.3798828
4355.2900391
4359.1098633
4367.2299895
4379.9399414
4420.6601563
6467.2402344
6648.2597656
6827.8701172
7004.8999023
7178.0200195
7345.0898438
4355.2900391
4359.1098633
4367.2999805
4379.9399414
4397.6601563
4420.6601563
6648.2597656
6827.8701172
7004.8999023
7178.0200195
7507.7299805
7346.0898438
The FastEdit scattered data converter expects to read an ASCII file that contains header
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.
Header
Data
A-14
0.0000000
0.0000000
0.0000000
0.0000000
500.0000000
500.0000000
FastEdit horizon
contours format
The FastEdit horizon contours converter expects to read an ASCII file that contains header
and data in the following format.
Header
Data
FastEdit 2D Grid
format
-1.0000000
8103.0097656
-1.0000000
11000.0000000
-1.0000000
8040.6127930
-1.0000000
-10800.0000000
The FastEdit 2D Grid converter expects to read an ASCII file that contains header and data
in the following format.
Header
Data
User Guide
A-15
A.7
The Irap RMS fault polygons or lines converter expects to read an ASCII file that contains
header data followed by a series of X, Y, and Z coordinates separated by one or more
spaces. The converter can read the classic or mapping format, and imports one object per
file.
Header
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
.
.
.
A-16
The Irap RMS triangle surface converter expects to read an ASCII file that contains header
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.
Data
The data portion should contain the X, Y, and Z coordinates separated by one or
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.
Begin GEOMATIC file header
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
.
.
.
The converter expects to read an ASCII file with header data that contains grid parameters
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:
Data
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
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.
User Guide
A-17
-8357.719727
-8347.599609
-8326.809570
.
.
.
Legend:
# of rows
x
y
min x
max x
min y
max y
# of columns
angle of rotation
=
=
=
=
=
=
=
=
=
151
100.565407
200.143738
1364.339966
16449.150391
19502.400391
49073.960938
151
270.000000
The converter expects to read an ASCII file that contains header data followed by
z-coordinates for the 2D grid defined in the header, and expects each coordinate to give
the z-location of a particular grid node. The nodes are laid out in column-major order,
column by column, row by row, starting in the upper-left corner of the grid and moving
down along the y-axis.
Header
Mapping format: The converter expects to read keywords that define grid
parameters. The keywords can occur in any sequence.
Data
The data portion should contain the xyz-coordinates separated by one or more
spaces.
Here is an example file that shows Irap RMS 2D grid mapping format.
Begin GEOMATIC file header
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
.
.
.
A-18
The Irap RMS Well converter expects to read an ASCII file that contains header data
followed by location coordinates. Property and marker data can be in the same file.
Header
The header section should contain a series of keywords that define the data.
Data
The data section should contain the X, Y, TVDSS, and MD coordinates separated by
one or more spaces.
Each line of data should contain location data for a single point on the Well.
Property and marker data, if any, should follow at the end of each line.
Here is an example file that shows the Irap RMS well data format:
1.0
Oil_and_Gas
wll7 -25.000000 -92.000000
3
Facies none linear
Porosity none linear
marker disc 0 ANGstructural 1 BATstructural
prop_horizons_morph_0 3 prop_horizons_morph_1
-25.000000 -92.000000 21.000000 -999 -999 -999
-25.000000 -92.000000 21.000000 -999 -999 -999
-25.000000 -92.000000 21.000000 -999 -999 -999
-25.000000 -92.000000 21.000000 -999 -999 -999
60.000000 668.000000 -1307.000000 -999 -999 -999
62.285698 672.507694 -1313.000000 -999 -999 -999
64.571404 677.143005 -1319.000000 -999 -999 -999
66.857101 681.713989 -1325.000000 -999 -999 -999
.
.
.
User Guide
A-19
A.8
LAS Format
The LAS converter expects to read an ASCII file that contains header and data in the
following format.
Important LAS files can vary considerably in content and format. The converter requires specific
data to be present in the import file.
If several wells are described in the same file, the converter loads them all.
LAS format
Each keyword the converter recognizes should be preceded by a tilde (~) followed by a
single uppercase letter, which may or may not be part of a longer word. For example, the
converter reads the phrase ~Version Information as the keyword ~V.
Header
The Header section can contain a series of standard LAS keywords that provide
information about the wells name, location, logs (if any), picks (if any), and
deviation survey (if any).
Required keywords: ~W, ~C. If these keywords do not appear in the header
portion of the LAS file, the converter will not work.
~W
Well Information: Provides general information about the well, such as: name,
location, service company, and so on. The converter creates a Well object or adds
data to an existing well object by using the name it finds in this section next to the
word WELL, or WN, or UWI.
~C
Curve (Log) Information: The converter uses the data in this section to name and
order the imported logs.
Optional keyword: ~T
Tops information (not shown in the example). If the file contains well picks
(markers), these should be included in the Header portion of the file with this
keyword.
Data
Required keyword: ~A
The data portion of the file should contain the property and deviation data values of
the properties defined by the ~C keyword in the header. The converter reads the
values in the same order as the properties listed in ~C.
Here is an example file that shows an LAS ASCII file with ~W, ~C, and ~A keywords:
~Version Information Block
VERS .
5.00: CWLS LOG ASCII STANDARD - VERSION 5.00
WRAP .
NO: One line per depth step
~Well Information Block
#MNEM.UNIT
Data Type
Information
#---------- ---------------- ----------STRT .F
703: START DEPTH
STOP .F
1262: STOP DEPTH
STEP .F
0.5: STEP
NULL .
-999.25: NULL VALUE
COMP .
: COMPANY
WELL .
W_1: WELL
.
.
.
~Curve Information Block
#MNEM.UNIT
API CODE
Curve Description
#---------- ---------------- ----------------DEPTH.F
:
CALI .IN
: Loaded from X.GEOASCII
CT
.MH/M
: True formation conductivity
CXO .MH/M
: Flushed zone conductivity
DRHO .G/C3
: Loaded from X.GEOASCII
A-20
.
.
.
~Parameter Information Block
#MNEM.UNIT
Value
Description
#---------- ---------------- ----------PROJECT.
Y.ras:
SET .
MMWORK:
~A
DEPTH
CALI
CT
CXO
FPRESS
FTEMP
GR
HMC
PHIT
RGRD
RHOB
RMC
RM
RXO
SWT
703.0000
8.6303
0.0044
0.0049
335.7760
60.8508
38.8602
0.0000
0.0043
228.5933
2.7125
3.1620
.
.
.
User Guide
DRHO
HMC
RMF
0.1130
0.0000
A-21
A.9
MPath Formats
The MPath converter expects to read MPath .act, .fid, .par, and .raw files created by the
Permedia Consortium Project. For more information, see www.permedia.ca.
The converter expects to read an .act file that contains simulation results output by
Migration, Dynamic Migration, Connections, Intrusion, or Analysis. The .act files can be
ASCII or binary.
The converter expects to read an ASCII header, followed by a 4-byte sequence to detect
the byte order of the file.
Header
The file should have an ASCII header that contains a series of keywords defining the
data. The converter ignores blank lines and lines starting with #.
.act required keywords:
Data
fid
par
extents
origin
cellsize
rotation
fields
gridcells
fields
data (the converter expects to start reading data immediately following this
keyword)
The converter expects to read data for the grid cells in binary format.
A-22
The converter expects to read grid data files consisting of a regular grid containing a
single value for each grid cell.
Header
(data
requirements are
the same,
whether the file
is in ASCII or
binary format)
The file should have an ASCII header that contains a series of keywords defining the
data. The converter ignores blank lines and lines starting with #.
.fid required keywords:
Data
The converter expects to read data for the grid cells in binary format.
origin
cellsize
rotation
cycling_order
extents
data
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.
Header
(data
requirements are
the same,
whether the file
is in ASCII or
binary format)
The file should have an ASCII header that contains a series of keywords defining the
data. The converter ignores blank lines and lines starting with #.
.fid required keywords:
Data
The converter expects to read data for the grid cells in binary format.
origin
cellsize
rotation
extents
data
User Guide
A-23
The converter expects to read a .par file that contains petrophysical parameters for each
flow unit ID contained in the .fid file.
Header
The file should have an ASCII header that contains a series of keywords defining the
data. The converter ignores blank lines and lines starting with #.
.par required keywords:
Data
Fid
Red
Green
Blue
The converter expects to read ASCII data for the grid cells.
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:
Header
The file should have an ASCII header that contains a series of keywords defining the
data. The converter ignores blank lines and lines starting with #.
.raw required keywords:
Data
A-24
445_214_192 fault 3
origin
cellsize
rotation
extents
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 xdimension, the second y, and the third z. Your raw data grids should have the same x, y-, and z-values as the .fid file you selected.
All lines appearing after the data keyword are data values, cycled through in the xzyorder.
The example shows extent: 30 40 585. This means 30 grid cells in the x-dimension, 40 in
the y-dimension, and 585 in the z-dimension are defined in the data block.
User Guide
A-25
A.10
2D SEG-Y format
SEG-Y Formats
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
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.
A-26
SP (Shot Point)
1
2
3
X
451346
451304
451262
Y
1390689
1390653
1390617
3D SEG-Y format
The 3D SEG-Y converter expects to read a three-dimensional SEG-Y file that contains
header data and seismic data.
The converter imports only post-stack data and reads a binary format, if the file adheres
to the standards defined on the Society of Exploration Geophysicists Web site at
www.seg.org. Files, examples of files, and keyword requirements for each file are fully
explained on this Web site. The converter can usually determine the correct format;
however, if you want to specify the file format, you can do so during the import
procedure.
The following table gives a brief description of the general contents expected to be in the
different 3D SEG-Y file types.
Header
Content
Binary
A standard 400-byte header that contains 2-byte and 4-byte integer values that apply to
the whole file.
Trace
A standard 240-byte header that contains 2-byte and 4-byte integer values that apply to
the associated trace. A SEG-Y file generally contains multiple traces (seismic amplitude
samples), with a separate 240-byte trace header describing the information contained in
each one.
For the converter to work properly, the 3D SEG-Y file being imported should be evenly
sampled and all traces should have the same length.
User Guide
A-27
A.11
SEP Format
The SEP converter expects to read two files that contain a data cube in SEP format. One
file contains the header data, one file contains the data.
Header
The converter expects a separate ASCII header file that has the same file name as the
data file, but with H added as the file name extension. The converter expects the file
to contain the following data:
# indicates a comment line.
Number of samples along each cube axisfor example: n1=81, n=41, n3 =81
Voxet originfor example 01=500, 02=300, 03=2100
Increment between samplesfor 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
A-28
A.12
Velf format
Velf Format
The converter expects to read two keywords that define the location and velocity values
for the Curve object:
SPNT This keyword defines the X, and Y location of one vertical line. The fourth
column defines X and the fifth column defines Y. For each line starting with SPNT, the
converter creates a vertical line.
IVEF This keyword defines for each vertical line the couples time_or_depth/velocity.
The converter can read up to five couples per IVEF line. For each line starting with
IVEF, the converter starts reading from the twentieth character and reads the velocity
value for each time or depth.
You can have many IVEF lines for one SPNT line.
User Guide
A-29
A.13
XYZ Format
The XYZ converter expects to read a three-column ASCII file that contains only data
values, and the data values should be separated by one or more spaces.
An X, Y, Z file consists of data lines onlyno 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
.
.
.
A-30
A.14
Z-MAP Formats
The Z-MAP converter can read the following Z-MAP file formats and create different
objects, based on the type of data in the file being imported.
The Z-MAP fault polygon converter expects to read an ASCII file that contains header data
followed by a series of fault polygon location coordinates and associated segment IDs in
the following format.
Header
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
X (EASTING)
Y (NORTHING)
SEG I.D.
@
X
4355.29
4355.29
4359.11
6367.23
4379.94
4397.66
4420.66
4455.74
.
.
.
User Guide
HEADER
, 1, 1, 1,
, 2, 2, 1,
, 3, 35, 1,
Y
6467.24
6648.26
6827.87
7004.90
7178.02
7346.09
7507.73
7667.89
1, 15,
16, 30,
31, 40,
FALT
7, 0.1000000E+31.
7, 0.1000000E+31.
1, 0.1000000E+31.
Segment ID
1.0
1.0
1.0
1.0
1.0
1.0
1.0
2.0
A-31
Z-MAP 2D Grid
format
The Z-MAP 2D Grid converter and the Z-MAP 2D Grid Properties converter expects to read
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.
Header
The data portion should contain the z-coordinates (w-property) for the 2D Grid
defined in the header. Each coordinate gives the z-location of a particular grid node.
The nodes are laid out in order, column by column, row by row, starting in the
upper-left corner of the grid and moving down along the y-axis (v).
-9999.99 identifies the no-data value, and the converter ignores any coordinate with
this value.
151 and 151 are the Nu and Nv valuesthe number of nodes along each axis.
Data values appearing after the end-of-header indicator (@) are the z/w-coordinates
for the 2D grid.
@BaseSand geometry
15
-9999.99
151
151
1364.34
@
Header grid
31385.9
3967.59
5
19052.4
A-32
A.15
VIP Formats
The VIP converter can read VIP file formats and create an SGrid object or add property
data to an existing SGrid object.
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:
Note If your grid file does not contain data values for the NX NY NZ keywords,
you need to supply the values in the Import an SGrid from VIP ASCII file dialog
box. See"Importing a VIP ASCII Grid File" on page 1-56.
Data
Property data
NY
20
NZ
1
NCOMP
0
Grid size
ARRAYS
CORP VALUE
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
31800.62 40780.29 9591.69 31223.06
31223.06 41427.86 9659.38 31800.62
31800.62 40780.29 9664.03 31223.06
C GRID BLOCK I = 2, J = 1, K = 1
31800.62 41427.86 9589.23 32378.19
.
.
.
User Guide
Required
41427.86
40780.29
41427.86
40780.29
9589.23
9589.00
9659.71
9660.13
41427.86 9591.28
A-33
The VIP SGrid properties converter expects to read an ASCII file that contains data in the
following format:
The text line defining each property should be in this format: property_name VALUE.
The converter reads property values cell by cell downward.
This example shows the beginning of data for the property Porosity1.
0 0 0 0 0 0
0 0 0 0 1 1
1 1 0 1 1 1
Porosity1 VALUE
0.166836 0.161804 0.150371 0.141576 0.13394 0.137214
0.128452 0.124265 0.127039 0.134051 0.132983 0.127658
0.119557 0.112348 0.104378 0.10151 0.101245 0.100864
0.0945651 0.00964849 0.00899982 0.00929927 0.0942273 0.00899488
.
.
.
Definition
POR
Porosity
KX
KY
KZ
NETGRS
SWR
SWRO
SGR
SGRO
SO
Oil saturation
SG
Gas saturation
SW
Water saturation
The VIP local grid refinement (LGR) converter requires an ASCII file that contains the
following keywords:
Note The data in the file should be Cartesian values only. The converter does not support the OMIT
or INGRID keywords.
A-34
Keyword
Definition
CARTREF
name
i1,i2,j1,j2,k1,k2
nx1,nx2
ny1,ny2
nz1, nz2
ENDREF
Index
Symbols
.act files
importing 1-18
.avf files
exporting velocity data to 2-17
importing 1-74
.bin files
importing 1-32
.cgm files
exporting 3D Viewer images
to 2-68
exporting views to 2-68
.cmg files
exporting an SGrid object
to 2-38
.dat files
importing 1-24, 1-35
importing CPS3 ASCII data
files 1-37, 1-76
.dxf files
exporting an object to 2-7
importing 1-22
.flt files
importing 1-27
.grd files
exporting s grids to ECLIPSE
ASCII files 2-43
importing 1-31
importing CPS3 ASCII 2D-Grid
files 1-39
Numerics
2D SEG-Y files
importing 1-68
2D view
exporting as an image 2-68
2D voxet
importing 1-44
2D-Grid objects
creating from horizon surface
data files 1-39
creating using FastEdit scattered
data converter 1-35
A
Add Log From Ascii File dialog
box 1-88
Adobe contours files
importing 1-37
Advanced Connect Parameters
dialog box 2-14
ArcView files
importing 1-21
ASCII file
exporting an object to a custom
ASCII file 2-5
Index-1
B
basic concept for importing 1-6
basin modeling
importing MPath .act files 1-18
importing MPath .fid files 1-19
importing MPath .par color map
files 1-19
importing MPath .raw
files 1-18
importing PetroMod 1-19
importing Temis 3D .t4d
files 1-16
importing Temis 3D color
map 1-17
binary files
exporting an SGrid object
to 2-51
C
CGM files
exporting 3D Viewer images
to 2-68
exporting views to 2-68
channels
exporting properties to an Excel
file 2-7
Charisma files, importing
fault interpretations files 1-26
fault polygon files 1-29
horizon points 1-34
CMG files
exporting SGrid objects to 2-38
Column as Production Data ECLIPSE format wizard 1-98
Column as Production Data General Format wizard 1-91
column-based file import wizard
import file format
requirements A-4
Index-2
column-based files
importing 1-35, 1-37, 1-76,
1-86
importing location data 1-87
importing well marker data
from 1-86
importing wizard 1-8
contour data
importing to create a Cure
object 1-37
CPS3
import file format
requirements A-6
CPS3 binary converter 1-25
CPS3 fault traces
importing 1-27
CPS3 files
exporting 2D-Grid objects
to 2-28
importing 1-35
importing CPS3 ASCII 2D-Grid
files 1-31, 1-39
importing CPS3 ASCII data
files 1-37, 1-76
importing CPS3 ASCII polygon
files 1-29
importing CPS3 binary
files 1-25, 1-31, 1-35
Create Well from IRAP File dialog
box 1-78
Create Well from WITSML File
dialog box 1-85
cross section
exporting as an image 2-68
CUBIT facet files
exporting a surface to 2-24
cultural data
importing .dxf files 1-22
importing ArcView files 1-21
curves
creating Curve objects from a
column-based file 1-37
creating Curve objects from a
SeisWorks fault sticks
file 1-28
creating Curve objects from
Charisma fault polygon ASCII
files 1-29
D
DDS files
exporting voxets to
DXF files
exporting to 2-7
2-31
E
ECLIPSE
import file format
requirements A-12
ECLIPSE binary file 1-101
ECLIPSE files
export well data of s grids
to 2-46
User Guide
Index-3
F
FastEdit
import file format
requirements A-14
FastEdit files
exporting 2D-Grid objects
to 2-29
exporting curves to 2-20
exporting points sets to 2-19
exporting surfaces to 2-25
importing 1-30
importing 2D grid files 1-40
importing 2D-Grids 1-31
importing FastEdit scattered data
files 1-35
importing horizon contour
files 1-37
importing scattered data 1-25
fault interpretations
importing Charisma fault
interpretations files 1-26
importing Charisma fault
polygon files 1-29
importing column-based
files 1-8, 1-25
importing CPS3 .dat files 1-24
importing CPS3 ASCII polygon
files 1-29
Index-4
G
Geoprobe 2D-Grid files
importing 1-40
GMI WellCheck MohrFracs files
exporting surfaces to 2-26
GSLib 2D Map file
importing as surface 1-40
GSLib 2D Map files
importing 1-35
H
horizon contours
importing Z-MAP horizon
contour files 1-38
horizon interpretations
importing Adobe
contours 1-37
importing Charisma horizon
points 1-34
importing column-based
files 1-35, 1-37
importing CPS3 .dat files 1-35
importing CPS3 ASCII data
files 1-37
importing FastEdit horizon
contours 1-37
importing FastEdit scattered
data 1-35
importing GSLib 2D Map
files 1-35
importing SeisWorks Inline Xline
XYZ files 1-36
importing X Y Z files 1-36
importing Z-MAP horizon
contours 1-38
horizon surface
importing data 1-39
importing GSLib 2D map as
surface 1-40
horizon surfaces
I
I J K properties
importing 1-59
images
exporting 3D Viewer images to
CGM files 2-68
exporting 3D Viewer images to
VRML files 2-71
exporting from 3D and 2D
views 2-70
exporting views to CGM
files 2-68
importing 1-43
import
column-based import file format
requirements A-4
CPS3 import file format
requirements A-6
ECLIPSE import file format
requirements A-12
FastEdit file import
requirements A-14
file format table A-2
Irap RMS import file format
requirements A-16
LAS import file format
requirements A-20
MPath import file format
requirements A-22
SEG-Y import file format
requirements A-26
SEP import file format
requirements A-28
User Guide
Index-5
CPS3 files
importing CPS3 ASCII data
files 1-37
cultural data 1-21
ECLIPSE ASCII grid file 1-46
ECLIPSE ASCII properties
files 1-58
ECLIPSE binary grid files 1-47
ECLIPSE faults 1-61
Excel files 1-77
FastEdit 2D-Grid files 1-31,
1-40
FastEdit fault polygon
files 1-30
FastEdit horizon contour
files 1-37
FastEdit scattered data 1-25
FastEdit scattered data
files 1-35
fault interpretations data 1-23
Geoprobe 2D-Grid files 1-40
GSLib 2D map as surface 1-40
GSLib 2D Map files 1-35
horizon surface data 1-39
I J K property files 1-59
image files 1-43
Irap RMS ASCII 2D-Grid
files 1-40
Irap RMS ASCII 2D-Grid property
files 1-41
Irap RMS fault polygons or
lines 1-30
Irap RMS Triangle Surface
files 1-32
Irap RMS well files 1-78
Jason traces 1-73
LAS well data 1-79
MPath .act files 1-18
MPath .fid 1-19
MPath .par color map
files 1-19
MPath .raw files 1-18
Norsar depth cube files 1-71
Norsar horizons files 1-41
Petrel Pillar files as
surfaces 1-32
Petrel Pillars files as curves 1-28
PetroMod 1-19
Index-6
J
Jason traces
importing 1-73
L
LAS
import file format
requirements A-20
LAS file
exporting wells to 2-65
LAS well data
importing 1-79
log data
importing from column-based
files 1-87
M
map
exporting as an image 2-68
Medica file
exporting 2D-Grid objects
to 2-16
exporting curves to 2-16
MPath
import file format
requirements A-22
importing .fid files 1-19
importing .par color map
files 1-19
importing .raw files 1-18
MPath .act files
importing 1-18
RC2 files
importing as wells 1-84
importing RC2 2D-Grid
files 1-32, 1-41
RESCUE file
exporting SGrid objects to 2-53
RESCUE model files
importing 1-32, 1-42
importing grids, horizons,
faults 1-56
reservoir grid data
importing 1-45
importing ECLIPSE ASCII
grids 1-46
importing ECLIPSE binary
grids 1-47
importing ECLIPSE faults 1-61
importing ECLIPSE
properties 1-58
importing I J K properties 1-59
importing RESCUE model (grids,
horizons, faults) 1-56
importing VIP grids 1-56
importing VIP LGR files 1-57
importing VIP properties 1-60
O
objects
exporting to a custom ASCII
file 2-5
exporting to an Isatis file 2-12
exporting to DXF files 2-7
P
Petrel Pillars
importing Petrel Pillars files as
curves 1-28
importing Petrel Pillars files as
surfaces 1-32
PetroMod
importing 1-19
points sets
creating from column-based-file
data 1-76, 1-86
creating from horizon surface
data files 1-39
creating from location data from
column-based files 1-87
creating PointsSet object from
Charisma ASCII file 1-34
creating PointsSet objects from
fault interpretations data
files 1-23
creating using FastEdit scattered
data converter 1-35
exporting properties to an Excel
file 2-7
exporting to a FastEdit file 2-19
Print Window to a CGM File dialog
box 2-68
Print Window to VRML dialog
box 2-71
ProMAX files
importing 1-73
User Guide
S
S Grid object
creating from velocity
data 1-73
Save SGrid Geometry and
Properties as Temis3D Format
dialog box 2-59
SEG-Y 3D files
importing as voxets 1-62
SEGY 3D to Voxet dialog
box 1-63
SEG-Y files
exporting voxets to 2-32
SEG-Y import file format
requirements A-26
seismic data
importing 1-62
importing 2D SEG-Y files 1-68
importing Norsar depth
cubes 1-71
Index-7
T
TDQ .avf files
importing 1-74
Temis 3D color map
importing 1-17
Temis 3D files
importing as s grids 1-16
importing as wells 1-84
Temis3D files
exporting SGrid objects to 2-59
triangulated surfaces
importing 1-32
V
Velf file, exporting velocity data
to 2-18
Velf files
importing 1-74
velocity data
exporting to a Velf file 2-18
exporting to an AVF file 2-17
importing 1-73
importing Jason traces 1-73
importing ProMAX files 1-73
importing TDQ .avf files 1-74
importing Velf files 1-74
view
exporting images to CGM
files 2-68
views
exporting images 2-70
VIP files
exporting SGrid objects to 2-54
importing grids 1-56
importing VIP LGR files 1-57
Index-8
W
well curves
exporting to an ASCII file 2-67
well data
importing 1-76
importing column-based
files 1-76, 1-86
importing CPS3 .dat files 1-76
importing Excel files 1-77
importing Irap RMS files 1-78
importing LAS files 1-79
importing location data from
column-based files 1-87
importing Temis 3D files 1-84
importing Velf files 1-74
importing WITSML files 1-85
well marker data
importing from column-based
files 1-86
well marker data importing
column-based file 1-86
well markers
exporting to an ASCII file 2-66
well section
exporting as an image 2-68
well symbol data
importing 1-89
wells
creating from column-based-file
data 1-76, 1-86
creating from location data from
column-based files 1-87
creating using RC2
converter 1-84
exporting 2-64
exporting properties to an Excel
file 2-7
exporting to an IRAP file 2-64
exporting to LAS files 2-65
importing Irap RMS files 1-78
importing using the X Y Z
converter 1-86
WITSML files
importing 1-85
X
X Y Z files
importing as points set 1-26
importing as wells 1-86
importing horizon data 1-36
XYZ import file format
requirements A-30
Z
Z-MAP files
exporting 2D-Grid objects
to 2-30
exporting curves to contours
files 2-23
exporting curves to faults
files 2-22
importing 2D-Grid object
to 1-33
importing ASCII 2D-Grid
properties 1-42
importing Z-MAP contour
files 1-38
importing Z-MAP fault or
contour files 1-28
Z-MAP import file format
requirements A-31