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:23] – rebecca130301_gmail.comgeoscene3d:project_content:datasets:logs_dataset [2020/03/22 18:14] (current) – external edit 127.0.0.1
Line 3: Line 3:
 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. 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.
  
-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:datasets:access_database_source|Access Database Source]] in [[:geoscene3d:project_content:datasets:gerda_database_format|GERDA Database Format]].+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|]].
  
 ==== 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.\\
-[[:geoscene3d:project_content:datasets:access_database_source|Access Database Source]] of any format\\ +[[:geoscene3d:project_content:sources:access_database_source|]] of any format\\ 
-[[:geoscene3d:project_content:datasets:csv_file_source|CSV File Source]]. Formatted as shown below\\ +[[:geoscene3d:project_content:sources:csv_file_source|]]. Formatted as shown below\\ 
-[[:geoscene3d:project_content:datasets:firebird_database_source|Firebird Database Source]] of any format\\ +[[:geoscene3d:project_content:sources:firebird_database_source|]] of any format\\ 
-[[:geoscene3d:project_content:datasets:odbc_source|ODBC Source]]+[[:geoscene3d:project_content:sources: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>
Line 38: Line 38:
 __X:__ Easting in scene units\\ __X:__ Easting in scene units\\
 __Y:__ Northing 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.\\+__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 __Param1:__ A numeric value for a parameter. The file may contain an unlimited number of parameters
  
Line 48: Line 48:
 __Y:__ Field or column name for Y coordinates (required).\\ __Y:__ Field or column name for Y coordinates (required).\\
 __Well ID:__ Field or column name for Well ID (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:project_content:datasets:project_settings|Project Settings]].\\+__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|]].\\
 __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. __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.
  
Line 66: Line 66:
 **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…:__ 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:project_content:datasets:dataset_viewer|Dataset Viewer]].+__Preview Data…:__ Shows a preview of the data resulting from the query using the [[:geoscene3d:application:data_management:dataset_viewer|]].
  
 ==== GERDA Database Source ==== ==== GERDA Database Source ====
  
-A logs dataset may be extracted directly from a [[:geoscene3d:project_content:datasets:gerda_database|GERDA Database]] in either Note: Because the GERDA logs dataset also uses a [[:geoscene3d:project_content:datasets:jupiter|Jupiter]] well database logs from GERDA is primarily intended for Danish users.\\ +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:datasets:access_database_source|Access Database Source]] in [[:geoscene3d:project_content:datasets:gerda_database_format|GERDA Database Format]]\\ +[[:geoscene3d:project_content:sources:access_database_source|]] in [[:geoscene3d:project_content:dataformats:gerda_database_format|]]\\ 
-[[:geoscene3d:project_content:datasets:firebird_database_source|Firebird Database Source]] in [[:geoscene3d:project_content:datasets:gerda_database_format|GERDA Database Format]]+[[:geoscene3d:project_content:sources:firebird_database_source|]] in [[:geoscene3d:project_content:dataformats: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.
Line 106: Line 106:
 **Preview Buttons** \\ **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 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:project_content:datasets:dataset_viewer|Dataset Viewer]].+__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