| Name | Basin |
|---|---|
| Entity Type | Table |
| Description | A geologic region drawn on the surface of the Earth, including the rocks near the surface. It may be defined by an outline that corresponds to the margin of a basin, sub-basin, or an area of consistent geologic traits such as a common stratigraphic sequence. |
| Submodel | Geology |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | Name , Existence_Kind , Version |
| Generalizations | Entity , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| Area_Outline_Id | Area |
|
The location that provides the outline for this basin on the earth surface. | 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) |
| Geologic_Province | R_Geologic_Province |
|
The standard name of the geologic province. | No |
VARCHAR2(64) |
| 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) |
| Nominal_Position_Id | Position |
|
The nominal position of the item. Considering the item has a spatial extent - meaning it is not a single point and could span more than one county or section or whatever - the Position created as the target of this link is just a representative location. If a more complete answer is needed a GIS query can intersect the polygon marking the outer boundary of this item with the desired item. For example, the Viking Graben (a basin) is mostly in Norway but extends over the border into the UK. Its Nominal_Position could be said to be Norway. If someone wondered exactly which countries it touched they would use GIS functionality to intersect the basin outline with a map layer containing the international boundaries to see which countries actually contain some portion of the basin | 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) |
| Parent_Basin_Id | Basin |
|
The geologic region that encloses this area. For example, the basin that includes this sub-basin. | No |
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) |
| 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) |
| Status | CODE | NA |
The status of a geologic region at a particular point in time | 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 |
|---|---|---|---|---|
| Basin | Parent_Basin | The geologic region that encloses this area. For example, the basin that includes this sub-basin. | Nullify | No |
| Basin_Parm | Basin | The unique identifier of the basin to which the parameter or property applies. | Cascade | Yes |
| Position_Xref | Basin | The unique identifier of the Basin that is associated with the Position. | Cascade | No |
| Strat_Column | Basin | The basin that contains the stratigraphic column or section. | Restrict | No |
| Link | To Entity | Description | Implementation Technique | Required |
|---|---|---|---|---|
| Area_Outline | Area | The location that provides the outline for this basin on the earth surface. | Control | No |
| Parent_Basin | Basin | The geologic region that encloses this area. For example, the basin that includes this sub-basin. | Nullify | No |
| Nominal_Position | Position | The nominal position of the item. Considering the item has a spatial extent - meaning it is not a single point and could span more than one county or section or whatever - the Position created as the target of this link is just a representative location. If a more complete answer is needed a GIS query can intersect the polygon marking the outer boundary of this item with the desired item. For example, the Viking Graben (a basin) is mostly in Norway but extends over the border into the UK. Its Nominal_Position could be said to be Norway. If someone wondered exactly which countries it touched they would use GIS functionality to intersect the basin outline with a map layer containing the international boundaries to see which countries actually contain some portion of the basin | Control | No |
| Geologic_Province | R_Geologic_Province | The standard name of the geologic province. | Restrict | No |