Name | Line |
---|---|
Entity Type | Table |
Description | A sequence of one or more line segments, which need not be connected (i.e., a line can have gaps). The line segments are a connected sequence of two or more points. For simplicity, there is no explicit line segment entity; line segmentation is merely an attribute of the vertices. |
Submodel | Spatial |
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 |
---|---|---|---|---|---|
BULK_COORDINATE_SYSTEM_Id | ID | NA |
Coordinate system of the Bulk Array data, including cartographic, elevation and azimuth references | No |
NUMBER(38) |
BULK_DATA_Id | ID | NA |
Bulk representation of the points in a line | No |
NUMBER(38) |
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) |
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_Coord_System_Id | Coordinate_System |
|
Coordinate system of the incoming line data, including cartographic, elevation and azimuth references. | 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) |
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) |
Shape | GEOMETRY | NA |
Binary spatial representation of the position. | No |
ST_GEOMETRY |
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 |
---|---|---|---|---|
Acquisition_2D | Source_Line | Refers to the source position during acquisition. | Control | No |
Acquisition_2D | Receiver_Line | Refers to receiver positions during the acquisition. | Control | No |
Alternative_Navigation | Line_Geometry | Line locations represented by spatial geometry. | Control | No |
Borehole_Seismic_Acq_Act | Source_Line | The line representing the source positions during acquisition. | Control | No |
Borehole_Seismic_Acq_Act | Receiver_Line | The line representing the positions of the receivers during acquisition. | Control | No |
Boundary | Line | The line describing the boundary, used in cases where the boundary is not closed. | Control | No |
Deviation_Survey | Survey_Trajectory | The spatial representation of the deviation survey | Control | No |
Fault_Polyline | Line | The line which describes the fault segment in 3D. | Control | No |
Line_Vertex | Line | The identifier of the line of which the vertices are points. | Cascade | Yes |
Plane_Intersection | Line | The line describing the intersection of two planes. | Control | No |
Seismic_Line | Line_Geometry | Refers to locations represented by spatial geometry. | Control | No |
Seismic_Line_DOV | Line_Geometry | Line locations represented by spatial geometry. | Control | No |
Link | To Entity | Description | Implementation Technique | Required |
---|---|---|---|---|
Original_Coord_System | Coordinate_System | Coordinate system of the incoming line data, including cartographic, elevation and azimuth references. | Restrict | No |