Specifying Header Locations (2D SEG-Y)
Mapping the byte locations of the headers is the most involved part of the loading process. It is possible that your data may have its values in unusual locations or formats in the SEG-Y files. The SEG-Y Loader will attempt to identify the most likely positions, but to correctly import your data, these must be confirmed. It will display a warning if it detects an unlikely value mapped to an important data, i.e. number of samples (ns), sample interval (dt), first sample delay (delrt), Common Midpoint (CMP), X or Y. This allows you to remap the headers before proceeding to the next step in the wizard.
To aid the remapping process, the Specify the byte locations of headers window has a number of useful tools including EBCDIC Header, Binary Header and Trace Header (see Investigating SEG-Y Headers).
The first three fields at the top of this window define the vertical extent of the whole volume.
- Number of Samples — By default, this value comes from the binary header and is usually correct. If necessary, you can define a constant value. This value is probably the most important as everything will not be loaded properly if it is wrong.
- Sample Interval — By default, this value comes from the binary header and is usually correct. It is recommended to always double-check the unit of measurement. For time-domain data, the standard unit used is microseconds, which is usually true. Meanwhile, data in depth-domain is normally sampled in metres or feet.
First Sample Time/Depth — This value defines the time/depth where all traces begin. Based on the standard SEG-Y format, the byte location for this is at 109 and is usually correct.
Note: If you are loading SEG-Y data that is exported from Kingdom, you must change the byte location for this field to "105" as Kingdom writes this information at this byte location.
Note: Number of Samples and Sample Interval must accurately match the input SEG-Y. If you want to load only a subset or resample the data, changing the values for Number of Samples and Sample Interval will cause you to have wrong results from the loading. Currently, you cannot use the SEG-Y Loader to resample or vertically clip the data. However, you can do these in Insight when you export the volume.
When loading 2D data, the Common Midpoint (cmp) header is used as the primary trace counter. The default value is usually correct.
Optionally, you can also define the Shotpoint (sp) header and Shotpoint Scalar (scalsp). Click the Apply shotpoint scale check box to apply the scale to the shotpoint.
Note: You can still map to some other value (e.g. a shotpoint number). However, in Insight, it will be displayed as a CMP value.
Navigation data is important to create a survey. A 2D survey in Insight defines the tie points between lines/CMPs and eastings/northings (X/Y). There are two methods that you can select to define the navigation data:
- I will import navigation file(s), and/or enter tie points manually, or use an existing survey — Select this option if you have already created a survey (when loading a previous volume) and this data belongs to the same survey, or if you wish to import navigation file(s) (see Loading Navigation Data Files). Also select this option if you want to provide the tie points that define the relationship between CMP in regards to X/Y points. With this option, you do not need to remap the X and Y headers.
- Calculate tie points from X/Y headers — By default, this is the option selected when you load 2D data. With this option, you must map the X and Y headers that contain sensible data. The standard locations for X and Y are bytes 181 (ENSEMBLE X) and 185 (ENSEMBLE Y), but it is also common to find these values at bytes 73 (SX) and 77 (SY), or 81 (GX) and 85 (GY). These values are usually encoded as int32, but in rare cases, they may be encoded as floats or IBM floats.
The following describes the automatic calculation of tie points from the X/Y trace headers in the SEG-Y Loader for 2D lines:
Analysis will track every CMP/X/Y point in the line. Once it has tracked the entire line, it removes as many unnecessary tie points as possible without introducing error in excess of 10 m (this is the default maximum error distance) (see Analysing 2D Data).
Select the Apply nav scale check box when you map the X/Y headers to apply navigation scaling. This is important to fit the X and Y in the space available or to gain extra precision. In the Trace Headers, X/Y values are sometimes stored after being divided or multiplied by a constant scalar. Hence, to get back the correct values, you must revert the scalar during the loading process. If you do not do this, data will be placed in the wrong geographical location. Usually, most files follow the correct scalar based on the SEG-Y standard, but you can still override it by typing a new scalar in the Coordinate Scalar (scalco) field.
In the Specify the byte locations of headers window, you can convert the SEG-Y coordinates to the project's coordinate reference system (CRS). This option is only available if you have a project CRS defined (see Creating a Project).
- Select the Type of coordinates (Eastings/Northings or Latitude/Longitude).
- Click Convert from to specify which CRS to convert from. The Standard CRS Table will be displayed.
- Type your preferred CRS in the Search (regex) bar and the table will automatically filter accordingly.
- Select a CRS and click OK. Alternatively, double click on the CRS to select it.
- Insight will automatically detect your project CRS to convert to.
- Click Next to proceed to the next step.
Click this to save your current header remapping settings to a .sdmap file. These can be used to quickly remap other SEG-Y files that share an identical data structure.
If you have an existing .sdmap file created, click this to use this file to map the headers. This is a quick way to map the headers of identically structured SEG-Y files.
DUG understands that importing SEG-Y data can be a confusing task.
Whether you are using a trial version or a fully-paid licence, we will help you to import your data to Insight so that you will get the maximum out of your data.
For more information, contact support at [email protected].