| Name | Fault_Polyline |
|---|---|
| Entity Type | Table |
| Description | A single polyline (stick) describing an interpretation. |
| Submodel | Seismic_Interpretation |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Closed_Flag | boolean | NA |
A flag to indicate if the polyline is closed or open. A value of 1 indicates that the polyline is closed. | No |
NUMBER(1) |
| Existence_Kind | REF_EXISTENCE_KIND | NA |
A reference value that describes the state of existence in the lifecycle of the entity, for example, Planned, Predicted, Required, Simulated, and Actual. | Yes Actual |
VARCHAR2(64) |
| GUID | STRING128 | NA |
Globally Unique IDentifier for an instance of a class. USAGE NOTES: There are two cases: 1) GUID is not populated or used; and 2) it is populated with a value that is globally unique. If the GUID is populated there are two means of doing so for a given project: 2a) Seabed automatically generates and populates the GUID when an instance is created (valid only on Oracle based systems); and 2b) the GUID is generated and populated by an application (other than Seabed) on instance creation. Whether Seabed automatically generates GUIDs for a project is determined by the Auto_GUID flag in SDS_Account. Note that techniques 2a and 2b can coexist in the same project. When GUIDs are automatically generated an application can override the automatically generated GUID with its own GUID by simply supplying the GUID value. Applications that generate their own GUIDs and populate the GUID column will function correctly on projects which have automatic GUID generation turned on. | No |
VARCHAR2(128) |
| Id | ID | No_Unit |
Unique identifier for this entity. | Yes |
NUMBER(38) |
| Insert_Date | DATE | NA |
Date the entity was created in the repository | No |
DATE |
| Insert_User | STRING64 | NA |
The name of the user responsible for the creation of this entity in the repository. | No |
VARCHAR2(64) |
| Interpreted_Feature_Type | STRING64 | NA |
The type of feature that is described by the polyline, for example a fault. This is a denormalization. | No |
VARCHAR2(64) |
| Line_Id | Line |
|
The line which describes the fault segment in 3D. | No |
NUMBER(38) |
| Maximum_X | double | No_Unit |
The maximum X coordinate value of the points in the fault segment | No |
NUMBER |
| Maximum_Y | double | No_Unit |
The maximum Y coordinate value of the points in the fault segment | No |
NUMBER |
| Maximum_Z | double | No_Unit |
The maximum Z coordinate value of the points in the fault segment | No |
NUMBER |
| Minimum_X | double | No_Unit |
The minimum X coordinate value of the points in the fault segment | No |
NUMBER |
| Minimum_Y | double | No_Unit |
The minimum Y coordinate value of the points in the fault segment | No |
NUMBER |
| Minimum_Z | double | No_Unit |
The minimum Z coordinate value of the points in the fault segment | No |
NUMBER |
| Name | ENTITY_NAME | NA |
The name given to any object or data item, e.g. name of Well, name of Field, etc. | No |
VARCHAR2(255) |
| Number_of_Points | ID | NA |
Number of points | No |
NUMBER(38) |
| Original_Source | STRING64 | NA |
The name of the person, Organization or project source that originally provided this entity, e.g. "IHS-EnergyData" or "FinderUpper Stratton Deeper Pool 15" | No |
VARCHAR2(64) |
| Polyline_Set_Id | Polyline_Set |
|
The Polyline set containing to which the Fault Polyline belongs. | Yes |
NUMBER(38) |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Remarks | STRING2000 | NA |
Any type of remarks added to an entity instance. | No |
VARCHAR2(2000) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Section_Name | STRING255 | NA |
The name of the seismic section on which the fault segment is interpreted. | No |
VARCHAR2(255) |
| Section_Type | STRING32 | NA |
The type of section on which the fault segment has been interpreted. | No |
VARCHAR2(32) |
| Segment_X_Unit | STRING64 | NA |
x unit of segment | No |
VARCHAR2(64) |
| Segment_Y_Unit | STRING64 | NA |
y unit of segment | No |
VARCHAR2(64) |
| Segment_Z_Unit | STRING64 | NA |
z unit of segment | No |
VARCHAR2(64) |
| Seis_Geom_Set_Id | ID | NA |
Seis Geom Set ID | No |
NUMBER(38) |
| Seismic_Line_Id | Seismic_Line |
|
The seismic line on which the polyline was picked. | No |
NUMBER(38) |
| Sequence_Number | int | No_Unit |
The sequence number of the fault segment in the polyline set. | Yes 1 |
NUMBER(10) |
| Source | STRING64 | NA |
Name of the person or organization responsible for this entitys E and P content and quality. Not the data technologist or IT expert creating the entity, for which see IT_Object.Insert_User and Update_User. | No |
VARCHAR2(64) |
| Survey_3D_Id | Seismic_Dataset_3D |
|
The 3D seismic survey on which the polylines were interpolated. | No |
NUMBER(38) |
| Survey_Name | STRING255 | NA |
The name of the survey that contains the line on which the fault segment was interpreted. | No |
VARCHAR2(255) |
| Update_Date | DATE | NA |
Date of the most-recent modification to the entity. | No |
DATE |
| Update_User | STRING64 | NA |
The name of the user responsible for the last modification to this entity. | No |
VARCHAR2(64) |
| Version | STRING255 | NA |
The form or variant of the entity. | Yes 1 |
VARCHAR2(255) |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Seismic_Line | Seismic_Line | The seismic line on which the polyline was picked. | Restrict | No |
| Survey_3D | Seismic_Dataset_3D | The 3D seismic survey on which the polylines were interpolated. | Nullify | No |
| Line | Line | The line which describes the fault segment in 3D. | Control | No |
| Polyline_Set | Polyline_Set | The Polyline set containing to which the Fault Polyline belongs. | Cascade | Yes |