User Tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
geoscene3d:project_content:datasets:logs_dataset [2020/02/12 16:18] – rebecca130301_gmail.comgeoscene3d:project_content:datasets:logs_dataset [2020/03/22 18:14] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Logs Dataset ====== ====== Logs Dataset ======
  
-A Logs Dataset is a specialized  [[Tabular Dataset|]] +A Logs Dataset is a specialized [[:geoscene3d:project_content:datasets:tabular_dataset|]] containing columnar data of values measured at different depths or elevations in wells. A dataset may contain multiple parameters from multiple wells.
- 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|]] +Logs datasets are extracted from any of the sources that may be used for a [[:geoscene3d:project_content:datasets:tabular_dataset|]] or from an [[:geoscene3d:project_content:sources:access_database_source|]] in [[:geoscene3d:project_content:dataformats:gerda_database_format|]].
- or from an  [[Access Database Source|]] +
- in  [[GERDA Database Format|]].+
  
-==== +==== Tabular Sources ====
-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. \\ +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|]] +[[:geoscene3d:project_content:sources:access_database_source|]] of any format\\ 
- of any format \\ +[[:geoscene3d:project_content:sources:csv_file_source|]]. Formatted as shown below\\ 
-[[CSV File Source|]]. Formatted as shown below \\ +[[:geoscene3d:project_content:sources:firebird_database_source|]] of any format\\ 
-[[Firebird Database Source|]] +[[:geoscene3d:project_content:sources:odbc_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.<code> Example of CSV file formatted for log data. Contains X, Y, Z, and three parameters. The columns may be in any order.<code>
  
 ID;X;Y;Z;Param1;Param2;Param3 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;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;55.44045;15.56755;117.55655;118.43845
- 
 Well1;713505.5;6193058.0;165.77625;8.38295;93.12655;94.451 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;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;26.68235;2.96495;65.77595;79.01795
- 
 Well2;713513.0;6193067.0;37.6344;8.2176;102.99935;110.6258 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;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;8.49285;11.02035;116.2594;117.1265
- 
 Well3;713519.5;6193063.5;11.54055;15.6092;114.78245;115.94835 Well3;713519.5;6193063.5;11.54055;15.6092;114.78245;115.94835
- 
 . .
- 
 . .
- 
 . .
  
 </code> </code>
  
-ID: +__ID:__ Any number or string identifying the well\\ 
-Any number or string identifying the well +__X:__ Easting in scene units\\ 
- +__Y:__ Northing in scene units\\ 
-X: +__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.\\ 
-Easting in scene units +__Param1:__ A numeric value for a parameter. The file may contain an unlimited number of parameters
- +
-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+
  
 +**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. 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 +**SELECT** \\ 
- +__X:__ Field or column name for X coordinates (required).\\ 
-X: +__Y:__ Field or column name for Y coordinates (required).\\ 
-Field or column name for X 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 [[:geoscene3d:application:project_settings|]].\\ 
-Y: +__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.
-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+
  
 +**FROM** \\
 List the tables that contain the fields listed above in the SELECT box. Note: For CSV File Sources this is always the filename. List the tables that contain the fields listed above in the SELECT box. Note: For CSV File Sources this is always the filename.
  
-WHERE+**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.
  
-Fixed Extent: +__Extent:__ Defines a rectangular area where data are extracted from the source.
-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: +__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.
-Defines a rectangular area where data are extracted from the source.+
  
-Additional "WHERE" Conditions (optional): +Example: Join two tables (Table1 and Table2) in the dataset. Both tables has an ID Field.\\ 
-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.+''Table1.ID = Table2.ID''
  
-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 [[:geoscene3d:application:data_management:dataset_viewer|]].
  
-Table1.ID = Table2.ID+==== GERDA Database Source ====
  
-Preview Buttons +A logs dataset may be extracted directly from a [[:geoscene3d:project_content:dataformats:gerda_database_format|GERDA Database]] in either Note: Because the GERDA logs dataset also uses a [[:geoscene3d:project_content:dataformats:jupiter_database_format|Jupiter]] well database logs from GERDA is primarily intended for Danish users.\\ 
- +[[:geoscene3d:project_content:sources:access_database_source|]] in [[:geoscene3d:project_content:dataformats:gerda_database_format|]]\\ 
-Preview SQL...: +[[:geoscene3d:project_content:sources:firebird_database_source|]] in [[:geoscene3d:project_content:dataformats:gerda_database_format|]]
-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|]]. +
- +
-GERDA Database Source +
- +
-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. 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) +**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. 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+**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
  
-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". +**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.\\ 
-Refresh: +__Remove:__ Removes the selected log from the list
-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+
  
 +**WHERE (conditions)** \\
 +**Horizontal Extent** \\
 The dataset is generated for wells within this area. The dataset is generated for wells within this area.
  
-Additional conditions (optional) +**Additional conditions (optional)** \\
 Standard SQL may be used for additional refinement of the data search (see "Log Type and Name"). 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 1, show only log for one named wells:\\ 
- +''BOREHOLENO = ' 89. 1490'''
-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+Examples 2, show only logs for two named wells:\\ 
 +''BOREHOLENO IN (' 89. 1490', ' 89. 1540')''
  
-Preview SQL...: +Examples 1, show only log for one named wells and a particular GERDA dataset:\\ 
-Shows a preview of the resulting query in the GERDA database. This is the query that may be refined using the "Additional Conditions"+''BOREHOLENO = ' 89. 1490' AND DATASET = 255802''
  
-Preview Data...: +**Preview Buttons** \\ 
-Shows a preview of the data resulting from the query using the  [[Dataset Viewer|]].+__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 [[:geoscene3d:application:data_management:dataset_viewer|]].
  
  

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also, you acknowledge that you have read and understand our Privacy Policy. If you do not agree, please leave the website.

More information