NaviPac UKOOA Exporter. Author: Alex Fischer Andersen Company: EIVA a/s Date:

Transcription

1 NaviPac UKOOA Exporter Author: Alex Fischer Andersen Company: EIVA a/s Date:

2 Table of Contents Revision table 2 1 PRINCIPLE 3 2 HEADER EDITOR Header view NaviPac based header setup Manual header setup Comments 7 3 DATA EXPORT Settings 8 Static Header 9 Runline 10 Sound velocity profile 10 Setup file 10 Data files 10 Vessel Id 10 Secondary Vessel 11 Inter event data 11 Display data Run exporter Data Format Event records Inter event records 12 Revision table Date Who Comment AFA Created OKR Upgraded to latest version OKR Version 3.8 Upgraded GUI 2

3 1 PRINCIPLE NaviPac Ukooa Exporter exports NaviPac data in P2/94 format. This requires some manual definition of header files, as some information has to be entered by the operator and some can be fetched from the NaviPac set-up database gensetup.db. The module is designed as an application running alongside NaviPac: The program is divided into two parts a header import/editor part and a data converter part. 2 HEADER EDITOR Some header data can be generated on basis of the NaviPac setup (saved in gensetup.db) but others have to be defined manually by the operator. To make this as easy as possible for the operator the program allows individual import and editing for each header group. H00 General Definition o H0000 taken from survey file name o H0008 taken from survey file o Rest manually specified H01 Geodetic Definitions o H0100 and H0101 manually specified o Rest taken from set-up file H02 Survey Definitions 3

4 o H0200 partly taken from set-up file o H0211 partly taken from set-up file o H0221 partly taken from set-up file o H0231 manually o H0241 partly taken from set-up file H1 Vessel Definitions o H1010 H141# taken from set-up file o H1500 & H1501 manually o Rest taken from set-up file H2 Streamer definitions o All partly taken from set-up file H3 Gun array definitions o All specified manually H4 Towed body definitions o All partly taken from set-up file H5 Survey Network Definitions o H5000 manually o H5110 from set-up file o Rest manually H6 Satellite System Definitions o H600# partly taken from set-up file o H620# partly taken from set-up file o Rest manually H7 User defined Observation Sets o Manually 2.1 Header view The one and only view in the UkooaExp is a textbased header view, intended to hold and display the header part of the ukooa export file. This view can also be used for the data part, as they can be appended to the view while exporting, and it can be used for opening and viewing of other ukooa files, as well as text based files in general. 4

5 The header can be freely modified by the user when inside the view, so it is the user responsibility to leave it into the right format, but a Format helper dialog and format help on the status bar, makes inspection and format easier. This format help conforms to the ukooa P294 specification, as it is taken directly from the original document. The status bar displays the actual field that the cursor is within, the size and limits of that field, and the datatype and the description for that field. The same help is found in the Format helper dialog, which is invoked on the current cursor line by clicking the on the toolbar or by holding down CTRL when clicking on the line to inspect. 2.2 NaviPac based header setup Insert all or part of the np setup into the header view by selecting in menu list. Anywhere in the headerview additional items can be inserted, by positioning the cursor somewhere at an existing line. If cursor is placed at the first colon (char) of a line, insertion will happen before that line, else it will happen after that line. Then select Head Insert\Navipac Setup\some group and that group is converted from the NaviPac db to the view. 5

6 All header data can be inspected after insertion and eventual manual completed, line by line for data content and conformation with the format rules. The entries inserted at each command will be sorted after header id, within the group related to that command. Data from set-up are formatted as specified, unless some information must be user specified, and marked with a?. Lines ending with? does not have the appropriate length of 80 chars and must be completed by the user. 2.3 Manual header setup Manual defined data can be guided from a menu, to an appropriate format. Anywhere in the headerview additional items can be inserted, by positioning the cursor somewhere at an existing line. If cursor is placed at the first colon (char) of a line, insertion will happen before that line, else it will happen after that line. Manual Item brings up a list of header items to select. 6

7 Clicking an item and pressing the Fill & Insert button brings up the Format helper dialog (se above), for formatting the particular item, and afterwards insertion in the header view. The Insert definition button just inserts the line selected in the header view. Lines edited by the Format helper dialog do have the fixed length of 80 chars. It is the users responsibility to ensure correct length and correct format on lines formatted/edited without the Format helper dialog, as it is possibly to edit (and corrupt) all lines freely, direct in the view, as well as it is possibly to import other header files, and to copy, cut and paste direct in the view Comments Comment can be inserted anywhere in the header by selecting a line (clicking it) and pressing. Then at the following line C001 will be inserted, and comment must be written direct in the view, and should have length 80 (append spaces to reach 80). User must modify type if other than C001 is needed. Ukooa have these rules for comments: 7

8 Additional Comments Three comment records are available for general, free text comments, considered relevant to the survey. C for information related to the entire project; C for information related to the seismic line only; C for information related to (inter-)event data. Any number of these records may be inserted in the data. C0001 and C0002 records may appear anywhere among the other header records, but after record H00@9. 3 DATA EXPORT 3.1 Settings There are a series of settings that the operator must be aware of prior to using the exporter. Please note that this also applies to the header definition. 8

9 Static Header The static header file is a tool that allows you to enter static text information that will replace unknown messages in the header. The software will search in all headers after? (things NaviPac don t know) and look it up in the INI file. The file must be defined like: [StaticHeaders] H1500-7= H =Some text H1621-9=1234 H =APJ TEST 9

10 The first part identifies the header number (eg H1500) and the second part defines the starting character (eg -7). Example: H1621-9=1234 Will modify the line H1621 2???? To H Note: The static information will not be activated until you enable the menu Export, Parse static headers Runline You may select reference to used runline file. The information will be used to generate the header data. Reference: H0008 & H0009 Sound velocity profile You may select reference to used sound file. The information will be used to generate the header data. Reference: H1500 & H1501 Setup file The UKOOA exporter is very dependent of the match between the selected files and the NaviPac setup. As default the exporter uses the setup in the default NaviPac database (\eiva\navipac\db\gensetup.db) but you may overrule this by selecting another file. Data files Select the NaviPac data files to be converted to ukooa data. You may remove a file by selecting it and pressing remove. Vessel Id The Applied Vessel ID inserted here is used as base both for header insertion and data export, and cannot be changed within an export. 10

11 Secondary Vessel The UKOOA exporter may add secondary vessel information to the file. This goes a.o. for a towed seismic operation where the towfish represents the secondary vessel. In that case you must enter the NaviPac object number and the vessel Id to use in the output file Inter event data Inter-event data of type T (if any in the NaviPac data) can be included in the export by selecting here. Display data Append exported data to headerview, writes the data to the header view while exporting, visualizing the data export, but also slowing down the export, therefore a progress bar will appear under export. 3.2 Run exporter Clicking or the menu Export\Run exporter starts the export, by first bringing up the export settings dialog, and the prompting for export file name and path. File name is automatically suggested as NaviPac data file name +.UkooaP294.txt. 3.3 Data Format The operator must specify if the exporter should handle event-only (default) or events and inter events data. Events are recorded in E records and inter events in T records Event records Includes one total data series for each generated event (shot-point) E1. Vessel related data E1000 General event data Line name, event number, date and time. Seismic identifier left blank E12@0 Positioning data Position of all relevant objects E14@0 Echosounder data E16@0 USBL Data 11

12 Motion data E2 Streamer data Streamer compass data Aux data Not available Streamer depth data E3 Gun array data Not available E5 Network data E52## Gives gyro data All other not available E6 GPS data E620# GPS data E621# GPS data continued All other not available E7 User defined data Not available Inter event records If selected, then the following inter event data will be available: T1. Vessel related data o T14@0 Echosounder data o T16@0 USBL data o T17@0 Motion sensor data T5 Network data T52## Gives gyro data All other not available T6 GPS data E620# GPS data E621# GPS data continued All other not available T7 User defined data Not available 12