| Name | Boundary |
|---|---|
| Entity Type | Table |
| Description | A fault boundary or surface boundary. |
| 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 |
|---|---|---|---|---|---|
| Boundary_Type | R_Boundary |
|
The boundary type, for example Fault Trace or Surface. | No |
VARCHAR2(64) |
| Domain_Property | R_Property |
|
The property of the domain in which the boundary is defined. For example, a boundary defined in time domain property in time might be One_Way_Time or Two_Way_Time. Similarly, a boundary defined in depth might have a domain property of Measured_Depth or True_Vertical_Depth. | No |
VARCHAR2(64) |
| 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) |
| Line_Id | Line |
|
The line describing the boundary, used in cases where the boundary is not closed. | No |
NUMBER(38) |
| Maximum_Throw | double | No_Unit |
The maximum amount of vertical displacement on the fault at this fault boundary. | 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) |
| 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) |
| Polygon_Id | Area |
|
The polygon describing a boundary, used in cases where the boundary s closed. | No |
NUMBER(38) |
| Primary_Feature_Id | Feature |
|
A primary feature associated with the boundary, for example a horizon that intersects a fault. | No |
NUMBER(38) |
| Primary_Feature_Tbl | Meta_Entity |
|
Feature type | No |
VARCHAR2(30) |
| 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) |
| Secondary_Feature_Id | Feature |
|
A secondary feature associated with the polyline, for example a horizon that intersects a fault. | No |
NUMBER(38) |
| Secondary_Feature_Tbl | Meta_Entity |
|
Feature type | No |
VARCHAR2(30) |
| 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) |
| 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) |
| From Entity | Link | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Study_Polygon | Boundary | The identifier of a surface boundary or fault boundary that is an element of the study. | Nullify | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Boundary_Type | R_Boundary | The boundary type, for example Fault Trace or Surface. | Restrict | No |
| Domain_Property | R_Property | The property of the domain in which the boundary is defined. For example, a boundary defined in time domain property in time might be One_Way_Time or Two_Way_Time. Similarly, a boundary defined in depth might have a domain property of Measured_Depth or True_Vertical_Depth. | Restrict | No |
| Secondary_Feature | Feature | A secondary feature associated with the polyline, for example a horizon that intersects a fault. | Cascade | No |
| Polygon | Area | The polygon describing a boundary, used in cases where the boundary s closed. | Control | No |
| Primary_Feature | Feature | A primary feature associated with the boundary, for example a horizon that intersects a fault. | Cascade | No |
| Line | Line | The line describing the boundary, used in cases where the boundary is not closed. | Control | No |