How to import ...

ILWIS 1.4 raster data

Raster data from ILWIS 1.4 can only be imported into ILWIS 3 through the command line of the Main window. The syntax is described in topic Appendices : ILWIS script language (syntax), section ILWIS 1.4 Raster Import.

This topic gives you some preparative hints and background information so that import from ILWIS 1.4 into ILWIS 3 will be a smooth process. In the remainder, ILWIS 1.4 is used meaning ILWIS 1.3, 1.4 or 1.41.

   

  1. First of all, make a backup of your existing data.
  2. Organize the data to be imported in one or more directories.

Before starting to import, it is strongly advised to carefully read the following paragraphs.

Importing satellite images:

The .MPD and .MPI files of the satellite bands should be available. Any .HSB or .COL files can be deleted. When importing, specify domain type Image for satellite imagery.

Importing color composites:

The .MPD, .MPI, and .COL files of the color composite should be available. You may need to save the color composite's color look up table (.COL) in ILWIS 1.4; give it the same name as the color composite. When importing, specify domain type Picture for the output color composites.

Importing raster maps that were created from vector data:

Specify the domain type for the output map as:

Importing raster maps obtained through calculations:

For maps containing measurable values, for example created by MCalc calculations or by interpolations, the .MPD and .MPI files should be available. Any .HSB, .HSI files can be deleted. When importing, specify domain type Value. If you have a byte map with a user-defined color lut, see the next paragraph.

Importing classified raster data:

Byte maps containing classes are expected to have an .INF table with the class names and a color lut .COL. Such maps may for instance be obtained by a classify operation in MCalc using a classify table, or are output maps of an image classification. However, maps created through a classify table do not yet have an .INF table; it is advised to create one before Import 1.4. You could do this in ILWIS 1.4 TabCalc: create a table with as many records as classes in your map, add one column Name$, and type the meanings of your classes for each record, save as .INF. Of course, the same can be obtained with an editor.

As mentioned before, Import 1.4 works smoothly when the .MPD, .MPI, .COL and .INF files are available. It is also advised that the files have the same file name, e.g. DISTCLAS.MPD, DISTCLAS.MPI, DISTCLAS.COL, and DISTCLAS.INF. When importing, specify domain type Class.

 

Mind: if you do not make the effort to create an .INF table beforehand, then specify domain type Class or ID during import, and edit this domain later yourself.

Importing other raster data:

To import bitmaps, the .MPD and .MPI files should be available. There is no need for a .COL file. Bitmaps are automatically imported with domain type Bit.

Scanned raster data can be imported when the .MPD, .MPI are available. If the scanned data consists of gray values, specify domain type Image during import. If the scanned data is in color, the .COL should also be available. Then, specify domain type Picture during import.

To start importing maps and tables from ILWIS version 1.4:

Type on the command line of the Main window, the syntax as described in topic Appendices : ILWIS script language (syntax), section ILWIS 1.4 Raster Import.

When Import has finished you can start to display your maps, etc., see Getting started with ILWIS.

See also: