Main window

Export

Select an object:

Select the ILWIS object which you want to export.

Export format:

Select the format to which you want to export.

Output file name:

Type a name for the output file.

Directories:

If necessary, change the current directory.

Drives:

If necessary, change the current drive.

Arc/Info ASCII:

Exports to Arc/Info non-compressed ASCII format (extension .ASC).

Erdas GIS:

Exports to Erdas .GIS format.

The Erdas-LAN and Erdas-GIS formats can only handle North-oriented maps.

The output consists of a .GIS file which contains the raster map, and, in case you exported a raster map with a class domain, a .TRL file which contains class and representation information.

Erdas LAN:

Exports a series of images in an ILWIS map list or a single raster map to the Erdas .LAN format.

The Erdas-LAN and Erdas-GIS formats can only handle North-oriented maps.

Furthermore, the Erdas-LAN format can only contain positive integers. This means that the ILWIS raster map(s) must use a class, ID domain or value domain; in case of a value domain, the values must be between 0 and (maximum) 32767, and the precision must be 1.

The output file contains a header (according to the Erdas .LAN format) with a description of the data that follows in the same file. In case you exported raster map with a class domain, also a trailer file (extension .TRL) will be written.

IDA image IMG:

Exports to IDA (Image Display and Analysis) image format (extension .IMG). IDA claims compatibility with the Terramar Micro-Image System. Image type and projection are set to 0, resp. generic and none.

Idrisi IMG/DOC:

Exports to Idrisi format (extensions .DOC, .IMG, and optionally .PAL)

The ILWIS raster map can have a class domain, an ID domain (only less than 32767 items allowed in Idrisi), the Image domain or a value domain. Furthermore, the ILWIS raster map must be north-oriented.

When exporting ILWIS value maps stored using 4 or 8 bytes per pixel, there is a possible loss of accuracy as Idrisi only supports floats (4 bytes per pixel).

The output consists of an Idrisi .DOC file which contains ASCII information on the map's store type, numbers of rows and columns, coordinates, etc., and a binary .IMG file which contains the actual map data.

When you export an ILWIS raster map with a class or ID domain, and the domain contains less than 255 items, then all class names or IDs are available in Idrisi as categories.

In case you export an ILWIS map with a class domain or a picture domain, also a file with color information (.PAL) is created. In Idrisi, this file must be translated into the internal Idrisi format with the palette workshop: read in as .PAL, and Save As .SMP.

ILWIS 1.4:

Exports to ILWIS 1.4 format (extensions .MPD, .MPI, and optionally .INF and .COL). Mind: ILWIS 1.4 map names may not be longer than 8 characters.

ILWIS ASCII:

Exports to ILWIS ASCII format (extension .ASC).

TIFF (GeoTiff):

Exports to Tagged Interchange File format (extension .TIF).

Any ILWIS raster map can be exported to TIFF format:

• When exporting a raster map with the Bit domain, the TIFF file is stored using 1 bit per pixel. Value 0 is represented by black and value 1 is represented by white.
• When exporting a raster map with a Bool domain, the TIFF file is stored using 8 bits per pixel. Colors will be available for True, False and Undefined values.
• When exporting a raster map with the Image domain, a picture domain, a class domain, an ID domain (with less than 256 IDs), or a value domain where the values are between 0 and 255 (and precision 1), i.e. when the ILWIS map is stored using 1 byte per pixel, then the TIFF file is stored using 8 bits per pixel and colors will be available for all values.
• For maps which use a Picture domain, colors in the TIFF file are taken from this Picture domain;
• For maps which use a Class domain, colors are taken from the representation Class that is currently linked to the class domain;
• For maps which use the Image domain, colors are taken from representation Gray;
• For maps which use use an ID domain, a number of primary colors are used;
• For maps which use a value domain, colors are taken from the representation value or gradual.
• When exporting raster maps with the Color domain, then the TIFF file is stored using 24 bits per pixel.
• When exporting raster maps which use an ID domain which contains more than 256 IDs, then the TIFF file is stored using 24 bits per pixel. For each value, a color will be created by first filling the Red plane from 0 to 255, then filling the Green plane from 0 to 255 and finally filling the Blue plane from 0 to 255. These colors may thus not correspond to the colors your ILWIS maps.
• When exporting raster maps which use a value domain where the values are not in the range between 0 and 255 and/or when the precision <> 1, i.e. ILWIS map is stored using 2, 4 or 8 bytes per pixel, then the TIFF file is stored using 24 bits per pixel. For each value, a color will be created.

Furthermore, information found in the raster map's georeference will be written into the regular GeoTiff tags, and information from the coordinate system will be written in string format in the GeoTiff citation tag.

The output file is an uncompressed TIFF file.

Windows Bitmap BMP:

Exports to Microsoft Windows bitmap format (extension .BMP). Any ILWIS raster map (domain Bit, Bool, Class, ID, Picture, Image, Value, Color) can be exported to a Windows bitmap. The procedure is similar to TIFF export.

Arc/Info E00 file:

Exports an ILWIS point, segment, or polygon map to an Arc/Info file in interchange format (extension .E00).

When exporting a point map, the output file will contain information on points (Arc/Info: Labels).

When exporting a segment map, the output file will contain information on segments (Arc/Info: Arcs).

When exporting a polygon map, the output file will contain information on segments and polygon label points.

Furthermore, the .E00 file will always contain a section with attribute information: .AAT for segments, .PAT both for polygons and points. This section lists for instance the class names, IDs, or values as used by the domain of the exported ILWIS map, and, in case the exported ILWIS map used an attribute table, also the attributes will appear.

When you export an ILWIS polygon map, the polygons will be transferred as segments and polygon labels. To recreate the polygons in Arc/Info, use the Arc/Info Build command after you have imported the .E00 file into a coverage. Attribute information will be retained.

Arc/Info ASCII vector LIN:

Exports an ILWIS segment map to an ASCII Arc/Info file (extension .LIN).

When the ILWIS segment codes are whole positive numbers, then these will be used as the IDs in Arc/Info. In other cases, a sequential number will be assigned to the individual segments. To obtain the lines in Arc/Info, you have to use the Generate command.

Arc/Info Generate PTS:

Exports an ILWIS point map to an ASCII Arc/Info file (extension .PTS).

To obtain the points in Arc/Info, you have to use the Generate command.

Arc/View Shape file SHP:

Exports an ILWIS point, segment or polygon map to files in Arc/View format (extensions .SHP, SHX, .DBF).

Atlas segments BNA:

Exports an ILWIS segment map to a file in Atlas/Mapedit format (extension .BNA).

The code of a segment is used to name a segment.

Also IDA (Image Display and Analysis) vector maps claims compatibility with the .BNA format.

AutoCad DXF:

Exports an ILWIS point, segment, or polygon map to a file in AutoCAD Drawing Exchange Format (extension .DXF).

The code of each segment is assigned to attribute 8.

ILWIS ASCII segments SMT:

Exports an ILWIS segment map to the ASCII ILWIS 1.x SegMenT-list format (extension .SMT).

The .SMT file lists for every segment, the segment's class names, IDs, or value and the segment's coordinates.

ILWIS version 1.4:

Exports an ILWIS 3 point or segment map to an ILWIS 1.4 point or segment map. For the output file name, you should type a new map name; there is no check whether the output map name already exists. Mind: ILWIS 1.4 map names may not be longer than 8 characters.

Extensions: .PNT for point tables and .SEG etc. for segments maps.

ILWIS version 2.x:

Exports an ILWIS 3 point, segment or polygon map to an ILWIS 2 point, segment or polygon map. For the output file name, you should type a new map name; there is no check whether the output map name already exists. Mind: ILWIS 2 map names may not be longer than 8 characters.

Infocam Sequential SEQ:

Exports an ILWIS point, segment and polygon maps to an Infocam separate SEQ files. Each vector file will be translated to one SEQ file. The values of the elements of the maps are retrieved from the domain. The coordinates of the elements of the map must be smaller than 1.000.000, because Infocam does not allow larger coordinates.

dBase III/IV table DBF:

Exports an ILWIS table or histogram to a dBase III/IV file (extension .DBF).

dBase SDF table:

Exports an ILWIS table or histogram to an ASCII dBase-SDF file (extension .SDF). This format is also known as Standard format, or Fixed format.

When exporting with Export 1.4; Enter width of columns: the number of characters for each column to define the length of a record is asked for.

Delimited Text TXT:

Exports an ILWIS table or histogram to an ASCII Comma Delimited file (extension .TXT).

ILWIS version 1.4 format:

Exports an ILWIS 3 table to ILWIS 1.4 format. Histograms cannot be exported. For the output file name, you should type a new table name; there is no check whether the output table name already exists. Mind: ILWIS 1.4 table names may not be longer than 8 characters.

ILWIS version 2.x format:

Exports an ILWIS 3 table to ILWIS 2 format. Histograms cannot be exported. This can be used to export tables which contain columns that use a coordinate system as domain. Mind: ILWIS 2 table names may not be longer than 8 characters.

ESRI ArcGIS .prj file:

Exports an ILWIS coordinate system projection or an ILWIS coordinate system latlon to an ESRI ArcGIS projection file (.PRJ). An ILWIS coordinate system should have an ellipsoid WGS 84 or an ellipsoid and a datum.