POSC Specifications: Epicentre Version 3.0 | Logical Data Model |
This is a combination of two coordinate systems which form a third coordinate system. A typical example is a 'geographic 2d' or a 'projected 2d' horizontal coordinate system, extended to become a 3d system by any gravity related or local vertical coordinate system (e.g. depths w.r.t. instantaneous sea level). Another example is a 'local 2d' coordinate system, extended by a gravity related vertical component. An example of the latter would be a seismic bin grid system combined with Mean Sea Level referenced depths. The order of the values in a coordinate tuple will be the values that represent the axes of the first system followed by the values that represent the axes in the second system. This should not be used to create an aggregate of similar systems, such as two horizontal 2D systems or a horizontal 2D system plus a 3D system which includes a horizontal component.
- first_system (M, K: simple_coordinate_system(compound_first_component)) (C148)
- This is the first coordinate system in the compound system. For well formed geodetic systems this will normally be a horizontal 2D system. Each compound_coordinate_system must have as first system one simple_coordinate_system.
- second_system (M, K: simple_coordinate_system(compound_second_component)) (C148)
- This is the second coordinate system in the compound system. For well formed geodetic systems this will normally be a vertical 1D system. Each compound_coordinate_system must have as second system one simple_coordinate_system.
- identifier (M, I: ndt_identifier) (C025)
- The name of the instance. Inherited from technical_reference.
- ref_coordinate_sys_constraint (M, I: ref_coordinate_sys_constraint(coordinate_system)) (C112, C138)
- The type of the coordinate system. This type specifies the number, order and kinds of axes that must be defined for this coordinate system. For example, a coordinate system of geographical 2D must have two axes of latitude and longitude in order. Each compound_coordinate_system must be a kind of one ref_coordinate_sys_constraint. Inherited from coordinate_system.
- description (O, I: ndt_comment) (C117)
- A remark or comment about the instance. Inherited from e_and_p_data.
- instance_create_date (O, I: ndt_date_tod) (C126)
- This is the date that this instance was created. This date is defined by the source if imported, or is the date the instance is created if a new instance. Inherited from e_and_p_data.
- instance_creator (O, I: ndt_identifier) (C126)
- This is the person, company or application that created this instance. This identifies the party responsible for loading this instance. Inherited from e_and_p_data.
- last_updated (O, I: ndt_date_tod) (C126)
- This is the date that this instance was last updated. This value should be updated when any part of this instance is altered (except for inverse relationships). Inherited from e_and_p_data.
- last_updated_by (O, I: ndt_identifier) (C126)
- This records the person or application making the update to this instance. Inherited from e_and_p_data.
- source (O, I: ndt_identifier) (C126)
- The provider of this instance, which is usually a data provider for imported/purchased data. If this instance is provided by POSC, then this attribute must be "POSC". Inherited from e_and_p_data.
- source_content (O, I: ndt_identifier) (C126)
- This is the original source of the data. This is the person, company or application that defined or specified the data (content) for this instance and is considered to be responsible for it. For example, POSC, EPSG, API, ISO, etc. This may be the same as or different from the provider of the instance (e.g., POSC). Inherited from technical_reference.
- source_reference (O, I: ndt_comment) (C042, C126)
- The reference used by source to provide the standard instance, such as Petroleum Industry Data Dictionary (PIDD), Websters Ninth New Collegiate Dictionary, etc. Inherited from technical_reference.
- status (O, I: ndt_instance_status) (C042)
- The status of this instance in the version of Epicentre running in a data store. This is an enumerated datatype for which the following are the possible values: current, provisional, deprecated. Current - use without restriction. Provisional - use with caution, this value is for comment and may not appear in future releases of Epicentre. Deprecated - avoid use if possible, it is planned to remove this value in the next major release of Epicentre. Inherited from technical_reference.
- data_collection (I, V: SET[0:?] data_collection_content(collection_part)) (C020)
- Indicates the data collections that include this instance of E and P data. Each compound_coordinate_system may be a member of one or more data_collection_content. Inherited from e_and_p_data.
- derived_interest (I, V: SET[0:?] derived_interest_makeup(interest_for)) (C071, C122)
- These are the ownership fractions for business associates of this object. Each compound_coordinate_system may be referenced by one or more derived_interest_makeup. Inherited from object_of_interest.
- document_information_content (I, V: SET[0:?] document_information_content(e_and_p_data)) (C136)
- These are the document specification parts that include this data value and define its meaning within a document specification. Each use may define a different meaning, and many uses are allowed. Each compound_coordinate_system may be included in one or more document_information_content. Inherited from e_and_p_data.
- earth_feature (I, V: SET[0:?] coordinate_system_earth_usage(coordinate_system)) (C139)
- These are the areas of the surface of the Earth that are defined as appropriate to use this coordinate system. Each compound_coordinate_system may be defined for use within one or more coordinate_system_earth_usage. Inherited from coordinate_system.
- graphical_element (I, V: SET[0:?] graphical_element(depicted_object))
- Specifies one or more graphical elements which are depicting this data item. Each compound_coordinate_system may be depicted by one or more graphical_element. Inherited from e_and_p_data.
- involving_activity (I, V: SET[0:?] object_activity_involvement(involved_object)) (C056)
- This are the activity involvements which affect the object. Each compound_coordinate_system may have involvements with one or more object_activity_involvement. Inherited from object_of_interest.
- map (I, V: SET[0:?] map(coordinate_system)) (C043)
- The maps which are positioned within this coordinate system. Each compound_coordinate_system may position one or more map. Inherited from coordinate_system.
- naming_system (O, I: naming_system(aliasable_technical_reference)) (C028)
- The naming system in which the identifier is specified and determined to be unique. Each compound_coordinate_system may have name specified by one naming_system. Inherited from aliasable_technical_reference.
- pty_geometry_2d_gis (I, V: SET[0:?] pty_geometry_2d_gis(coordinate_system)) (C046)
- The set of OpenGIS formatted geometries which use this coordinate system Each compound_coordinate_system may specify values for one or more pty_geometry_2d_gis. Inherited from coordinate_system.
- pty_geometry_simple_1d_edge (I, V: SET[0:?] pty_geometry_simple_1d_edge(coordinate_system)) (C139)
- These are the simple geometries which are defined using values in this coordinate system. Each compound_coordinate_system may be used in one or more pty_geometry_simple_1d_edge. Inherited from coordinate_system.
- technical_reference_alias (I, V: SET[0:?] technical_reference_alias(aliased_object)) (C029)
- Indicates the various identifiers by which this instance is known. Each compound_coordinate_system may be known by one or more technical_reference_alias. Inherited from aliasable_technical_reference.
- version (O, I: ref_version(technical_reference)) (C042, C126)
- This describes the version of this instance as defined by the provider. Each compound_coordinate_system may version one ref_version. Inherited from technical_reference.
Local rules:
Supertype path(s):
Referenced in Diagrams:
Generated on Tue Jul 10 15:40:05 2001
© Copyright 2001 POSC. All rights reserved.