SCUA-GOCAD Import-Export.pdf

Full text

(1)SKUA® and GOCAD® User Guide. Part II: Data Import and Export.

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

(3) Contents. Part II: Data Import and Export 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.5. 1.6. 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. 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. Importing Fault Interpretations Data .............................................................1-23 1.6.1. Importing a CPS3 ASCII Data (.dat) File ...........................................1-24. 1.6.2. Importing a CPS3 Binary File ............................................................1-25. 1.6.3. Importing a Column-Based File ........................................................1-25. 1.6.4. Importing a FastEdit Scattered Data File ...........................................1-25. 1.6.5. Importing an XYZ File ......................................................................1-26. 1.6.6. Importing a Charisma Fault Interpretations File .................................1-26. 1.6.7. Importing a CPS3 ASCII Data (.dat) File ............................................1-27. 1.6.8. Importing a CPS3 ASCII Polygons (.ply) File.......................................1-27. 1.6.9. Importing a CPS3 ASCII Fault Traces (.flt) File ....................................1-27. 1.6.10 Importing a CPS3 Binary File ............................................................1-27 1.6.11 Importing a Column-Based File ........................................................1-28 1.6.12 Importing a Petrel Pillars File ............................................................1-28 1.6.13 Importing a SeisWorks Fault Sticks File .............................................1-28. Contents. iii.

(4) 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. 1.8. 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. 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.3. Importing a CPS3 Binary 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.11 Importing a CPS3 Binary 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.2. Importing a CPS3 Binary File ........................................................... 1-39. 1.9.3. Importing a FastEdit 2D-Grid File ..................................................... 1-40. 1.9.4. Importing a Geoprobe 2D Grid (.gvw) File ....................................... 1-40. 1.9.5. Importing a GSLib 2D Map as Surface File ....................................... 1-40. 1.9.6. Importing an Irap RMS ASCII 2D-Grid File ........................................ 1-40. 1.9.7. Importing an Irap RMS ASCII 2D-Grid Property File ........................... 1-41. 1.9.8. Importing a Norsar Horizons File ..................................................... 1-41. 1.9.9. Importing an RC2 2D-Grid File ........................................................ 1-41. 1.9.10 Importing a RESCUE Model File ....................................................... 1-42 1.9.11 Importing a Z-MAP ASCII 2D-Grid File ............................................. 1-42 1.9.12 Importing a Z-MAP ASCII 2D-Grid Property File ................................ 1-42. iv. Contents. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

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

(6) 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. Contents. 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.5. vi. 2.2.1. 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. 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. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(7) Part II: Data Import and Export. 2.6. 2.7. 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. 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. 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.10. 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. 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. Appendix A. User Guide. Exporting an SGrid and Data to an Isatis File .................................................2-73. 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. Contents. vii.

(8) viii. Contents. 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. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(9) 1 Importing Data. In this chapter. Overview. •. "Converters and Supported Formats," page 1-2. •. "Importing Horizon Interpretations Data," page 1-34. •. "Basic Concept for Importing Data," page 1-6. •. "Importing Horizon Surface Data," page 1-39. •. "Common Process for Importing a Column-Based File," page 1-8. •. "Importing Image Files," page 1-43. •. •. "Importing Basin Modeling Files," page 1-15. "Importing Reservoir Grid Data," page 1-45. •. •. "Importing Seismic Data," page 1-62. "Importing Cultural Data," page 1-21. •. •. "Importing Velocity Data," page 1-73. "Importing Fault Interpretations Data," page 1-23. •. "Importing Well Data," page 1-76. •. "Importing Fault Surfaces Data," page 1-31. •. "Importing Cross Section Data," page 1-104. In Paradigm™ SKUA ® and Paradigm™ GOCAD ® , you can import many types of data from numerous external sources. For example, you can import data in the form of industry standard formats, raw data, and many formats from other software products. When you import data, you can:. • • • •. Create a modeling object. Overwrite an existing object. Add property data to an existing object. Overwrite property data in an existing object.. You can find the importing commands from the File menu on the Import submenu. This submenu is organized first by the categories of data you can import and then by the supported programs or data types. These topics explain how to import the related files and identify the objects that you can create from the imported files. Paradigm adds support for new formats based on client need. To inquire about new options, contact us at: www.pdgm.com/support.. 1-1.

(10) Before you begin. The validity and accuracy of the data in your file determines the success of what you import. Therefore, ensure that all files you want to import contain valid data and are in the correct format. Reviewing ASCII files in an editor, like Notepad, before importing is a good idea. Appendix A, "Import File Formats," identifies the import formats that SKUA and GOCAD support and describes how the converters read the files.. 1.1. Converters and Supported Formats Table 1–1 identifies the kind of data you can import, the programs or data types, the file name extensions, and objects created from the imported data. Note The Irap RMS converter supports RMS versions up to version 2009.. Table 1–1 Converters and resulting 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. Cultural data. Colormap. MPath. .act, .fid, .raw, .par. PetroMod. .pmb. ArcView. .dbf, .shp, and .shx. AutoCAD. .dxf. PointsSet, Curve, Surface. Seisworks cultural data. .asc. Curve. Digital Elevation Model (DEM) ER Mapper 1. .ers. DEM. Fault interpretation fault sticks. PointsSet, Curve. DEM. DEM binary1 Fault interpretation points. PointsSet, Voxet. 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. XYZ. User defined. Charisma fault interpretations. PointsSet 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-2. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(11) Part II: Data Import and Export. If you want to import this type of data Fault interpretation fault polygons or traces. Fault surfaces. In this data format (or from this program). With this common extension. Charisma fault polygons CPS3 ASCII polygons. Curve .ply. FastEdit fault polygons Irap RMS fault polygons or lines. Curve. SeisWorks fault polygons. Curve. CPS3 ASCII 2D-Grid. .grd. 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. .bin. Surface. StrataModel 2D grid. .smg. Surface Surface. Charisma horizon points. .gridexp. PointsSet. CPS3 ASCII data. .dat. PointsSet. CPS3 binary. .svd. FastEdit scattered data. .dat. PointsSet. Seisworks Inline Xline X Y Z. .asc. PointsSet. XYZ. User defined. PointsSet. PointsSet. 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 Curve. Z-MAP contour. .zmap. 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 Images. PointsSet PointsSet. GSLib 2D map. Horizon surfaces. Surface. RESCUE. Column-based file. Horizon interpretation contours. Curve Curve. Z-MAP ASCII 2D grid Horizon interpretation points. You can create these objects. 2D Grid. Z-MAP ASCII 2D grid property. 2D Grid properties. Images. 2D Grid (Continued 2 of 4). User Guide. 1.1 Converters and Supported Formats. 1-3.

(12) 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. Reservoir grid. ECLIPSE ASCII grid. .grdecl. SGrid. ECLIPSE binary grid. .grid, .egrid, .init, .unrst. SGrid. Reservoir grid properties. RESCUE (grids, horizons, faults). .bin. SGrid. VIP ASCII grid. .cor. SGrid. VIP LGR. .lgr. SGrid. ECLIPSE ASCII properties. .grdecl. I J K property VIP ASCII properties. .cor. SGrid properties. ECLIPSE ASCII faults Reservoir grid simulation results. SGrid. 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. Seismic data cubes. SGrid properties SGrid properties. SGrid and properties, wells and properties. Column-based file. User defined. SGrid and properties, wells and properties. 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. 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. 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. .gz, .xml. Well. Temis3D WITSML. Well (Continued 3 of 4). 1-4. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(13) Part II: Data Import and Export. If you want to import this type of data. In this data format (or from this program). With this common extension. Well data - path. Columns-based file. User defined. Well. X Y Z file. User defined. Well. User defined. Well. Locations from column-based file Well data markers Well data - logs. Column-based file. You can create these objects. Well. 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. Column-based file. User defined. Well. Well data Production data. ECLIPSE binary files. Well properties. ECLIPSE RSM file. Well properties. ECLIPSE column-based user file Cross sections. 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 ASCII file with header. Dip. Dip column-based file. Dip (Continued 4 of 4). 1. Importing a DEM or Dip data requires the Structural Analysis (Kine3D-1) module. For more information about importing a DEM or Dip, see Part VII: Geologic Interpretation, "Importing a DEM" on page 4-13 or "Importing Dip Data" on page 4-30.. User Guide. 1.1 Converters and Supported Formats. 1-5.

(14) 1.2. Basic Concept for Importing Data For each importing command requires, you need to enter various options that the converter needs to quickly and accurately import your data files. Some commands require only basic information, such as the name of the file that contains your data, while other require more detailed data. This section explains the basic importing procedure and the remaining sections in this chapter explain detailed procedures for specific converters.. Important When you import a file to create an object, the name of the new object is the same name as the import file, without the extension. With the exception that the commands comply with the SKUA and GOCAD naming conventions. If you import a file that does not follow the naming conventions, the import command renames the file. For example, an asterisk (*) is not allowed as a part of the file name. If your file is named W1*1, the command renames the file as W1_1. For more information about naming conventions, see Part I: Getting Started, "Naming Objects and Other Items" on page 3-9. Basic procedure for importing. 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-6. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(15) Part II: Data Import and Export. 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. User Guide. Click OK or Apply.. 1.2 Basic Concept for Importing Data. 1-7.

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

(17) Part II: Data Import and Export. To import this data. And create this object. Well data (X, Y, MD, TVDSS). Well. Well Data > Path > Path and Logs > Markers, Logs, or Completion Data (depending upon the type of data in the file) > Column-based file.. Well production data. Wells. Well Data > Production Data > ECLIPSE User File (column-based) or General Format User File (column-based).. Select. Figure 1–1 Wizard for importing fault interpretations as a point set. To specify the file type for a columnbased 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.. User Guide. 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.. 1.3 Common Process for Importing a Column-Based File. 1-9.

(18) For more information, see "Tips for specifying the data type for a column-based file" on page 1-10. 4. Tips for specifying the data type for a column-based file. 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. 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.. 1-10. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(19) Part II: Data Import and Export. To specify the column separation 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 1–2 Column separation for delimited fault interpretation data. 1. Specify the column separation by doing one of the following depending on the data type: For this data type. Do this. Delimited. 1. Select one or more of the check boxes: Tab, Semicolon, Comma, Space, and Other. Tab and space are preselected. Note You can select as many delimiters as needed.. 2 3. 4. Fixed width. 2. If you select Other, type the delimiter in the box. 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. 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.. 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.3 Common Process for Importing a Column-Based File. 1-11.

(20) To specify miscellaneous information for a column-based file. In the column-based importing wizards, the Miscellaneous information page (see example, Figure 1–3) 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 1–3 Miscellaneous information for fault interpretation data. 1. To answer a question click Yes, No, or another option if a question has other options. The area to the left of the questions presents additional information to help you answer the questions.. 2. When you finish answering all of the questions, click Next.. Note In the example shown,. • •. To specify the column assignment for a column-based file. 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 1–4), you need to specify the location of the items in the file. Note This page is not exactly the same in all column-based import wizards, and not all wizards include this page. Where you encounter differences, follow the instructions in the wizard.. 1-12. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(21) Part II: Data Import and Export. Figure 1–4 Column assignment for fault interpretation data. User Guide. 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.. 1.3 Common Process for Importing a Column-Based File. 1-13.

(22) 4. To add a property or parameter: a. Click Add, type the name (any name you want) in the New Property Name box, and then click OK.. b. Select the property or parameter in the list, and then enter the column location number in the Column number box.. The wizard will add the property in your file to the existing object. 5. To remove a property, select the name in the Property List and parameters box and then click Remove.. 6. If you want the wizard to read a specific value as a no-data value (a number always read as null), select the Use no-data value check box, and then type the number in the box. Tip For well production data, use -99999 as the no-data value to prevent null data from appearing as zeros in production plots. For more information about importing production data, see "Importing Well Production Data from an ECLIPSE Column-Based File," page 1-97.. 7. If you want to specify the time or depth domain or the units of measurement for the data, click Advanced, and then do the following as necessary:. •. To specify the domain, click Time or Depth.. •. To specify units, click the Specify units of selected files check box, and then click options for the area, depth, and depth axis units.. Note The preselected options are those of the current project.. To complete the importing process. Tip To save the new objects in your project, remember to save the project.. 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.. 2. Import the data or adjust the settings for additional files as follows: To do this. Do this. Import only the file shown in the preview pane and then configure additional files.. 1. 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.. Click Apply on current file. The wizard imports the data from only the current file. 2 Select another file in the Current file box The settings you made are preselected for the other files in the list. 3 Adjust the configuration settings throughout the wizard as necessary. 4 Import the file. Repeat the process for all of the files in the list.. The wizard creates objects and any object properties from the imported data. You can find the new objects and properties in the Objects browser.. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(23) Part II: Data Import and Export. 1.4. Importing Basin Modeling Files You can import various types of files that contain basin modeling data in the form of grids or reservoir fluid transport models. You can create SGrid, Voxet, PointsSet, and Colormap objects from these data files. Supported import sources and how to import the specific files are described in this section.. • • •. 1.4.1. "Import Temis/Medica Files," page 1-15 "Importing MPath Files," page 1-18 "Importing a PetroMod File," page 1-19. Import Temis/Medica Files You can use the Temis1 converters to import fault polygon data and create a Curve object, stratigraphic data to create an SGrid, and topographic data to create a Colormap object.. To import a Fault 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.. 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.. User Guide. 1.4 Importing Basin Modeling Files. 1-15.

(24) 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.. • •. 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. 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.. 7. 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.. 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:. •. 1-16. Importing Data. Roamer (or Age). List of model ages (age of a layer deposition) in the selected file.. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(25) Part II: Data Import and Export. •. 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.. 6. 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.. 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. In the Colormap name box, type the name you want to use for the map. The default name is Temis_Colormap.. 4. Click OK or Apply.. 1.4 Importing Basin Modeling Files. 1-17.

(26) 1.4.2. Importing MPath Files You can use the MPath converters to import reservoir fluid transport models and create Voxet, PointsSet, and Colormap objects. MPath is a high-resolution fluid transport modeling toolkit available from The Permedia Research Group. SKUA and GOCAD includes converters for importing four MPath file types:. • • • • To import MPath .act file as a Voxet. .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. 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.. 5. 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.. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(27) Part II: Data Import and Export. 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. Importing a PetroMod File Use the PetroMod1 converter to create an SGrid object from a PetroMod binary file that contains basin modeling data. The converter creates an SGrid object from each file that you import.. To import a PetroMod IES 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).. User Guide. 1.4 Importing Basin Modeling Files. 1-19.

(28) 2. Click 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:. • • 4. 1-20. Importing Data. Facies. Creates a cell-centered SGrid. Overlays. Create a corner-point grid.. 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:. • • 5. to browse for the file you want to import, and then double-click the file. 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.. Click OK or Apply.. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(29) Part II: Data Import and Export. 1.5. Importing Cultural Data You can import data files (from various software products) that contain cultural data, primarily in the form of geographical maps. Cultural data is typically geographical representation data that lets you:. • •. Explore spatial data results Identify location information such as lease blocks. Supported import sources and how to import the specific files are described in this section.. • • •. 1.5.1. "Importing an ArcView File," page 1-21 "Importing a DXF File," page 1-22 "Importing a SeisWorks Cultural Data File," page 1-22. Importing an ArcView File Use the ArcView 1 converter to create a PointsSet or Curve object from an ArcView Shape (.shp) file that contains cultural topography data. The converter requires three ASCII files be present for the import process. All three files should have the same name but different file name extensions (.dbf, .shp, and .shx). The file selector looks for only the shape (.shp) file; the other two files are necessary to describe data in the shape file. If the file contains geometry data for more than one object, the converter creates a PointsSet or Curve object for each set of geometry data.. To import an ArcView 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.5 Importing Cultural Data. 1-21.

(30) 1.5.2. Importing a DXF File Use the DXF1 converter to create a PointsSet, Curve, or Surface (triangulated surface) object from an AutoCAD .dxf drawing file that contains cultural topography data. The .dxf format is a tagged data representation of all the information contained in an AutoCAD drawing file. If the file contains geometry data for more than one object, the converter creates a PointsSet, Curve, or Triangulated Surface object for each set of geometry data.. To import a .dxf file. 1. Select File > Import > Cultural Data > DXF to open the Import DXF file dialog box.. 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.. 4. 1.5.3. Click OK or Apply.. Importing a SeisWorks Cultural Data File Use the SeisWorks2 converter to create a Curve object from a SeisWorks (.asc) ASCII file that contains cultural topography data. If the file contains geometry data for more than one object, the converter creates a Curve object for each set of geometry data.. To import a SeisWorks 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. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

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

(32) 1.6.1. Importing a CPS3 ASCII Data (.dat) File You will use the CPS3 1 ASCII Data converter to import a .dat ASCII file that contains fault, horizon, or well data. You determine which object to create based on the type of data in the .dat file, and then select the appropriate object in the import dialog box. If your file contains fault interpretations points, the converter creates one PointsSet object from each file that you import.. To import a .dat file as a PointsSet, a Curve, or a Well. 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. 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).. Do this. Either choice opens the same 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. Do one of the following:. 4. •. To create a PointsSet object, click Import as PointsSet.. •. To create a Curve object, click Curve.. •. To create a Well object, click Well.. Click OK or Apply.. 1. CPS3 (a mapping system) is a part of the GeoFrame software product available from Schlumberger.. 1-24. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(33) Part II: Data Import and Export. 1.6.2. Importing a CPS3 Binary File You can use the CPS3 binary converter to create a PointsSet, Curve, or 2D Grid object from a CPS3 binary file. However, if your file contains fault points, the converter expects to read an .svd file and create a PointsSet object. The converter creates one object from each imported file.. To import a CPS3 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. Importing a Column-Based File You can use a column-based file wizard to import fault interpretation data (from an ASCII file) and create a PointsSet object (or a Curve or Well object), depending on the type of data in your file. The procedure is similar whether you are importing Curve, PointsSet, or Well data. For information, see "Common Process for Importing a Column-Based File" on page 1-8.. 1.6.4. Importing a FastEdit Scattered Data File Use the FastEdit Scattered Data converter to create a PointsSet from a FastEdit scattered data file.. To import a FastEdit 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.6 Importing Fault Interpretations Data. 1-25.

(34) 1.6.5. Importing an XYZ File Use the X Y Z file converter to create a PointsSet object from a fault interpretation X, Y, Z ASCII data file. Each line in the file becomes a point in the PointsSet object, with the three data values as X, Y, and Z coordinates.. To import an X, Y, Z ASCII file as a PointsSet. 1.6.6. 1. Select File > Import > Fault Interpretations > PointsSets > X Y Z to open the Import X Y Z ASCII 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 program enters the selected file name in the File name 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-datavalue is -9999. The no-data-value option is unavailable unless you select the ignore points with no data value check box.. 4. Click OK or Apply.. Importing a Charisma Fault Interpretations File Use the Charisma 1 Fault Interpretations converter to create a Curve object from a Charisma ASCII file. The converter creates a Curve object for each import file.. To import a Charisma 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. Charisma is a part of the GeoFrame software product available from Schlumberger.. 1-26. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(35) Part II: Data Import and Export. 1.6.7. Importing a CPS3 ASCII Data (.dat) File You will use the CPS3 ASCII Data converter to import .dat data and create a PointsSet, Curve, or Well object. For information about how to import this type of file, see "Importing a CPS3 ASCII Data (.dat) File" on page 1-24. If your file contains fault sticks data, the converter creates a Curve object from each file that you import.. 1.6.8. Importing a CPS3 ASCII Polygons (.ply) File Use the CPS3 ASCII Polygons converter to create a PointsSet object from the X, Y data coordinates in a CPS3 ASCII Polygons (.ply) file. The converter creates a PointsSet object for each import file.. To import a .ply file as a 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.. For more information about how to complete the importing process, see "Basic procedure for importing" on page 1-6.. 1.6.9. Importing a CPS3 ASCII Fault Traces (.flt) File Use the CPS3 ASCII Fault Traces converter to create a Curve object from a CPS3 ASCII Fault Trace (.flt) file. The converter creates a Curve object for each import file.. To import a .flt file as a 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.. For more information about how to complete the importing process, see "Basic procedure for importing" on page 1-6.. 1.6.10. Importing a CPS3 Binary File You can use the CPS3 Binary converter to create a PointsSet, Curve, or 2D-Grid object from a CPS3 binary file. However, if your file contains fault sticks data, the converter expects to read an .svf file and create a Curve object. The converter creates a new object for each import file.. To import a CPS3 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.6 Importing Fault Interpretations Data. 1-27.

(36) 1.6.11. Importing a Column-Based File You can use a column-based file wizard to import fault stick data (from an ASCII file) and create a Curve object (or a PointsSet or Well object), depending on the type of data in your file. The procedure is similar whether you are importing Well, PointsSet, or Curve data. For information, see "Common Process for Importing a Column-Based File" on page 1-8.. 1.6.12. Importing a Petrel Pillars File Use the Petrel1 Pillars converter to create a Curve object from a Petrel Pillars file.. To import a Petrel 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. Importing a SeisWorks Fault Sticks File Use the Seisworks 2 fault sticks converter to create a Curve object from a SeisWorks fault sticks file.. To import a SeisWorks 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.. Importing a Z-MAP Fault or Contour File Use the ZMAP 3 Fault or Contour converter to create a Curve object from a Zmap fault or contour file.. To import a Zmap 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. 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-28. Importing Data. SKUA® and GOCAD® – Paradigm™ 2011 With Epos® 4.1 Data Management.

(37) Part II: Data Import and Export. 1.6.15. Importing a Charisma Fault Polygons File Use the Charisma Fault Polygons converter to create a Curve object from a Charisma Fault Polygons ASCII file. The converter creates one Curve object from each file.. To import a Charisma Fault Polygon file as a Curve. 1.6.16. 1. Select File > Import > Fault Interpretations > Fault Polygons (Curves) > Charisma Fault Polygons to open the Import ASCII Charisma Fault Polygon To Curve 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. 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.. 7. Click OK or Apply.. Importing a CPS3 ASCII Polygons (.ply) File Use the CPS3 ASCII Polygons converter to create a Curve object from a .ply file. The converter creates one PointsSet object per import file.. To import a CPS3 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.6 Importing Fault Interpretations Data. 1-29.

No results found