Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
OpenGround | gINT | Keynetix
  • Product Communities
OpenGround | gINT | Keynetix
gINT | Keynetix Wiki Why Can HoleBASE SI Not Handle High Precision Data?
    • Sign In
    • -gINT | Keynetix Wiki
      • +gINT
      • +gINT Collector
      • +gINT Civil Tools
      • -Keynetix
        • +Installing or Upgrading to CONNECT Edition
        • +Archive Webinars
        • -HoleBASE
          • +Getting Started
          • +HoleBASE - Setup and Installation
          • HoleBASE Professional Release Notes
          • -HoleBASE: FAQs
            • +Background Mapping
            • +Components and Configuration Packs
            • -Data Management
              • 'Project Currently Locked' message when attempting an import
              • 'Unrecognised Column' warning when importing data
              • AGS Import Warning : [Field Name] will be ignored because the destination is a calculated field
              • AGS mapping isn't showing but the data exports correctly
              • How can a GPS file be prepared for import?
              • How CPT Data Works in the HBSI
              • How many locations do I have in HoleBASE?
              • How to do a basic Export of AGS data from HoleBASE SI
              • How to enter Pipe Records in HoleBASE SI
              • How To Enter Special Characters
              • How to Export multiple projects to AGS from HoleBASE 3.1 to import to HBSI
              • How To set up installation instrument drawing types
              • How To Template
              • How To Use a Case Sensitive Search to Create Geology Code 2 data automatically
              • Importing AGSv4 file and get a message saying TYPE table can't be found
              • Incorrect Display Format Error Message when importing Test Schedule
              • Is there a list of non-standard AGS 4 fields that have been added to HoleBASE SI?
              • ISPT - ISPT_NVAL will be ignored... message when importing data into HoleBASE SI
              • What is a CSV file?
              • What is the Data Journey?
              • Where should coring data be entered or edited
              • Why Can HoleBASE SI Not Handle High Precision Data?
            • +Depth Linking
            • +Logs
            • +Trigger Sets and Report Grids
            • +User Accounts
            • +Working with Projects
          • +How Tos
          • +Issues
        • +HoleBASE Civil Extension
        • +HoleBASE Data Entry
        • +HoleBASE Excel Extension
        • +HoleBASE Template Studio
        • +KeyAGS
        • +KeyLAB
        • +Keynetix Component Downloads
        • +Working from Home with Keynetix Products
        • Hardware Specifications and Recommendations
        • Supported Platforms

     
     Questions about this article, topic, or product? Click here. 

    Why Can HoleBASE SI Not Handle High Precision Data?

      Product(s): Keynetix
      Version(s): 1.0
      Area: Assist

    Why Can HoleBASE SI Not Handle High Precision Data?

    Question

    How can I get HoleBASE SI to handle data with very high precison?

    Answer

    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.

    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:

    If editing this data, the interface changes and displays the data in its standard form:

    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.

    Explanation

    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:

    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:

    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.

    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.

    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.

    • Migrated
    • Share
    • History
    • More
    • Cancel
    • wiki.author Created by Bentley Colleague wiki.author
    • When: Tue, Jun 9 2020 5:44 PM
    • Revisions: 1
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies