Newer
Older
Thomas Gehrmann [InvitedE]
committed
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
<a name="TOC"></a>**Table of Contents**
[[_TOC_]]
# Subdomain "Geophysics"
**Description:** The physics of the Earth, especially its electrical, gravitational and magnetic fields and propagation of elastic (seismic) waves within it.
* This subdomain belongs to the parent [Subsurface](Domain-Subsurface.md).
* Back to [Domain overview](../Domains.md).
* Back to [OSDU Forum Getting Started](https://osduforum.org/getting-started/osdu-data-definition-documentation).
## Types Governed by the "Geophysics" Data Domain
* **master-data--Seismic2DInterpretationSet** — [osdu:wks:master-data--Seismic2DInterpretationSet:1.2.0](../master-data/Seismic2DInterpretationSet.1.2.0.md)<br>_A seismic 2D interpretation set is a collection of logical processed lines and associated trace datasets that represent an important and uniform set for interpretation. It does not comprise all of the datasets with a common processing geometry, nor all of the lines/datasets from a processing project, nor all of the lines/datasets from an acquisition project, because some are not suitable for interpretation. An interpretation survey may include 2D lines and datasets from more than one acquisition or processing project. Consequently, it is not an acquisition survey nor a processing survey. It is not an application project, which is a collection of all the various objects an application and user care about for some analysis (seismic, wells, etc.). It inherits properties shared by project entities because it can serve to capture the archiving of a master or authorized project activity. Interpretation objects (horizons) are hung from an interpretation project to give context and to derive spatial location based on the processing geometry of the associated 2D lines. Trace datasets and seismic horizons are associated through LineageAssertion, although a master collection of trace datasets and horizons are explicitly related through a child relationship property._
* **master-data--Seismic3DInterpretationSet** — [osdu:wks:master-data--Seismic3DInterpretationSet:1.2.0](../master-data/Seismic3DInterpretationSet.1.2.0.md)<br>_A seismic 3D interpretation survey is a collection of trace datasets with a common bin grid that are important for interpretation. It does not comprise all of the datasets with a common bin grid, nor all of the datasets from a processing project, nor all of the datasets from an acquisition project, because some are not suitable for interpretation. An interpretation survey may include datasets from more than one acquisition or processing project. Consequently, it is not an acquisition survey nor a processing survey. It is not an application project, which is a collection of all the various objects an application and user care about for some analysis (seismic, wells, etc.). It inherits properties shared by project entities because it can serve to capture the archiving of a master or authorized project activity. Interpretation objects (horizons) are hung from an interpretation survey to give context and to derive spatial location based on the common bin grid. Trace datasets and seismic horizons are associated through LineageAssertion, although a master collection of trace datasets and horizons are explicitly related through a child relationship property._
* **master-data--SeismicAcquisitionSurvey** — [osdu:wks:master-data--SeismicAcquisitionSurvey:1.4.0](../master-data/SeismicAcquisitionSurvey.1.4.0.md)<br>_A seismic acquisition project is a type of business project that deploys resources to the field to record seismic data. It may be referred to as a field survey, acquisition survey, or field program. It is not the same as the geometry of the deployed equipment (nav), which is a work product component._
* **master-data--SeismicProcessingProject** — [osdu:wks:master-data--SeismicProcessingProject:1.3.0](../master-data/SeismicProcessingProject.1.3.0.md)<br>_A seismic processing project is a type of business project which manages the creation of processed seismic work products. It is not the same as the geometry of the processed traces (binning or bin grid), which is a work product component, although it typically defines a single binning. A processing project may merge data from multiple field surveys, so it is not required to be equated to a single field survey. Original processing and re-processing activities generate separate and independent processing projects._
* **work-product-component--NotionalSeismicLine** — [osdu:wks:work-product-component--NotionalSeismicLine:1.2.0](../work-product-component/NotionalSeismicLine.1.2.0.md)<br>_The set of geometries comprising a full seismic transect (referenced through parent-child relationships). This entity encompasses the concept of a logical processed line. The parts comprising it cover things like extensions and boundary crossings. It is largely a data management object to help collect all the geometries pertaining to a transect. It is not needed for interpretation. The universal WPC Name property is essential for describing the principal, preferred line name for the full transect._
* **work-product-component--ProcessedInSAR** — [osdu:wks:work-product-component--ProcessedInSAR:1.2.0](../work-product-component/ProcessedInSAR.1.2.0.md)<br>_Interferometric Synthetic Aperture Radar (InSAR) is a representation of surface or ground deformation from satellite radar image data over time_
* **work-product-component--SeismicAcquisitionDocuments** — [osdu:wks:work-product-component--SeismicAcquisitionDocuments:1.1.0](../work-product-component/SeismicAcquisitionDocuments.1.1.0.md)<br>_Files produced during the course of Seismic Acquisition, including observer logs, source and receiver information tables, and unprocessed navigation._
* **work-product-component--SeismicBinGrid** — [osdu:wks:work-product-component--SeismicBinGrid:1.3.0](../work-product-component/SeismicBinGrid.1.3.0.md)<br>_A representation of the surface positions for each subsurface node in a set of processed trace data work product components with common positions. Different sampling (spacing) and extents (ranges) in the trace data may be handled by the same bin grid._
* **work-product-component--SeismicFault** — [osdu:wks:work-product-component--SeismicFault:1.2.0](../work-product-component/SeismicFault.1.2.0.md)<br>_A representation of a single fault picked on the basis of seismic data. The record carries information about the seismic geometry context. It can be part of an UnsealedSurfaceFramework._
* **work-product-component--SeismicFieldTraceData** — [osdu:wks:work-product-component--SeismicFieldTraceData:1.1.0](../work-product-component/SeismicFieldTraceData.1.1.0.md)<br>_A logical dataset containing seismic traces. The traces are the original recordings, prior to processing._
* **work-product-component--SeismicHorizon** — [osdu:wks:work-product-component--SeismicHorizon:1.3.0](../work-product-component/SeismicHorizon.1.3.0.md)<br>_A set of picks related to seismic processing geometry which define a surface. The geometry used is referenced by the Interpretation Project._
* **work-product-component--SeismicLineGeometry** — [osdu:wks:work-product-component--SeismicLineGeometry:1.2.0](../work-product-component/SeismicLineGeometry.1.2.0.md)<br>_The 2D processing geometry of a 2D seismic line. This is not the navigation (acquisition surface geometry). The fully sampled geometry is contained in the work product component's file. This shows the relationship between CMP, X, Y, and station label. The ends and bends version for mapping purposes is in the work product component's spatial area. The Name universal property is essential for describing the Line Name._
* **work-product-component--SeismicTraceData** — [osdu:wks:work-product-component--SeismicTraceData:1.5.0](../work-product-component/SeismicTraceData.1.5.0.md)<br>_A single logical dataset containing seismic samples._
* **work-product-component--VelocityModeling** — [osdu:wks:work-product-component--VelocityModeling:1.3.0](../work-product-component/VelocityModeling.1.3.0.md)<br>_An earth model describing seismic velocities._
[Back to TOC](#TOC)
---
## Types Consumed by the "Geophysics" Data Domain
* **master-data--Agreement** — [osdu:wks:master-data--Agreement:1.1.0](../master-data/Agreement.1.1.0.md)<br>_A contract or other covenant between Company and counterparties which is relevant to the data universe because it includes terms governing use of data._
* **master-data--Basin** — [osdu:wks:master-data--Basin:1.2.0](../master-data/Basin.1.2.0.md)<br>_A natural geographic area covering a single depositional system._
* **master-data--Field** — [osdu:wks:master-data--Field:1.1.0](../master-data/Field.1.1.0.md)<br>_A mineral deposit that has been exploited for commercial purposes._
* **master-data--Play** — [osdu:wks:master-data--Play:1.1.0](../master-data/Play.1.1.0.md)<br>_A named area that likely contains a combination of certain geological factors making it prospective for mineral exploration. It is often considered to be a set of prospects with a common set of characteristics._
* **master-data--Prospect** — [osdu:wks:master-data--Prospect:1.1.0](../master-data/Prospect.1.1.0.md)<br>_A named area or location, likely containing commercial deposits of a mineral, that is a candidate for extraction. This normally means a candidate drilling location.._
* **master-data--ReferenceLevel** — [osdu:wks:master-data--ReferenceLevel:1.1.0](../master-data/ReferenceLevel.1.1.0.md)<br>_A reference level or horizontal reference surface, which can be re-used by many other entities. The area of use is indicated by data.SpatialLocation - as a polygon or as a point if used in context of a Well or Wellbore._
* **master-data--Reservoir** — [osdu:wks:master-data--Reservoir:0.0.0](../master-data/Reservoir.0.0.0.md)<br>_Preliminary placeholder for the Reservoir schema._
* **master-data--Reservoir** — [osdu:wks:master-data--Reservoir:1.0.0](../master-data/Reservoir.1.0.0.md)<br>_A reservoir is a subsurface rock formation which 1) is a volume of porous and permeable rock and 2) contains an individual and separate natural accumulation of moveable fluids that are confined by impermeable rock formations. Fluids may be produced from a reservoir and injected into a reservoir for increased recovery, storage or disposal._
* **master-data--ReservoirSegment** — [osdu:wks:master-data--ReservoirSegment:0.0.0](../master-data/ReservoirSegment.0.0.0.md)<br>_Preliminary placeholder for the ReservoirSegment schema._
* **master-data--ReservoirSegment** — [osdu:wks:master-data--ReservoirSegment:1.0.0](../master-data/ReservoirSegment.1.0.0.md)<br>_A reservoir segment is an earth volume within a reservoir (e.g., reservoir zone, reservoir pattern, subsidence bowl, drainage region of one or more wells, etc.). Each reservoir segment is a unique and spatially non-overlapping part of a reservoir.A comprehensive set of Segments can be built with a PersistedCollection._
* **master-data--Risk** — [osdu:wks:master-data--Risk:1.1.0](../master-data/Risk.1.1.0.md)<br>_Possible risk potentially encountered during the run of a drilling program or a single string run._
* **master-data--RockVolumeFeature** — [osdu:wks:master-data--RockVolumeFeature:1.1.0](../master-data/RockVolumeFeature.1.1.0.md)<br>_A volume of rock that is identified based on some specific attribute, like its mineral content or other physical characteristic. It exists typically in the scope of a model._
* **work-product-component--Activity** — [osdu:wks:work-product-component--Activity:1.4.0](../work-product-component/Activity.1.4.0.md)<br>_Instance of a given activity_
* **work-product-component--DataQuality** — [osdu:wks:work-product-component--DataQuality:1.3.0](../work-product-component/DataQuality.1.3.0.md)<br>_This is used to store result from a run of Data Quality Metric Evaluation engine. Captures summary information, such as which Business rule-set(s) and rule(s) have been used, when this was run and by whom. Detailed result (such as which rule failed, for which meta data item and what was offending value causing the rule to fail) is meant to be made available in a file that is linked to this work-product component. Through Lineage Assertion, this can relate to the entities which were used for the run of Evaluation engine, such as a collection of wells whose meta data were inspected by using a set of rules._
* **work-product-component--DataQuality** — [osdu:wks:work-product-component--DataQuality:2.0.0](../work-product-component/DataQuality.2.0.0.md)<br>_This is used to store the result from a run of a Data Quality Metric Evaluation engine. Captures summary information, such as which rule-set(s) and rule(s) have been used, when this was run and by whom. Detailed results may be associated with a dataset._
* **work-product-component--Document** — [osdu:wks:work-product-component--Document:1.2.0](../work-product-component/Document.1.2.0.md)<br>_A document can be any document that is required to be stored in an electronic format. Examples of this could be daily drilling reports, drilling schematics, or material quality analysis reports._
* **work-product-component--FaultInterpretation** — [osdu:wks:work-product-component--FaultInterpretation:1.2.0](../work-product-component/FaultInterpretation.1.2.0.md)<br>_Geologic information associated to fault-related objects (marker, fault sticks, modeled objects like triangulated surface)_
* **work-product-component--FaultSystem** — [osdu:wks:work-product-component--FaultSystem:1.4.0](../work-product-component/FaultSystem.1.4.0.md)<br>_A set of picked faults. In the earth modeling domain this entity corresponds to a PersistedCollection containing GenericRepresentation or SeismicFault items._
* **work-product-component--HorizonInterpretation** — [osdu:wks:work-product-component--HorizonInterpretation:1.2.0](../work-product-component/HorizonInterpretation.1.2.0.md)<br>_Geologic information associated to horizon-related object types (marker, seismic picks, modeled objects etc…)_
[Back to TOC](#TOC)
---