Importing Data

Overview

Within Metis Transform there are a number of ways in which data can be entered / imported into a project. With multiple options, import comes with a variety of tools to make data loading smooth, accurate and efficient.

Version: 2.0+ (Oct 2021)

Usage: Project --> Import data... --> Import text data...

Import p:IGI-3 data...

Import Excel data...

How to use in practice

Data Import

There are a number of ways in which data can be added to either a new, or existing, project:

Importing data from a p:IGI-3 file - this is not a simple mapping, as p:IGI-3 mixed together data from a number of analyses. We have suggested default mappings, but users are advised to review any bulk imported data from p:IGI-3 and user columns will need to be mapped by the user.
Importing data from a text file e.g. (.csv or.txt) - this is particularly suitable for importing large blocks of data with a regular 'rectangular' shape, such as those produced by a bulk export. It is more memory efficient that Excel import and should be preferred for very large files.
Importing data from an Excel file - this is very flexible, but will not scale to very large files with more than around ten thousand samples. It is particularly suitable for data provided by labs and can read in all sorts of tabulated data.
- - Importing data from an APT generated IGI compatible Excel file - This is a flat-file format export of APT analysed data that uses the positive import features of Excel import.
Importing direct from an existing p:IGI+ / Metis Transform file is achieved using data export and subsequent auto-import of the zip file - simply drag the zip file onto the workspace to initialise import.
Importing well data is possible from a range of different types of input files.
Manual input of data into individual spreadsheets - it is possible to copy-paste, or manually type data to pages. This is however, error prone, as there is no checking you are pasting the data in the right properties (columns) with the right units etc, and to the right samples (rows). We recommend using import where possible. Note with manual input the property Well Name.Well cannot be bulk pasted into, but must be manually entered on a sample by sample basis.

The import process can be complex but is strongly preferred to copy/paste, or manual data entry, as human errors are less likely to corrupt data values, however the process of linking the different inputs from the file to the properties in the IGI property model is important to get right. This includes defining the import units. Help on identifying properties is available throughout the system using the Geochemistry help viewer.

During import into Transform, all rows are treated as 'candidate' wells and samples. In particular, unlike p:IGI+, wells are not automatically created on import, rather they are identified as part of the Project Merge tool specific to Transform. The user is thus given complete control over which well data to retain and how to manage wells and samples in their Transform projects.

In v2.5 wells (candidate wells) can now be manually created in Transform.

After a file has been imported Undo (Ctrl+Z) can be used to remove the imported data from the project - this can also be re-done.