Import from Excel files
Data import directly from Excel provides the most flexible approach to data entry. Excel import uses smart table detection to identify data blocks and import data efficiently.
Version: 1.7.2+ (Aug 2017)
Usage: Project --> Import data --> Import Excel data...
How to use in practice
Excel Data Import
When importing an Excel file the process can be broken into the following steps:
- Select the file to be imported. We look for files with a .xlsx, and .xls file extension, and cannot currently import macro-enabled Excel files.
- Stage 1 - Configure the file reader: a preview of the data is provided along with tools to define the file structure.
- Stage 2 - Property linking: where you can define the relation between the properties in your file and the IGI property model.
- During the actual data import an import summary screen shows progress and any issues encountered.
During Stage1 the user is given the option to configure the structure of the Excel file being imported. This is shown below (version 2.0+):
The software will attempt to automatically identify several features of the Excel file, in particular:
- The sheets within the Excel file will be listed, and the first one (with data) selected by default. The user can import data from any one sheet in a given import session.
- The tables within each sheet are auto-detected, and listed. Table detection will also try and identify transposed (rows = properties, columns = samples). It is possible to turn off table detection if this does not work.
- Metadata (data about the data in the table), for example the well name, or the source of the data can be auto-detected and then added to each row of the table.
- The location of the header information is autodetected, but can be refined by the user (version 2.0+ adds significantly improved autodetection). The user can change the row on which the properties are defined, and on which indicators, units and ratios are defined, if present. It is possible that indicators, units and ratios are contained in the property row in which case the user can specify how to identify the components, for example being contained in . The user can also specify whether ion channel information is present for molecular data.
- The extent of the data can be specified too, with the option to automatically exclude properties with no data, or duplicate data (absolutely identical information) from the linking stage, which can save time in linking.
Finally the user can specify the default datums to be assumed for the well absolute datum (what the software should interpret as zero depth - we suggest this is always left as Mean Sea Level, but it maybe to Lowest Astronomical Tide in some parts of the world) and also the sample measured depth / true vertical depth datums. Typically these will be the well Kelly Bushing (Drillers Reference), but could be Mean Sea Level or some other reference depth. It is important these values are defined, in order for the depth conversion and associated logic to work in the system.
When importing date and time data (version 2.0+) it is also possible to specify the date-time format used (where this is ambiguous). The default will be your computers current region settings. This is relevant for dates such as 01/08/2021 which would be interpreted as the 1st of August 2021 in most parts of the world, but in the USA and some other places would be read as the 8th of January 2021. If you know your data has dates in the US format (MM/DD/YYYY) you can force import to use US format, and if you are in the US and know the data uses 'UK' format (DD/MM/YYYY) you can force the use of this format. In general we would suggest using an unambiguous date format (e.g. ISO8601) like 2021-08-01 which will be interpreted as the 1st of August in all countries.
Once you are happy the selections have been correctly made, selecting the Next button will take you to the linking screen.
© 2022 Integrated Geochemical Interpretation Ltd. All rights reserved.