OpenGround Cloud and HoleBASE CONNECT Edition Database Model Upgrades

Note: A previous version of this article was available with a different proposed solution. This article supersedes any information that was previously available about this topic. 

Please review the section “Actions required by our users” to determine what actions (if any) will be required following the upgrade.  

Introduction  

This article details the planned changes to provide support for AGS 4.0.4 and enable further standardization. It applies to HoleBASE and OpenGround Cloud.  

The main focus of this release is to increase compatibility with the UK AGS 4.0.4 data standard while maintaining our core concepts of a standardized data model and minimizing any disruption and inconvenience for all of our users. 

This upgrade is currently planned for release for early 2021. OpenGround Cloud users will receive a service maintenance notification via the App Launcher confirming when this upgrade will take place. 

What is included in this update?  

New Value Fields 

The primary focus of this update is to support the storage of non-numeric data relevant to fields that have been traditionally formatted for numeric only.  

Our previous approach, and one taken by the AGS, would have been to convert these fields to text. However, this causes further data management issues, such as preventing data from being reported in the correct precision, enforcing data validation and preventing data being used correctly in graphs and in calculations.  

The adopted solution continues with the use of numeric fields and add a text field which will predominately be used for data input and reporting.  

The new text field will be the primary field for entering and storing data and any new outputs (either reports or data transfer) and the existing numeric field can then carry on being used for log outputs, Excel Sheets, Civils templates and older data export formats.  

All data presently in the numeric fields will be moved into the corresponding text field. 

Before Upgrade 

PID Result (Number Field) 

23 

24 

25 


After Upgrade 

PID Result (Text Field) 

PID Result Value (number Field) 

23 

23 

24 

24 

25 

25 


The Result Value fields are set up as equation fields with the following default equation ExtractValue(Result).  ExtractValue is a new function that will extract the first set of numeric values from a text sting   

Text 

ExtractValue 

23 

23 

-23 

-23 

<10 

10 

NP 

 


Affected Fields  

The below is a list of affected fields.   

Table  

Old Field (value)  

Upgraded Fields 

Fracture Spacing  

Fracture Spacing Average  

Fracture Spacing Average  (text) 

Fracture Spacing Average Value (number) 

Previous values are moved to the text field and the result field is auto calculated from this field. 

Fracture Spacing  

Fracture Spacing Max  

Fracture Spacing Average  (text) 

Fracture Spacing Average Value (number) 

Previous values are moved to the text field and the result field is auto calculated from this field. 

Laboratory Vane Tests  

Undrained Shear Strength Peak  

Undrained Shear Strength Peak  (text) 

Undrained Shear Strength PeakValue (number) 

Previous values are moved to the text field and the result field is auto calculated from this field. 

Laboratory Vane Tests  

Undrained Shear Strength Remolded  

Undrained Shear Strength Remolded (text) 

Undrained Shear Strength Remolded Value (number) 

Previous values are moved to the text field and the result field is auto calculated from this field. 

On Site Volatile Headspace Testing by Photo Ionisation Detector  

PID Result  

PID Result  (text) 

PID Result Value (number) 

Previous values are moved to the text field and the result field is auto calculated from this field. 

On Site Volatile Headspace Testing Using Flame Ionisation Detector  

FID Result  

FID Result  (text) 

FID Result Value (number) 

Previous values are moved to the text field and the result field is auto calculated from this field. 


The equation has been updated for any fields that previously used this method.  For example the Plastic Limit Value field equation has been updated from if(isnumber(PlasticLimit),PlasticLimit,null) to ExtractValue(PlasticLimit).  These equations have not been updated if you have changed them in your config pack. 

Data Import and Export Mapping Auto Updates 

The above changes have led to a requirement to update the AGS and CSV import mappings so that they can support the affected fields. 

  • AGS 3.1 Import – AGS 3.1 mapping has been updated to include the new fields and to evaluate the changed fields so that data will be imported into the correct text fields on import. All custom user mapping will be retained. An archive data mapping has also been created which will store a copy of the previous mapping for support purposes. 
  • AGS 3.1 Export – AGS 3.1 mapping has been updated to include the new fields and will still export the numeric fields into the relevant AGS3.1 field. All custom user mapping will be retained. An archive data mapping has also been created which will store a copy of the previous mapping for support purposes. 
  • AGS 4 Import – AGS 4 import has been updated to include the new fields and will now import AGS 4.0.3 and AGS 4.0.4 data. An update has also been applied that will create a new value field and split values into a text and a value field as required (see above). All custom user mapping will be retained. An archive data mapping has also been created which will store a copy of the previous mapping for support purposes. 
  • AGS 4.0.3 Export – This is no longer the default export mapping but can be selected from the mapping dropdown list when selecting AGS4 as the export type. The mapping has been updated to include the new fields and will still export the value fields into the relevant AGS 4.0.3 field (AGS 4.0.3 does not support different data types in numeric fields). All custom user mapping will be retained. An archive data mapping has also been created which will store a copy of the previous mapping for support purposes. 
  • AGS 4.0.4 Export – This is now the default export mapping when selecting AGS 4 as the export type. The mapping has been updated to include all of the new fields and will export the text fields into the relevant AGS 4.0.4 field (With the new XN data type). All custom user mapping will be retained.  
  • CSV Import – CSV Import mapping has been updated to include all of the new fields. 
  • CSV Export – CSV Export mapping has been updated to include all of the new fields. 
  • PLOG Import - PLOG Import mapping has been updated to include all of the new fields but will also support existing files. 
  • GINT Import – GINT Import mapping has not been updated and will need review. Please contact your Implementation Manager or the person who created your gINT import mapping for assistance with this. 

If you have edited any of the above listed fields’ mapping already, then we advise you to contact our support team who can advise the best course of action to resolve any issues. 

Table Title Changed 

The Window or Windowless Sampling Run Details table has been renamed to the Dynamic Sampling Run Details table to better match the purpose of the data stored within the table. 

New Fields 

The following fields were added in AGS 4.04 and are now included. 

Table 

Field 

Description 

LocationDetails 

NationalDatumRefSystem 

National Datum Referencing System used 

LocationDetails 

OriginalHoleID 

Original Hole ID 

LocationDetails 

OriginalJobReference 

Original Job Reference 

LocationDetails 

OriginatingCompany 

Originating Company 

SampleInformation 

SampleRecoveryLength 

Length of sample recovered 

RockPorosityAndDensity 

DryDensityIntact 

Intact dry density 

GeotechnicalChemistry 

DetectionLimit 

Limit of detection 


Field Updates 

Point Loads – Uncorrected Point Load and Point Loads – Corrected Point Load are now reported to 2 decimal places by default 

Triaxial Total Stress – CU is now reported to 2 significant figures by default. 

Actions Required by Our Users 

Users who enter data via the Data Entry App or the Data Entry Module may need to update their data entry profiles to include the new fields listed above. 

Users with custom gINT import mappings may require an update to support the changes. Contact the consultant who created your import mapping for more details on how we can help to apply these updates. 

Users who enter data via import, with the Data Entry Feedback Tool, Data Converter Tool or via custom Excel sheets which are output to CSV and imported will need to add the newly created fields if they want to use them. Users may need to update their Excel cell formats to ensure that text values can be added if required. 

Users with Template Studio Templates, Excel Extension Reports and Civils Extension Strips and Templates are recommended to check if the number fields are used in any equations or charts.  If so they will need to be updated to use the ResultValue field instead. 

When opening a project for the first time after the upgrade, you will be asked to run some calculations for that project. Please proceed with this to ensure that all data is moved into the correct locations within the database. This may take a few minutes on larger projects. 

 

More warning messages may appear on data import regarding fields being ignored due to fields being calculated fields. This data will import, it will just now be split into the text field with the numeric data also stored as mentioned above. 

Any configuration packs that were created in older versions of the software will import and attempt to upgrade during the import process. 

Please contact our support team for help or more information on the above and we will help guide you through any of the changes that you need to make. 

How to get hold of this update? 

Please see the below section, depending on the solution that you use. 

OpenGround Cloud 

All OpenGround Cloud users will be updated to this latest model, currently scheduled for January 2021. 

HoleBASE CONNECT 

We are currently planning on releasing an AGS404 compatible version of HoleBASE CONNECT and connected applications early 2021, more information on when this will be available in due course. Users on HoleBASE CONNECT will be prompted to download the latest update through the CONNECT centre. Once downloaded, any HoleBASE administrator user can login and initiate the database upgrade by logging into the software and allowing the process to complete. 

HoleBASE Professional and Standard 

We do not plan to release this update to users on this solution at this time. 

Users who wish to upgrade can do so by upgrading to a HoleBASE CONNECT edition licence and then following the instructions in this section above. 

Anonymous