Lynx Seismap

Use this layer for Lynx Seismap 2D seismic (checkbox) - check this box to activate Seismap for this layer and enable the rest of the parameters on this property page.

Filepath Field - select the attribute table field which contains the path of the SEG-Y file. This field must be a string field, and should contain the path to the seismic data file for each seismic profile (feature). File paths are resolved in a similar way to that used for standard ArcMap hyperlinks - see File name resolution (below) for more information. To use the basemap labelling, export and intersection functionality of Seismap without any seismic data files to display, select the <No Filepath Field> option from the dropdown list.

SP Source - select Seismic File Header or Attribute Table.
For 2D seismic data, the shotpoint range of the seismic data file, and the measure values of the 2D seismic feature class, are used to show the current display range on the map, and mark intersections in the seismic viewer windows. If the shotpoint range is not stored in the seismic data file, then ranges and intersections will be incorrectly displayed.

• Seismic File Header - the first shotpoint and shotpoint increment are read from the seismic file header. Use this option for Lynx Trace files (TR files) and Lynx-variant SEG-Y data, which store these values in un-used slots in the binary file header. Standard SEG-Y contains no information on the exact shotpoint range (although integer shotpoint values may be stored in each trace header). SEG-Y Revision 1 files should contain decimal shotpoint numbers - see Import 2D Seismic Data for how to read these values.
• Attribute Table - for SEG-Y data (both standard and Revision-1) which does not contain shotpoint information in the file header, the first and last shotpoint values can be read from fields in the basemap layer's attribute table.

The following 2 parameters are only displayed if SP Source (above) is set to Attribute Table. For seismic data stored as SEG-Y format, there may be no shotpoint information available from the file itself. These parameters allow you to read shotpoint values from the feature class attribute table.

First Shotpoint Field - Select the field from this 2D Seismic Layer attribute table which contains the shotpoint value for the first trace of each seismic profile.

Last Shotpoint Field - Select the field from this 2D Seismic Layer attribute table which contains the shotpoint value for the last trace of each seismic profile.

Show Line Intersections (checkbox) - Indicate whether to display intersections with other lines in the shotpoint scale bar of seismic viewer windows.

Highlight Current SP Range on Map (checkbox) - Indicate whether to highlight viewer window shotpoint/CDP ranges on the map. The current range is interactive - you can use the 'hand' tool on the Seismap toolbar to grab and pan a displayed range in ArcMap's data view.

Highlight Colour - Select a colour for the current shotpoint/CDP range highlight

Highlight Width (px) - Set the width in pixels for the current shotpoint range highlight.

Line Name and SP Labels - click this button to access the simplified line and shotpoint labelling options for 2D seismic data. The options on this page can all be set within ArcMap using the 'Labels' and 'Hatches' tabs in the Layer Properties dialogue accessed by right-clicking on a layer in the ArcMap Table of Contents. However, for infrequent users, these options are often hard to find and obscure to set. The parameters as presented here provide a simpler interface to labelling which is specific to seismic shotpoint maps. These options do not provide a comprehensive alternative interface to ArcMap's hatch annotation options, but rather a 'quick and dirty' way to display annotation which can be fine-tuned later using the existing ArcMap interface.

Export...

4.2 3D Seismic Layer Properties

3D seismic inlines and crosslines can be displayed for 4-dimensional polygon feature classes (coordinate values must contain either X,Y,Z,M or X,Y,ID,M values)

4.3 Seismic Viewer Window

Each seismic viewer window displays a 2D seismic profile or a 3D inline or crossline.
Multiple windows can be open viewing different profiles at the same time.
The shotpoint/CDP range currently displayed will be superimposed on the 2D line or 3D survey in ArcMap's data view.

The Seismic Display parameters allow you to set display and scale parameters globally for all 2D and 3D seismic viewer windows. Changes made here will be applied to all currently open and subsequently open seismic viewer windows. These parameters are accessed via the Seismic Display Options  menu on the Seismap toolbar and the Options-Display Properties  menu item in seismic viewer windows.

Parameters are displayed in a wizard-style PRMEDIT dialogue.

The seismic viewer window uses standard Lynx Viewer component menus and toolbar buttons which allow you to zoom in and out, compress horizontally or vertically, flip the display, and print the profile, which are described in detail in Viewer Common Functionality. and Seismic 3D Inline Display.

In addition to the standard viewer toolbars, the seismic viewer window also has a toolbar containing tools specific to Seismap - the Identify Toolbar - which has the following tools:

2D Profiles

3D Inlines and Crosslines

For details of the additional options available for viewing 3D seismic data, see Seismic 3D Inline Display

4.4 Import 2D Seismic Locations

You can convert a UKOOA/SEG-P1 file or CSV file containing shotpoint/CDP coordinates into a file geodatabase feature class or shape file using the Lynx Seismap toolbar menu option Import/Export - Import Seismic Locations. This uses the Lynx utility UKO2SHP. For more information about converting UKOOA/CSV files, see the help for UKO2SHP. After you have converted your input file, you will be prompted to select a spatial reference for the generated feature class. This feature class will be added to the current ArcMap data frame.
In order to use the feature class created here as a 2D seismic basemap layer in Seismap, you will need to import 2D seismic data using the option below, or add a field to the attribute table and edit seismic data filepaths into this field.

Metadata will automatically be created for the generated feature class, listing the import process. Only FGDC format metadata is supported in this version. To turn off generation of metadata by Seismap, edit the import metadata key in the [startup] section of the seismap.ini file to be a blank value.

4.5 Import 2D Seismic Data

Seismap reads seismic data in its pre-existing SEG-Y format or Lynx Trace file format - there is no need to reformat the seismic data files. The seismic 2D import wizard displayed by the Import 2D Seismic Data menu provides a simple method of importing seismic data, but you can also use standard ArcGIS Desktop functionality to create and edit existing layers.

The wizard provides a choice of output layer types: you can create a route event using a seismic list in a standalone File Geodatabase or dBASE table, or a new feature class in a File Geodatabase or shapefile.

Before using this wizard, you must already have the seismic locations loaded as a layer in the current ArcMap data frame (see Import 2D Seismic Locations). The wizard provides visual confirmation that the line-names of your seismic data files match your existing seismic locations layer, but you should verify independently that shotpoint ranges in your seismic data files match those in your seismic locations. For more advanced reconciliation tools, see the Lynx Seismatch application.

First, select your seismic 2D locations layer from the drop-down list. Select from all available polyline-M layers in the current map data frame

The Import 2D Seismic Options determine how the required information is read from the listed SEG-Y files.

Next, drag SEG-Y files from an Explorer window onto the wizard window, or click Add Files to browse for SEG-Y files. Each selected file will be added to the displayed list.
Click Delete Selected to remove selected records from the list.
Click Import Options to edit the Import 2D Seismic Options (see above).
Click Refresh to re-read filepaths, linenames and shotpoint ranges from the seismic files using the current import options.
Click Edit Mode/Select Mode to switch between row-select mode, which allows you to select multiple records for deletion, and field-edit mode, which allows you to manually edit field values in the list.

The line name for each SEG-Y file will be highlighted in red or green. A red highlight means the line name is not present in the selected seismic 2D basemap layer. Click the '...' button in the linename field when in Edit Mode (or press Ctrl+Enter) to display the linename picklist to select the correct linename from your seismic 2D basemap layer. Linenames often differ in spacing or capitalisation - you must ensure that line names match exactly for the table relationships created by Arcmap to function correctly. A green highlight means the line name is present in your selected seismic 2D basemap layer.

The buttons at the bottom of the wizard window allow you to save and reload the displayed list of SEGY files:

• - load an existing dBASE (DBF) file saved in this wizard.
• - save the current list as a dBASE (DBF) file.
• - display this help.

Choose the type of layer to create - either a new route event layer or a new feature class:

• Route Event - your list is saved as a standalone table in a File Geodatabase or in dBASE format. This list is then added to your current ArcMap data frame as a new route event layer, using the line-names to match features in your selected seismic 2D basemap layer, and the first and last shotpoints as linear referencing on the basemap layer polyline measures.
• New Feature Class - stored in a File Geodatabase or as a shapefile. This option creates a new feature class layer containing a copy of the line geometry for each matched line from your selected seismic 2D basemap layer. This new layer is then added to your current ArcMap data frame.

For either of these options, it is important that the line names in your seismic list match the line names in your seismic 2D basemap layer.

You can choose to copy the symbology of your basemap layer to your newly created layer by ticking the Copy Symbology checkbox.

Select a name and output location: for route event output, you will be creating a standalone table in a File Geodatabase or in dBASE format; for new feature class output, select a File Geodatabase and specify a new name, or create a new shapefile.

Click Import to save your seismic list, create the layer, and set the Seismap layer properties for this new layer. You can then activate the Select Seismic Profile tool and view your SEG-Y files

4.6 Import 3D Seismic Data

Seismap uses polygons to define 3D seismic surveys.

Using the Import 3D Seismic Data Wizard, Seismap can read trace coordinate values from trace headers in 3D seismic SEG-Y files, to generate the survey outline polygons.

Each seismic survey is defined as a single polygon feature. Inline and crossline numbers are defined at each of the polygon vertices. Locations of intermediate CDPs are calculated on the fly by using a Delaunay triangulation, thus reducing the size of the polygon feature class required for display by ArcMap.

A single polygon layer may store the locations for multiple 3D seismic surveys.

The underlying format of the feature class determines whether the inline and crossline numbers are stored in each point's ID and M (geodatabase feature classes) or Z and M (shape files).

3D Survey Import Wizard

Drag 3D seismic SEG-Y files from an Explorer window onto the wizard window, or click Add 3D Surveys to browse for SEG-Y files. Each selected file will be added to the displayed list.
Click Delete Selected to remove selected records from the list.
Click Import Options to edit the Import 3D Seismic Options (see below).
Click Refresh to re-read filepaths from the seismic files using the current import options.
Click Edit Mode/Select Mode to switch between row-select mode, which allows you to select multiple records for deletion, and field-edit mode, which allows you to manually edit field values in the list.

You can double-click in the Filepath column to view the C-Card headers for the selected file, or in the Preview column to preview the survey outline for selected file using the current Import Options (see below). Note that previewing a large SEG-Y file involves reading all trace headers - this may take some time.

The Import 3D Seismic Options determine how the required information is read from the listed SEG-Y files.

Once your import parameters are set and you have added your 3D seismic survey SEG-Y files and edited their survey names, select an output polygon feature class to create - you can choose to create either a polygon shapefile or a polygon feature class in a file geodatabase. If you choose a feature class which already exists, it will be overwritten.

The buttons at the bottom of the wizard window allow you to save and reload the displayed list of SEGY files:

• - load an existing dBASE (DBF) file saved in this wizard.
• - save the current list as a dBASE (DBF) file.
• - display this help.

Click the Import button - a dialog will be displayed showing your current import options, click OK to start the import process.
3D seismic survey SEG-Y files are very large, and this import process may take a considerable amount of time - 10 to 30 minutes would not be unusual.

When the import process is complete, the generated polygon feature class will be added to your active data frame in ArcMap, and initialised as a Seismap 3D seismic layer.

Note that this initial import implementation builds the inline and crossline index files for each seismic survey used for fast display of inlines and crosslines in the seismic viewer. These index files are stored on your local PC in your Lynx CUSTOM folder (see Cached Seismic Data for details). These indexes will be regenerated automatically if they do not exist, but this can take some time, and may delay the initial display of inlines/crosslines. If you intend to access this MXD from multiple PCs, then you can move these inline and crossline index files into the same folder as the SEG-Y files - this will avoid these index files being recreated locally on each PC or for each user.

4.7 Cached Seismic Data

Seismap stores 2D profile, horizon and well intersection information after its initial calculation for quick retrieval. This information is stored in the MXD along with other Seismap parameters. Seismap also creates inline and crossline index files for 3D seismic volumes when a 3D seismic data file is first opened, which speeds up subsequent displays of the same file - these index files are stored in your Lynx CUSTOM folder. If you change inline or crossline header information, or if you edit geometries manually, this cached information may become out of date, and cause Seismap to display data incorrectly. The Cache Management option on the Seismap toolbar menu can be used to delete this cached information, so that intersections and index files will be recreated the next time a seismic file is displayed.

---

5. Seismic Horizons, Surfaces and Faults

• 5.1 Horizon and Fault Layer Properties
• 5.2 Horizon Z-Value Colour Ramp Renderer
• 5.3 Horizon/Fault Import and Export
• 5.4 Horizon/Fault Polyline Export
• 5.5 Horizon/Fault Polyline Import
• 5.6 Grid Import and Export
• 5.7 Exporting a Z-Map Grid
• 5.8 Importing a Z-Map Grid

Lynx Seismap can display polylines with Z values, as well as TIN and raster grid surfaces, as horizon and fault overlays on 2D and 3D seismic profiles.

5.1 Horizon and Fault Layer Properties

The polyline layers or surfaces must be listed in the current document in ArcMap, as part of the same data frame as the 2D and/or 3D seismic basemap layer. To display TIN surfaces you must have the 3D Analyst extension installed and licensed. To display polyline-Z layers or raster grid surfaces no extra licence is necessary. The polylines or surfaces must be attributed with Z-values in two-way-time in milliseconds (to match the seismic data vertical scale), as depth-to-time conversion using velocity data is not yet implemented. Polyline feature classes used for horizon/fault overlay must include a primary display field which uses the same line names as the corresponding 2D seismic layer. Seismap layer properties can be accessed as a tab in the standard Layer Properties dialog.

The drawing order of horizons and faults as seismic overlays will be the same as the display order listed in ArcMap's table of contents view - the last horizon/fault listed is drawn first - later horizons will overlay earlier ones.

5.2 Horizon Z-Value Colour Ramp Renderer

Seismap includes a custom feature renderer to display horizon and fault polylines by their Z value with a user-specified colour ramp.

The settings for this custom renderer can be accessed on the Symbology tab in the Layer Properties dialog.

You can use the arrow buttons to browse backwards and forwards through the standard colour ramps from the ESRI Style Manager. The 'From Layer' buttons can be used to set the upper and lower Z values for calculating the corresponding colour for each intermediate Z value. Z values outside the bounds entered here will be displayed with the high-bound or low-bound colour.

This polyline-Z colour ramp symbology can be saved into layer files and previewed in ArcCatalog; however, ArcScene and ArcGlobe are not supported.

5.3 Horizon/Fault Import and Export

Seismap provides import and export options for interpreted horizon and fault picks.

Seismic interpretation systems provide a number of export formats for horizons and faults. The import options in Seismap are flexible enough to deal with many different formats exported from seismic interpretation systems or digitising applications, using a spreadsheet-like (CSV or column-delimited) layout or shapefile, as long as they contain at least the following information:

• Linename
• Shotpoint
• X coordinate (can be interpolated from existing seismic line locations if not present)
• Y coordinate (can be interpolated from existing seismic line locations if not present)
• Z-value (TWT in seconds or milliseconds)
• In addition, the format must contain some method of separating line segments - either with a segment identifier, or with null-value records in between each segment.

5.4 Export Horizon/Fault Polylines

You can export horizon/fault layers from Seismap using the Export to ASCII button on the 'Seismap Horizon/Fault Overlay' tab page of the Layer Properties dialog. These exported files can be imported into SMT Kingdom, Landmark, or other seismic interpretation systems.

Select the horizon/fault and export format from the drop-down lists. The formats currently supported for horizon/fault export are:

• Line Trace X Y Time (with nulls) - Z-values will be converted from milliseconds to seconds. Comma-delimited output
• Landmark Time (with nulls) - Z-values will be output as-is - assumes milliseconds. Column-delimited output
• Charisma (faults). Column-delimited output
• Custom - see below

Set the output shotpoint increment for lateral sampling of the horizon. This is only applicable for the 'Line Trace X Y Time' and 'Landmark Time' formats, which separate segments with null values. You should select a shotpoint increment value which will output a value for each trace in the seismic data.

If you select the Custom format option, the next page of the export wizard will allow you to specify how to write your output file, by specifying the field order. Use the 'Segments Separated By: Null Values/Segment ID' option to determine the type of line-part separator in your output file, and select the output units for the Z-value.

For Custom formats, you will also need to specify the precision used to write shotpoint, coordinate and Z-values. The precision is the number of decimal places used.

For space-delimited custom formats, you must also specify the column width and alignment for each output column. Enter the width for each in the list as shown. A positive width value implies that the column will be left-justified, and a negative width value implies that the column will be right-justified.

5.5 Import Horizon/Fault Polylines

You can import horizons and faults for any seismic lines in your seismic 2D basemap layers.
The import process can use linear referencing to create XYZM polyline features from your imported horizon shotpoint/TWT coordinates.
Your seismic locations must cover the full shotpoint range of your horizons, as no shotpoint extrapolation is performed by this import operation.

The Import Horizon/Fault dialog is accessed from the Import/Export menu on the Seismap toolbar.

Select your input file and its format. The formats currently supported for horizon/fault import are:

• Line Trace X Y Time (with nulls)
• Landmark Time (with nulls)
• Charisma (faults)
• Custom Text Format - use a CSV or column-delimited ASCII file and specify the columns and segment separators to use
• XZ Shapefile - digitised horizon polylines saved in shapefile format using a pseudo-XZ coordinate system. Your digitised shapefile should be calibrated to use seismic shotpoints or distance along line as the X coordinate, and two-way time in msec as the Y coordinate. Your shapefile can contain a multi-part polyline feature for each digitised horizon/fault, or multiple features with the same feature name for a single horizon - these will be combined into a multi-part polyline. You can include different horizons in the same shapefile - a separate output shapefile will be created for each named horizon. Your shapefile must include attributes listing the HORIZON NAME and SEISMIC LINE NAME for each polyline.

The first 3 formats above are compatible with horizon/fault export options offered by IHS Kingdom.

Select 'Import As' Single Horizon or Multiple Horizons or Faults from the drop-down list. Horizons and faults are treated differently on import. When importing a horizon, the entire import file is assumed to refer to a single horizon, and so a single horizon feature class will be created. When importing faults, multiple named and un-named faults and fault-segments may be included in the same import file. so a separate feature class will be created for each named fault, and all unnamed fault segments will be added to an 'unassigned faults' feature class.

If you select the Custom format option, the next page of the import wizard will allow you to specify how to read your input file, by specifying the field order. The shotpoint field is optional - if it is not present in your input file, set this value to zero. Use the 'Segments Separated By: Null Values/Segment ID' option to determine the type of line-part separator in your input file, and select the units for the Z-value.

If you select the XZ Shapefile format option, the next page of the import wizard will allow you to define the measurement systems used for your input coordinates, and the attribute fields used to retrieve the horizon name and seismic line name for each horizon in your input shapefile.
Your input shapefile must contain an attribute naming the seismic line for each feature (the seismic line names used here must match a line name in one of your existing seismic 2D basemap layers). If your shapefile contains more than 1 horizon, you must also have an attribute naming the horizon. If you only have a single horizon in your input file, you can use the name of the input shapefile as your horizon name.
If you have multiple horizons with the same name in your input shapefile, these will be combined into a single multi-part horizon polyline in the output feature class.
You can have horizons for multiple seismic lines and/or multiple horizons in the same input file - separate output feature classes will be created for each horizon, containing the horizon polylines for multiple seismic lines.

On the final page of the wizard, select an output feature class or destination folder/file geodatabase, and a spatial reference. For single horizon import from a text file, select an output feature class in either file geodatabase format or shapefile format.
For multiple horizon/fault import, select an output file geodatabase or folder - each named horizon/fault in the input file will be stored as a separate feature class/shapefile in this output destination). If your destination already contains feature classes, then you can tick the 'Add new features to existing feature classes' option to merge your new features into these existing feature classes if the feature class names match your input horizon/fault names.

Final page of the Import Horizon/Fault Profile wizard

You can simplify the imported horizon/fault profiles by waypointing using a specified maximum vertical deviation in ms. This will create a much smaller feature class which will display more quickly in the seismic viewer windows. This option is only available for input from text file formats.

The 'Close this dialog after successful import' option allows you to import multiple text files easily, by reselecting a new input file if all other import parameters remain constant.

The import process will create a shapefile containing polyline-XYZM features for each horizon import file, or a shapefile for each named horizon/fault in the fault import file or XZ shapefile.
Z-values will be two-way time in ms, and M-values will be shotpoint values (if present in the input ASCII file). The imported feature class will be added to the Horizon/Fault list for display as a seismic overlay.
The picked horizon/fault for each seismic profile will be stored as a separate feature. The profile (seismic line) names used in the horizon layer must match those used in a 2D seismic layer. Multi-part polylines allow discontinuous horizons and reverse faults to be correctly represented. See 5. Horizons and Faults (above) for more information on displaying overlays on seismic profiles.

5.6 Grid Import and Export

Seismap allows interchange between File Geodatabase Grids and ESRI Raster Grids and Z-Map ASCII grid files. ZMap is commonly used exchange format for gridded data such as seismic horizon and fault surfaces.

There are a few important differences between Z-Map and ESRI grid formats.
Firstly, the Z-Map grid format allows independent grid sample intervals in the X and Y directions, whereas an ESRI grid must have square cells. Seismap will interpolate the grid values if required, to recalculate cell values using the smaller of the X or Y grid sample intervals. Interpolation will result in a larger number of cells in the output ESRI grid
Secondly, the limits of a Z-Map grid are defined by the coordinates of the corner nodes, whereas the limits of an ESRI grid are extended by half a grid cell size around the cell centroid.

5.7 Exporting a Z-Map Grid

You can export grid and TIN surfaces from Seismap using the Export to ZMAP Grid button on the 'Seismap Horizon/Fault Overlay' tab page of the Layer Properties dialog for grid and TIN surfaces. The output grid file will use the same spatial reference as the input surface layer. An output .dat file will be created in ZMAP ASCII Grid format.

5.8 Importing a Z-Map Grid

The Import ZMAP Grid dialog is accessed from the Import/Export menu on the Seismap toolbar.

Select the input Z-Map grid file, and specify an output name and path for the File Geodatabase grid or ESRI raster grid file (note that the standard restrictions apply to ESRI raster grid filenames - max 13 characters, no spaces etc). If the output grid already exists, you will be prompted to confirm overwriting it. Select the spatial reference used by the input Z-Map grid. If this is not known, the output raster grid will use an undefined projection, and you will have difficulty integrating the grid with other layers.

The input Z-Map grid will be read, and a corresponding ESRI grid will be created and added to the current data frame of your MXD. A summary of the input and output properties will be displayed. Metadata will automatically be created for the generated grid, listing the import process. Only FGDC format metadata is supported in this version. To turn off generation of metadata by Seismap, edit the import metadata key in the [startup] section of the seismap.ini file to be a blank value.

---

6. Wireline Log and Tops Viewer

• 6.1 Wireline Log Layer Properties
  • Well Tops
  • Export
    • Export iLogview shapefiles
    • Export 3D Curves
• 6.2 Wireline Log Viewer Window
  • Wireline Display Parameters
  • Wireline Curve Master List
• 6.3 Import Wireline Logs

6.1 Wireline Log Layer Properties

Wireline logs can be displayed for point feature classes. Seismap layer properties can be accessed as a tab in the standard Layer Properties dialog.

6.2 Wireline Log Viewer Window

To display wireline data, activate the Show Well Viewer  tool on the Lynx Seismap toolbar, then click a well point to launch a viewer. This tool uses ArcMap's Selection Tolerance to select features in a similar way to ArcMap's Select Features tool, Select By Graphics command, Edit tool and Identify tool. When you click on the map, wells within the radius of the selection tolerance will be selected. If more than one well is selected, a dialogue box will be displayed for you to choose which well to display.

You can also browse the attribute table of the wireline log layer to select logs to view. Open the attribute table by right-clicking on the layer in the Arcmap Table of Contents panel, then browse to the record for the log you wish to display. Right-click on the record-marker to display the Table Record Marker Context Menu, and then click View wireline curves.

Wireline Display Parameters

Wireline Display Parameters can be accessed via the Wireline Display Options  menu on the Seismap toolbar and the Options-Display Properties   menu item in wireline viewer windows.
These parameters allow you to set display and scale parameters globally for all wireline viewer windows. Changes made here will be applied to all currently open and subsequently open viewer windows.

Each well log viewer window displays the wireline curves from a single LIS/LAS file.

Wireline Curve Master List

The Seismap wireline log viewer shares configuration files with the standalone Lynx Logview application. You can configure a network-wide master curve list, to store layout information for all defined curves and mnemonics, plus your individual customisations are stored in a user-specific layout file in your profile folder. Changes you make to curve layouts will be visibile in both Seismap and Logview.

See the Logview help for more information about:

• Unknown Curve Mnemonics
• Track Editor and Curve Display Properties
• Defining a Master Curve List
• Synchronising changes between user layout and master curve list

6.3 Import Wireline Logs

Seismap reads wireline logs in pre-existing LAS or LIS formats. You can create a new feature class for your wireline logs in a file geodatabase or shapefile using this wizard, displayed by the Import Wireline Logs menu.

Before using this wizard, you must already have the well locations loaded as a point layer in the current ArcMap data frame. This wizard provides a simple mechanism for adding wireline log files to an ArcMap document for use with Seismap - you can also use other import and geodatabase editing facilities within ArcGIS Desktop to create Seismap wireline log layers.

First, select your well locations layer from the drop-down list. Select from all available point layers in the current map frame.

The Import Wireline Options determine how the required information is read from the listed wireline log files.

Next, drag LAS/LIS files from an Explorer window onto the wizard window, or click Add Files to browse for wireline log files. Each selected file will be added to the displayed list.
Click Delete Selected to remove selected records from the list.
Click Import Options to edit the Import 2D Seismic Options (see below).
Click Refresh to re-read filepaths and well names from the wireline log files using the current import options.
Click Edit Mode/Select Mode to switch between row-select mode, which allows you to select multiple records for deletion, and field-edit mode, which allows you to manually edit field values in the list.

The well name for each log file will be highlighted in red or green. A red highlight means the line name is not present in the selected well basemap layer. Click the '...' button in the well name field when in Edit Mode (or press Ctrl+Enter) to display the well name picklist to select the correct well name. Well names often differ in spacing or capitalisation - you must ensure that well names match exactly for the table relationships created by Arcmap to function correctly. A green highlight means the well name is present in your selected well basemap layer.

If your existing well locations layer includes a UWI (Unique Well Identifier) attribute, you can choose to include this in your output layer in addition to the well name field. This UWI is often used to relate the well features to other tables and feature classes in your geodatabase, instead of linking on the well name. Tick the 'Include UWI Field' checkbox and select the UWI attribute field from the drop-down list.

You can also choose to copy the symbology from your selected well basemap layer to your new output wireline log layer by ticking the Copy Symbology checkbox. If the symbology depends on any of the other attribute fields, then these fields will be copied into your output feature class.

The buttons at the bottom of the wizard window allow you to save and reload the displayed list of wireline log files:

• - load an existing dBASE (DBF) file saved in this wizard.
• - save the current list as a dBASE (DBF) file.
• - display this help.

After you have added all wireline log files, and verified the well names, select a feature class destination to save this wireline log list in a File Geodatabase table or as a new shapefile.

Click Import to create your new output feature class. This will create a new feature class layer containing a copy of the point geometry (plus any additional attribute fields selected above) from your selected well basemap layer. This new layer is then added to your current ArcMap data frame. You can then activate the Select Well tool to view your wireline logs

---

7. Cross-Section Viewer

• 7.1 Cross-Section Layer Properties
• 7.2 Cross-Section Raster Viewer Window
• 7.3 Import Cross-Sections

7.1 Cross Section Layer Properties

Raster cross-sections can be displayed for simple polyline feature classes. Seismap layer properties can be accessed as a tab in the standard Layer Properties dialog.

7.2 Cross-Section Raster Viewer Window

To display raster and PDF cross-sections, activate the Show Cross-Section   tool on the Seismap toolbar, then click a cross-section feature in the map view to view the associated cross-section. This tool uses ArcMap's Selection Tolerance to select features in a similar way to ArcMap's Select Features tool, Select By Graphics command, Edit tool and Identify tool. When you click on the map, polyline features within the radius of the selection tolerance will be selected. If more than one feature is selected, a dialogue box will be displayed for you to choose which cross-section to display. Note that the feature's primary display field must be set, and must contain a non-null value, as this is used as the cross-section viewer title. Multiple windows can be open viewing different profiles at the same time.

The displayed range of the cross-section will be highlighted on the map, and you can use the Seismap Pan tool to move the displayed range. You can also use the zoom and pan tools on the cross-section viewer toolbar manipulate the current view.

When the current cross-section is a page from a PDF file, the PDF Toolbar is activated (these options are also available in the View menu):

• Display PDF Document - open the whole PDF document in your default PDF viewer application. The icon displayed in this toolbar may vary depending on your default PDF viewer application.
• Show/Hide PDF Layers - if the PDF document contains layered content, you can turn individual layers on/off.
• Reload PDF - re-read the page from the PDF document file.

7.3 Import Cross-Sections

You can associate cross-sections in raster format or as individual pages in PDF files, with lines of cross-section which already exist as polyline layer. The Import Cross-Sections wizard provides a simple mechanism for adding cross-sections to an ArcMap document for use with Seismap - you can also use other import and geodatabase editing facilities within ArcGIS Desktop to create Seismap cross-section layers.

First, select your cross-section basemap layer from the drop-down list. Select from all available polyline layers in the current map frame.

The Import Cross-Section Options determine how the required information is read from the listed raster files.

Next, drag raster or PDF files from an Explorer window onto the wizard window, or click Add Files to browse for files to add. Each selected file will be added to the displayed list.
Click Delete Selected to remove selected records from the list.
Click Import Options to edit the Import 2D Seismic Options (see below).
Click Refresh to re-read filepaths and well names from the wireline log files using the current import options.
Click Edit Mode/Select Mode to switch between row-select mode, which allows you to select multiple records for deletion, and field-edit mode, which allows you to manually edit field values in the list.

The cross-section name for each file will be highlighted in red or green. A red highlight means the name is not present in the selected cross-sections basemap layer. Click the '...' button in the Name field when in Edit Mode (or press Ctrl+Enter) to display the Name picklist to select the correct Name. You must ensure that well names match exactly for the import process to function correctly. A green highlight means the Name is present in your selected cross-sections basemap layer.

For PDF files, you can also edit the Page Number field for each added file. This is the page that contains the cross-section image to be displayed. Page numbers in PDF files are always counted from the first page in the document 1. The page number field is not used for raster formats (TIFF, JPEG, BMP).

The buttons at the bottom of the wizard window allow you to save and reload the displayed list of cross-sections:

• - load an existing dBASE (DBF) file saved in this wizard.
• - save the current list as a dBASE (DBF) file.
• - display this help.

After you have added all cross-section files, and verified the names and page numbers, select a feature class destination to save this cross-section list in a File Geodatabase or as a new shapefile.

Click Import to create your new output feature class. This will create a new feature class layer containing a copy of the polyline geometry from your selected cross-section basemap layer. This new layer is then added to your current ArcMap data frame. You can then activate the Select Cross-Section tool to view your sections

---

8. Filename Resolution

The files used by all Seismap layers must be referenced in the layer's attribute table. There are three ways in which you can define file paths:

• 8.1 Absolute paths
• 8.2 Relative paths
• 8.3 Environment variables

File paths on Windows are not usually case sensitive.

8.1 Absolute paths

8.2 Relative paths

8.3 Environment variables