User Tools

Differences

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

Link to this comparison view

Next revision
Previous revision
geoscene3d:project_content:datasets:odv_dataset [2020/02/12 16:11] – created rebecca130301_gmail.comgeoscene3d:project_content:datasets:odv_dataset [2020/03/22 18:04] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== ODV Dataset ====== ====== ODV Dataset ======
  
-An ODV Dataset represents a group of ODV (One Dimensional Vertical) geophysical resistivity layer models. The dataset is defined with a query that consists of a rectangular extent, settings for data type, and optional SQL. ODV Datasets are used in the  [[ODV Models (1D Geophysics) Object|]].+An ODV Dataset represents a group of ODV (One Dimensional Vertical) geophysical resistivity layer models. The dataset is defined with a query that consists of a rectangular extent, settings for data type, and optional SQL. ODV Datasets are used in the [[:geoscene3d:project_content:objects:odv_models:odv_models_1d_geophysics_object|]].
  
-==== +==== Source Types ====
-Source Types   ====+
  
-[[Access Database Source|]] +[[:geoscene3d:project_content:sources:access_database_source|]] in [[:geoscene3d:project_content:dataformats:gerda_database_format|]]\\ 
- in  [[GERDA Database Format\\ +[[:geoscene3d:project_content:sources:firebird_database_source|]] in [[:geoscene3d:project_content:dataformats:gerda_database_format|]]\\ 
-Firebird Database Source|]] +[[:geoscene3d:project_content:sources:csv_file_source|]] (generic CSV file format)
- in  [[GERDA Database Format|]] +
-  \\ +
-[[CSV File Source|]] +
- (generic CSV file format)+
  
-When using a generic CSV file source it must be formatted as show here. The column names are identical to field names in the  [[GERDA Database Format|]]. All columns are required but may be in any order. Corresponding table and field names from GERDA is shown in parenthesis in the field description below the example.<code>+When using a generic CSV file source it must be formatted as show here. The column names are identical to field names in the [[:geoscene3d:project_content:dataformats:gerda_database_format|]]. All columns are required but may be in any order. Corresponding table and field names from GERDA is shown in parenthesis in the field description below the example.<code>
  
 NAME;IDENT;DATATYPE;DATSUBTYPE;MODEL;POSITION;XUTM;YUTM;ELEVATION;LAYER;RHO;THICKNESS;DEPTOP;DEPBOTTOM NAME;IDENT;DATATYPE;DATSUBTYPE;MODEL;POSITION;XUTM;YUTM;ELEVATION;LAYER;RHO;THICKNESS;DEPTOP;DEPBOTTOM
Line 38: Line 33:
  
 NAME: Short name of model (MODEL.NAME)\\ NAME: Short name of model (MODEL.NAME)\\
-IDENT:  Long dame of model (MODEL.IDENT) \\ +IDENT: Long dame of model (MODEL.IDENT)\\ 
-DATATYPE: Primary datatype (ODVMODSE.DATATYPE) \\ +DATATYPE: Primary datatype (ODVMODSE.DATATYPE)\\ 
-DATSUBTYPE: Secondary datatype (ODVMODSE.DATSUBTYPE) \\ +DATSUBTYPE: Secondary datatype (ODVMODSE.DATSUBTYPE)\\ 
-MODEL: Primary Model ID (ODVPOS.MODEL) \\ +MODEL: Primary Model ID (ODVPOS.MODEL)\\ 
-POSITION: Secondary Model ID in case the same model consists of multiple sub models (ODVPOS.POSITION) \\ +POSITION: Secondary Model ID in case the same model consists of multiple sub models (ODVPOS.POSITION)\\ 
-XUTM: Easting (ODVPOS.XUTM) \\ +XUTM: Easting (ODVPOS.XUTM)\\ 
-YUTM: Northing (ODVPOS.YUTM) \\ +YUTM: Northing (ODVPOS.YUTM)\\ 
-ELEVATION: Model elevation (ODVPOS.ELEVATION) \\ +ELEVATION: Model elevation (ODVPOS.ELEVATION)\\ 
-LAYER: Model layer ID (ODVLAYER.LAYER) \\ +LAYER: Model layer ID (ODVLAYER.LAYER)\\ 
-RHO: Layer resistivity (ODVLAYER.RHO) \\ +RHO: Layer resistivity (ODVLAYER.RHO)\\ 
-THICKNESS: Layer thickness (ODVLAYER.THICKNESS) \\ +THICKNESS: Layer thickness (ODVLAYER.THICKNESS)\\ 
-DEPTOP: Layer top depth (ODVLAYER.DEPTOP) \\+DEPTOP: Layer top depth (ODVLAYER.DEPTOP)\\
 DEPBOTTOM: Layer bottom depth (ODVLAYER.DEPBOTTOM) DEPBOTTOM: Layer bottom depth (ODVLAYER.DEPBOTTOM)
  
-==== +==== Configuration ====
-Configuration  ====+
  
 Regardless of source an ODV Dataset is defined in the same way Regardless of source an ODV Dataset is defined in the same way
  
-__ +__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:__ +
-Defines a rectangular area where data are extracted from the source.+
  
-** +**Model Selection ** \\ 
-Model Selection ** \\ +__Type:__ Data type, e.g., "PACES" or "TEM". This setting corresponds to the field ODVMODSE.DATATYPE in the GERDA Database\\ 
-__Type:__ +__Sub Type:__ Data sub type e.g., "TEM40" or "SKYTEM1". Used for data type "TEM" only. This setting corresponds to the field ODVMODSE.DATSUBTYPE in the GERDA Database\\ 
-Data type, e.g., "PACES" or "TEM". This setting corresponds to the field ODVMODSE.DATATYPE in the GERDA Database \\ +__Edition:__ Selection of all model edition or a specific model edition. This setting corresponds to the field MODEL.EDITION in the GERDA Database.\\
-__Sub Type:__ +
-Data sub type e.g., "TEM40" or "SKYTEM1". Used for data type "TEM" only. This setting corresponds to the field ODVMODSE.DATSUBTYPE in the GERDA Database \\ +
-__Edition:__ +
-Selection of all model edition or a specific model edition. This setting corresponds to the field MODEL.EDITION in the GERDA Database.  \\+
 Note: Use following SQL to select more than one model edtion in SKYTEM data (In this dataset, the model edtions are numbered 3269, 3370 and 3391) Note: Use following SQL to select more than one model edtion in SKYTEM data (In this dataset, the model edtions are numbered 3269, 3370 and 3391)
  
 {{:geoscene3d:project_content:datasets:dc825e2b04d6bbc1fc9064e6607ca834.png}} {{:geoscene3d:project_content:datasets:dc825e2b04d6bbc1fc9064e6607ca834.png}}
  
-** +**Model Layers ** \\ 
-Model Layers ** \\ +__More Than____:__ Include models with more than this number of layers\\ 
-__More Than__ +__Less Than____:__ Include models with less than this number of layers
-__:__ +
-Include models with more than this number of layers \\ +
-__Less Than__  __ +
-: __+
  
-Include models with less than this number of layers +__Additional "WHERE" conditions (optional):__ The dataset may be refined further using SQL. This is an advanced option that can be used for users that has an in depth knowledge of the [[:geoscene3d:project_content:dataformats:gerda_database_format|]]. May also be used with the generic CSV format but field names in the SQL is of course limited to the fields present in the CSV File\\ 
- +__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|]].
-Additional "WHERE" conditions (optional): __ +
-The dataset may be refined further using SQL. This is an advanced option that can be used for users that has an in depth knowledge of the  [[GERDA Database Format|]]. May also be used with the generic CSV format but field names in the SQL is of course limited to the fields present in the CSV File  \\ +
-__ +
-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|]].+
  
  

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