Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| geoscene3d:project_content:datasets:logs_dataset [2020/01/31 10:50] – created gs3d | geoscene3d:project_content:datasets:logs_dataset [2020/03/22 18:14] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | v | + | ====== Logs Dataset ====== |
| + | |||
| + | A Logs Dataset is a specialized [[: | ||
| + | |||
| + | Logs datasets are extracted from any of the sources that may be used for a [[: | ||
| + | |||
| + | ==== Tabular Sources ==== | ||
| + | |||
| + | Any of tabular sources can be used for a Logs Dataset. All sources must contain WellID, X, Y, Z, and at least one logged parameter.\\ | ||
| + | [[: | ||
| + | [[: | ||
| + | [[: | ||
| + | [[: | ||
| + | |||
| + | Example of CSV file formatted for log data. Contains X, Y, Z, and three parameters. The columns may be in any order.< | ||
| + | |||
| + | ID; | ||
| + | Well1; | ||
| + | Well1; | ||
| + | Well1; | ||
| + | . | ||
| + | . | ||
| + | Well2; | ||
| + | Well2; | ||
| + | Well2; | ||
| + | . | ||
| + | . | ||
| + | Well3; | ||
| + | Well3; | ||
| + | Well3; | ||
| + | . | ||
| + | . | ||
| + | . | ||
| + | |||
| + | </ | ||
| + | |||
| + | __ID:__ Any number or string identifying the well\\ | ||
| + | __X:__ Easting in scene units\\ | ||
| + | __Y:__ Northing in scene units\\ | ||
| + | __Z:__ Depth or elevation of measurement. NOTE: if Z is elevation then the first Z value for each well must be the elevation at the top of the well. If Z is depth then the first Z value for each well must be zero.\\ | ||
| + | __Param1:__ A numeric value for a parameter. The file may contain an unlimited number of parameters | ||
| + | |||
| + | **Configuration** \\ | ||
| + | A tabular logs dataset is defined as a SQL query containing the three usual sections: SELECT, FROM, and WHERE. The configuration dialog reflects these three sections. | ||
| + | |||
| + | **SELECT** \\ | ||
| + | __X:__ Field or column name for X coordinates (required).\\ | ||
| + | __Y:__ Field or column name for Y coordinates (required).\\ | ||
| + | __Well ID:__ Field or column name for Well ID (required).\\ | ||
| + | __Z:__ Field or column name for Z coordinates. Be sure to check the "Z = Elevation" | ||
| + | __Value fields (Optional): | ||
| + | |||
| + | **FROM** \\ | ||
| + | List the tables that contain the fields listed above in the SELECT box. Note: For CSV File Sources this is always the filename. | ||
| + | |||
| + | **WHERE** \\ | ||
| + | __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. | ||
| + | |||
| + | __Additional " | ||
| + | |||
| + | Example: Join two tables (Table1 and Table2) in the dataset. Both tables has an ID Field.\\ | ||
| + | '' | ||
| + | |||
| + | **Preview Buttons** \\ | ||
| + | __Preview SQL…:__ 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 [[: | ||
| + | |||
| + | ==== GERDA Database Source ==== | ||
| + | |||
| + | A logs dataset may be extracted directly from a [[: | ||
| + | [[: | ||
| + | [[: | ||
| + | |||
| + | Warning: Log data may contain a very large number of data points. It is recommended to limit that number of logs to less that 10 in each dataset. | ||
| + | |||
| + | **Jupiter Wells Source (XYZ coordinates)** \\ | ||
| + | The GERDA database does not contain XY-coordinates for the log data. Therefore, coordinates are extracted from a Jupiter database using the well ID (BOREHOLENO) that is stored in GERDA. | ||
| + | |||
| + | **Available Logs** \\ | ||
| + | The upper list box contains the log types that are available in one or more wells within the area defined by the horizontal extent. The lower list box contains the different names used for the selected log type in the upper list box. NOTE: if one well has multiple loggings of the same log type all the logs will be plotted. To further narrow down the data selection use " | ||
| + | __Refresh: | ||
| + | __Add:__ Adds the selected log type / log name to the selected logs list | ||
| + | |||
| + | **Selected Logs** \\ | ||
| + | The list shows the selected logs. The selected logs will be extracted from the source and will be available for visualization and interpolation.\\ | ||
| + | __Remove:__ Removes the selected log from the list | ||
| + | |||
| + | **WHERE (conditions)** \\ | ||
| + | **Horizontal Extent** \\ | ||
| + | The dataset is generated for wells within this area. | ||
| + | |||
| + | **Additional conditions (optional)** \\ | ||
| + | Standard SQL may be used for additional refinement of the data search (see "Log Type and Name" | ||
| + | |||
| + | Examples 1, show only log for one named wells:\\ | ||
| + | '' | ||
| + | |||
| + | Examples 2, show only logs for two named wells:\\ | ||
| + | '' | ||
| + | |||
| + | Examples 1, show only log for one named wells and a particular GERDA dataset: | ||
| + | '' | ||
| + | |||
| + | **Preview Buttons** \\ | ||
| + | __Preview SQL…:__ Shows a preview of the resulting query in the GERDA database. This is the query that may be refined using the " | ||
| + | __Preview Data…:__ Shows a preview of the data resulting from the query using the [[: | ||
| + | |||