Support Center Email Support Knowledge Base Videos
Geoscience > Main Launcher > Horizon Menu > Horizon Import

Import Horizons

The Import Horizons dialog allows you to import different formats of text data representing horizons.

General Information

Input Files

Specify files to import here.

Files: Bring up a file selector dialog to choose files for import.

  Remove All: Remove all the files from the Input Files list.

  Remove: Remove selected files from the Input Files list.

 File Format: Choose the format of the input file.

  • SeisWare Format: This is the standard export from SeisWare and several other packages including SeisX (sample 2D file, sample 3D file).

  • Columnar ASCII: This format represents horizons as columnar data. Define the horizon column by giving it a horizon name. Then define information about the trace using one of four methods. Note: You can define an optional "Line Name" column. Defining this column will match lines in the file against lines in the database.

    • Define the "Map X" and "Map Y" columns in which case the data will be imported spatially based on the map location.

    • Define the "Trace" and "Line" columns in which case the data will be imported by matching the line and trace values. This option is only available for 3D lines.

    • Define the "Shot" column. This will import horizons by matching the shotpoint value. This option is only available for 2D lines.

    • Define the "CDP" column. This will import horizons by matching the CDP value. This option is only available for 2D lines.
  • Landmark 2D: This is one of the text export formats from SeisWorks for 2D seismic lines. Shotpoints are used to determine which trace to load each individual horizon pick into (sample file).

  • Landmark Spatial 2D: This uses one of the text export formats from SeisWorks for 2D seismic lines. It differs from the Landmark 2D import by using the spatial (map coordinate) information rather than shotpoints when trying to match traces. Although this format is slower to import it is often preferred because the export files frequently contain inaccurate shotpoint information (sample file).

  • Landmark 3D: This imports several text export formats from SeisWorks for 3D seismic lines. SeisWare will attempt to determine the export format and load the data (sample 3D file with trace and line values, sample 3D file with positional values, sample 3D file with trace/line and positional values).

  • Landmark Spatial 3D: This imports the spatial export format from SeisWorks for 3D seismic lines (sample 3D file with positional values). Note: This format can be used to import data spatially where the line and trace values of the 3D have been flipped. Selecting this format with a 3D file with trace/line and positional values will force the importer to ignore the line and trace information in the file and instead use the map coordinate information.

  • GeoFrame ASCII 2D: This is one of the text export formats from GeoFrame for 2D seismic lines. Shotpoints are used to determine which trace to load each individual horizon pick into (sample file).

  • GeoFrame ASCII Spatial 2D: This uses one of the text export formats from GeoFrame for 2D seismic lines. It differs from the GeoFrame ASCII 2D import by using the spatial (map coordinate) information rather than shotpoints when trying to match traces. Although this format is slower to import it is often preferred because the export files frequently contain inaccurate shotpoint information (sample file).

  • GeoFrame ASCII 3D: This imports several text export formats from GeoFrame for 3D seismic lines. SeisWare will attempt to determine the export format and load the data (sample file).

  • GeoFrame ASCII Spatial 3D: This imports the spatial export format from GeoFrame for 3D seismic lines (sample file). Note: This format can be used to import data spatially where the line and trace values of the 3D have been flipped. Selecting this format will force the importer to ignore the line and trace information in the file and instead use the map coordinate information.

Columnar ASCII Parameters

Specify parameters when importing a file of columnar values.

Define Columns: Define the columns in the ASCII file. The columns that you define will be different, depending on the type of file (2D/3D) that you are importing.

 Null Value: Specify a value for missing picks. Normally columnar ASCII files will use blanks for unpicked locations, but occasionally a Null value needs to be specified. This is frequently -9999.99.

 Horizon Type: Specify a type for the input horizon. Note: If the horizon already exists within SeisWare, this parameter has no effect. Possible horizon types are:

  • Normal: Normal horizons are horizons that contain both a structure and amplitude component. They are suitable for display in the Seismic Viewer.

  • Computed Structure: Computed structure horizons have only a structure component. Select this option to prevent a bulk shift from being applied to horizon values when displaying them within SeisWare.

  • Computed Amplitude: Computed amplitude horizons have only an amplitude component.

Landmark 3D Parameters

Use seismic line name from file: Toggle this on to use “Project Name” in file as the line name when loading horizons onto a specified 3D volume. You can limit the import further by selecting Seismic Lines. Note: The line name must exist in the project.

Seismic Lines

Select the lines you want to import the horizons onto. When you are importing horizons using X and Y values this will help control which lines the horizons are imported onto.

Left click to select a seismic line, left click while pressing the Ctrl key on your keyboard to select multiple seismic lines, or select a group of lines from the Basemap. To help you make your line selections, you can sort any column by left clicking on the column header, you can apply a filter (), or you can type a search string into the search bar to limit the list using Name, or Owner information. 

For additional selection and navigation options right click on the Seismic Lines list to access the shortcut menu.

Include SEG-P lines: Select this item to include SEG-P lines in the list.  Some interpreters will have horizons imported into their SEG-P lines. This allows computations to be performed on those lines.

Parameters

Specify additional parameters. These parameters apply to several of the file formats.

Units: Select the units that the imported horizon data is in. Options are Milliseconds, Meters and Feet.

Depths are Subsea: Turn this on when importing depth horizons that were exported as subsea.

Subtract bulk shift from the database: Turn this on to remove the static shift that has been applied to each line from the imported horizons. Normally you will leave this item unchecked, but some horizons such as those exported from Landmark and Kingdom already have the static shift applied. Turning this on will remove the static shift so the horizons appear at the correct vertical position. The working set file for a given seismic line is the file that is used to determine the static shift.

Bulk Shift: Add a static shift to the imported horizons. Normally you will leave this as zero, but occasionally you will receive data that has been exported with static shifts already applied. This allows you to correct the horizons on import.

Search Radius: This specifies how close a pick in the file needs to be to a pick in the actual seismic for the horizon value to be set. If more than one pick is within the search radius the closest pick is always used. This parameter is only used for columnar ASCII, Landmark Spatial 2D and Landmark 3D file formats.

Scale Factor: Apply a scale factor to the horizon values. This is most useful if you have horizon data that is in seconds rather than milliseconds.

Also See

MORE INFORMATION