Importing data

Importing takes a PC file of numbers (usually text) and adds it into a dataset. For example, you can import measured depths, pressures and temperatures into a measured discharge profile dataset. The file to import can be created by other PC applications (including this application itself) or by field instruments.

Overview of importing

  1. You need a suitable data file to import.
  2. Create an empty dataset set to receive the imported data.
  3. Start the import and choose the file format of the file to be imported.
  4. Select the file name to import.
  5. Assign field names and units to the numbers being imported.
  6. Select any options required.
  7. Import the data. If there are errors, fix them and import the data again or cancel.

Example: importing a csv file

This section will step you through a typical import, of this comma separated value file:

to this measured discharge profile:

Note that the comma separated value file above has an error in line 5: the pressure is X8.58675 but it obviously should be 78.58675.

Requirements of the file to import

The file must have one of these standard file formats:

Creating an empty data set to receive the imported data

Click the data type to import (for example Measured discharge profiles), then click Data, then click New:

Starting the import and choosing the file format

Selecting the file to import

Some import options have special procedures:

For the other import options, an Open file window appears. Navigate to the folder containing the file to import, click the file name and click Open. The import setup window appears.

Assigning field names and units to the numbers being imported

The import setup window has the values in the file arranged into rows and columns, for example:

Each column has a field name and optional unit at the top:

The first line of the file we are importing in this example has the field names and units of the numbers in the columns. This is because it was exported by the export module. However, files you get from other sources might not have a line like this, in which case you must know the correct field names and units separately.

When it starts, the import module guesses field names and units, based on what you selected last time you imported. In this case the module has guessed badly, and all the field names above are wrong - compare each field name in row 1 with the correct name in row 2.


Now, finally, set the field names and units to their correct values:

  1. If the guesses for field names are wrong, then first click to set all field names to Ignore:

  2. Change the field names and possible units to their correct values: For each column you want to import, click the field name and click the correct name in the menu. If the name in the menu requires units it has an arrow head; move the mouse to the right and click the correct units (the units of the number in the file, ft), for example:

  3. Change all field names to their correct values and units, to end up with:


When you are assigning field names to the columns, you must click NON-VISIBLE COLUMNS to choose fields that are not currently visible in the header window:

If you select one of these fields, WellSim reminds you that the field is not visible. To make the field visible see here.

Selecting any options required

For this example do not select any options:

Empty destination before import

The export module will delete any numbers already in the data set before it inserts the imported numbers.

No numbers deleted.

Ignore first rows

Enter a number of rows of the file to ignore. If the first row of the file has the field names and units, as in this case, then normally set this to 1. However, we will not do that in this example.

Strip delimiters

If you added delimiters when you exported the file, then choose the delimiter from the dropsdown list, so the import module can remove it.

Group delimiter on read


Does not

Clear all

Click to set all field names to Ignore.

Date format

If you are importing a date field, then select the format from this dropdown list, so the import module can import it correctly.

Thousands (and decimal) separator

This option is to handle unexpected separators in the data you are importing. If your Windows Region and language has your thousands separator as a , and your decimal separator as a . then the options are:

Importing the data and fixing any errors

In this example I have put errors in the file being imported, to show how to correct them. Normally there need not be errors.

  1. Click to start the import. The window displays errors on two lines:

  2. The error in the second line is the X in the pressure. Change the X to a 7.

  3. Click again. The window displays an error on one line:

  4. The error is that the line 1 of the file being imported does not have numbers, as the import module is expecting, instead it has the field names. We don't need to import line 1, so click to stop importing.

    NOTE We could have avoided this error by setting the option Ignore first rows to 1.

The import module returns to the data set, now with values of vertical depth, pressure and temperature. The vertical depths have been converted from ft to m.

  1. Enter a description Imported profile, 27.5 kg/s (99 t/hr).

  2. Enter a Mass flowrate 99 [t/hr].

  3. Click to check the data, calculate vertical depths and order the values by vertical depth.

The result is this measured discharge profile:

Importing from Borland Paradox

Importing from Microsoft Access

Importing from General ADO