POSC Specifications: Epicentre Version 3.0 | Logical Data Model |
Identifies the collection of geophysical data that exists at a particular state of the processing. Processing that changes the data will normally create a new data set.
- geometry_set (M: geophysical_geometry_set(data_set))
- The acquisition geometry that this data represents. Each geophysical_data_set must represent one geophysical_geometry_set.
- data_value (O, I: ndt_trace_value) (C115)
- A multidimensional array of data containing one or more characteristics which can be indexed in various ways. Inherited from data_trace.
- description (O, I: ndt_comment) (C117)
- A remark or comment about the instance. Inherited from e_and_p_data.
- identifier (O, I: ndt_identifier) (C049)
- The identifying label assigned to a data trace. Inherited from data_trace.
- 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.
- activity (O, I: activity(process_data))
- Defines the activity which created this instance. Each geophysical_data_set may be the result of one activity. Inherited from process_data.
- applied_data (V: SET[0:?] geophysical_data_association(applied_to))
- Defines the sets of data which have been applied directly to this data set. Each geophysical_data_set may have had applied one or more geophysical_data_association.
- applied_to (V: SET[0:?] geophysical_data_association(applied_data))
- This defines the data sets that this data has been applied to. This should not also point to the children of the data set unless this data was also directly applied to the child. Each geophysical_data_set may have been applied to one or more geophysical_data_association.
- data_alias (I, V: SET[0:?] data_trace_alias(aliased_object)) (C115)
- Indicates alternative identifiers of this data. Each geophysical_data_set may be known by one or more data_trace_alias. Inherited from data_trace.
- 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 geophysical_data_set may be a member of one or more data_collection_content. Inherited from e_and_p_data.
- derived_data (V: SET[0:?] geophysical_data_set(derived_from))
- This defines the set of data sets that are created as a direct result of modifying or analyzing this data set. This does not include children-of-children but does include secondary data such as residual statics or velocities which were derived from the parent. Each geophysical_data_set may be source of one or more geophysical_data_set.
- derived_from (O: geophysical_data_set(derived_data))
- This defines the data set from which this data set was derived. This excludes secondary data (e.g., velocities, statics) which influenced the algorithm that modified the data. Each geophysical_data_set may be derived from one geophysical_data_set.
- 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 geophysical_data_set may be included in one or more document_information_content. Inherited from e_and_p_data.
- geophysical_display (V: SET[0:?] geophysical_display(data_set)) (C139)
- The set of displays which primarily represent this data set. Each geophysical_data_set may be represented by one or more geophysical_display.
- graphical_element (I, V: SET[0:?] graphical_element(depicted_object))
- Specifies one or more graphical elements which are depicting this data item. Each geophysical_data_set may be depicted by one or more graphical_element. Inherited from e_and_p_data.
- grid_geometry_behavior (O, I: grid_geometry_behavior(grid_element_behavior))
- This is the description of grid geometry for which this set of grid element properties are defined. Each geophysical_data_set may use the geometry of one grid_geometry_behavior. Inherited from grid_element_behavior.
- naming_system (O, I: naming_system(data_trace)) (C115)
- The naming system in which the identifier is specified and determined to be unique. Each geophysical_data_set may have name specified by one naming_system. Inherited from data_trace.
- offline_data (V: SET[0:?] geophysical_offline_data(data_set))
- Defines the offline data which is represented by this data set. Each geophysical_data_set may may be characterized by one or more geophysical_offline_data.
- processing_indicator (V: SET[0:?] geophysical_proc_indicator(data_set))
- This defines the list of "high level" indicators of the processing steps which have occurred in the processing history of this set of data. The ordering attribute allows the same type of processing to occur more than once . In general, this list should match the processing of the "parent" data except that new steps may be added. Each geophysical_data_set may have processing steps of one or more geophysical_proc_indicator.
- process_data_item (I, V: SET[0:?] process_data_item(process_data))
- Defines where this data was used by an activity. Each geophysical_data_set may be the value for one or more process_data_item. Inherited from process_data.
- pty_geometry_1d_edge (V: SET[0:?] pty_geometry_1d_edge(geophysical_data_set))
- Defines the spatial location of the nodes on the grid utilized by attribute data value. The grid used must be the same as the grid used by data value. If the geometry is defined using processing index values then the spatial locations may be found on the utilized processing grid. If the geometry is defined using acquisition index values then the spatial locations may be found on the utilized measurement grid. Each geophysical_data_set may have a property of one or more pty_geometry_1d_edge.
- pty_geometry_2d_edge (V: SET[0:?] pty_geometry_2d_edge(geophysical_data_set))
- May have a property of pty geometry 2d edge. Defines the spatial location of the nodes on the grid utilized by attribute data value. The grid used must be the same as the grid used by data value. Each geophysical_data_set may have a property of one or more pty_geometry_2d_edge.
- pty_geometry_2d_face (V: SET[0:?] pty_geometry_2d_face(geophysical_data_set))
- May have a property of pty geometry 2d face. Defines the spatial location of the nodes on the grid utilized by attribute data value. The grid used must be the same as the grid used by data value. If the geometry is defined using processing index values then the spatial locations may be found on the utilized processing grid. If the geometry is defined using acquisition index values then the spatial locations may be found on the utilized measurement grid. Each geophysical_data_set may have a property of one or more pty_geometry_2d_face.
- utilized_processing_grid (O: geophysical_processing_grid(utilizing_data_set))
- Defines the processing grid used for the grid of the data. Each geophysical_data_set may utilize grid from one geophysical_processing_grid.
- utilized_uid_grid (O: geophysical_geometry_set(data_grid_use))
- Defines the geometry set which specified the uid grid used in the data. Each geophysical_data_set may utilize grid from one geophysical_geometry_set.
Local rules:
- Abstract supertype:
- Each GEOPHYSICAL_DATA_SET must be instantiated as one of its subtypes. These subtypes are: potential_field_data_set, seismic_data_set
- Different Related Instance
-
The entity instance defined by the derived_from data set must not be included in the set defined by the derived_data data set. An entity instance must not be derived from itself.
Supertype path(s):
Referenced in Diagrams:
Generated on Tue Jul 10 15:42:57 2001
© Copyright 2001 POSC. All rights reserved.