POSC Specifications: Epicentre Version 3.0 | Logical Data Model |
Add the capability to assert geometrical relationships independent of topological assertions. For example, objects AA and BB might have a topological assertion that AA is "disjoint" from BB and might also have multiple geometrical assertions such as AA is "above" BB and AA has a 20ft "separation" from BB.
CHANGE ERP_geometrical_relationship (*<REQUEST>1347*) ADD ENTITY geometrical_relationship SUBTYPE OF (transient_association) (*<DESC>Defines a geometrical relationship between two spatial objects.*); primary_spatial_object : spatial_object (*<DESC>Indicates a spatial object in the role of primary agent.*) (*<VERB>primarily involve*); secondary_spatial_object : spatial_object (*<DESC>Indicates a spatial object in the role of secondary agent.*) (*<VERB>secondarily involve*); relationship_type : ref_geometrical_relationship (*<DESC>Defines the type of relationship.*) (*<VERB>be type of*); nominal_distance: OPTIONAL ndt_length (*<DESC>The nominal distance between the primary and secondary object.*); minimum_distance: OPTIONAL ndt_length (*<DESC>The approximate minimum distance between the primary and the secondary object. Let A be the primary and B the secondary object. Define d(y,A) = min (x in A) d(x,y), for every y in B. The minimum_distance (A,B) = min (y in B) [d(y,A)]. For sets that are not disjoint, this value is zero.*); maximum_distance: OPTIONAL ndt_length (*<DESC>The approximate maximum distance from the secondary object, B, to the primary object, A is max (y in B) [d(y,A)], where d(y,A) is as defined for minimum_distance. This value should not be used for sets that are not disjoint.*); INVERSE pty_fault_separation : SET[0:?] OF pty_fault_separation FOR geometrical_relationship (*<VERB>have a property of*); pty_fault_slip : SET[0:?] OF pty_fault_slip FOR geometrical_relationship (*<VERB>have a property of*); pty_fault_slip_variable : SET[0:?] OF pty_fault_slip_variable FOR Geometrical_relationship (*<VERB>have a property of*); UNIQUE si: start_time, end_time, primary_spatial_object, secondary_spatial_object, relationship_type; END_ENTITY; ADD ENTITY ref_geometrical_relationship SUBTYPE OF (ref_code); (*<DESC>Defines the types of geometrical relationships. Each of these require some relative knowledge of the geometries of two objects as well as some method of comparing them.*) (*<POPULATION>OPEN*) INVERSE geometrical_relationship : SET [0:?] OF geometrical_relationship FOR relationship_type (*<DESC>The Geometrical Relationships which are of this type.*) (*<VERB>define the type of*); UNIQUE si : identifier; END_ENTITY; ALTER ENTITY spatial_object; INVERSE ADD secondary_geometrical_relationship : SET [0:?] OF geometrical_relationship FOR secondary_spatial_object (*<DESC>Indicates a geometrical relationship in which this spatial object has the role of secondary agent.*) (*<VERB>be involved in*); ADD primary_geometrical_relationship : SET [0:?] OF geometrical_relationship FOR primary_spatial_object (*<DESC>Indicates a geometrical relationship in which this spatial object has the role of primary agent.*) (*<VERB>be primarily involved in*); END_ENTITY; DROP ENTITY fault_plane_orientation (*<CHANGE>Redundant to Geometrical_relationship.*); DROP ENTITY ref_fault_side (*<CHANGE>Only used by fault_plane_orientation. Redundant to ref_geometrical_relationship.*); ALTER ENTITY pty_fault_separation; ALTER earth_position_face AS geometrical_relationship ALTER TYPE AS geometrical_relationship; END_ENTITY; ALTER ENTITY pty_fault_slip; ALTER earth_position_face AS geometrical_relationship ALTER TYPE AS geometrical_relationship; END_ENTITY; ALTER ENTITY pty_fault_slip_variable; ALTER earth_position_face AS geometrical_relationship ALTER TYPE AS geometrical_relationship; END_ENTITY; DROP ENTITY geologic_object (*<CHANGE>No longer needed since both rock_material and geologic_feature will now be geometrically comparable.*); ALTER ENTITY geologic_object_association AS geologic_feature_association; (*<DESC>Describes the consequence of a relationship between two geologic features, primary and secondary. The relationship is asymmetric if the consequence applies only to the primary feature. If the consequence could apply equally well to either the primary or the secondary feature, the relationship is symmetrical and either feature may be arbitrarily assigned the consequence. Examples include; "a horizon is the top of a sand layer" (asymmetrical), or "a sand layer is interbedded with a shale layer" (symmetrical).*) (*<CHANGE>Move relationships to point to Geologic_feature instead of the dropped Geologic_object. Replace the term "object" with "feature". Replace the term "description" with "consequence".*) ALTER primary_geologic_object AS primary_geologic_feature ALTER TYPE AS geologic_feature (*<DESC>Indicates a geologic feature in the role of primary agent. The primary feature is defined by a consequence relative to the secondary object. Consequences are asymmetrical or symmetrical. For asymmetric interactions, the consequence, such as "top", can only apply to the primary feature. For example, "a horizon (primary feature) is the top (consequence) of a sand layer (secondary feature)". Here only the horizon can be a "top". If the relationship between the two features is symmetrical both features can be described equally well by the consequence, and either could be chosen as the primary agent with the other chosen as the secondary agent. An example of a symmetrical relationship is "a sand layer (primary feature) is interbedded (consequence) with a shale layer(secondary feature)".*); ALTER secondary_geologic_object AS secondary_geologic_feature ALTER TYPE AS geologic_feature (*<DESC>Indicates a geologic feature in the role of secondary agent. The secondary feature relates the primary feature to a consequence. The consequence does not apply to the secondary feature but tells where it is derived from. For example in, "a horizon (primary feature) is the top (consequence) of a sand layer (secondary feature)" the secondary feature shows where the consequence is coming from. If the relationship between the two features is symmetrical both can be described equally well by the consequence, and either could be chosen as the primary agent with the other chosen as the secondary agent. An example of a symmetrical relationship is "a sand layer (primary feature) is interbedded (consequence) with a shale layer(secondary feature)".*); ALTER ref_geologic_object_association AS consequence (*<DESC>This describes the consequence of the interaction between two geologic feature, primary and secondary. It describes, in geologic terms, the primary feature relative to the secondary feature.*) (*<VERB>have a consequence of*); END_ENTITY; ALTER ENTITY ref_geologic_object_association AS ref_geologic_feature_association; (*<DESC>This reference describes the consequence of the interaction between two geologic features, primary and secondary. It describes, in geologic terms, the primary feature relative to the secondary feature.*) (*<CHANGE>Replace the term "object" with "feature".*) INVERSE ADD geologic_feature_association : SET [0:?] OF geologic_feature_association FOR consequence (*<DESC>The associations have this consequence.*) (*<VERB>be the consequence for*); END_ENTITY; ALTER ENTITY geologic_feature; INVERSE ADD secondary_feature_association : SET [0:?] OF geologic_feature_association FOR secondary_geologic_feature (*<DESC>Indicates a geologic feature association in which a geologic feature takes the role of secondary agent. The secondary feature relates the primary feature to a consequence. The consequence does not apply to the secondary feature but tells where it is derived from. For example in, "a horizon (primary feature) is the top (consequence) of a sand layer (secondary feature)" the secondary feature shows where the consequence is coming from. If the relationship between the two features is symmetrical both can be described equally well by a consequence, and either could be chosen as the primary agent with the other chosen as the secondary agent. An example of a symmetrical relationship is "a sand layer (primary feature) is interbedded (consequence) with a shale layer(secondary feature)".*) (*<VERB>be secondarily involved in*); ADD primary_feature_association : SET [0:?] OF geologic_feature_association FOR primary_geologic_feature (*<DESC>Indicates the geologic association in which a geologic feature has the role of primary agent. The primary feature is defined by a consequence relative to the secondary feature. Consequences are asymmetrical or symmetrical. For asymmetric interactions, the consequence, such as "top", can only apply to the primary feature. For example, "a horizon (primary feature) is the top (consequence) of a sand layer (secondary feature)". Here only the horizon can be a "top". If the relationship between the two features is symmetrical both features can be described equally well by the consequence, and either could be chosen as the primary agent with the other chosen as the secondary agent. An example of a symmetrical relationship is "a sand layer (primary feature) is interbedded (consequence) with a shale layer(secondary feature)".*) (*<VERB>be primarily involved in*); END_ENTITY; END_CHANGE;