<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Why Can HoleBASE  SI  Not Handle High Precision  Data?</title><link>https://communities.bentley.com/products/geotechnical1/w/wiki/49834/why-can-holebase-si-not-handle-high-precision-data</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Why Can HoleBASE  SI  Not Handle High Precision  Data?</title><link>https://communities.bentley.com/products/geotechnical1/w/wiki/49834/why-can-holebase-si-not-handle-high-precision-data</link><pubDate>Tue, 09 Jun 2020 21:44:05 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a035e591-6d18-4582-981a-a149b2e80848</guid><dc:creator>wiki.author</dc:creator><comments>https://communities.bentley.com/products/geotechnical1/w/wiki/49834/why-can-holebase-si-not-handle-high-precision-data#comments</comments><description>Current Revision posted to gINT | Keynetix Wiki by wiki.author on 6/9/2020 9:44:05 PM&lt;br /&gt;
&lt;table style="border:0px solid #dce5f0;background-color:#dce5f0;" border="0"&gt;
	&lt;tbody&gt;
		&lt;tr&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;Product(s):&lt;/strong&gt;&lt;/td&gt;
			&lt;td&gt;Keynetix&lt;/td&gt;
			&lt;td&gt;&lt;/td&gt;
		&lt;/tr&gt;
		&lt;tr&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;Version(s):&lt;/strong&gt;&lt;/td&gt;
			&lt;td&gt;1.0&lt;/td&gt;
			&lt;td&gt;&lt;/td&gt;
		&lt;/tr&gt;		
		&lt;tr&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;&lt;/td&gt;
			&lt;td style="text-align:right;"&gt;&lt;strong&gt;Area:&lt;/strong&gt;&lt;/td&gt;
			&lt;td&gt;Assist&lt;/td&gt;
			&lt;td&gt;&lt;/td&gt;
		&lt;/tr&gt;		
	&lt;/tbody&gt;
&lt;/table&gt; &lt;br /&gt; 
  
    &lt;p&gt;&lt;/p&gt;
  
  
    &lt;h1&gt;Why Can HoleBASE  SI  Not Handle High Precision  Data?&lt;/h1&gt;
    &lt;h2&gt;Question&lt;/h2&gt;
    &lt;p&gt;How can I get HoleBASE  SI  to handle data with very high precison?&lt;/p&gt;
    &lt;h2&gt;Answer&lt;/h2&gt;
    &lt;p&gt;Within HoleBASE SI it may be necessary to adjust the precision of certain fields within the database in order to allow for full representation of your data. This may also be affecting AGS imports of data due to the program rejecting values that are set to a higher precision then is currently allowed within the project.&lt;/p&gt;
    &lt;p&gt;A good example of this is the permeability result field as illustrated below.  Notice how the data is displayed in scientific notifcation due to the level of precision:&lt;/p&gt;
    &lt;p&gt;
      &lt;img src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-01-05/5504.precision1.png" alt=" " /&gt;
    &lt;/p&gt;
    &lt;p&gt;If editing this data, the interface changes and displays the data in its standard form:&lt;/p&gt;
    &lt;p&gt;
      &lt;img src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-01-05/4370.precision2.png" alt=" " /&gt;
    &lt;/p&gt;
    &lt;p&gt;In this example, the client has asked for the precision of data to be reported to an additional two decimal places. However, when editing to this within HoleBASE SI, the program rejects this value and the following occurs when trying to save the data.&lt;/p&gt;
    &lt;p&gt;
      &lt;img src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-01-05/7120.precision3.png" alt=" " /&gt;
    &lt;/p&gt;
    &lt;h2&gt;Explanation&lt;/h2&gt;
    &lt;p&gt;In order for the extra precision to be set within HoleBASE SI the configuration will have to be adjusted.  Browse through to the Model Structure option underneath the Configuration tab within a project. From within this interface, select the Edit option next to the table in which the field exists - in the current example this will be the Laboratory Permeability Tests table:&lt;/p&gt;
    &lt;p&gt;
      &lt;img src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-01-05/8780.Lab-Perm-Tests-1.PNG" alt=" " /&gt;
    &lt;/p&gt;
    &lt;p&gt;Following this, select the Edit option that corresponds to the field that needs to be edited. In this example this is the Coefficient of Permeability field:&lt;/p&gt;
    &lt;p&gt;
      &lt;img src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-01-05/6082.lab-perm-2.PNG" alt=" " /&gt;
    &lt;/p&gt;
    &lt;p&gt;The edit heading screen will then appear allowing for the field definition to be changed. In this case it is necessary for the Decimal Places value to be edited under the Database Options section. Select the dropdown and change the value to whatever is needed.&lt;/p&gt;
    &lt;p&gt;
      &lt;img src="/cfs-file/__key/communityserver-wikis-components-files/00-00-00-01-05/7673.precision6.png" alt=" " /&gt;
    &lt;/p&gt;
    &lt;p&gt;Save the changes and the program will reload all of the data grids to reflect the changes made. The data can then be edited to contain up to 19 decimal places of precision.&lt;/p&gt;
    &lt;p&gt;This will then effect all values within the project that the change has been made. If this change needs expanding into other new projects then a configuration pack can be made.&lt;/p&gt;
    &lt;p&gt;&lt;/p&gt;
  
&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Migrated&lt;/div&gt;
</description></item></channel></rss>