Main window

Import

Import Map

Import General Raster

Import Table Wizard

Select a file:

Select the file that you wish to import.

Directories:

If necessary, change the current directory.

Drives:

If necessary, change the current drive.

Import format:

Select the format of the file which you wish to import. When an import format is selected, the input files that have the correct extension in the current directory will be shown.

Tip:

• There are separate Help topics for the Import formats  Aster(1A/1B), and  Use General Raster Import (click the links).
• You can also click Import General Raster Import in the header of this topic.

Output file name:

Type a name for the output ILWIS object(s). Do not specify an extension for the ILWIS object(s); ILWIS will add its own extensions.

Height offset:

Only for GARtrip import (see below).

Arc/Info ASCII:

Imports an Arc/Info non-compressed ASCII file; the input file is expected to have extension .ASC or .NAS.

Arc/Info .E00:

Imports an Arc/Info .E00 file. For more information, refer to the Vector import below.

Tip: To import Arc/Info Grid files, export the Arc/Info files to .E00 or to non-compressed ASCII.

Compuserve-GIF:

Imports a GIF image. First, it is checked whether the file contains the GIF signature. Then, it is checked whether a color lookup table is available. When a color lookup table is found, the raster map will use domain Picture, otherwise, the map will use domain Image. After that the (LZW compressed) raster data is retrieved.
A GIF file does not contain any geographic information, therefore the resulting raster map in ILWIS will not be georeferenced. Furthermore, the raster map will always be stored as using 1 byte per pixel (maximum of 256 colors).

Tip: When the colors in a GIF file represent classes, and when you obtained a raster map with a Picture domain from import, you can easily change the Picture domain to a Class domain in the properties of the raster map. After that you can edit the class names in the Domain Class/ID editor. For more information, see How to change the domain of a map (section on From a Picture domain to a Class domain).

Erdas-GIS:

Imports an Erdas .GIS file (thematic map). You can import any maps stored as 4, 8 or 16 bits per pixel. Coordinate information is retrieved from the Erdas .GIS file. Note: Information on class names and representation colors is retrieved from the trailer file (.TRL), if available. Both pre-version 7.4 and Erdas version 7.4 files can be imported.
The resulting raster map will have a georeference corners.

Erdas-LAN:

Imports an Erdas .LAN file (Remote Sensing Images). You can import any map stored as 4, 8 or 16 bits per pixel. Coordinate information is retrieved from the Erdas .LAN file. Both pre-version 7.4 and Erdas version 7.4 files can be imported.
The import results are a map list and a number of individual raster maps which will have a georeference corners.

IDA image:

Imports an IDA (Image Display and Analysis) image (.IMG).

Idrisi map:

Imports an Idrisi raster image. Select the .DOC file which accompanies the .IMG file. All required information will be extracted from the .DOC file. When a color file (.PAL) is found, this will be used to create a representation. You can import Idrisi byte maps, integer maps and real maps. When the Idrisi file contains classes, ILWIS will create a class map; otherwise an Image (for Idrisi byte maps) or a Value map (for Idrisi integer and real maps) will be created.

ILWIS ASCII raster:

Imports an ILWIS 1.x ASCII raster file (.ASC).

Paintbrush-PCX:

Imports a Paintbrush file (.PCX); the resulting map will not have coordinates.

TIFF:

Imports a Tag Image File Format file (.TIF). ILWIS can import:

• raster data with 1 bit per pixel: to a raster map with the Bit domain;
• raster data with 4 or 8 bits per pixel: to a raster map with the Image domain,
• raster data with 4 or 8 bits per pixel and a color lookup table: to a map with a Picture domain,
• raster data with 24 bits per pixel (RGB): to a raster map with the Color domain.

Tip: When the colors in a TIFF file represent classes, and when you obtained a raster map with a Picture domain from import, you can easily change the Picture domain to a Class domain in the properties dialog box of the raster map. After that you can edit the class names in the Domain Class/ID editor. For more information, see How to change the domain of a map (section on From a Picture domain to a Class domain).

ILWIS can import raster data from the TIFF file that is uncompressed, LZW-compressed (for 8 bits per pixel or more), or Packbits compressed (run-length encoded).

Furthermore, ILWIS can import GeoTiff information to create a georeference corners (1 or 2 tiepoints) or a georeference tiepoints (3 or more tiepoints). An empty coordinate system is created which contains textual information in its description: you have to edit the coordinate system yourself and specify projection parameters and datum, etc. as found in the description.

After it is checked whether the input file is a TIFF file, the TIFF file is scanned to find:

• the number of lines and columns,
• the number of bits per pixel,
• the number of values (may be different from the number of bits per pixel!),
• the availability of a color lookup table,
• the TIFF compression method,
• GeoTiff information.

Finally, the raster data is imported and decompressed if necessary.

Windows bitmap:

Imports a Microsoft Windows bitmap (.BMP). You can import any bitmap stored as 1, 4, 8, 16 or 24 bits per pixel. The resulting raster map will not have coordinates.

.MPA:

the object definition file for the polygon map; contains all properties. This file will be visible in the Catalog.

.MPAP#

contains coordinates of the bounding box around each polygon, polygon areas, length of polygon boundaries, polygon codes and references to the topology of the polygons.

.MPAT#

contains coordinates of polygon boundaries, coordinates of nodes, and topology information of the polygon map.

.MPS:

the object definition file for the segment map; contains all properties. This file will be visible in the Catalog.

.MPS#

contains coordinates of intermediate points, coordinates of nodes and segment codes.

.MPP:

the object definition file for the point map; contains all properties. This file will be visible in the Catalog.

.PT#

contains all point coordinates and the codes of the points.

Arc/Info .E00:

Imports an Arc/Info file in interchange format (.E00) into an ILWIS raster, a polygon map, a segment map and/or a point map.

When attributes are available, also one or more ILWIS tables will be created. When the .E00 file contains a table only, this table is imported with domain None.

The E00 import can handle compressed, partially compressed, and uncompressed files.

The conversion first scans the .E00 file to gather information, such as:

• Types of maps included in the .E00 file,
• Codes of segments (IDs), polygons (IDs) and points (labels),
• Value range for raster,
• Attribute tables,
• Map boundary.

Next, the E00 file is imported, taking into account a number of E00 tags. When the Arc/Info export split the data into several consecutive .E00 files (same file name, extensions .E00, E01, E02, etc.), ILWIS reads all data until the EOF tag is encountered.

Output:

When the .E00 file contains:

• a segment map only (ARC section only): ILWIS creates a segment map and a table which consists of a single column containing the original Arc/Info IDs;
• a segment map with attributes (.AAT): ILWIS creates a segment map and an attribute table where one column contains the original Arc/Info IDs, and where the other columns contain the attribute values;
• a point map only: ILWIS creates a point map and a table which consists of a single column containing the original Arc/Info IDs;
• a point map with attributes (.PAT): ILWIS creates a point map and an attribute table where one column contains the original Arc/Info IDs, and where the other columns contain the attribute values;
• a segment map and a point map; ILWIS creates a segment map and a point map and tables for the segment map and the point map with a single column containing the original Arc/Info IDs,
• a segment map, a point map and a polygon map (.PAL): a question is asked whether the user wants to obtain a polygon map or not.
• When this question is answered with No, ILWIS creates a segment map and a point map and tables with a single column containing the original Arc/Info IDs for the segment map and the point map;
• When this question is answered with Yes, ILWIS creates a polygon map using the ILWIS Segments to Polygons operation, a point map and a table with a single column containing the original Arc/Info IDs of the points. By using the Assign labels to polygons operation, the original label point IDs can be applied to the polygons.
• a segment map, a point map and a polygon map with point or polygon attributes (.PAL + .PAT): a question is asked whether the user wants to obtain a polygon map or not.
• When this question is answered with No: then ILWIS creates a segment map and a point map and tables with a single column containing the original Arc/Info IDs for the segment map and the point map;
• When this question is answered with Yes, then ILWIS creates (a) a polygon map using the ILWIS Polygonize operation, (b) a point map and (c) a table where one column contains the original Arc/Info IDs, and where the other columns contain the attribute values.
• a raster map (GRD section): ILWIS creates a raster map with a value domain.
• a table only: ILWIS creates a table with domain None.

The output map(s) usually obtain the same name as the input .E00 file. The same is also true for any class or ID domain; however when a domain with that name already exists, the domain name is slightly adjusted to be unique.

Limitations:

• Arc/Info IDs that are whole positive numbers up to 2 billion are supported.
• This version does not import possible coordinate system information contained in the .E00 file. Furthermore, some sections may be recognized but ignored (see E00 tags).
• Extracting attribute information for raster maps is not yet implemented.

Arc/Info .LIN, .PTS ASCII:

Imports files that were created with the Arc/Info ungenerate command (extension .LIN/.PTS). A .LIN file will be converted to a segment map; a .PTS file to a point map. The extension .GEN (generate) is also used by some systems.

LIN file: .LIN files are considered to contain segments (arcs in Arc/Info terminology); the output map will be a segment map. The segment map will obtain an ID domain and an attribute table will be linked to the map. The attribute table has a single column which contains the original segment codes. The column which contains the Arc/Info IDs is usually called mapname_ID. To obtain a segment map with these original codes, you will have to use the Attribute map of segment map operation after import.

The ILWIS map usually has the same name as the input file. The same is also true for its domain, unless there already is a domain carrying the envisioned name, in which case the domain name is slightly adjusted to be unique.

The attribute table will get a name based on the map name, making sure the table name is unique. The name of the attribute column will be mapname_ID.

PTS file: .PTS files are considered to contain points; the output map will be a point map. The output point map will obtain an ID domain and an attribute table will be linked to the map. The attribute table has a single column which contains the original point codes. The column which contains the Arc/Info IDs is usually called mapname_ID. To obtain a point map with these original codes, you will have to use the Attribute map of point map operation after import.

The ILWIS map usually has the same name as the input file. The same is also true for its domain, unless there already is a domain carrying the envisioned name, in which case the domain name is slightly adjusted to be unique.

The attribute table will get a name based on the map name, making sure the table name is unique. The name of the attribute column will be PtsValue.

Tip: To reconstruct a polygon map, see the remarks under the E00 import.

Arc/View Shape files .SHP:

Imports Arc/View Shape files to an ILWIS polygon and/or segment and/or point map. Furthermore, also possible attribute data will be imported into attribute tables. ILWIS expects to find three files to perform the conversion: filename.SHP, filename.SHX and filename.DBF files, such as for instance landuse.shp, landuse.shx and landuse.dbf. Newly created ILWIS attribute tables will be automatically linked to the maps to which they refer. New Shape types like Measure types (M-types) and Elevation types (Z-types) are recognized but the extra information in these file types is skipped.

Atlas .BNA:

Imports a file in Atlas/Map Edit format (.BNA).

Depending on the contents of the BNA file, you can obtain a polygon map and/or a segment map and/or a point map.

The output ILWIS map(s) and attribute table(s) will use an internally defined UniqueID domain; all columns in the attribute table will use the system String domain.

• You can convert the String columns in the attribute table to regular Class or ID columns via the Column Properties.
• You can change the domain of the table from a UniqueID domain to a regular Class or ID domain (containing point, segment or polygon codes) with the Change domain of table operation.
• You can obtain original codes of the point, segments or polygons in the output maps by performing an Attribute map operation on the output maps.
• You can check whether an attribute table is linked to a map through the properties of the map.

AutoCAD .DXF:

Imports vector files in AutoCAD Drawing eXchange Files (.DXF).

Depending on the contents of the DXF file, you can obtain a polygon map and/or a segment map and/or a point map.

First, the DXF file is scanned to find for instance information on:

• Segment codes
• Boundary
• Height information

Then, the domain is determined:

• When the codes contain numeric values only, and the difference between the minimum and maximum value is greater than 1, then a value domain will be created.
• Else, the number of classes is checked;
• When there is more than one class, a class domain will be created.
• Else, i.e. when all elements have the same code, the height information is checked:
• When the maximum height difference is more than 10 meters, a value domain will be created containing height values.
• Else, i.e. when no height information is available and all elements have the same non-numeric code, the domain will become a class domain with a single class.

Next, the DXF file is imported. The following DXF elements are recognized and imported:

• LWPOLYLINE (DXF14 or higher; imported as a polygon when closed, otherwise imported as a segment)
• POLYLINE (and thus VERTEX, including bulge; imported as a polygon when closed, otherwise imported as a segment)
• LINE (line segment with only two points)
• ARC (part of circle; imported as one segment)
• POINT (single point)

The codes of these DXF elements are used for the class names, values, etc. of the imported segments and points. In case of LWPOLYLINE and POLYLINE: the class name, value, etc. is taken to be the code of the LWPOLYLINE or POLYLINE, not of any VERTEX within.

When several LINE items follow each other, Import will check whether they are connecting. If this is the case, the lines will be combined into one single segment. Other elements (such as BLOCKS sections, INSERT entities and others) are ignored and skipped.

Tip: To import BLOCK sections, first Explode all the blocks to layer 0 in AutoCad.

GARtrip Text .TXT:

Imports a GARtrip file (.TXT) with GPS data. It is expected that the input file is created by using the Export option in GARtrip. GARtrip (http://www.gartrip.de) is PC shareware software for Garmin and Magellan GPS receivers.

• When the first line in the GARtrip file contains the word 'Waypoints', an ILWIS point map and an attribute table will be created.
• When the first line in the GARtrip file contains the word 'Track', an ILWIS point map and an attribute table will be created, and furthermore an ILWIS segment map will be created.
• When a UTM projection is used, also an ILWIS coordinate system (with UTM projection and WGS84 datum) will be created. When the UTM projection uses multiple zones, then all coordinates are automatically transformed to the first zone encountered in the file.
  If no UTM projection is used, ILWIS will use coordinate system Unknown.
  You may adapt the initially created coordinate system yourself after import.
• Optionally, height values in an Altitude 'Alt' column in the input file can be corrected by using the Height offset option in this Import Map dialog box:
• a positive value for the Height offset will increase the 'Altitude' values;
• a negative value for the Height offset will decrease the 'Altitude' values.

The output ILWIS point map and its attribute table will use an internally defined UniqueID domain; columns in the attribute table will either use system domain String or system domain Value.

An output ILWIS segment map will use a new ID domain.

ILWIS ASCII segments .SMT:

Imports an ILWIS 1.x ASCII file (.SMT) into an ILWIS segment map. If the first line is not 'Segments', an error message will be displayed.

SMT file structure:

1st line: Segments

Defines a segment map.

2nd line: min X min Y

Defines the minimum coordinate boundaries of the map.

3rd line: max X max Y

Defines the maximum coordinate boundaries of the map.

4th line: the class name, ID, or value of the first segment.

5th line and following:

Each line will contain an XY-coordinate of the segment until all coordinates of the segment are listed.

The next line states the class name, ID, or value of the second segment. And again, from the next line onward, all coordinates of the second segment will be listed. Example of an .SMT segment file.

To import an .SMT file which contains polygons, use Convert1.4 to import the file into ILWIS 1.4, then use Import to import the results into ILWIS 3.

Infocam Sequential .SEQ:

Imports an Infocam sequential file (.SEQ) to a point map and/or a segment map and/or a polygon map. The different types of vector maps that may be present in the .SEQ file are imported as different ILWIS maps. For each map, an attribute table is created in which information on the points, segments and polygons is stored. An Infocam object may have different attributes per element, thus the attribute table may be sparsely filled. The ILWIS maps will always obtain an ID domain; the IDs in the domain will be according to code information.

Limitations: Double polygon boundaries are not removed thus topology may not be correct. Furthermore, Spline or Arc information in a .SEQ file is not translated.