A Logs Dataset is a specialized Tabular Dataset containing columnar data of values measured at different depths or elevations in wells. A dataset may contain multiple parameters from multiple wells.
Logs datasets are extracted from any of the sources that may be used for a Tabular Dataset or from an Access Database Source in GERDA Database Format.
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.
Access Database Source of any format
CSV File Source. Formatted as shown below
Firebird Database Source of any format
ODBC Source
Example of CSV file formatted for log data. Contains X, Y, Z, and three parameters. The columns may be in any order.
ID;X;Y;Z;Param1;Param2;Param3 Well1;713505.5;6193058.0;0.75095;6.44935;109.2679;115.91155 Well1;713505.5;6193058.0;55.44045;15.56755;117.55655;118.43845 Well1;713505.5;6193058.0;165.77625;8.38295;93.12655;94.451 . . Well2;713513.0;6193067.0;2.2157;4.56575;27.70745;35.7794 Well2;713513.0;6193067.0;26.68235;2.96495;65.77595;79.01795 Well2;713513.0;6193067.0;37.6344;8.2176;102.99935;110.6258 . . Well3;713519.5;6193063.5;1.15555;0.7734;108.9809;115.92065 Well3;713519.5;6193063.5;8.49285;11.02035;116.2594;117.1265 Well3;713519.5;6193063.5;11.54055;15.6092;114.78245;115.94835 . . .
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” and “Z = Depth” radio buttons. Note: If Z = Depth the Z values are converted to elevation using the designated scene terrain model surface. See Project Settings.
Value fields (Optional): List the names of the parameter value fields that should be included in the resulting dataset. The default “*” means that all fields will be included. If this box is left blank all fields are included.
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 “WHERE” Conditions (optional): The dataset may be refined further using SQL. This makes it possible to use regular SQL to query the source database or CSV file 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: Join two tables (Table1 and Table2) in the dataset. Both tables has an ID Field.
Table1.ID = Table2.ID
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 Dataset Viewer.
A logs dataset may be extracted directly from a GERDA Database in either Note: Because the GERDA logs dataset also uses a Jupiter well database logs from GERDA is primarily intended for Danish users.
Access Database Source in GERDA Database Format
Firebird Database Source in GERDA Database Format
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 “Additional conditions”.
Refresh: Refreshes the lists from source
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:
BOREHOLENO = ' 89. 1490
'
Examples 2, show only logs for two named wells:
BOREHOLENO IN (' 89. 1490', ' 89. 1540')
Examples 1, show only log for one named wells and a particular GERDA dataset:
BOREHOLENO = ' 89. 1490' AND DATASET = 255802
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 “Additional Conditions”
Preview Data…: Shows a preview of the data resulting from the query using the Dataset Viewer.