2 import export

SKUA and GOCAD User Guide

Part II: Data Import and Export

Published October 10, 2012

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/.

iiiContents

Contents


Chapter 1 Importing Data..........................................................................................1-1

1.1 Converters and Supported Formats................................................................ 1-2

1.2 Basic Concept for Importing Data .................................................................. 1-6

1.3 Common Process for Importing a Column-Based File ...................................... 1-8

1.4 Importing Basin Modeling Files .....................................................................1-15

1.4.1 Import Temis/Medica Files ................................................................1-15

1.4.2 Importing MPath Files .....................................................................1-18

1.4.3 Importing a PetroMod File ...............................................................1-19

1.5 Importing Cultural Data ...............................................................................1-21

1.5.1 Importing an ArcView File ...............................................................1-21

1.5.2 Importing a DXF File ........................................................................1-22

1.5.3 Importing a SeisWorks Cultural Data File ..........................................1-22

1.6 Importing Fault Interpretations Data .............................................................1-23

1.6.1 Importing a CPS3 ASCII Data (.dat) File ...........................................1-24

1.6.2 Importing a CPS3 Binary File ............................................................1-25

1.6.3 Importing a Column-Based File ........................................................1-25

1.6.4 Importing a FastEdit Scattered Data File ...........................................1-25

1.6.5 Importing an XYZ File ......................................................................1-26

1.6.6 Importing a Charisma Fault Interpretations File .................................1-26

1.6.7 Importing a CPS3 ASCII Data (.dat) File ............................................1-27

1.6.8 Importing a CPS3 ASCII Polygons (.ply) File.......................................1-27

1.6.9 Importing a CPS3 ASCII Fault Traces (.flt) File ....................................1-27

1.6.10 Importing a CPS3 Binary File ............................................................1-27

1.6.11 Importing a Column-Based File ........................................................1-28

1.6.12 Importing a Petrel Pillars File ............................................................1-28

1.6.13 Importing a SeisWorks Fault Sticks File .............................................1-28

Contentsiv SKUA and GOCAD Paradigm 2011With Epos 4.1 Data Management

1.6.14 Importing a Z-MAP Fault or Contour File ........................................ 1-28

1.6.15 Importing a Charisma Fault Polygons File ........................................ 1-29

1.6.16 Importing a CPS3 ASCII Polygons (.ply) File ...................................... 1-29

1.6.17 Importing a FastEdit Fault Polygons File ........................................... 1-30

1.6.18 Importing an Irap RMS Fault Polygons or Lines File ........................... 1-30

1.6.19 Importing a SeisWorks Fault Polygon File ......................................... 1-30

1.7 Importing Fault Surfaces Data...................................................................... 1-31

1.7.1 Importing a CPS3 ASCII 2D-Grid (.grd) File....................................... 1-31

1.7.2 Importing a CPS3 Binary File ........................................................... 1-31

1.7.3 Importing a FastEdit 2D-Grid File ..................................................... 1-31

1.7.4 Importing an Irap RMS Triangle Surface File ..................................... 1-32

1.7.5 Importing a Petrel Pillars File ........................................................... 1-32

1.7.6 Importing a RC2 2D-Grid File .......................................................... 1-32

1.7.7 Importing a Z-MAP ASCII 2D-Grid File ............................................. 1-33

1.8 Importing Horizon Interpretations Data ........................................................ 1-34

1.8.1 Importing a Charisma Horizon Points File......................................... 1-34

1.8.2 Importing a CPS3 ASCII Data (.dat) File............................................ 1-35


1.8.4 Importing a Column-Based File ....................................................... 1-35

1.8.5 Importing a FastEdit Scattered Data File........................................... 1-35

1.8.6 Importing a GSLib 2D Map File........................................................ 1-35

1.8.7 Importing a SeisWorks Inline Xline X Y Z File.................................... 1-36

1.8.8 Importing an X, Y, Z File ................................................................. 1-36

1.8.9 Importing an Adobe Contours File................................................... 1-37

1.8.10 Importing a CPS3 ASCII Data (.dat) File............................................ 1-37


1.8.12 Importing a Column-Based File ....................................................... 1-37

1.8.13 Importing a FastEdit Horizon Contour File........................................ 1-37

1.8.14 Importing a Z-MAP Contour File ...................................................... 1-38

1.9 Importing Horizon Surface Data................................................................... 1-39

1.9.1 Importing a CPS3 ASCII 2D-Grid (GRD) File ...................................... 1-39


1.9.3 Importing a FastEdit 2D-Grid File ..................................................... 1-40

1.9.4 Importing a Geoprobe 2D Grid (.gvw) File ....................................... 1-40

1.9.5 Importing a GSLib 2D Map as Surface File ....................................... 1-40

1.9.6 Importing an Irap RMS ASCII 2D-Grid File ........................................ 1-40

1.9.7 Importing an Irap RMS ASCII 2D-Grid Property File ........................... 1-41

1.9.8 Importing a Norsar Horizons File ..................................................... 1-41

1.9.9 Importing an RC2 2D-Grid File ........................................................ 1-41

1.9.10 Importing a RESCUE Model File ....................................................... 1-42

1.9.11 Importing a Z-MAP ASCII 2D-Grid File ............................................. 1-42

1.9.12 Importing a Z-MAP ASCII 2D-Grid Property File ................................ 1-42

Contents vUser Guide


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

1.11 Importing Reservoir Grid Data ......................................................................1-45

1.11.1 Importing an ECLIPSE ASCII Grid File ................................................1-46

1.11.2 Importing an ECLIPSE Binary Grid File ...............................................1-47

1.11.3 Importing a CMG Grid and Simulation Results ..................................1-54

1.11.4 Importing a RESCUE Model (Grids, Horizons, Faults) File ...................1-56

1.11.5 Importing a VIP ASCII Grid File .........................................................1-56

1.11.6 Importing a VIP or ECLIPSE LGR File .................................................1-57

1.11.7 Importing ECLIPSE ASCII Properties File ............................................1-58

1.11.8 Importing an I J K Property File ........................................................1-59

1.11.9 Importing a VIP ASCII Properties File ................................................1-60

1.11.10 Importing an ECLIPSE ASCII Faults File ..............................................1-61

1.12 Importing Seismic Data ................................................................................1-62

1.12.1 Importing a SEG-Y 3D File as Voxet ..................................................1-62

1.12.2 Importing a VoxelGeo File as a Voxet ...............................................1-68

1.12.3 Importing a 2D SEG-Y File ...............................................................1-68

1.12.4 Importing an SEP File.......................................................................1-71

1.12.5 Importing a Norsar Depth Cube File .................................................1-71

1.12.6 Importing a 2D SEG-Y File as Seismic Lines .......................................1-72

1.12.7 Importing a SeisWorks Colormap .....................................................1-72

1.13 Importing Velocity Data ...............................................................................1-73

1.13.1 Importing a Jason ASCII Traces File...................................................1-73

1.13.2 Importing a ProMAX File .................................................................1-73

1.13.3 Importing a TDQ (.avf) File ...............................................................1-74

1.13.4 Importing a Velf File ........................................................................1-74

1.13.5 Importing a SEG-Y 3D as Voxet File ..................................................1-74

1.13.6 Importing an SEP File.......................................................................1-74

1.13.7 Importing a VoxelGeo File................................................................1-74

1.13.8 Importing a 2D SEG-Y as Surface File ...............................................1-74

1.13.9 Importing a 2D SEG-Y as SGrid File ..................................................1-75

1.14 Importing Well Data ....................................................................................1-76

1.14.1 Importing Well Paths and Logs.........................................................1-76

Importing a Column-Based File ........................................................1-76

Importing a CPS3 ASCII Data (.dat) File ............................................1-76

Importing an Excel File ....................................................................1-77

Importing an Irap RMS File ..............................................................1-78

Importing an LAS File ......................................................................1-79

Importing an RC2 File......................................................................1-84

Importing a Temis3D File .................................................................1-84

Importing a WITSML File..................................................................1-85

Contentsvi SKUA and GOCAD Paradigm 2011With Epos 4.1 Data Management

1.14.2 Importing Well Paths ...................................................................... 1-86

Importing a Column-Based File ....................................................... 1-86

Importing an X Y Z File ................................................................... 1-86

Importing Coordinates from a Column-Based File ............................ 1-86

1.14.3 Importing Well Marker Data from a Column-Based File .................... 1-86

1.14.4 Importing Well Log Data ................................................................. 1-87

Importing Log Data from Column-Based File .................................... 1-87

Importing Log Data from an LAS File ............................................... 1-87

Importing Log Data from an ASCII File with a Header ....................... 1-88

1.14.5 Importing Well Symbol Data ........................................................... 1-89

1.14.6 Importing Well Completion Data ..................................................... 1-90

1.14.7 Importing Well Production Data ...................................................... 1-91

Importing Well Production Data from a General Format User File or VOL File ......................................................................................... 1-91

Importing Well Production Data from an ECLIPSE Column-Based File 1-97

Importing Well Production Data from an ECLIPSE Binary File ........... 1-101

Importing Well Production Data from an ECLIPSE RSM File ............. 1-102

1.15 Importing Cross Section Data .................................................................... 1-104

1.15.1 Importing a DXF File ..................................................................... 1-104

1.15.2 Importing a GeoSec Cross Section File ........................................... 1-104

1.15.3 Importing a Locace File ................................................................. 1-104

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

2.1 Converters.................................................................................................... 2-2

2.2 Basic Procedures for Exporting Data ............................................................... 2-4

2.2.1 Exporting an Object to a Custom ASCII File ....................................... 2-5

2.2.2 Exporting an Object to a DFX File ...................................................... 2-7

2.2.3 Exporting Object Properties to Excel .................................................. 2-7

2.2.4 Exporting an Object to an Isatis File................................................. 2-12

2.2.5 Exporting Curves or 2D Grids to a Medica File ................................. 2-16

2.2.6 Exporting Velocity Data to an AVF File ............................................. 2-17

2.2.7 Exporting Velocity Data to a Velf File ............................................... 2-18

2.3 Exporting PointsSet Data ............................................................................. 2-19

2.4 Exporting Curve Data .................................................................................. 2-20

2.4.1 Exporting a Curve to a FastEdit Fault Polygon File ............................ 2-20

2.4.2 Exporting a Curve to an IRAP File .................................................... 2-21

2.4.3 Exporting a Curve to a SeisWorks Fault Sticks File ............................ 2-21

2.4.4 Exporting a Curve to a Z-MAP Faults File ......................................... 2-22

2.4.5 Exporting a Curve to a Z-MAP Contours File .................................... 2-23

2.5 Exporting Surface Data ............................................................................... 2-24

2.5.1 Exporting a Surface to a CUBIT Facet File......................................... 2-24

2.5.2 Exporting a Surface to a FastEdit File ............................................... 2-25

Contents viiUser Guide


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

2.5.4 Exporting a Surface to a GMI WellCheck MohrFracs File ....................2-26

2.6 Exporting 2D-Grid Data................................................................................2-28

2.6.1 Exporting a 2D-Grid to a CPS3 File ...................................................2-28

2.6.2 Exporting a 2D-Grid to a FastEdit File ...............................................2-29

2.6.3 Exporting 2D-Grid Data to an IRAP File.............................................2-29

2.6.4 Exporting 2D-Grid Data to a Z-MAP File ...........................................2-30

2.7 Exporting Voxet Data ...................................................................................2-31

2.7.1 Exporting a Voxet to a DDS File........................................................2-31

2.7.2 Exporting a Voxet to a SEG-Y File .....................................................2-32

2.7.3 Exporting a Voxet to an SEP File .......................................................2-33

2.7.4 Exporting a Voxet to a VoxelGeo File ................................................2-34

2.8 Exporting Seismic Line Data .........................................................................2-35

2.9 Exporting SGrid Data ...................................................................................2-36

2.9.1 About the Grid Origin .....................................................................2-37

2.9.2 Exporting an SGrid to a CMG File ....................................................2-38

2.9.3 Exporting an SGrid to an ECLIPSE ASCII File ......................................2-43

2.9.4 Exporting an SGrid to an ECLIPSE Binary File.....................................2-51

2.9.5 Exporting an SGrid to a RESCUE File ................................................2-53

2.9.6 Exporting an SGrid to a VIP File........................................................2-54

2.9.7 Exporting an SGrid to a Temis3D (libnf) File ......................................2-59

2.9.8 Exporting LGR Data from an SGrid to a Flow Simulator .....................2-59

2.10 Exporting Well Data .....................................................................................2-64

2.10.1 Exporting a Well to an IRAP File .......................................................2-64

2.10.2 Exporting a Well to an LAS File ........................................................2-65

2.10.3 Exporting Well Markers to an ASCII File............................................2-66

2.10.4 Exporting Well Logs to an ASCII File .................................................2-67

2.11 Exporting a View as an Image ......................................................................2-68

2.11.1 Exporting a View to a CGM File .......................................................2-68

2.11.2 Exporting a View to an Image File ....................................................2-70

2.11.3 Exporting a 3D Viewer Image to a VRML File ....................................2-71

2.12 Exporting an SGrid and Data to an Isatis File .................................................2-73

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

A.1 Import File Formats ....................................................................................... A-2

A.2 Column-Based Formats ................................................................................. A-4

A.3 CMG Formats ............................................................................................... A-5

A.4 CPS3 Formats ............................................................................................... A-6

A.5 ECLIPSE Formats ......................................................................................... A-12

A.6 FastEdit Formats ......................................................................................... A-14

A.7 Irap RMS Formats ....................................................................................... A-16

A.8 LAS Format ................................................................................................ A-20

Contentsviii SKUA and GOCAD Paradigm 2011With Epos 4.1 Data Management

A.9 MPath Formats ........................................................................................... A-22

A.10 SEG-Y Formats............................................................................................ A-26

A.11 SEP Format ................................................................................................. A-28

A.12 Velf Format................................................................................................. A-29

A.13 XYZ Format ................................................................................................ A-30

A.14 Z-MAP Formats ........................................................................................... A-31

A.15 VIP Formats ................................................................................................ A-33

1-1

1Importing Data

In this chapter "Converters and Supported Formats," page 1-2

"Basic Concept for Importing Data," page 1-6

"Common Process for Importing a Column-Based File," page 1-8

"Importing Basin Modeling Files," page 1-15

"Importing Cultural Data," page 1-21

"Importing Fault Interpretations Data," page 1-23

"Importing Fault Surfaces Data," page 1-31

"Importing Horizon Interpretations Data," page 1-34

"Importing Horizon Surface Data," page 1-39

"Importing Image Files," page 1-43

"Importing Reservoir Grid Data," page 1-45

"Importing Seismic Data," page 1-62

"Importing Velocity Data," page 1-73

"Importing Well Data," page 1-76

"Importing Cross Section Data," page 1-104

Overview In Paradigm SKUA and Paradigm GOCAD, you can import many types of data from numerous external sources. For example, you can import data in the form of industry standard formats, raw data, and many formats from other software products. When you import data, you can:

Create a modeling object. Overwrite an existing object. Add property data to an existing object. Overwrite property data in an existing object.

You can find the importing commands from the File menu on the Import submenu. This submenu is organized first by the categories of data you can import and then by the supported programs or data types.

These topics explain how to import the related files and identify the objects that you can create from the imported files.

Paradigm adds support for new formats based on client need. To inquire about new options, contact us at: www.pdgm.com/support.

Importing Data1-2 SKUA and GOCAD Paradigm 2011With Epos 4.1 Data Management

Before you begin The validity and accuracy of the data in your file determines the success of what you import. Therefore, ensure that all files you want to import contain valid data and are in the correct format. Reviewing ASCII files in an editor, like Notepad, before importing is a good idea.

Appendix A, "Import File Formats," identifies the import formats that SKUA and GOCAD support and describes how the converters read the files.

1.1 Converters and Supported FormatsTable 11 identifies the kind of data you can import, the programs or data types, the file name extensions, and objects created from the imported data.

Note The Irap RMS converter supports RMS versions up to version 2009.

Table 11 Converters andresulting objects If you want to

import this type of data

In this data format (or from this program)

With this common extension

You can create these objects

Basin Modeling Medica Fault Polygons .fau Curve

Medica Topographic Surface .g Surface

Medica Topographic Surface Advanced

.g PointsSet, 2D Grid, Surface, Voxet, SGrid

Temis3D Grid .td4 SGrid

Temis3D Colormap Colormap

MPath .act, .fid, .raw, .par PointsSet, Voxet

PetroMod .pmb

Cultural data ArcView .dbf, .shp, and .shx PointsSet, Curve

AutoCAD .dxf PointsSet, Curve, Surface

Seisworks cultural data .asc Curve

Digital Elevation Model (DEM)ER Mapper1

.ers DEM

DEM binary1 DEM

Fault interpretation - points

CPS3 ASCII data .dat PointsSet

CPS3 ASCII polygons .ply PointsSet

CPS3 ASCII fault traces .flt PointsSet

CPS3 binary .svd PointsSet

Column-based file User defined PointsSet

FastEdit scattered data .dat PointsSet

X Y Z User defined PointsSet

Fault interpretation - fault sticks

Charisma fault interpretations Curve

CPS3 ASCII data .dat Curve

CPS3 ASCII polygon .ply Curve

CPS3 ASCII fault traces .flt Curve

CPS3 binary .svd Curve

Column-based file User defined Curve

Petrel pillars .dat Curve

Seisworks fault sticks .dat Curve

Z-MAP fault or contour Curve

(Continued 1 of 4)


1.1 Converters and Supported Formats 1-3User Guide

Fault interpretation - fault polygons or traces

Charisma fault polygons Curve

CPS3 ASCII polygons .ply Curve

FastEdit fault polygons Curve

Irap RMS fault polygons or lines Curve

SeisWorks fault polygons Curve

Fault surfaces CPS3 ASCII 2D-Grid .grd Surface

CPS3 binary .svd, .svs, .svf, .svp Surface

FastEdit 2D grid .dat Surface

Irap RMS triangle surface .dat Surface

Petrel pillars .dat Surface

RC2 2D grid .gz Surface

RESCUE .bin Surface

StrataModel 2D grid .smg Surface

Z-MAP ASCII 2D grid Surface

Horizon interpretation - points

Charisma horizon points .gridexp PointsSet

CPS3 ASCII data .dat PointsSet

CPS3 binary .svd PointsSet

Column-based file PointsSet

FastEdit scattered data .dat PointsSet

GSLib 2D map PointsSet

Seisworks Inline Xline X Y Z .asc PointsSet

X Y Z User defined PointsSet

Horizon interpretation - contours

Adobe contours .esp Curve

CPS3 ASCII data .dat Curve

CPS3 binary .svf, .svp Curve

Column-based file User defined Curve

FastEdit horizon contours .dat Curve

Z-MAP contour .zmap Curve

Horizon surfaces CPS3 ASCII 2D grid .grd 2D Grid

CPS3 binary .svd, .svs, .svf, .svp 2D Grid

FastEdit 2D grid .dat PointsSet, Curve, 2D Grid

Geoprobe 2D grid .gvw 2D Grid

GSLib 2D map Surface

Irap RMS ASCII 2D-grid property 2D Grid properties

Norsar horizons Voxet

RC2 2D grid .gz 2D Grid

RESCUE .bin Surface

StrataModel 2D grid .smg 2D Grid

StrataModel 2D grid property .smg 2D Grid properties

Z-MAP ASCII 2D grid 2D Grid

Z-MAP ASCII 2D grid property 2D Grid properties

Images Images 2D Grid

If you want to import this type of data




(Continued 2 of 4)


Reservoir grid ECLIPSE ASCII grid .grdecl SGrid

ECLIPSE binary grid .grid, .egrid, .init, .unrst

SGrid

RESCUE (grids, horizons, faults) .bin SGrid

VIP ASCII grid .cor SGrid

VIP LGR .lgr SGrid

Reservoir grid - properties

ECLIPSE ASCII properties .grdecl SGrid properties

I J K property SGrid properties

VIP ASCII properties .cor SGrid properties

ECLIPSE ASCII faults SGrid

Reservoir grid - simulation results

CMG IMEX grid properties .irf, .IRF SGrid and properties, wells and properties

ECLIPSE RSM file .rsm SGrid and properties, wells and properties

ECLIPSE binary grid .GRID, .grid, .EGRID, .egrid, .GRD

SGrid and properties

ECLIPSE column-based user file SGrid and properties, wells and properties

Column-based file User defined SGrid and properties, wells and properties

Seismic data - cubes

SEG-Y 3D as voxet .sgy, .segy Voxet

VoxelGeo .vol Voxet

SEP .h Voxet

Norsar depth cube Voxet

Seismic data - lines

2D SEG-Y as SeismicLine .sgy, .segy SeismicLine

Seismic data - color maps

SeisWorks .clr Colormap

Velocity functions Jason ASCII traces

(Jason Geoscience Workbench)

Curve with velocity properties

Promax

TDQ .avf

Velf .velf Curve

Velocity cubes SEG-Y 3D as voxet .sgy, .segy Voxet

SEP .h Voxet

VoxelGeo .vol 2D Grid

Velocity lines 2D SEG-Y as SeismicLine .sgy, .segy SeismicLine

Well data -

path and logs

Column-based file User defined Well

CPS3 ASCII data .dat Well

Excel .xls Well

Irap RMS .log, .decode Well

LAS .las Well

RC2 .gz, .asc, .out Well

Temis3D Well

WITSML .gz, .xml Well





(Continued 3 of 4)


1.1 Converters and Supported Formats 1-5User Guide

Well data - path Columns-based file User defined Well

X Y Z file User defined Well

Locations from column-based file Well

Well data - markers


Well data - logs Column-based file User defined Well

LAS .las Well

ASCII file with header Well

Completion Well

Well data - Symbols

Well status symbols Well

Well data - Completion data

ECLIPSE DATA file .DATA, .data Well


Well data - Production data

ECLIPSE binary files Well properties

ECLIPSE RSM file Well properties

ECLIPSE column-based user file Well properties

Column-based file User defined Well properties

Cross sections DXF .dxf PointsSet, Curve, or Surface

Paradigm Geosec .ihf Curve or PointsSet

Locace .ext Curve

Dip data1 Dip ASCII file with header Dip

Dip column-based file Dip

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.





(Continued 4 of 4)


1.2 Basic Concept for Importing DataFor each importing command requires, you need to enter various options that the converter needs to quickly and accurately import your data files. Some commands require only basic information, such as the name of the file that contains your data, while other require more detailed data.

This section explains the basic importing procedure and the remaining sections in this chapter explain detailed procedures for specific converters.

Important When you import a file to create an object, the name of the new object is the same name as the import file, without the extension. With the exception that the commands comply with the SKUA and GOCAD naming conventions. If you import a file that does not follow the naming conventions, the import command renames the file. For example, an asterisk (*) is not allowed as a part of the file name. If your file is named W1*1, the command renames the file as W1_1. For more information about naming conventions, see Part I: Getting Started, "Naming Objects and Other Items" on page 3-9.

Basic procedure forimporting

1 Select File > Import, point to the data type, and then click the appropriate command. The dialog box for the specific command opens.

For example:

2 Click to open the Select Text File dialog box, browse for the file you want to import, and then double-click the file name.

or

In the File name box, type the full path and file name.


1.2 Basic Concept for Importing Data 1-7User Guide

3 To set the units indicating how the file is to be imported, click Advanced, and then do any of the following:

a If the z-axis value in the file you are importing differs from the default z-axis set for your project, change the domain for this new object. To change the z-axis value from depth to time, or time to depth click the appropriate option.

Note SKUA or GOCAD automatically selects units based on the default z-axis setting (in the New Project dialog box) chosen when the project was created.

b If the units in the file differ from the default units set for your project, select the Specify Units of Selected File check box, and then click the appropriate units.

For information about setting units for your project, see Part I: Getting Started, "Setting Units for a Project" on page 1-19.

4 Click OK or Apply.


1.3 Common Process for Importing a Column-Based FileYou can use the column-based import wizards to import ASCII files for multiple types of data. Depending on the data in your files, you can create objects such as PointsSets, Curves, and Wells, and many types of object properties.

For more information about the types of data that you can import and objects you can create from data in this format, see "Converters and Supported Formats" on page 1-2.

For most column-based data, you can:

Import all or only a portion of a file Import property data Specify a name for new objects (rather than automatically assigning a name or

reading the name from the file)

For point set or curve data, the import wizards create an object from each file that you import. However, for well data, the wizard creates a Well object for each well identified in the file.

The importing process is similar for most of the column-based importing wizards. The following describes the general procedure. Where you encounter differences from this procedure, follow the instructions in the wizard.

Note You can import certain types of data only if you load specific modules with SKUA or GOCAD. For information about data that you can import with a particular module, see the topics that describe the module.

For more information about common settings in column-based import wizards, see:

"To access a column-based importing wizard," page 1-8 "To specify the file type for a column-based file," page 1-9 "Tips for specifying the data type for a column-based file," page 1-10 "To specify the column separation for a column-based file," page 1-11 "To specify miscellaneous information for a column-based file," page 1-12 "To specify the column assignment for a column-based file," page 1-12 "To complete the importing process," page 1-14

For information about specifying additional settings for well production data and time-dependent grid properties, see:

"Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97 "Importing Well Production Data from a General Format User File or VOL File,"

page 1-91

To access a column-based importing

wizard

Select File > Import, and then do one of the following to access the wizard.To import this data

And create this object

Select

Fault interpretations PointsSet Fault Interpretations > PointsSet > Column-based file.

Horizon interpretations PointsSet Horizon Interpretations > PointsSet > Column-based file.

Fault interpretations, fault sticks

Curve Fault Interpretations > Fault Sticks > Column-based file.

Horizon interpretations, contours

Curve Horizon Interpretations > Contours > Column-based file.


1.3 Common Process for Importing a Column-Based File 1-9User Guide

Figure 11 Wizard for importing fault interpretations as a point set

To specify the filetype for a column-

based file

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 Type the path and file name or click , browse for the file or files that you want to import, and then double-click the selected files.

Note In this step, you can select multiple files to import. All of the files that you select appear in the Current file list. Settings that you make for one apply to all of the files in the list. Later, you have the option to import them all with the same settings or import them one at a time, adjusting the settings for each file.

Tip If the data is not what you expect, click Cancel. You can select a different file and then begin the import procedure again, or edit the file in a text editor.

2 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.

3 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.

Well data (X, Y, MD, TVDSS) Well Well Data > Path > Path and Logs > Markers, Logs, or Completion Data (depending upon the type of data in the file) > Column-based file.

Well production data Wells Well Data > Production Data > ECLIPSE User File (column-based) or General Format User File (column-based).

To import this dataAnd create this object

Select


For more information, see "Tips for specifying the data type for a column-based file" on page 1-10.

4 Click Next.

Tips for specifyingthe data type for acolumn-based file

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:

Misaligned data:

In this data, lines 2 and 3 in the "Date" column heading are empty, and the wizard aligns the data as follows:

In this case, specify Fixed width instead.

With the Delimited setting, when you advance to the next page of the wizard (Column Separation) and select delimiters, the columns should be highlighted with alternate colors. For example:

If the columns are not selected as shown, return to the previous page and select Fixed width instead.

If you select Fixed width, when you advance to the next page in the wizard, you can delineate the columns based on fixed field width.

DATE FPRHbarsaFIELD

FWPRHsm^3/dFIELD

FGPRHsm^3/dFIELD

FOPRHsm^3/dFIELD

1/1/1988 397.802 0.0000 0.0 0.001/1/1989 307.55 0.0000 1356750.0 9000.001/1/1990 233.713 0.0000 1217807.5 9000.00

DATEbarsaFIELD

FPRHsm^3/dFIELD

FWPRHsm^3/dFIELD

FGPRHsm^3/dFIELD

FOPRH

1/1/1988 397.802 0.0000 0.0 0.001/1/1989 307.55 0.0000 1356750.0 9000.001/1/1990 233.713 0.0000 1217807.5 9000.00



To specify the columnseparation for a

column-based file

In column-based import wizards, the Column Separation page previews the column structure of the file. Yellow highlighting appears in alternate columns.

Figure 12 Columnseparation for delimitedfault interpretation data

1 Specify the column separation by doing one of the following depending on the data type:

2 Click Next.

Note In the production data importing wizards, the next pages are specific to production data. For information about these pages, see:

"Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97 "Importing Well Production Data from a General Format User File or VOL File," page 1-91

For this data type Do this

Delimited 1 Select one or more of the check boxes: Tab, Semicolon, Comma, Space, and Other. Tab and space are preselected.

Note You can select as many delimiters as needed.

2 If you select Other, type the delimiter in the box.3 To specify a character that separates text from the data, select the

character in the Text qualifier box: double quotation mark, single quotation mark, or none.

4 If the file contains comments, in the Comment string box, type the characters that identify comment text. For example, in a 3DSL file, the percent character (%) indicates a comment.

Fixed width Specify column breaks by clicking within the preview pane to add a column break or double-clicking a break to remove it.


To specifymiscellaneous

information for acolumn-based file

In the column-based importing wizards, the Miscellaneous information page (see example, Figure 13) presents a series of questions, one at a time. The questions vary depending on the type of object data you are importing. Follow the instructions in the wizard to answer the questions.

Note Not all column-based importing wizards include this page. You can skip this section if you do not see this page.

Figure 13 Miscellaneous information for fault interpretation data

1 To answer a question click Yes, No, or another option if a question has other options.

The area to the left of the questions presents additional information to help you answer the questions.

2 When you finish answering all of the questions, click Next.

Note In the example shown,

If there is no x-, y-, or z-column in the file, the wizard automatically assigns a value of zero for that coordinate.

If there is an x-, y-, or z-column, on the next page of the wizard, you need to specify the location of this data in the file.

To specify the columnassignment for a

column-based 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.



Figure 14 Column assignment for fault interpretation data

1 Depending on the option selected on the previous page (under To name the objects), you may type a name for the new object in the Object name box, select a column, or use the file name.

2 In the Start at line box, type the line number or click and pick the line number where you want the converter to start reading the file. Do the same to identify the line number where you want the converter to stop reading the file in the End at line box. The defaults are (1,0) which means read the entire file. (Zero means end-of-file.)

3 Specify the column location for identified properties and parameters. Highlight the value in the Property List and parameters box and then enter the column location number in the Column number box.


4 To add a property or parameter:

a Click Add, type the name (any name you want) in the New Property Name box, and then click OK.

b Select the property or parameter in the list, and then enter the column location number in the Column number box.

The wizard will add the property in your file to the existing object.

5 To remove a property, select the name in the Property List and parameters box and then click Remove.

6 If you want the wizard to read a specific value as a no-data value (a number always read as null), select the Use no-data value check box, and then type the number in the box.

Tip For well production data, use -99999 as the no-data value to prevent null data from appearing as zeros in production plots. For more information about importing production data, see "Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97.

7 If you want to specify the time or depth domain or the units of measurement for the data, click Advanced, and then do the following as necessary:

To specify the domain, click Time or Depth.

To specify units, click the Specify units of selected files check box, and then click options for the area, depth, and depth axis units.

Note The preselected options are those of the current project.

To complete theimporting process

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.

2 Import the data or adjust the settings for additional files as follows:

Tip To save the new objects in your project, remember to save the project.

The wizard creates objects and any object properties from the imported data. You can find the new objects and properties in the Objects browser.

To do this Do this

Import only the file shown in the preview pane and then configure additional files.

1 Click Apply on current file.The wizard imports the data from only the current file.

2 Select another file in the Current file boxThe settings you made are preselected for the other files in the list.

3 Adjust the configuration settings throughout the wizard as necessary.

4 Import the file.

Repeat the process for all of the files in the list.

Import multiple files with the same configuration settings as the current file.

Click OK.The wizard imports the data from all of the files and closes the wizard.


1.4 Importing Basin Modeling Files 1-15User Guide

1.4 Importing Basin Modeling FilesYou can import various types of files that contain basin modeling data in the form of grids or reservoir fluid transport models. You can create SGrid, Voxet, PointsSet, and Colormap objects from these data files.

Supported import sources and how to import the specific files are described in this section.

"Import Temis/Medica Files," page 1-15 "Importing MPath Files," page 1-18 "Importing a PetroMod File," page 1-19

1.4.1 Import Temis/Medica FilesYou can use the Temis1 converters to import fault polygon data and create a Curve object, stratigraphic data to create an SGrid, and topographic data to create a Colormap object.

To import a FaultPolygon 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 aTopographic 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.


To import a Medica2D 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.

2 Click to open the Select Text File dialog box, browse for the file you want to import, and then double-click the file name. The program enters the selected file name in the File name box.

3 If you want the converter to do a calculated best-guess and fill holes where there is missing data in the input file, click Fill holes.

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


4 To select which object type you want the converter to create when importing the file, click one of the following:

Create PointsSet Create Surface. In the Decimation Level box, select how you want the

converter to use the data in the file. None. Keep all points. Level 1. Take into account all data points when creating the Surface. Level 2. Take into account four out of nine points when creating the Surface.

In the Maximum error box, type the value for maximum distance you want the converter to use when computing errors.

Note Values are measured in the units you set for the project. To check the project units: select File > Project Properties.

Create Voxet. In the Property name box, type a name you want the converter to use when storing the data values.

Create SGrid

5 In the Output no data value box, type the value that you want the converter to recognize as a no-data value.

6 If you want to assign a name for the imported file, rather than using the default of having the converter assign a name, click the Use file name check box, and then type a name in the GOCAD object name box.


To import a Temis3DGrid file

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.

2 Click to open the Select Text File dialog box, browse for the file you want to import, and then double-click the file name. The converter enters the selected file name in the Temis3D file box. This should be a visco.t4d file.

As soon as you select the file, the dialog box is updated to show the following:

Roamer (or Age). List of model ages (age of a layer deposition) in the selected file.



Variables. List of Temis3D properties.

Vectors. List of Temis3D vectors.

3 Click one or more entries in the Roamer column. You can create an SGrid for each entry in the list. Hold down the CTRL key to select more than one entry.

4 Click one or more properties in the Variables column.

Note If you select more than one entry in the Roamer column (meaning that you want to create more than one SGrid), all the properties you select in the Variables column are imported for each SGrid.

5 Click one or more entries in the Vectors column.

Note If you select more than one entry in the Roamer column (meaning that you want to create more than one SGrid), all the entries you select in the Vectors column are imported for each SGrid.


To import a Temis3DColormap

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.


3 In the Colormap name box, type the name you want to use for the map. The default name is Temis_Colormap.



1.4.2 Importing MPath FilesYou can use the MPath converters to import reservoir fluid transport models and create Voxet, PointsSet, and Colormap objects.

MPath is a high-resolution fluid transport modeling toolkit available from The Permedia Research Group.

SKUA and GOCAD includes converters for importing four MPath file types:

.act contains data values that represent simulation results at particular points in space .fid contains (in a 3D grid format) flow unit data values for each grid cell in the mode .raw contains single values for each grid cell .par contains petrophysical data values for each identified flow unit in the .fid file

To import MPath .actfile as a Voxet

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.

1 Select File > Import > Basin Modeling > MPath ACT to open the Import Permedia ACT File dialog box.

2 Click to open the Select Text File dialog box, browse for the file you want to import, and then double-click the file name. the converter enters the selected file name in the ACT file box.

3 If you want the converter to create a PointsSet object click PointsSet. By default, the converter imports this file and creates a Voxet object.

4 If you want to also import the related .fid and .par files, select the Import Related .fid and .par File check box.


To import anMPath .raw file as a

Voxet

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.




To import anMPath .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.


To import anMPath .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.


1.4.3 Importing a PetroMod FileUse the PetroMod1 converter to create an SGrid object from a PetroMod binary file that contains basin modeling data.

The converter creates an SGrid object from each file that you import.

To import a PetroModIES file as an SGrid

1 Select File > Import > Basin Modeling > PetroMod to open the Import PetroMod ACT File dialog box.

1. PetroMod is a multi-dimensional modeling software system available from Integrated Exploration Systems (IES).


2 Click to browse for the file you want to import, and then double-click the file name.

3 Specify whether you want to import facies or overlays and create a cell-centered or corner-point grid by clicking one of these:

Facies. Creates a cell-centered SGrid. Overlays. Create a corner-point grid.

4 If you want to specify the domain or units of measurements for data in the selected files, click Advanced and then do the following as necessary:

Click either Time or Depth to specify the domain. Select the Specify units of selected files check box, and then click the

appropriate units for the Area units and Time units.



1.5 Importing Cultural Data 1-21User Guide

1.5 Importing Cultural DataYou can import data files (from various software products) that contain cultural data, primarily in the form of geographical maps.

Cultural data is typically geographical representation data that lets you:

Explore spatial data results Identify location information such as lease blocks


"Importing an ArcView File," page 1-21 "Importing a DXF File," page 1-22 "Importing a SeisWorks Cultural Data File," page 1-22

1.5.1 Importing an ArcView FileUse the ArcView1 converter to create a PointsSet or Curve object from an ArcView Shape (.shp) file that contains cultural topography data.

The converter requires three ASCII files be present for the import process. All three files should have the same name but different file name extensions (.dbf, .shp, and .shx). The file selector looks for only the shape (.shp) file; the other two files are necessary to describe data in the shape file.

If the file contains geometry data for more than one object, the converter creates a PointsSet or Curve object for each set of geometry data.

To import an ArcViewfile

Select File > Import > Cultural Data > Arcview, and then select the file or type the full path and file name in the dialog box.


1. ArcView is a geographic information system available from the Environmental Systems Research Institute (ESRI).


1.5.2 Importing a DXF FileUse the DXF1 converter to create a PointsSet, Curve, or Surface (triangulated surface) object from an AutoCAD .dxf drawing file that contains cultural topography data. The .dxf format is a tagged data representation of all the information contained in an AutoCAD drawing file.

If the file contains geometry data for more than one object, the converter creates a PointsSet, Curve, or Triangulated Surface object for each set of geometry data.

To import a .dxf file 1 Select File > Import > Cultural Data > DXF to open the Import DXF file dialog box.

2 Click to open the Select Text File dialog box, browse for the file you want to import, and then double-click the file name. The converter enters the selected file names in the File name box.

3 Select the Import text check box, if you want to include text as a part of the object.

Note Including text with the object significantly increases processing time.


1.5.3 Importing a SeisWorks Cultural Data FileUse the SeisWorks2 converter to create a Curve object from a SeisWorks (.asc) ASCII file that contains cultural topography data.

If the file contains geometry data for more than one object, the converter creates a Curve object for each set of geometry data.

To import a SeisWorksfile

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.


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


1.6 Importing Fault Interpretations Data 1-23User Guide

1.6 Importing Fault Interpretations DataYou can import various types of files that contain fault interpretation data in the form of points, fault sticks, fault polygons, or traces. You can create PointsSet and Curve objects from these data files.

Fault interpretation modeling lets you:

Evaluate fault surface construction Estimate the temporal evolution of a flat network Appraise fault geometry and displacement Interpret 3D seismic data across a large fault area

The following topics provide information about import sources for each type of object and how to import specific files.

For information about point sets, see:

"Importing a CPS3 ASCII Data (.dat) File," page 1-24 "Importing a CPS3 Binary File," page 1-25 "Importing a Column-Based File," page 1-25 "Importing a FastEdit Scattered Data File," page 1-25 "Importing an XYZ File," page 1-26

For information about fault sticks (Curves), see:

"Importing a Charisma Fault Interpretations File," page 1-26 "Importing a CPS3 ASCII Data (.dat) File," page 1-27 "Importing a CPS3 ASCII Polygons (.ply) File," page 1-27 "Importing a CPS3 ASCII Fault Traces (.flt) File," page 1-27 "Importing a CPS3 Binary File," page 1-27 "Importing a Column-Based File," page 1-28 "Importing a SeisWorks Fault Sticks File," page 1-28 "Importing a Z-MAP Fault or Contour File," page 1-28

For information about fault polygons or traces (Curves), see:

"Importing a Charisma Fault Polygons File," page 1-29 "Importing a CPS3 ASCII Polygons (.ply) File," page 1-29 "Importing a FastEdit Fault Polygons File," page 1-30 "Importing an Irap RMS Fault Polygons or Lines File," page 1-30 "Importing a SeisWorks Fault Polygon File," page 1-30


1.6.1 Importing a CPS3 ASCII Data (.dat) FileYou will use the CPS31 ASCII Data converter to import a .dat ASCII file that contains fault, horizon, or well data. You determine which object to create based on the type of data in the .dat file, and then select the appropriate object in the import dialog box.

If your file contains fault interpretations points, the converter creates one PointsSet object from each file that you import.

To import a .dat fileas a PointsSet, aCurve, or a Well

1 Select File > Import >, and then do one of the following to open the dialog box.

Either choice opens the same dialog box.


3 Do one of the following:

To create a PointsSet object, click Import as PointsSet.

To create a Curve object, click Curve.

To create a Well object, click Well.


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


To create this type of object

Do this

Fault interpretations PointsSet Select Fault Interpretations > PointsSet > CPS3 ASCII Data (.dat).

Horizon interpretations PointsSet Select Horizon Interpretations > PointsSet > CPS3 ASCII Data (.dat).

Fault interpretations, fault sticks Curve Select Fault Interpretations >Fault Sticks > CPS3 ASCII Data (.dat).

Horizon interpretations, contours

Curve Select Horizon Interpretations > Contours > CPS3 ASCII Data (.dat).

Well data (X, Y, TVDSS) Well Select Well Data > Path and Logs > CPS3 ASCII Data (.dat).



1.6.2 Importing a CPS3 Binary FileYou can use the CPS3 binary converter to create a PointsSet, Curve, or 2D Grid object from a CPS3 binary file. However, if your file contains fault points, the converter expects to read an .svd file and create a PointsSet object. The converter creates one object from each imported file.

To import a CPS3binary .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.


1.6.3 Importing a Column-Based FileYou can use a column-based file wizard to import fault interpretation data (from an ASCII file) and create a PointsSet object (or a Curve or Well object), depending on the type of data in your file.

The procedure is similar whether you are importing Curve, PointsSet, or Well data. For information, see "Common Process for Importing a Column-Based File" on page 1-8.

1.6.4 Importing a FastEdit Scattered Data FileUse the FastEdit Scattered Data converter to create a PointsSet from a FastEdit scattered data file.

To import a FastEditScattered Data file as

a PointsSet

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.



1.6.5 Importing an XYZ FileUse the X Y Z file converter to create a PointsSet object from a fault interpretation X, Y, Z ASCII data file. Each line in the file becomes a point in the PointsSet object, with the three data values as X, Y, and Z coordinates.

To import an X, Y, ZASCII file as a

PointsSet

1 Select File > Import > Fault Interpretations > PointsSets > X Y Z to open the Import X Y Z ASCII File dialog box.


3 If you want the converter to ignore points with no data value, select the ignore points with no data value check box, and in the no data value box, type the null value. By default the converter considers all points to be active. The default no-data-value is -9999. The no-data-value option is unavailable unless you select the ignore points with no data value check box.


1.6.6 Importing a Charisma Fault Interpretations FileUse the Charisma1 Fault Interpretations converter to create a Curve object from a Charisma ASCII file. The converter creates a Curve object for each import file.

To import a Charismafile 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. Charisma is a part of the GeoFrame software product available from Schlumberger.



1.6.7 Importing a CPS3 ASCII Data (.dat) FileYou will use the CPS3 ASCII Data converter to import .dat data and create a PointsSet, Curve, or Well object. For information about how to import this type of file, see "Importing a CPS3 ASCII Data (.dat) File" on page 1-24.

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

1.6.8 Importing a CPS3 ASCII Polygons (.ply) FileUse the CPS3 ASCII Polygons converter to create a PointsSet object from the X, Y data coordinates in a CPS3 ASCII Polygons (.ply) file. The converter creates a PointsSet object for each import file.

To import a .ply file asa PointsSet

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.


1.6.9 Importing a CPS3 ASCII Fault Traces (.flt) File Use the CPS3 ASCII Fault Traces converter to create a Curve object from a CPS3 ASCII Fault Trace (.flt) file. The converter creates a Curve object for each import file.

To import a .flt file asa Curve

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.


1.6.10 Importing a CPS3 Binary FileYou can use the CPS3 Binary converter to create a PointsSet, Curve, or 2D-Grid object from a CPS3 binary file. However, if your file contains fault sticks data, the converter expects to read an .svf file and create a Curve object.

The converter creates a new object for each import file.

To import a CPS3binary .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.



1.6.11 Importing a Column-Based FileYou can use a column-based file wizard to import fault stick data (from an ASCII file) and create a Curve object (or a PointsSet or Well object), depending on the type of data in your file.

The procedure is similar whether you are importing Well, PointsSet, or Curve data. For information, see "Common Process for Importing a Column-Based File" on page 1-8.

1.6.12 Importing a Petrel Pillars FileUse the Petrel1 Pillars converter to create a Curve object from a Petrel Pillars file.

To import a PetrelPillars 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.


1.6.13 Importing a SeisWorks Fault Sticks FileUse the Seisworks2 fault sticks converter to create a Curve object from a SeisWorks fault sticks file.

To import a SeisWorksfault sticks file as a

Curve

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.


1.6.14 Importing a Z-MAP Fault or Contour FileUse the ZMAP3 Fault or Contour converter to create a Curve object from a Zmap fault or contour file.

To import a Zmapfault traces or

contour file as aCurve

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.


1. Petrel is a software product available from Schlumberger.2. SeisWorks is a software product available from Landmark Graphics.3. Z-Map is a software product available from Landmark Graphics.



1.6.15 Importing a Charisma Fault Polygons FileUse the Charisma Fault Polygons converter to create a Curve object from a Charisma Fault Polygons ASCII file. The converter creates one Curve object from each file.

To import a CharismaFault Polygon file as a

Curve

1 Select File > Import > Fault Interpretations > Fault Polygons (Curves) > Charisma Fault Polygons to open the Import ASCII Charisma Fault Polygon To Curve dialog box.


3 Type the number that represents the distance between two segment extremities in the maximum closure distance box. If the distance between two segment extremities is within this number, the two extremities will be linked. The default is 25.

4 Type the no-data-value in the value when undefined box. The default is 0.

5 Clear the Use prefix check box if you do not want each Curve object imported from this file to have the same prefix. The check box is selected by default (meaning each Curve object will have the same prefix).

6 If you chose to use a prefix, type the prefix you want in the Fault prefix box.


1.6.16 Importing a CPS3 ASCII Polygons (.ply) FileUse the CPS3 ASCII Polygons converter to create a Curve object from a .ply file. The converter creates one PointsSet object per import file.

To import a CPS3Polygons 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.



1.6.17 Importing a FastEdit Fault Polygons FileUse the FastEdit Fault Polygons converter to create a Curve object from a FastEdit fault polygons file.

To import a FastEditfault 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.


1.6.18 Importing an Irap RMS Fault Polygons or Lines FileUse the Irap1 RMS Fault Polygons or Lines converter to create a Curve object from an Irap RMS lines file. The converter can import either the Irap RMS Classic or Mapping format. The converter creates one Curve object from each import file.

To import an Irap RMSfile as a Curve

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.


1.6.19 Importing a SeisWorks Fault Polygon FileUse the SeisWorks2 Fault Polygon converter to create a Curve object from a SeisWorks fault polygon file. The converter expects to read X and Y coordinates file in the SeisWorks default export format.

To import a SeisWorksFault 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.


1. IRAP RMS is a software product available from ROXAR.2. SeisWorks is a software product available from Landmark Graphics.


1.7 Importing Fault Surfaces Data 1-31User Guide

1.7 Importing Fault Surfaces DataSKUA or GOCAD includes converters for importing various files that contain fault surface data in the form of grids, triangle surface, or pillars. You can create Surface objects from these data files.


"Importing a CPS3 ASCII 2D-Grid (.grd) File," page 1-31 "Importing a CPS3 Binary File," page 1-31 "Importing a FastEdit 2D-Grid File," page 1-31 "Importing an Irap RMS Triangle Surface File," page 1-32 "Importing a Petrel Pillars File," page 1-32 "Importing a RC2 2D-Grid File," page 1-32 "Importing a RESCUE Model File," page 1-32 "Importing a Z-MAP ASCII 2D-Grid File," page 1-33

1.7.1 Importing a CPS3 ASCII 2D-Grid (.grd) FileUse the CPS3 ASCII 2D-Grid converter to create a 2D-Grid (gridded surface) object from a CPS3 grid (.grd) file. The converter creates a new 2D-Grid object for each import file.

To import a CPS3 .grdfile as a 2D-Grid

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.


1.7.2 Importing a CPS3 Binary FileYou can use the CPS3 Binary converter to create a new PointsSet, Curve, or 2D-Grid object from a CPS3 binary file. If your file contains fault surface data, the converter creates a Surface object. The converter creates one object from each import file.

To import a CPS3binary .svs file as a

2D-Grid

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.


1.7.3 Importing a FastEdit 2D-Grid FileUse the FastEdit 2D-Grid converter to create a 2D-Grid object from a FastEdit file.

To import a FastEdit2D grid file as a 2D-

Grid

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.



1.7.4 Importing an Irap RMS Triangle Surface FileUse the Irap RMS Triangle Surface converter to create a Surface (triangulated surface) object from an Irap RMS Triangle Surface file.

To import an Irap RMSTriangleSurface file as

a Surface

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.


1.7.5 Importing a Petrel Pillars FileUse the Petrel1 Pillars converter to create a Surface object from a Petrel Pillars file.

To import a PetrelPillars 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.


1.7.6 Importing a RC2 2D-Grid FileUse the RC22 2D-Grid converter to create a 2D-Grid object from an RC2 file.

To import an RC22DGrid file as a 2D

Grid

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.


Importing a RESCUEModel File

Use the RESCUE Model converter to import a .bin file. Depending on the type of data in your file, you can:

Create an SGrid object Create a Surface object Add property data to an existing SGrid object.

The converter imports grid data as an SGrid object and horizon or fault data as a girded Surface object (2D Grid).

RESCUE, a Joint Industry Project managed by the Petrotechnical Open Software Corporation (POSC), is an acronym for REServoir Characterization Using Epicentre.

A RESCUE file is typically composed of multiple file types. The converter reads only files with a .bin file extension, and only files produced up to and including RESCUE Version 37.

Output from a RESCUE project typically contains different types of data: surfaces, grids and properties. The converter can import grids, horizons, faults and properties.

Note The converter can read only horizons or faults that are represented by a regular I, J grid. This converter cannot import Well data.

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


1.7 Importing Fault Surfaces Data 1-33User Guide

To import a RESCUEfile as an SGrid orSurface (2D Grid)

1 Select File > Import > Reservoir Grid > RESCUE Model (Grids, Horizons, Faults) to open the Import RESCUE as SGrid dialog box.

2 Click to browse for and select the file you want to import.

3 If the data includes stratigraphic units and the logical order for those units, the command creates a stratigraphic column resource from the data in the file. In the New stratigraphic column name box, type a name for this new resource. (After the import, you can find it in the Resources browser.)

4 Specify whether you want to load the following data:

Load reservoir grid. Imports the grid and creates and SGrid object. Load properties. Imports property data as object properties. Load horizon and fault surfaces. Imports horizons and faults as triangulated

surfaces, gridded surfaces, point sets, and curves. If you deselect this option, the command imports all horizon and fault data as 2D-Grid Surface objects.

5 If you want to extract fault block information from imported grid, in the Advanced area, select the Recreate fault blocks check box.


1.7.7 Importing a Z-MAP ASCII 2D-Grid FileYou can use the Z-MAP1 converter to create a 2D-Grid object from a Z-MAP.

To import a Z-MAP 2Dgrid 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.


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


1.8 Importing Horizon Interpretations DataSKUA and GOCAD include converters for importing various files that contain horizon interpretation data in the form of points, contours, or grids. You can create Point Sets, Curves, or 2D-Grid objects from these data files.

The following topics provide information about supported import sources for specific objects and how to import the files.

For information about point sets, see:

"Importing a Charisma Horizon Points File," page 1-34 "Importing a CPS3 ASCII Data (.dat) File," page 1-35 "Importing a CPS3 Binary File," page 1-35 "Importing a Column-Based File," page 1-35 "Importing a FastEdit Scattered Data File," page 1-35 "Importing a GSLib 2D Map File," page 1-35 "Importing a SeisWorks Inline Xline X Y Z File," page 1-36 "Importing an X, Y, Z File," page 1-36

For information about contours (Curves), see:

"Importing an Adobe Contours File," page 1-37 "Importing a CPS3 ASCII Data (.dat) File," page 1-37 "Importing a CPS3 Binary File," page 1-37 "Importing a Column-Based File," page 1-37 "Importing a FastEdit Horizon Contour File," page 1-37 "Importing a Z-MAP Contour File," page 1-38

1.8.1 Importing a Charisma Horizon Points FileUse the Charisma Horizon Points converter to create a PointsSet object from a Charisma ASCII file. The converter creates a PointsSet object from each import file.

To import a Charismafile 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.



1.8 Importing Horizon Interpretations Data 1-35User Guide

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

1.8.3 Importing a CPS3 Binary FileYou can use the CPS3 Binary converter to create a PointsSet, Curve, or 2D-Grid object from a CPS3 binary file. However, if your file contains horizon points data, the converter expects to read an .svd file and create a PointsSet object. The converter creates one object from each import

2 import export

Documents

paradigm andor

paradigm products

paradigm logo

united states of america

united states code

data import

patent numbers

paradigms actual damages