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:qc_and_statistics:interpretationdatabaseqc [2021/07/23 08:28] – linda_jacobsengeoscene3d:qc_and_statistics:interpretationdatabaseqc [2021/07/30 09:43] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Interpretation Database QC ====== ====== Interpretation Database QC ======
  
-//This tool is used for quality control of interpretation points. It can be used before and after modelling especially for checking if manually interpretation have caused errors somewhere. //+//This tool is used for quality control of interpretation points. It can be used during and after modelling especially for checking if manually interpretation have caused errors somewhere. //
  
 **__Requirements: __ ** **__Requirements: __ **
  
-   * Layered model +   * Interpretation database
-  * 1D geophysical data+
  
 ---- ----
  
-==== Step 1. Running interpretation tool ====+==== Step 1. Setup the calculation tool ====
  
 1. See [[:geoscene3d:building_a_layered_model:modelsetup-stepbystep|Setting Up Data for Modelling]]. 1. See [[:geoscene3d:building_a_layered_model:modelsetup-stepbystep|Setting Up Data for Modelling]].
  
-  * Profile window with interpretation points connected to the boreholes.+  * A profile window with data points marking the layer interpretation connected to the boreholes.
  
 {{:geoscene3d:qc_and_statistics:profile.png?nolink&}} {{:geoscene3d:qc_and_statistics:profile.png?nolink&}}
  
-1. "QC and Statistics" menu –> "Interpretation Database QC…" –> next –> select the database file –> next.+  * It can be checked if all data points have individual coordinates or if overlaps exist. 
 + 
 +2. "QC and Statistics" menu –> "Interpretation Database QC…" –> next –> select the database file –> next.
  
 {{:geoscene3d:qc_and_statistics:interpretation_db.png?nolink&}} {{:geoscene3d:qc_and_statistics:interpretation_db.png?nolink&}}
  
-2. Select one or more layers for point interpretation.+3. Select one or more tables and the coordinate dimension.
  
-  * The menu is called "tables" because information about the data points for all layers are stored in the MS Access DB in tables. +  * The menu is called "tables" because information about the data points for all surfaces are stored in the MS Access database in tables. 
-  * In "Calculation Mode(s)" a box needs to be clicked to the left and right. The point dimension (XY or XYZ) and the extent of the QC - within one layer/table or across all layers/tables.+  * In "Calculation Mode(s)" a box needs to be clicked to the left and right. The point dimension (XY or XYZ) and the extent of the QC - within one table or across all tables.
  
 {{:geoscene3d:qc_and_statistics:table_l1_xy_intern.png}} {{:geoscene3d:qc_and_statistics:table_l1_xy_intern.png}}
  
-==== Step 2. Overlaps within each table ====+==== Step 2a. Overlaps within each table ====
  
 1. Overlapping points in one layer for a chosen dimension (XY or XYZ) can be controlled by clicking "Overlaps Within each Table". 1. Overlapping points in one layer for a chosen dimension (XY or XYZ) can be controlled by clicking "Overlaps Within each Table".
  
-  * The underlying picture shows two places in the layer boundary where points are overlapping in the XYZ dimension. The point legend describes with yellow color that two points are overlapping at each location. +  * This setting "within the table" will possibly be more prefareble to use if only one or a small amount of layers has been manually edited. 
-  * L1 XY intern + L1 XYZ intern - same output+  * The underlying profile shows two places in the layer boundary where points are overlapping in the XYZ dimension. The point legend describes with yellow color that two points are overlapping at each location.
  
 {{:geoscene3d:qc_and_statistics:l1_xyz_intern.png}} {{:geoscene3d:qc_and_statistics:l1_xyz_intern.png}}
  
-  * To find the exact coordinates for the problematic points the MS Access DB can be opened. Correctly, the table consistently agree with two sets of points located at the same position both in the 2nd and 3rd dimension.+  * To find the exact coordinates for the problematic points the MS Access DB can be opened. Consistently the tables agree with two sets of points located at the same position both for points in XY and for points in XYZ.
  
 {{:geoscene3d:qc_and_statistics:ms_l1xy.png}} {{:geoscene3d:qc_and_statistics:ms_l1xy.png}}
  
-  * It can be doublechecked+  * Further it can be argued that if doublepoints exist within the table it will almost always be in the XYZ dimension because it is most unlikely that points will be made inside the layer which in that case could generate double XY coordinates.
  
 {{:geoscene3d:qc_and_statistics:ms_l1xyz.png?nolink&}} {{:geoscene3d:qc_and_statistics:ms_l1xyz.png?nolink&}}
  
-2. When the same settings are used on the next layer the underlying picture gives an output of 3 sets of overlapping points with 2 points at each location according to the legend.+2. Repeat step 2.1. for layer 2.
  
-  * L2 XY intern + L2 XYZ intern - same output+  * When the same settings are used on the next layer the underlying picture gives an output of 3 sets of overlapping points with 2 points at each location according to the legend.
  
 {{:geoscene3d:qc_and_statistics:l2_xyz_intern.png}} {{:geoscene3d:qc_and_statistics:l2_xyz_intern.png}}
Line 56: Line 57:
 {{:geoscene3d:qc_and_statistics:ms_l2xyz.png?nolink&}} {{:geoscene3d:qc_and_statistics:ms_l2xyz.png?nolink&}}
  
-==== Step 3. Overlaps across all tables ====+==== Step 2b. Overlaps across all tables ====
  
   * Data points across more or all layers can also be controlled for overlaps.   * Data points across more or all layers can also be controlled for overlaps.
  
-1. Repeat step 1.2. for "overlaps across all tables".+1. Repeat step 1.3. just for "overlaps across all tables".
  
   * In the profile below calculation has been performed across all layers for XY points. There are multiple locations with 2 overlapping points according to the legend.   * In the profile below calculation has been performed across all layers for XY points. There are multiple locations with 2 overlapping points according to the legend.
-  * Note the difference between the profile in step 2.1. and the underlying profile. Here, three new overlapping points can be observed tied to the wells that wasn't apparant before in the profile from step 2.1. This difference can only be ascribed to a different vertical position but with identical XY coordinates. The most likely interpretation correlates to points snapped to the vertical oriented well for a layer boundary in another layer that results in overlapping XY points.+  * Note the difference between the profile in step 2.1. and the underlying profile. Here, three new overlapping points can be observed tied to the wells that wasn't apparant before in the profile from step 2.1. This difference can only be ascribed to a different vertical position but with identical XY coordinates. The most likely interpretation correlates to points snapped to the borehole for a new layer boundary that results in overlapping XY points.
  
 {{:geoscene3d:qc_and_statistics:l1_l2_xy_across.png?nolink&}} {{:geoscene3d:qc_and_statistics:l1_l2_xy_across.png?nolink&}}
  
-  * In the next profile the calculation has been performed across all tables for XYZ coordinates. Compared to the profile from step 2.2. there are no new surprises hence all doublepoints can be ascribed to XY points within the layer.+  * In the next profile the calculation has been performed across all tables for XYZ coordinates. Compared to the profile from step 2.2. there are no new overlapping data points hence all double points can be ascribed to XY points within the layer.
  
 {{:geoscene3d:qc_and_statistics:l1_l2_xyz_across.png}} {{:geoscene3d:qc_and_statistics:l1_l2_xyz_across.png}}
  
  

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