Acquisition_3D

General

Seismic acquisition on land or marine, carried in an area by equally spaced lines is defined as 3D acquisition. Typically in marine, the vessel navigates along a planned line by pulling multiple streamers (receiver cables) and the energy source tied to the boat. The energy source (Air Guns) is fired at each fixed interval forming a line of common mid points (CMPs) between the energy source and receivers on the cable. The seismic reflection data is then recorded by onboard seismic recording systems connected to the cables, for further processing. Onboard navigation systems provide positioning of the receiver positions and source positions. The vessel then navigates to the next line and the process is repeated until it covers the whole area planned for 3D seismic survey. On land, the seismic cables are laid at equally spaced intervals and the vibrator or dynamites are fired at fixed intervals (distance) forming CMPs between the seismic receivers and seismic source. The seismic reflection data is recorded by the recording system connected to the cable and the positioning of receivers on cable and energy source provides the CMP location of seismic reflection.

Acquisition_3D defines acquisition parameters for 3D seismic acquisition and inherits all the properties of the class Entity. At least Name, Remarks of Entity object must be defined to make Acquisition_3D meaningful.

Acquisition_Start_Date and Acquisition_End_Date define the start and end of the survey conducted to acquire the seismic data and may be filled whenever the dates are available.

Cable_Count, Cable_Depth, Cable_Length, Cable_Spacing, Energy_Source_Depth, Group_Channel_Count, Group_Count, Group_Interval, Line_Count, Line_Spacing, and Source_Count, Source_Spacing must be filled for Seismic 3D acquisition whenever they are available.
Marine_Land must be filled with "Marine" if the acquisition area is offshore and "Land" if the acquisition area is on Land.

Usage Rules

1. Acquisition_3D object must refer to Survey_3D with Survey_Data_Type as "Seismic Data".
2. Seismic data collected must be stored as Geophysical_Inventory items with Acquisition_Format "SEGD" and Acquisition_Data_Type as "ACQUISITION_SEISMIC".
3. Navigation data representing receiver and source positions must be stored as Geophysical_Inventory item with Acquisition_Format "UKOOA_P2" and Acquisition_Data_Type as "NAVIGATION_DATA". Spatial positions of receiver and source can be stored as Line.
4. Report files can be stored as a Geophysical_Inventory item with Acquisition_Data_Type as "REPORT".
5. Image files can be stored as a Geophysical_Inventory item with Acquisition_Data_Type as "IMAGE".

Alternative_Navigation

Application_Project

General

Seismic interpretation applications store seismic data belonging to a seismic survey in terms of projects. These projects contain seismic trace data, navigation data associated with the seismic survey. Normally this data is stored in a datastore with access controls.

Application_Project provides attributes necessary to access the project data of the interpretation project storage for which the seismic survey data is associated. Application_Project inherits all the properties of the class Entity. At least Name of Entity class must be defined to make Application_Project meaningful.

Account_Name, Account_Password must be filled to provide an access to the interpretation project.
App_Project_Unique_Locator must be specified to find the seismic data storage in the application project.
Seismic_Boundary_Polygon must be defined to cover the project area.

Usage Rules

1. Account_Name and Account_Password must be secure and must be encrypted.

Archive_File_Inventory_X

General

Archive_File_Inventory_X is an intersection class that provides the details of archive file and the names of the files stored in an archive file, along with location information in the archive file..

Borehole_Seismic_Acq_Act

Borehole_Seismic_Survey

Dataset_Inventory_X

Dataset_Representation

General

Dataset_Representation defines the storage cube (brick) size and the compression factor at a remote datastore. It is common to divide large seismic cubes of data into small cubes (bricks) and store the data as a sequence of bricks either in I_Axis direction or J_Axis direction.

Usage Rules

1. Brick_Storage_I_Size, Brick_Storage_J_Size, Brick_Storage_K_Size must all be positive.
2. Compression_Factor must be expressed between 0 and 1 (0 indicating lower and 1 indicating higher level) to represent the level of compression.

Geophysical_Inventory

General

Geophysical_Inventory holds all the files/tapes associated with the seismic data. The seismic data could be related to acquisition 2D/3D, processed 2D/3D, or interpretation workstation seismic data.

Geophysical_Inventory inherits all the properties of the object Entity. At least Name of Entity object must be defined to make Geophysical_Inventory meaningful.

Usage Rules

1. Foreign_Object_Id must be filled with legacy foreign repository system id if the file has been migrated from another repository system.
2. MMS_Tape must be filled with Western Geco tape identification number on robotic system if the file is synchronized with the Western Expeditor system.
3. Tape_Creation_Date must be filled with the date the data was originally written to the tape.
4. Author should be filled with the name of original tape creator.
5. Barcode may be filled with Western Geco's barcode identification system.
6. Usage Note: The Inventory_Item_Rank column in this table will be deprecated in a future Seabed release and replaced with a column called Sequence_Number to be more consistent with the meaning of this column.

Header_Template

General

Sometimes the seismic data recorded may deviate from the standard defined by the industry in order to store some special information. It is also possible to change the meaning of the attribute stored in the data. Because of this, it may be necessary to clearly define some attributes of the header associated with the dataset.

Header_Template defines the attributes necessary to identify the format and type of header being defined. It has association with Header_Element to store individual data items.

Inventory_Boundary

General

This provides a view into Seismic_Boundary_Polygon for boundaries which describe the areal limits of export jobs.

Live_Trace_Boundary

General

This provides a view into Seismic_Boundary Polygon for areas that define the boundary of live traces.

MS_Event_Detail

Project_Boundary

General

This provides a view into Seismic_Boundary Polygon for boundaries that describe the areal limits of projects.

R_Acquisition_Data

General

R_Acquisition_Data reference table provides codes necessary to select the object type of acquisition seismic or navigation data collected during seismic survey. If the data is navigation, it should "NAVIGATION_DATA" and if the data is seismic it should be "ACQUISITION_SEISMIC".

R_Borehole_Seismic_Survey

R_File_Type

General

R_File_Type reference table provides codes necessary to select the type of inventory file. Ex: "ASCII", "BINARY", "EBCDIC".

R_MS_Event_Type

R_Point_Type

General
The UKOOA P1/90 standard defines the following point types:
"S” = Center of Source
“G” = Receiver Group
“Q” = Bin Center
“A” = Antenna Position
“T” = Tailbuoy Position
“C” = Common Mid Point
“V” = Vessel Reference Point
“E” = Echo Sounder
“Z” = Other (defined in H0800 record)
Usage Rules:
The UKOOA standard has a record identification assigned to each point, however the usage here is that a point type is assigned to a line.

R_Recording_System

General

R_Recording_System reference table provides codes necessary to select recording system used in acquiring seismic data.

R_Seismic_Data_Type

General

R_Seismic_Data_Type reference table provides codes necessary to define whether the data is PROCESSED SEISMIC, SEISMIC VELOCITY, or POSTPLOT NAV.

R_Seismic_Format

General

R_Seismic_Format reference table provides codes necessary to select the seismic format of the dataset. For example: SEGY, or UKOOA_P1.

R_Seismic_Line_Style

General

R_Seismic_Line_Type reference table provides codes necessary to define the contents of seismic line. For example,, navigation only, seismic only, or seismic with nav.

R_Seismic_Receiver

R_Seismic_Survey_Alias

R_Seismic_Transaction

R_Streamer

R_Tape_Label

Sail_Line_Owner

Seismic_Acquisition_Act

Seismic_Boundary_Polygon

General

The subtypes of Seismic_Boundary_Polygon define the spatial boundary defining the area covered by a survey, project, dataset, or partial selection of a seismic data set.


Usage Rules

1. Use "Live Trace Boundary" subtype for a boundary that relates to seismic data set with trace data.
2. Use "Survey Boundary" subtype for a boundary that relates to seismic survey.
3. Use "Saved_Item_Boundary" for a boundary that relates to saved selections.
4. Use "Purchase_Boundary" for a boundary that relates to purchases.
5. Use "Entitlement_Boundary" for a boundary that relates to entitlement items.
6. Use "Inventory_Boundary" for a boundary that relates to items in inventory.
7. Use "Project_Boundary" for a boundary that describes the limits of an application project.
8 Use "Export_Boundary" for a boundary that describes the limits of an export job.
9. Use "Dataset_Boundary" for a boundary that describes the limits of an export job.

Seismic_Dataset_2D

General

This child was created to provide a view into Seismic_Dataset for the 2D case.

Seismic_Line

General

Seismic_Line object defines the attributes for each line belonging to processed seismic or interpretation project seismic survey composed of lines.
Seismic_Line inherits all the properties of the object Entity. At least Name of Entity object must be defined to make Seismic_Line meaningful.
A Seismic_Line should belong to only one survey.

Foreign_Object_Id must be defined if the data is synchronized with other repository system.
Nominal_Line_Length, Nominal_Shot_Interval must be entered if available.
Shot_Divisor is needed only for Western Geco's multi client data.

First_CDP, Last_CDP, and CDP_Increment or First_Shot, Last_Shot, and Shot_Increment must be entered for each line.
Line_Geometry must be defined for each processed 2D seismic and interpretation 2D seismic.

Usage Note: The Line_Rank column in this table will be deprecated in a future Seabed release and replaced with a column called Sequence_Number to be more consistent with the meaning of this column.

Seismic_Line_Correction

Usage Rules
If a surface (Horizon_Interp_2D_Geom) is specified then Seismic_Line_Id must refer to the same Seismic_Line specified in that instance of Horizon_2D_Interp_Geom.
Shift_Property only applies to First_Shift and Last_Shift. If the shift values are stored in a bulk array use the property in the bulk array.

Seismic_Line_Tie

To avoid discrepancies, .only one method SP,CDP or Position, should be used to describe the tie.

Seismic_Record

General

Seismic data is recorded in terms of seismic headers and seismic records using Society of Exploration Geophysicists standards like SEG-D and SEG-Y. Sometimes it is necessary to store some records in their entirety, rather than only some attributes of the records.

Seismic_Survey

20-
General

Seismic_Survey is the top level object of the seismic data model and it must be filled for all types of seismic data. Seismic_Survey inherits all the properties of the object Entity. At least Name of Entity object must be defined to make Seismic_Survey meaningful.

The following attributes of Seismic_Survey must be filled in as specified for various types of seismic data.
Survey_Area_Name must be filled in for all types of seismic data.
Survey_Project_Name must be filled in for 2D or 3D acquisition seismic data.
Survey_Prospect_Name must be filled in for acquisition and processed seismic data.
License_Holder must be the owner who has an access to the data and must refer to the company/group defined as a Business_Associate.

Usage Rules

1. Seismic_Survey must reference an App_Project_Source, if the data came from an interpretation workstation project.
2. Survey_CRS must be specified for all types of seismic data.

Seismic_Survey_BA_Int

SP_CDP_Mapping

General

SP_CDP_Mapping defines the relationship between shotpoints and common depth points (CDP) for processed 2D seismic and interpretation 2D seismic.
SP_CDP_Mapping inherits all the properties of the object Entity. At least Name of Entity object must be defined to make SP_CDP_Mapping meaningful. These attributes must define the unique nature (may include the segment of the line in name) of the mapping to be meaningful.
First_CDP, Last_CDP, First_Shot_Point, Last_Shot_Point must be entered for each mapping.

Survey_2D

General

Survey_2D is a generalization of Seismic_Survey and inherits all attributes of Seismic_Survey. Please see the description/usage rules associated with Seismic_Survey.

Survey_Boundary

General

This provides a view into Seismic_Boundary Polygon for boundaries that describe the areal limits of 3d seismic surveys.

Treatment_Dataset