Name | Log_Image_Part |
---|---|
Entity Type | Table |
Description | Manages a part of a log image and is used to stretch or shrink that part of the image to the desired interval depth, elevation or time interval. |
Submodel | Utility |
Entity Scope | Project |
Primary Key | Id |
Natural Key | |
Generalizations | IT_Object , Tracked_Object |
Specializations |
Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
---|---|---|---|---|---|
End_Image_Row | int | No_Unit |
The ending pixel row of the sample image for the section | No |
NUMBER(10) |
End_Index | double | No_Unit |
The end index (time,depth...) for the section | No |
NUMBER |
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) |
Index_Type | R_Property |
|
The index type for the involvement. Examples of this would be Length, Depth etc | No |
VARCHAR2(64) |
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) |
Log_Image_Id | Document |
|
The image of which the section is a part. | Yes |
NUMBER(38) |
Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
Start_Image_Row | int | No_Unit |
The starting pixel row of the sample image for the section | No |
NUMBER(10) |
Start_Index | double | No_Unit |
The start index (time,depth...) for the section | No |
NUMBER |
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 |
---|---|---|---|---|
Log_Image | Document | The image of which the section is a part. | Cascade | Yes |
Index_Type | R_Property | The index type for the involvement. Examples of this would be Length, Depth etc | Restrict | No |