Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| geoscene3d:project_content:datasets:jupiter_wells_dataset [2020/02/12 16:00] – created rebecca130301_gmail.com | geoscene3d:project_content:datasets:jupiter_wells_dataset [2020/03/22 17:54] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Jupiter Wells Dataset ====== | ====== Jupiter Wells Dataset ====== | ||
| - | A Jupiter Wells Dataset represents a group of wells. The dataset is defined with a query that consists of a rectangular extent and optional SQL. Wells Datasets are used in the [[Wells Object|]]. | + | A Jupiter Wells Dataset represents a group of wells. The dataset is defined with a query that consists of a rectangular extent and optional SQL. Wells Datasets are used in the [[: |
| - | ==== | + | ==== Source Types ==== |
| - | Source Types ==== | + | |
| - | [[Access Database Source|]] | + | [[: |
| - | in [[Jupiter Database Format|]]. \\ | + | [[: |
| - | [[Access Database Source|]] | + | [[: |
| - | in [[Jupiter Generic Database Format|]] | + | |
| - | (generic well database format). \\ | + | |
| - | [[CSV File Source|]] | + | |
| - | (generic CSV file format, layers only). | + | |
| - | When using a generic CSV file source it must be formatted as show below. The column names are identical to field names in the [[Jupiter Database format|]]. All columns are required but may be in any order. Corresponding table and field names from Jupiter is shown in parenthesis in the field description below the example. NOTE: Only layers are supported with the CSV format< | + | When using a generic CSV file source it must be formatted as show below. The column names are identical to field names in the [[: |
| BOREHOLENO; | BOREHOLENO; | ||
| Line 47: | Line 42: | ||
| </ | </ | ||
| - | BOREHOLENO: Primary unique well ID [String] (BOREHOLE.BOREHOLENO) \\ | + | BOREHOLENO: Primary unique well ID [String] (BOREHOLE.BOREHOLENO)\\ |
| - | ELEVATION: Well elevation [Float] (BOREHOLE.ELEVATION) \\ | + | ELEVATION: Well elevation [Float] (BOREHOLE.ELEVATION)\\ |
| - | XUTM: Well easting [Float] (BOREHOLE.XUTM) \\ | + | XUTM: Well easting [Float] (BOREHOLE.XUTM)\\ |
| - | YUTM: Well northing [Float] (BOREHOLE.YUTM) \\ | + | YUTM: Well northing [Float] (BOREHOLE.YUTM)\\ |
| - | SAMPLENO: Layer ID [Integer] (LITHSAMP.SAMPLENO) \\ | + | SAMPLENO: Layer ID [Integer] (LITHSAMP.SAMPLENO)\\ |
| - | TOP: Layer top depth [Float] (LITHSAMP.TOP) \\ | + | TOP: Layer top depth [Float] (LITHSAMP.TOP)\\ |
| - | BOTTOM: Layer bottom depth [Float] (LITHSAMP.BOTTOM) \\ | + | BOTTOM: Layer bottom depth [Float] (LITHSAMP.BOTTOM)\\ |
| - | ROCKSYMBOL: Layer lithology. This string must correspond to the | + | ROCKSYMBOL: Layer lithology. This string must correspond to the <font inherit/ |
| - | <font inherit/ | + | |
| - | field when loading color symbols using the [[Lithology Editor|]] | + | |
| - | [String] (LITHSAMP.ROCKSYMBOL) | + | |
| - | ==== | + | ==== Configuration ==== |
| - | Configuration | + | |
| Regardless of source type the following configuration is required. The Wells Dataset dialog sets up a query that is used to extract wells from the source. | Regardless of source type the following configuration is required. The Wells Dataset dialog sets up a query that is used to extract wells from the source. | ||
| - | ** | + | **Extent ** \\ |
| - | Extent ** \\ | + | __Fixed Extent:__ By default the dataset extent is identical to the current scene extent. However, this option makes it is possible to fix the extent to any area. |
| - | __Fixed Extent:__ | + | |
| - | By default the dataset extent is identical to the current scene extent. However, this option makes it is possible to fix the extent to any area. | + | |
| - | __ | + | __Extent:__ Defines a rectangular area where data are extracted from the source. |
| - | Extent: __ | + | |
| - | Defines a rectangular area where data are extracted from the source. | + | |
| - | ** | + | **Additional " |
| - | Additional " | + | |
| The wells dataset may be refined further using SQL. This makes it possible to use regular SQL to query the source within the extent. This is an advanced option that can be used for users that has an in depth knowledge of the source format. | The wells dataset may be refined further using SQL. This makes it possible to use regular SQL to query the source within the extent. This is an advanced option that can be used for users that has an in depth knowledge of the source format. | ||
| - | Example 1: Include only wells deeper than 50 meters. \\ | + | Example 1: Include only wells deeper than 50 meters.\\ |
| '' | '' | ||
| - | Example 2: Include only wells deeper than 50 meters and at a location with an elevation of more than 70 meters. \\ | + | Example 2: Include only wells deeper than 50 meters and at a location with an elevation of more than 70 meters.\\ |
| '' | '' | ||
| - | ** | + | **Preview Buttons ** \\ |
| - | Preview Buttons ** \\ | + | __Preview SQL…:__ Shows a preview of the resulting query. Advanced users can use this option to analyze the resulting query.\\ |
| - | __Preview SQL...:__ | + | __Preview Data…:__ Shows a preview of the data resulting from the query using the [[: |
| - | Shows a preview of the resulting query. Advanced users can use this option to analyze the resulting query. \\ | + | |
| - | __Preview Data...:__ | + | |
| - | Shows a preview of the data resulting from the query using the [[Dataset Viewer|]]. | + | |