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:jupiter_wells_dataset [2020/02/12 16:00] rebecca130301_gmail.comgeoscene3d: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 [[:geoscene3d:project_content:datasets:wells_object|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 [[:geoscene3d:project_content:objects:jupiter_wells_object|Wells Object]].
  
 ==== Source Types ==== ==== Source Types ====
  
-[[:geoscene3d:project_content:datasets:access_database_source|Access Database Source]] in [[:geoscene3d:project_content:datasets:jupiter_database_format|Jupiter Database Format]].\\ +[[:geoscene3d:project_content:sources:access_database_source|]] in [[:geoscene3d:project_content:dataformats:jupiter_database_format|]].\\ 
-[[:geoscene3d:project_content:datasets:access_database_source|Access Database Source]] in [[:geoscene3d:project_content:datasets:jupiter_generic_database_format|Jupiter Generic Database Format]] (generic well database format).\\ +[[:geoscene3d:project_content:sources:access_database_source|]] in [[:geoscene3d:project_content:dataformats:jupiter_generic_database_format|]] (generic well database format).\\ 
-[[:geoscene3d:project_content:datasets:csv_file_source|CSV File Source]] (generic CSV file format, layers only).+[[:geoscene3d:project_content:sources: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 [[:geoscene3d:project_content:datasets:jupiter_database_format|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<code>+When using a generic CSV file source it must be formatted as show below. The column names are identical to field names in the [[:geoscene3d:project_content:dataformats:jupiter_database_format|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<code>
  
 BOREHOLENO;ELEVATION;XUTM;YUTM;SAMPLENO;TOP;BOTTOM;ROCKSYMBOL BOREHOLENO;ELEVATION;XUTM;YUTM;SAMPLENO;TOP;BOTTOM;ROCKSYMBOL
Line 49: Line 49:
 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 <font inherit/Courier New,Courier,monospace;;inherit;;inherit>CODE</font> field when loading color symbols using the [[:geoscene3d:project_content:datasets:lithology_editor|Lithology Editor]] [String] (LITHSAMP.ROCKSYMBOL)+ROCKSYMBOL: Layer lithology. This string must correspond to the <font inherit/Courier New,Courier,monospace;;inherit;;inherit>CODE</font> field when loading color symbols using the [[:geoscene3d:application:misc:symbol_list_editor|Lithology Editor]] [String] (LITHSAMP.ROCKSYMBOL)
  
 ==== Configuration ==== ==== Configuration ====
Line 58: Line 58:
 __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 "WHERE" conditions (optional) ** \\ **Additional "WHERE" conditions (optional) ** \\
Line 71: Line 71:
 **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|]].
  
  

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