GeoStore

Version 2.2

© Geoleader, 2017
Contents

INTRODUCTION..............................................................................................................................................................3

1 REQUIRED EQUIPMENT/SOFTWARE..............................................................................................................4

2 CONNECTION AND CONFIGURATION OF TAPE DEVICE..........................................................................5

3 INSTALLATION AND CONFIGURATION OF GEOSTORE............................................................................6

4 FUNCTIONALITY OF GEOSTORE.....................................................................................................................8

5 INTERFACE...........................................................................................................................................................13
5.1 DATABASE ATTRIBUTE TABLE...................................................................................................................................13
5.1.1 Database attribute table toolbar.....................................................................................................................14
5.2 STORAGE..................................................................................................................................................................30
5.3 DELIVERY.................................................................................................................................................................41
5.4 QUALITY CONTROL..................................................................................................................................................43
5.5 AUDIT.......................................................................................................................................................................45
6 DESCRIPTION OF SUPPORTED ENCAPSULATED FORMATS.................................................................47
6.1 SEG RODE.................................................................................................................................................................48
6.2 STAGE.......................................................................................................................................................................49
6.3 TIF (TAPE IMAGE FORMAT).....................................................................................................................................50
6.4 LACEY....................................................................................................................................................................51
6.5 KELMAN................................................................................................................................................................52
 GeoStore
User manual

INTRODUCTION

GeoStore – utility package for creation and management of E&P data formats (explorations and
production) RODE, STAGE1, TIF, KELMAN, LACEY. Brief description of these formats is provided
in Chapter 6 «Description of supported encapsulated formats». Archived encapsulated data are
generated as a result of transcription operation from magnetic tapes, DVD, HDD and other input media.
The input media is specified by the unique barcode.

The main function of GeoStore is reading E & P data from input media, encapsulation of data
into specified format and data storage in encapsulation formats. Subsequently, archived data can be
allocated, de-encapsulated and sent into original format, to determine the output medium. GeoStore
also supports its own database, where the attributes of seismic data, encapsulated formats and the
transcription results are stored.

© Geoleader 3
 GeoStore
User manual

1 REQUIRED EQUIPMENT/SOFTWARE

Operating systems:
 Red Hat Enterprise Linux 3 and higher
 Sun Solaris 7 and higher

Connected devices:
 Any tape device, connected through SCSI port and controlled by “st”
driver
 CD/DVD ROM (according to demands)

Database Oracle 8.x and higher.

© Geoleader 4
 GeoStore
User manual

2 CONNECTION AND CONFIGURATION OF TAPE DEVICE

GeoStore works with any tape device, connected through SCSI port and controlled by st driver.
It can be the following:
 Exabyte
 LTO
 DLT
 IBM 3490
 etc.
To use a device with GeoStore, first of all it is necessary to make sure that it is properly
connected and configured. Before running GeoStore, check the following steps:
1. The tape device is connected to SCSI controller
2. To make sure that the device is properly configured, execute the following shell commands:
 Linux host
”mt -f /dev/stX stat”, where X – identification number of your scsi device. The example of
the answer is below:
-bash-3.00# mt -f /dev/st0 stat
SCSI 2 tape drive:
File number=0, block number=0, partition=0.
Tape block size 0 bytes. Density code 0x9 (GCR (37871 bpi)).
Soft error count since last status=0
General status bits on (41010000):
BOT ONLINE IM_REP_EN
 Solaris host
”mt -f /dev/rmt/X stat”, где X – identification number of your scsi device. The example of
the answer is below:
# mt -f /dev/rmt/1 stat
Vendor 'IBM ' Product 'ULT3580-TD2 ' tape drive:
sense key(0x0)= No Additional Sense residual= 0 retries= 0
file no= 0 block no= 0
More detailed information about scsi tape devices can be found at: http://www.ibm.com

© Geoleader 5
 GeoStore
User manual

3 INSTALLATION AND CONFIGURATION OF GeoStore

Please, unpack GeoStore from tar gzip archive GeoStore.tar.gz into user-defined place.
GeoStore works with the same database as RAM. If RAM rdds scheme is not installed in your
Oracle database, this scheme can be installed from Oracle dump file rdds.dmp, which is located in
install/ directory in the place, where you unpacked GeoStore. RDDS user must be preliminarily created
in your database.
If Oracle database has not been installed yet, the following steps must be done:
1) Install Oracle RDBMS software with the help of setup wizard.
2) Create copy of Oracle, using Oracle DBCA utility (following documentation to Oracle)
3) Being in Oracle environment, create RDDS user (with analogous password) and load RDDS
scheme, executing the following commands:

[ora10@oblivion ~]$ sqlplus / as sysdba

SQL> create user rdds identified by rdds;
SQL> grant connect,resource to rdds;
SQL> exit
[ora10@oblivion ~]$ imp system/<system_password>
FILE=<your_GeoStore_location/install>/rdds.dmp fromuser=rdds touser=rdds

After execution of the above described operations, RDDS scheme will be created and ready for
data load.

The next steps of GeoStore configuration are described below.

1. Go to ./bin directory and open ./geos file in any text editor available.
 Set GR_HOME environment variable in accordance with location of all the
GeoStore directories
 Set ORACLE_HOME environment variable
2. Go to ./etc directory and open devices.xml. in any text editor available. This xml text file contains
information on all the input devices and disc formats used as input for transcription processes.
Please, define the names of tape devices, which will be used (just insert the right value of Drive
variable in the first two sections of Device tag). Default values: /dev/nst0 for Linux and /dev/rmt/0mbn
for Solaris.

© Geoleader 6
 GeoStore
User manual

Example:
<Device Label="&tape device\non linux host"
Icon="exabyte.png"
Host="localhost"
Drive="/dev/nst0"
Type="TAPE">
</Device>
<Device Label="&tape device\non solaris host"
Icon="exabyte.png"
Host="localhost"
Drive="/dev/rmt/1mbn"
Type="TAPE">
</Device>
………………….
…………………..
…………………..
NB! It is recommended to use device identification, as /dev/nstX for Linux and /dev/rmt/Xmbn
for Solaris (X – device identificator in your host), NOT /dev/stX and /dev/rmt/X, because of
specifications of st driver.

3. Go to ./setup directory and open ./RAM_profile file in any text editor.

 Set TWO_TASK and TNS_ADMIN variables. These variables will be used by
GeoStore to access Oracle database.

© Geoleader 7
 GeoStore
User manual

4 FUNCTIONALITY OF GeoStore

This part of the document describes all the characteristics of GeoStore, as well as main
algorithm mechanisms, used in GeoStore system.
GeoStore is runned under Motif graphic user interface. It is assumed that you are familiar with
this environment.

Fig. 1 Scheme of GeoStore system

© Geoleader 8
 GeoStore
User manual

Main functions of GeoStore:

 Storage
 Delivery
 Quality Control
 Audit

Fig. 2 Scheme of «Storage» function

Fig. 3 Scheme of «Delivery» function

© Geoleader 9
 GeoStore
User manual

Fig. 4 Scheme of «Quality Control» function

© Geoleader 10
 GeoStore
User manual

Fig. 5 Scheme of «Audit» function

© Geoleader 11
 GeoStore
User manual

5 INTERFACE

5.1 Database attribute table

Fig. 6 Database attribute table

© Geoleader 12
 GeoStore
User manual

Database attribute table shows information on current status and allows to search and select
data from the Database. The main window also gives access to Storage, Quality Control, Delivery
and Audit functions.
There is also a possibility to apply some user settings, such as to locate archive data place, copy
magnetic tapes to HDD preserving the whole tape structure, check external device status, etc., through
menu options (most menu options are not available yet, but will be activated later, if required).
After running GeoStore, the main Database attributes are loaded to be displayed in Database
attribute table on the main page.
Database attribute table may be set through sql-request, contained in bc_lr_main.sql file. Using
this request, the data (columns) from two main Database tables "barcode" and "logical_reel" are
defined, to be displayed in Database attribute table.

5.1.1 Database attribute table toolbar

The toolbar with a variety of icons is located in the upper part of the window. A tooltip is shown
when you put the mouse cursor over the icon.

Fig. 7 Toolbar

Filter Delete

Columns Export

Find Import

Sort Show headers

Select upward Viewer

Report Update

Edit Loading to PetroVision

© Geoleader 13
 GeoStore
User manual

Filter
It is a simple query designer, which helps selecting data in accordance with the user
requirements.

Fig. 8 Filter

© Geoleader 14
 GeoStore
User manual

Columns
This option allows defining columns to be displayed in the Database attribute table.

Fig. 9 Columns

© Geoleader 15
 GeoStore
User manual

Find
This function enables data search with required values.

Fig. 10 Data search

© Geoleader 16
 GeoStore
User manual

Sort
Data sorting in the Database attribute table.

Fig. 11 Sorting

Select upward

© Geoleader 17
 GeoStore
User manual

Bring the selected data to front.

Fig. 12 Selection of lines

Fig. 13 Moving selected lines up

© Geoleader 18
 GeoStore
User manual

Report
Save Database attributes to the text file.

Fig. 14 Report generation

© Geoleader 19
 GeoStore
User manual

Edit
Edit option allows manual changes in record values of the table. Press F2 to start editing, then
specify new values in the dialog window and press Apply. New values are recorded to the Database
and interactively displayed in selected lines.
The figure below shows the example of FMT_NUM_RECORDS attribute value change for
00940009.sgd record.

Fig. 15 «Edit» function dialog window

© Geoleader 20
 GeoStore
User manual

Fig. 16 Editing result

© Geoleader 21
 GeoStore
User manual

Delete
This function allows deleting selected records from the Database attribute table. The removal
is performed in the interactive mode (simultaneous deletion from the Database and from the Database
attribute table).
Confirm your decision to delete a record.

Fig. 17 Delete confirmation

© Geoleader 22
 GeoStore
User manual

The message confirming successful removal appears as below:

Fig. 18 Removal

Export
The function is designed for Database attributes export to text file.

Fig. 19 Export

© Geoleader 23
 GeoStore
User manual

Import from text file

This function allows populating the Database with the text file (flatfile) attributes.

Fig. 20 Import

Text file (flatfile) structure is similar to that of exported text file.

Fig. 21 Text file structure

© Geoleader 24
 GeoStore
User manual

Specify import parameters and press Import to start the process.

Fig. 22 Import process

The details of import process are saved to log file, which is defined in import window. If log file
is not specified, the messages are sent to terminal window. When the import process is over, the new
records are added to the Database and interactively displayed in the Database attribute table.

© Geoleader 25
 GeoStore
User manual

Show headers
This function enables showing SEGY and SEGD file headers.

Fig. 23 SEGY file EBCDIC header view

© Geoleader 26
 GeoStore
User manual

Viewer
This function runs SEGYViewer (SEGY file view program) and displays SEGY and RODE-
encapsulated SEGY file of the selected file. Set environment variable SEGY_VIEWER_HOME in
start script bin/geos equal to binary SegyViewer start file. If you have any other application which can
input RODE (SEGY) file, you may set SEGY_VIEWER_HOME equal to start file of your application.

Fig. 24 SEGY file view

Update
Data update in the Database attribute table.

© Geoleader 27
 GeoStore
User manual

Loading to PetroVision
Data generation for loading seismic information to PetroVision.

Fig. 25 Load to PetroVision

© Geoleader 28
 GeoStore
User manual

5.2 Storage

Fig. 26 Storage

© Geoleader 29
 GeoStore
User manual

«Storage» function reads the data from one of the following types of sources:
 SEGY file  LACEY file
 SEGD file  408 HD format
 RODE file  428HD format
 STAGE file  GeoRes format
 TIF file  SEGY file group
 KELMAN file  Magnetic tape

Fig. 27 List of original source data

© Geoleader 30
 GeoStore
User manual

GeoStore encapsulates the data into one of the specified formats and then archives them to the
disc. When processing tape media, GeoStore either operates in a single tape mode, or can handle up to
10 tapes at a time, in sequence, if an auto-loading stacker is used
During Storage, GeoStore uses format recognition techniques to determine the format of the
data being archived. It has the possibility to determine SEG-formats (SEG-Y, SEG-D). Depending on
the data format, GeoStore may extract some additional attribute values (from SEG-headers) and
populate the database with them.
For example, when SEG-D format is being processed, the attribute values for file classification,
record length and sample frequency are extracted and recorded to the Base.
For data in SEG-Y format, additional information may be extracted, such as a number of user-
defined trace header parameters and values from the binary header and EBCDIC header.
The data source is a device the data are read from (magnetic tape or disc file in one of the
following formats: TIF, SEGY, SEGD, STAGE, RODE, KELMAN, LACEY, 408 HD, 428HD,
GeoRes).
Storage parameters – magnetic tape or encapsulated format: STAGE, RODE, TIF, KELMAN,
LACEY, SEGY, Pude Data, 408 HD, 428HD
Run button activates status-line and starts the algorithm.
Details on Storage process are displayed on statistics bar in the lower part of the window. It can
later be saved to the log-file.

© Geoleader 31
 GeoStore
User manual

Archive process
1) Select input source type from the list in Data source section. If the tape media name is
correctly defined in $GR_HOME/etc/devices.xml file, the device status will appear immediately.
2) If the tape media is selected as input data for Storage, the upper part of Data source section
will contain some functions for device control: rewind, go to next file, tape ejection, etc. The Barcode
is at the center of Data source section. Before archiving, specify the barcode here, which later will be
added to Database.

Fig. 28 Input data specification

3) The tape media type may also be specified by Robot feed option. Press this button to switch
to the mode, which supports control of up to 10 barcodes at a time.

Fig. 29 «Robot feed» function

© Geoleader 32
 GeoStore
User manual

4) TIF, STAGE, RODE, SEGY files may also be chosen as input source. When one of them is
chosen, select TIF, STAGE, SEGY or RODE file, press Add and choose the necessary file. In this case
the barcode is generated as input file name and added to the Database when storage process is over.

Fig. 30 RODE files selection

© Geoleader 33
 GeoStore
User manual

5) The data may also be retrieved from 408HD format. When this format is chosen as input,
press Add and choose one of the files from the directory with 408HD SEGD files. After that, define the
barcode in the field below.

Fig. 31 SEGD file selection

6) Then define the output file type. Choose the required output format type and fill the field
"Destination" manually or through the dialog, which appears by pressing the button on the right.

Fig. 32 Definition of storage parameters

© Geoleader 34
 GeoStore
User manual

After that press Storage and watch the archiving progress.

Fig. 33 SEGD file archiving process

After the successful completion of Storage process, the last line in the Database attribute
table will contain information, which has just been archived.
During archiving operation the fields "barcode" and "logical_reel" in the table are populated
with the following mandatory attributes:
barcode: BC_ID, INPUT_SOURCE_BC, INPUT_TYPE,STORE_INPUT_DEVICE, STORE_STATUS,
STORE_TIMESTAMP, DISK_OUTPUT_PATH, OUTPUT_FILENAME, OUTPUT_FILESET_NUM,
OUTPUT_FILE_ID, OUTPUT_TYPE
logical_reel: LR_ID, BC_ID, LINE, FMT_SRATE, FMT_RECLEN, FMT_FIRST_RECORD,
FMT_LAST_RECORD, FMT_FORMAT, FMT_NUM_RECORDS, FMT_NUM_BYTES, SEGD_SEIS_CHANNELS,
SEGD_AUX_CHANNELS, SEGD_FCODE

© Geoleader 35
 GeoStore
User manual

The special file log_settings.ini has to be set, in case the additional information needs to be
retrieved from SEGD and SEGY file headers and saved to the Database.

#TYPE VAR_NAME FIRST_BYTE FORMAT REPORT_INTO_DB

#-------------------------------------------------------------
SDFH FRMT 3 INT2 REP
SDTH TRCN 5 INT4 REP
SYBH SPLI 17 INT2 REP
SYTH CDPN 25 INT4 REP
SYTH FMT_SRATE 117 INT2 REP
SYTH CDPN 205 INT4 REP
SYTH FMT_SRATE 209 INT4 REP
SDFH FORMAT 5 BCD4 LST
SDTH TRCN 5 BCD4 REP
SYBH S_RATE 17 INT2 LST
SYTH FIRST_RECORD 1 INT4 MIN
SYTH LAST_RECORD_NO 1 INT4 MAX
SYTH RCVR_Y_COORD 81 IEEE REP

Fig . 34 log_settings.ini file structure

TYPE may be set to:

SDFH - SEGD file header,
SDTH - SEGD file trace header,
SYEH - SEGY file EBCDIC header,
SYBH - SEGY file binary header,
SYTH - SEGY file trace header.

REPORT_INTO_DB may be set to:

REP - retrieved information is not saved to the Database, but is put to log file (report);
MIN - minimum attribute value is saved to the Database,
МАХ - maximum attribute value is saved to the Database,
FST - first attribute value is saved to the Database,
LST - last attribute value is saved to the Database.

VAR_NAME – the name of the additional attribute in the logical_reel table

© Geoleader 36
 GeoStore
User manual

FIRST_BYTE – byte number in file

FORMAT – data format, where, for example,

INT2 – sign integer of 2 bytes length,
INT4 – sign integer of 4 bytes length,
BCD4 – sign number in binary-decimal code of 2 bytes length,
IEEE – real number with floating point in IEEE format of 4 bytes length

In order the additional attributes to be read from SEGD and SEGY file headers, specify the log
level in Global log settings.

Fig. 35 Log-file settings

© Geoleader 37
 GeoStore
User manual

Fig. 36 1st level log selection

0 log level - additional attributes will not be read, log-file is not generated
1 log level - additional attributes will be read from file headers, log-file is generated
2 log leve - additional attributes will be read from trace headers, log-file is generated

Fig. 37 1st level log-file contents

© Geoleader 38
 GeoStore
User manual

Fig. 38 2nd level log-file selection

Рис. 39 2nd level log-file contents

© Geoleader 39
 GeoStore
User manual

5.3 Delivery
The Delivery function reads encapsulated data from encapsulated formats, de-encapsulates it
and then outputs to the tape.
To run the Delivery function, first select data in the Database attributes table.

Fig. 40 Delivery

© Geoleader 40
 GeoStore
User manual

The upper part of the window contains the table with information on encapsulated files,
received as a result of Storage process.
The storage parameters – a device, specified for storing the data, received from Delivery
operation. The tape media may be rewind forward or back or after Delivery operation execution.
The other functions are the same as in Storage option. Just choose the tape for transcription
from the list in Storage parameters section and run Delivery process.

Fig. 41 Delivery to tape medium

© Geoleader 41
 GeoStore
User manual

5.4 Quality Control

Quality Control function verifies the archive data integrity by bit-comparing it with the
original data from the input media.

Fig. 42 Quality Control

© Geoleader 42
 GeoStore
User manual

Quality Control job runs until the file end mark in both data flows or until the error is detected.
Before running Quality Control function, select the data in the Database attributes table.
Information on encapsulated file will appear in the upper part of Quality Control window. Specify the
data source, where encapsulated file has been retrieved from during Storage process.
Press Quality Control to run the data bit-comparison algorithm. The user is notified after each
step in the job progress.
When the Quality Control is completed successfully, GeoStore outputs the operation status to
the Database, which can later be found in the Database attributes table.

© Geoleader 43
 GeoStore
User manual

5.5 Audit
Audit function checks the encapsulated archive data.
GeoStore reads the encapsulated format (RODE, STAGE, TIF) data from the storage and de-
encapsulates it. Then it employs format recognition techniques to determine data format and,
depending on this, extracts certain attribute values from the data.

Fig. 43 Audit

© Geoleader 44
 GeoStore
User manual

Before running Audit function select the data from the Data attributes table.
The upper part of the window in Data source section will show the information on selected file.
As a result of Audit function, the selected file will be parsed, the file attributes may be found on
statistics bar at the bottom of the window. This information may later be saved to the audit-report file.

© Geoleader 45
 GeoStore
User manual

6 DESCRIPTION OF SUPPORTED ENCAPSULATED FORMATS

Digital data comprise the base for the exploration geophysics. The formats used for data and
client information are designed for the very specific needs, which to a large extent are determined by
the available storage systems. As a consequence, these formats depend on discipline, system and
application. These data are archived and stored for many years. There are several millions seismic tapes
at production site. These archives grow fast with the increase of 3D survey usage for exploration and
estimation.
The new high efficiency media may lower the cost of the survey, processing and storage, and
help organize automatic access to the vast volumes of digital data. The processing options are oriented
towards the support of new devices and formats, thus protecting the investments made to the existing
software and data processing options, basing on work experience with the old and new devices. The
standard encapsulated format is the conventional way of migration the old data to the new environment.
It allows recording the new data to the new media rationally, using the existing formats.
The introductory part of the document states that the main GeoStore function is reading E&P
data from the original media, encapsulating it to specialized format and then outputting the archived
data to storage. Now we go over to the brief description of the supported encapsulated formats (also
called archive formats).

© Geoleader 46
 GeoStore
User manual

6.1 Seg Rode

The RODE format has first been issued in 1996 as a method of well log encapsulation. This
method had been employed by different oil companies: Shell, Mobil, CGG, etc. Nowadays RODE is
often used as a method of encapsulating the seismic data, which contains the information on original
tape structure, as well as on some additional attributes about organization, acquisition. Rode is a very
complicated encapsulation mechanism. More detailed information may be found at:
 http://www.seg.org/SEGportalWEBproject/prod/SEG-Publications/Pub-Technical-
Standards/Documents/seg_rode.doc
 http://www.posc.org/technical/data_exchange/RP66/V2/rp66v2.html

© Geoleader 47
 GeoStore
User manual

6.2 Stage

STAGE – tape disc image. It is an encapsulated format, commonly used for storing seismic
data on the disk. Each block starts with 4-byte field, containing the size of this block in bytes. EOF
(end of file indicator) is represented by 20 bytes, containing ASCII line ">>>>End of file<<<<",
following the byte, containing 0x00 value, which is the line end.

© Geoleader 48
 GeoStore
User manual

6.3 TIF (Tape Image Format)

This encapsulation format is more commonly used for well logs, rather than for seismic traces.
It has been developed by Dresser Atlas for well log storage on the disk. Each record starts with three 4-
byte integer fields, each of them written in little-endian byte order. The first 0 number (normal record)
or 1 (file indicator), the second is the shifting in bytes of the previous record start, the third is the
shifting in bytes of the next record start. Since the absolute shifts are used, the file size is limited to
4GB. TIF8 format has been developed for TIF extension. It is based on 24-byte prefix with ASCII
“TIF8” symbols, followed by 4-byte record type and two additional blocks with shifts, each of them is
now 8 bytes instead of 4. TIF also uses little-endian order. GeoStore supports only the original TIF.

© Geoleader 49
 GeoStore
User manual

6.4 LACEY

LACEY – 8-byte introductory header.

LACEY is an encapsulated format for any type of data. It is very simple and consists of byte
stream, composed from all the data blocks, concatenated by adding to the beginning of each 8-byte
header. The first 4 bytes is a sequence of blocks inside the data set, and the second is a byte size of the
block, following the header.
The byte sequence order and integer lengths are big-endian.
Example. Hex dump of Seg-Y record is coded as Lacey disk file. The number sequence is red,
the block size is blue. The number is represented in hexadecimal system, for reference: hex c80 is 3200
in decimal. Hex 190 is 400 decimal. Hex 1860 is 6240 decimal.

00000: 00000001 00000c80 c340f140 c3d3c9c5 d5e34040 40404040 40404040 40404040

00032: 40404040 40404040 4040c3d6 d4d7c1d5 e8404040 40404040 40404040 40404040
00064: 40404040 40404040 c3d9c5e6 40d5d640 40404040 40404040 c340f240 d3c9d5c5
.
. Some lines removed
.
03168: 40404040 40404040 40404040 40404040 40404040 40404040 40404040 40404040
03200: 40404040 40404040 00000002 00000190 000083d0 00000018 00001125 00600000
03232: 07d007d0 05dc05dc 00010000 00010001 00000000 00000000 00000000 00000000
03264: 00010002 00010000 00000000 00000000 00000000 00000000 00000000 00000000
.
. Some lines removed
.
03584: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
03616: 00000003 00001860 00000001 00000001 0000019f 00000001 00000000 00000000
03648: 00000000 00010001 00000001 00000000 00000000 00000000 00000000 00000000
03680: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
.
. Some lines removed
.
09824: be3cf800 be5a8800 be70bc00 be7e7400 be827800 be7ca000 be6de000 be57d800
09856: be3cc000 406e8c00 00000004 00001860 00000002 00000002 0000019f 00000002
09888: 00000000 00000000 00000000 00010001 00000001 00000000 00000000 00000000
09920: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

© Geoleader 50
 GeoStore
User manual

6.5 KELMAN

It is a disk format used for record block size and file marker storage.
KELMAN format consists of two files. Data file, which is a binary copy of data from the
record, recorded as a flow to the disk file without any structure. The second file – index file - contains
information about tape structure, as described below.
1. 12-byte header, which seems out-of-date, but is necessary for compatibility support. This
header may be read or ignored.
2. The remaining part of the file is a series of 36-byte records (described below)

Byte Description
1-4 File number. The series starts with 1, goes up with each EOF
5-8 obsolete, ignored
9-12 Record number. The series starts with 1 and goes up with each record.
13-20 obsolete, ignored
21-24 Record length. Length in bytes, goes up with each EOF.
25-36 obsolete, ignored

Example:
00000: 00000001 000000a9 0000ae7e 00000001 00000000 00000001 00000000 00000000
00032: 00001e00 00000000 00000000 00000000 00000001 00000000 00000002 00000000
00064: 00000000 00001888 00000000 001e0000 00000000 00000001 00000000 00000003
00096: 00000000 00000000 00001888 00000000 88360000 00000000 00000001 00000000
00128: 00000004 00000000 00000000 00001888 00000000 104f0000 00000000 00000001
00160: 00000000 00000005 00000000 00000000 00001888 00000000 98670000 00000000
.
. Some lines removed
.
07264: 00000000 00001888 00000000 40481300 00000000 00000001 00000000 000000cb
07296: 00000000 00000000 00001888 00000000 c8601300 00000000 00000001 00000000
07328: 000000cc 00000000 00000000 00000000 00000000 50791300 00000000 00000002
07360: 00000000 000000cd 00000000 00000000 00001e00 00000000 50791300 00000000
07392: 00000002 00000000 000000ce 00000000 00000000 00001888 00000000 50971300
07424: 00000000 00000002 00000000 000000cf 00000000 00000000 00001888 00000000

Note that the underlined record is EOF.

© Geoleader 51