| Name | Land_Desc_XREF |
|---|---|
| Entity Type | Table |
| Description | Allows relationships between land descriptions to be described. Could be used to indicate spatial relationships between land agreements and offshore parcels, for example. (PPDM3.7) |
| Submodel | Land_Agreement |
| Entity Scope | Project |
| Primary Key | Id |
| Natural Key | |
| Generalizations | Transient_Association , IT_Object , Tracked_Object |
| Specializations |
| Name | Value Domain | Property / Storage Unit | Description | Required / Default | Type |
|---|---|---|---|---|---|
| End_Date | DATE | NA |
End time of the association | No |
DATE |
| 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) |
| Land_Desc_1_Id | Land_Description |
|
The first of the land descriptions participating in a relationship with another land description. | Yes |
NUMBER(38) |
| Land_Desc_2_Id | Land_Description |
|
The 2nd of the land descriptions participating in a relationship with another land description. | Yes |
NUMBER(38) |
| Land_Desc_XREF_Type | R_Land_Desc_XREF |
|
The type of relationship between the two land descriptions. For example, a topologic relationship or a business relationship. | No |
VARCHAR2(64) |
| Overlap_Land_Desc_Id | Land_Description |
|
The land description that represents the area of overlap. | No |
NUMBER(38) |
| Overlap_Size | double | Area m2 |
The size of the overlap between two parcels. (PPDM 3.7) | No |
NUMBER |
| Produced_By | STRING64 | NA |
The name of application role that created the entity, for data created programmatically. | No |
VARCHAR2(64) |
| Remarks | REMARKS_STR | NA |
General remarks about the relationship between the two land descriptions. | No |
VARCHAR2(999) |
| SDAT_Label | int | No_Unit |
Label used by the security system for entitlements. SDAT is Secure Data Access Technology. | No |
NUMBER(10) |
| Start_Date | DATE | NA |
Start time of the association. | No |
DATE |
| 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 |
|---|---|---|---|---|
| Land_Desc_2 | Land_Description | The 2nd of the land descriptions participating in a relationship with another land description. | Restrict | Yes |
| Overlap_Land_Desc | Land_Description | The land description that represents the area of overlap. | Restrict | No |
| Land_Desc_XREF_Type | R_Land_Desc_XREF | The type of relationship between the two land descriptions. For example, a topologic relationship or a business relationship. | Restrict | No |
| Land_Desc_1 | Land_Description | The first of the land descriptions participating in a relationship with another land description. | Restrict | Yes |