Appendices

File extensions

In ILWIS 2 and beyond, all ILWIS objects have an ASCII object definition file which refers to the object's data file, domain, store type, projection, georeference, representation (color, line width etc.), etc. Thus, object definition files may refer to further object definition files and to binary data files. The last character of the extension of a binary data file is mostly #. 

ILWIS file extensions:

.AT#

Binary data file for an annotation text object. Stores text strings, positions of text strings (XY-coordinate or RowCol numbers) and settings such as font name, font size, bold, italics, underline, justification, color, transparent and rotation for all text items. Always together with a .ATX file.

.ATX

Object definition file for an annotation text object. ASCII file. Always together with a .AT# file.

.CS#

Binary data file for a coordinate system tiepoints. Stores the tiepoints (X, Y, Xref, Yref, dX, and dY). Always together with a .CSY file.

.CSY

Object definition and data file for a coordinate system. ASCII file. Coordinate systems store the possible minimum and maximum XY-coordinates or LatLon-coordinates that can be used in point, segment, and polygon maps and in georeferences of raster maps. A coordinate system tiepoints also has a .CS# file.

.DOM

Object definition file for a domain. Stores the set of valid IDs, Class names or values for a data object. ASCII file. Domains of type Class, ID and Group also have a binary data file (.DM#).

A domain is used by one or more raster, polygon, segment and/or point maps, tables and/or columns in tables. A domain Class, Value, and Picture use a representation.

.DM!

Binary data file for an internal class, ID or group domain of a point map. If a point map has an internal domain, the object definition file of the point map (.MPP) contains a reference to this .DM! file. A .DM! file is comparable to a .DM# file.

.DM@

Binary data file for an internal class, ID or group domain of a polygon map. If a polygon map has an internal domain, the object definition file of the polygon map (.MPA) contains a reference to this .DM@ file. A .DM@ file is comparable to a .DM# file.

.DM#

Binary data file for a domain ID, Class, or Group. Always together with a .DOM file.

.DM$

Binary data file for an internal class, ID or group domain of a segment map. If a segment map has an internal domain, the object definition file of the segment map (.MPS) contains a reference to this .DM$ file. A .DM$ file is comparable to a .DM# file.

.DM%

Binary data file for an internal class, ID or group domain of a raster map. If a raster map has an internal domain, the object definition file of the raster map (.MPR) contains a reference to this .DM% file. A .DM% file is comparable to a .DM# file.

.FIL

Object definition file for filters which includes its ASCII data file. Standard filters are available in the \SYSTEM directory.

.FND

ASCII data file for functions. Always together with a .FUN file.

.FUN

Object definition file for functions. ASCII file. Always together with a .FND file. Standard functions are available in the \SYSTEM directory.

.GR#

Binary data file for a georeference tiepoints, a georef direct linear and a georef orthophoto. Stores the tiepoints (row, col, X, Y, drow, and dcol), uses a background raster map. Always together with a .GRF file.

.GRF

Object definition file for the georeference of raster maps. Stores the relation between rows and columns and real-world coordinates. ASCII file. A georeference tiepoints, a georef direct linear and a georef orthophoto, also have a .GR# file. A georeference can be used by one or more raster maps. A georeference uses a coordinate system; a georeference tiepoints also uses a background raster map on which tiepoints are positioned.

.GRH

Object definition file for a graph. Stores the table name(s) which contain the columns from which the graph was created and stores display options of the graph. ASCII file.

.HA#

Binary data file for a histogram of a polygon map. Always together with a .HSA file.

.HI#

Binary data file for a histogram of a raster map. Always together with a .HIS file.

.HIS

Object definition file for histograms of a raster map. ASCII file. Always together with a .HI# file. A histogram of a raster map belongs to the raster map with the same name.

.HP#

Binary data file for a histogram of a point map. Always together with a .HSP file.

.HS#

Binary data file for a histogram of a segment map. Always together with a .HSS file.

.HSA

Object definition file for histograms of a polygon map. ASCII file. Always together with a .HA# file. A histogram of a polygon map belongs to the polygon map with the same name.

.HSP

Object definition file for histograms of a point map. ASCII file. Always together with a .HP# file. A histogram of a point map belongs to the point map with the same name.

.HSS

Object definition file for histograms of a segment map. ASCII file. Always together with a .HS# file. A histogram of a segment map belongs to the segment map with the same name.

.ILO

Object definition file for layouts. Stores the name and location of the map view(s) that were inserted in the layout; stores the display settings of annotation (Legend, Map Border, North Arrow, Scale Bar, Scale Text, Text, Box) inserted in the layout, and; stores inserted Bitmaps and/or Pictures completely. When the layout does not contain bitmaps or pictures, this file is an ASCII file. When the layout does contain bitmaps or pictures, the file is partly binary.

.IOC

Object definition file for object collections and database collections. ASCII file. Stores the name and location of the object definition files that are included in this object collection.

.ISF

ILWIS Script File. ASCII data file for a script, containing the commands and expressions. Always together with a .ISL file.

.ISL

ILWIS Script Language. Object definition file for a script. ASCII file. Always together with a .ISF file.

.MAT

Object definition and data file for a matrix. ASCII file. A matrix is for instance produced by the operations Principle Components and Factor Analysis.

.MP#

Binary data file for a raster map. Stores the raw values of a raster map. Always together with an .MPR file.

.MPA

Object definition file for polygon maps (A for Area). Together with an .MPAP# and an .MPAT# file, unless a dependent polygon map was not calculated yet. A polygon map uses a domain and a coordinate system. Maps of domain Class, ID or Group can have an attribute table.

.MPAP#

Binary data file for polygon maps. Stores coordinates of the bounding box around each polygon, polygon areas, length of polygon boundaries, polygon codes and contains references to the topology of the polygons. Always together with an .MPA and an .MPAT# file.

.MPAT#

Binary data file for polygon maps. Stores coordinates of polygon boundaries, coordinates of nodes, and topology information of the polygon map. Always together with an .MPA and an .MPAP# file.

.MPL

Object definition and data file for map lists. Stores the names of raster maps in the map list. ASCII file. A map list thus has a reference to a number of raster maps, and to a georeference. If a variance-covariance or correlation matrix is calculated, then the values are stored in the .MPL.

.MPP

Object definition file for point maps. ASCII file. Together with a .PT# file, unless a dependent point map was not calculated yet. A point map uses a domain and a coordinate system. Maps of domain Class, ID or Group can have an attribute table.

.MPR

Object definition file for raster maps. ASCII file. Together with an .MP# file, unless a dependent raster map was not calculated yet. Optionally, also a file for the pyramid layers (.MPY#) may exist. A raster map uses a domain and a georeference. Maps of domain Class, ID or Group can have an attribute table.

.MPS

Object definition file for segment maps. ASCII file. Together with an .MPS# file, unless a dependent segment map was not calculated yet. A segment map uses a domain and a coordinate system. Maps of domain Class, ID or Group can have an attribute table.

.MPS#

Binary data file for segment maps. Stores coordinates of intermediate points, coordinates of nodes and segment codes. Always together with an .MPS file.

.MPV

Object definition file for map views. ASCII file. Stores the names and display options of the data and annotation layers that were saved as a map view.

.MPY#

Binary file for a raster map that has been stored with pyramid layers. Stores the raw values of a raster map at all possible zoom factors (factors of 2). Always together with an .MPR and an .MP# file.

.PT#

Binary data file for point maps. Stores all point coordinates and the codes of the points. Always together with an .MPP file.

.RP!

Binary data file for an internal representation class of a point map. When a point map has an internal representation, the object definition file of the point map (.MPP) contains a reference to this .RP! file. A .RP! file is comparable to a .PR# file.

.RP@

Binary data file for an internal representation class of a polygon map. When a polygon map has an internal representation, the object definition file of the polygon map (.MPP) contains a reference to this .RP@ file. A .RP@ file is comparable to a .PR# file.

.RP#

Binary data file for a representation belonging to a domain Class, Group, or Picture. Always together with a .RPR file.

.RP$

Binary data file for an internal representation class of a segment map. When a segment map has an internal representation, the object definition file of the segment map (.MPS) contains a reference to this .RP$ file. A .RP$ file is comparable to a .PR# file.

.RP%

Binary data file for an internal representation class of a raster map. When a raster map has an internal representation, the object definition file of the raster map (.MPR) contains a reference to this .RP% file. A .RP% file is comparable to a .PR# file.

.RP^

Binary data file for an internal representation class of a picture domain. When a picture domain has an internal representation, the object definition file of the domain (.DOM) contains a reference to this .RP^ file. A .RP^ file is comparable to a .PR# file.

.RPR

Object definition file for representation. Stores the representation of raster, polygon, segment or point maps: colors, line width, etc. ASCII file. A representation for a domain type Class, Group, or Picture also has a binary data file (.RP#). A representation uses a domain.

.SMC

Object definition file for criteria trees. ASCII file. Stores references to the name(s) of the output map(s), the names of all criteria, whether these are factors, constraints or a group, the names of all input maps, and the methods of standardization and weighing.

.SMS

Object definition file for sample sets. ASCII file. Stores references to a sample map with positions of training pixels, a map list and a background map.

.STP

Object definition file for a stereo pair. ASCII file. Contains references to two input raster maps, position of fiducial marks, principal points, transferred principal points, and optional scaling points. If the stereo pair is calculated, it also stores the names of the Left and Right output raster maps.

.T2#

Binary data file for a two-dimensional table. Always together with a .TA2 file.

.TA2

Object definition file for two-dimensional tables. ASCII file. Always together with a T2# file.

.TB#

Binary data file for a table. Always together with a .TBT file.

.TBT

Object definition file for tables. Stores attribute information belonging to raster, polygon, segment, and/or point maps. ASCII file. Together with a .TB# file, unless a dependent table was not calculated yet. A table uses a domain.

The following ILWIS 2 file extensions for vector maps can be read by ILWIS 3.x: .PC#, .PD#, .PL#, .PS#, .TP# (polygons), .CD#, .SC#, .SG# (segments), .PN# (points). However, these extensions are obsolete as soon as the ILWIS 2 vector map is edited in ILWIS 3.x. Furthermore, all ILWIS 1.4 file extensions are obsolete since ILWIS 3.x.

See also: