youtube-logo 34xtwitter-1-logo 34xgithub-logo 34x

ILWIS 3.7 now has the following vector applications:

PolygonMapBuffer
PolygonMapConvexHull
PolygonMapIntersect
PolygonMapDifference
PolygonMapSymetricDifference
PolygonMapRelate
PolygonMapUnion
SegmentMapVoronoi
SegmentMapTIN
SegmentMapDifference
SegmentMapSymetricDifference
SegmentMapUnion
SegmentMapIntersect
SegmentMapRelate
PointMapIntersect
PointMapDifference
PointMapSymetricDifference
PointMapUnion
PointMapRelation
PointMapPointInSegment

New Polygon Applications

PolygonMapBuffer

The buffer of a Point/Segment/Polygon at a distance r is the Polygon or MultiPolygon which contains all points within a distance d of the feature.


Syntax
PolygonMapBuffer(InputMap, BufferDistance,EndCapStyle);

The operation has three parameters:

Input map
Any polygon/point or segment map
Buffer distance
The distance of the points included. Positive and negative values are supported (dilation & erosion)
End cap style How the ends of lines are calculated

PolygonMapConvexHull

The convex hull of a Point/Segment/Polygon is the smallest convex Polygon that contains all the points in the Point/Segment/Polygon (collection).

Syntax
PolygonMapConvexHull(InputMap, isCombined)

Input map Any polygon/point or segment map
isCombined
Either create the convexhull over all the features or treat every element separately (which, in some case, might not make sense )



PolygonMapDifference

Calculates the difference between polygons in the two inputmaps. From Each polygon in the first input map the covering polygon(s) from the second input map, if any, is substracted.

(grey and orange lines are the boundaries of the original 2 polygons)

Syntax
PolygonMapDifference(Inputmap1, Inputmap2)

Inputmap1
PolygonMap
Inputmap2
PolygonMap

PolygonMapSymetricDifference

Calculates the symmetric difference between polygons in the two inputmaps. From Each polygon in the first input map the symmetric difference with any of the polygons from the secondmap is calculated

Syntax
PolygonMapSymetricDifference(Inputmap1, Inputmap2)

Inputmap1
PolygonMap
Inputmap2
PolygonMap

PolygonMapIntersect

Calculate the intersection of a polygon of the input map with polygons of the output map. The map will be associated with an attribute table that contains the values of the original maps in a certain polygon.


(grey and orange lines are the boundaries of the original 2 polygons)

Syntax
PolygonMapIntersect((Inputmap1, Inputmap2)

Inputmap1
PolygonMap
Inputmap2
PolygonMa

PolygonMapRelate

For each polygon in the first inputmap a Boolean test is done to each feature in the second output map to see if it holds true. If so, the polygon is included in the output map.

The following relations are implemented

Contains
returns true if this polygon contains the specified feature (excluding boundary).
CoveredBy
returns true if this polygon is covered by the specified feature.
Crosses returns true if this polygon crosses the specified feature. The features have some but not all interior points in common.
Disjoint returns true if this polygon is disjoint to the specified feature. The two features have no point in common.
Equals returns true if this polygon is equal to the specified feature. The two features have at least one point in common and no point of either feature lies in the exterior of the other feature.
Intersects returns true if this polygon intersects the specified feature. The two features have at least one point in common (intersect is the reverse of disjoint).
Overlaps

returns true if this polygon overlaps the specified feature. The features have some, but not all points in common. They have the same dimension and the intersection of the interiors of the two features has the same dimension as the features themselves.

Touches returns true if this polygon touches the specified geometry. The features have at least one point in common, but their interiors do not intersect.
Within returns true if this polygon is within the specified feature. Every point of this polygon is a point of the other feature and the interiors of the two features have at least one point in common.

Example for “contains”; only polygons that contain the pointmap (yellow dots) are shown.

Syntax
PolygonMapRelate(inputmap1, Inputmap2, relation, negation)

Inputmap1
PolygonMap
Inputmap2 Polygon/Segment or Pointmap
Relation See table above
Negation The relation can be negated to give the opposite result(“true”,”false”)

PolygonMapUnion

Merges polygons of the first input map with polygons of the second input map

New Segmentmap Applications

The set operations for segments are identical for segmentmaps: SegmentMapIntersect, SegmentMapDifference, SegmentMapSymetricDifference, SegmentMapUnion, SegmentMapRelate. The only difference is that the set operations for segmentmaps can use a polygonmap (if it is not a segmentmap) as second inputmap. In such a case, the operation works on the boundaries of the polygonmap.

SegmentMapVoronoi

From a pointmap, it creates the segmentmap that forms the Voronoi map in which all points on the segments have equal distance to the closest points. Note that the “areas” are not closed, because the boundary segment at the edge of the map would, in theory, go on forever.



Syntax
PolygonMapRelate(Input Pointmap, minimal distance)

Input pointmap
The input map used to calculate the voronoi boundaries.
Minimal distance The smallest distance which is used to calculate the boundaries. Points with a distance smaller than the minimum are not used in the calculation in relation to each other.



SegmentMapTIN

Creates an irregular triangulated network from a input pointmap. This is a ‘bare bones’ implementation of a TIN and only deals with the creation of the segment map. Optionally it can choose to use conves hulls for elements at the edge of the TIN to create a better area filling.



Syntax
SegmentMapTIN(Input pointmap, use Convex hull)

Input pointmap
The input map used to calculate the TIN
Use convex hull “True” or “False”. Determines if the TIN will cover the area defined by the convxhull of all the points in the input set.

New Pointmap Applications

The set operations for pointmaps are identical for segmentmaps: PointMapIntersect, PointMapDifference, PointMapMapSymetricDifference, PointMapMapUnion, PointMapMapRelate. The only difference is pointmap intersect accepts Pointmaps, Segmentmaps or Polygonmaps as input. It will use the intersection of segments and boundaries to determine the intersection points.

PointMapPointInSegment

A convenience application that determines a suitable point in a segment to determine its “middle”. This can be a real centroid, an existing vertex that is the best estimate or a point on of the edges that is closest to the centroid.

The three options in one map. Triangle=Centroid, Circle=Vertex, Diamond=MiddlePoint.

Syntax
PointMapPointInSegment(input segment map, option)

Input pointmap
The input segment map
Option The option can be “Centroid”,”Vertex” or “MiddlePoint”.




ILWIS 3.8 beta 2

This is the second beta version of ILWIS 3.8. There is no proper installer, just copy the ilwis folder from the zip to the desired location. The main focus of this version has been visualization and the bulk of the changes can be found there. There are, however, additional significant changes.The list below contains the bulk of them.

Changes for Ilwis 3.8 beta-2 with respect to beta-1

MapWindow

  • new tools
    • Hovmoller diagram
    • change coordinate system
    • color composite tool
    • map info tool
    • point editor (probably still needs some work)
    • segment editor (probably still needs some work)
  • other
    • full screen mode (menu : Options->Full Screen)
    • base maps (add layer form and context menu in catalog). This only works with maps that have proper coordinate systems (so no CoordSystem unknown).
    • optional decimal Lat/Lon on info bar.
    • copy clipboard

General

  • String translation system has been reworked to make it easier to translate ILWIS to other languages. ILWIS 3.8 will contain a spanish translation of the UI (almost finished).

Not yet finished

  • sample set editor
  • Stereo and Anaglyph
  • UI Clean up. This is partially done. There are still a number of items in the menu that do not work properly anymore, because their functionality has be subsumed in the layer view.

ILWIS 3.8 beta

This is the first beta release. There is no proper installer, just copy the ilwis folder from the zip to the desired location. The focus of this version is visualization.

Changes for Ilwis 3.8 beta-1

Mapwindow

  • No display options form anymore. Functionality has been subsumed in the Layer view
  • Leading spatial reference system for the view is the first layer added to the view. Rastermap georeferencing is now irrelevant. Everything is reprojected/resampled on the fly. Display of multiple raster maps with different georeferencing is possible as long as the coordinate systems are convertible.
  • Improved performance: OpenGL is the main graphics library
  • Greatly improved support for animations. Animations are now a normal layer in a mapwindow. All tools applicable to that type of layer should be applicable to the animations.
  • All views can also be displayed in 3D.
  • Almost all elements can be made transparent.
  • Increased interactive behaviour
  • Layer (tree) view has been substantially changed and extended.
  • The layer now contains a node called Display tools which contains all the "tools" (listed below) used in rendering a view.
  • The Display tools node has a right mouse button menu with which you can add/remove tools from the tools branch
  • Display tools is a general term used for all distinct modules that can manipulate a subset of properties of a view. For example there is a display tool that manages the transparency of items. Tools appear as separate nodes in the display tool branch. Some tools are "umbrella tools", they only function as organizational nodes as they have a number of other tools as children. Please note that on many nodes you may double click to open a form with properties of the tool.

Available tools

  • Transparency tool: transparency of feature, layers, line etc..
  • Grid tool: draws grid lines at fixed distances
  • Gratticule tool: draws gratticule lines of the lat/lon system
  • 3D tool (global): switches the perspective to 3D
  • Attribute table tool: attribute data source for features/pixels
  • Color tool: contains fixed color tool and representation tool
    • fixed color tool: single color or multiple colors for class/id domains
    • representation tool: setting of the current representation
  • Legend tool: shows the distribution of values in the range for the specific domain (class/ value). Class items may be switched on/off individually.
  • Boundary tool: switches the boundaries on/off in polygon layers
  • Area tool: switches the filled areas on/off in polygon layers
  • Stretch tool: interactive stretching for value maps
  • 3D Properties tool: Umbrella tool for some 3D tools
    • Data Source tool: any numeric source can be used for the z-values in a map. This is traditionally a dtm, but ILWIS accepts any source.
    • Scaling: the z - exaggeration and z - offset in z images
    • Extrusion: a downward extension of a feature to make its location on the ground level clearer
  • Interactive Representation tool: interactively makes value representations (can also be used for interactive slicing)
  • Annotations: Umbrella tool for the annotation tools. Currently only one child tool present, others will follow.
    • Annotation Legend: "On Map" legend
  • 3D Stack (global): In 3D view it will layer the layers with fixed distances.
    • 3D Cursor: In 3D view it will draw a line from the selected location to the ground level, intersecting with all layers.
  • Line Style tool: properties of lines
  • Point Symbolization tool: Symbolization of points
  • Point Scaling tool: point size scaling with attributes
  • Track Profile tool: profile of a drawn track on the map. Can have multiple legs and multiple sources. For both value and class domains
  • Cross Section tool: all the values of one or more map lists on one or more locations in a graph
  • Distance Measures tool: the length of a line of one or more legs on the map
  • Run tool (animation layer only): speed and synchronization of animations
  • Time Selection (animation only): Which frames will be included in the animation
  • Area of Interest Selection (animation only)
  • Feature Tracking tool (animation only): tracks features over time in a object collection
  • Layer info table (old pixel info) available in the view.
  • Point symbols are svg-like (tiny subset) xml files that can be added, changed etc. (located in resources\symbols)

Applications

  • Change detection
  • Aggregate map list
  • Create time column (not a true application)
  • PolygonMapListTracking


Help files: now available as true HTML in the browser and can be located in the installation folder of ILWIS.
Operation List: (not tree) in the main window now has a finder edit box.
Domain Time: ILWIS now supports Time as a domain (Date + Time) as defined by ISO 8601.
Command Zip: makes a zip file of an ILWIS file plus all the support files it needs.


ILWIS 3.7.2

This release contains a number of important bug fixes for ILWIS 3.7.1:

  • fixed import shape files bug
  • fixed a number of related point map bugs which caused a shift of one record in the point table:
    • Table to PointMap
    • some statistical methods using pointmaps
  • improved the legend of the mapwindow for value maps
  • corrected parsing of the sinusoidal projection
  • corrected incorrect deletion of members of a maplist
  • created a new application to solve some of the issues with MapListStatistics called MapListAggregate
  • created a more robust way of opening polygon files with corrupt polygons
  • solved some issues when importing raster maplists

ILWIS 3.7.1

New applications include:

  • PolygonMapSliverRemoval: removes small polygons with an area below a certain threshold (percentage wise or absolute number)
  • PointMapCross: combines a pointmap with a maplist by adding the values of the maps in the list at a point's coordinate as columns to the pointmap's attribute table
  • French translation of the ILWIS user interface (not including help files): available through the preference form (use extension .fr)
  • Bug fixes

ILWIS 3.7

New vector operations include:

PolygonMapBuffer
PolygonMapConvexHull
PolygonMapIntersect
PolygonMapDifference
PolygonMapSymetricDifference
PolygonMapRelate
PolygonMapUnion
SegmentMapVoronoi
SegmentMapTIN
SegmentMapDifference
SegmentMapSymetricDifference
SegmentMapUnion
SegmentMapIntersect
SegmentMapRelate
PointMapIntersect
PointMapDifference
PointMapSymetricDifference
PointMapUnion
PointMapRelation
PointMapPointInSegment

other changes:

  • The data format for polygon files has been changed and is not compatible with ILWIS 3.6. ILWIS 3.7 will read the ILWIS 3.0 data format for polygon files but only save to the new format.
  • The ILWIS 2.0 data format for vectors is no longer supported.
  • Some operations that disappeared in 3.6 are back in 3.7 (e.g. some matrix operations).
  • WMS locations in the navigator remain after closing the application.
  • Customization of the operations menu/tree is (limited) possible.
  • About form has been significantly changed.
  • A number of bugs have been solved.

ILWIS 3.6.1

WMS

  • Inherited spatial reference systems from top layers in a WMS now handled correctly
  • WMS Catalog(Ilwis object) works properly

Import

  • Output pathing for the imported file fixed
  • Shape file import works properly
  • Dxf file import works properly

Export

  • GeoTif export rewritten. It is less rigid in what it exports and stays truer to its original content
  • SEBS Operations menu corrected

Batch Command line processing

  • ILWIS as a client should not interfere anymore with running batch command scripts (multi threading problemn is fixed)

ILWIS 3.6

New features are:

  • Inclusion of GDAL in much the same way as Geogateway once was included. Non ILWIS raster data can be used natively in ILWIS. This is a big improvement with respect to the previous support of GDAL.
  • Postgres tables and Postgis point and segment maps can be accessed natively from a Postgis database. A first implementation has ben made to access these sources of data.
  • User interface for Import has been improved to support a plug-in model for imports.
  • Imports now largely follow a plug-in model (some old ones excepted). New imports can be added without changing ILWIS.
  • The plug-in model has been extended to cover plug-in,s stored in zip files, that need their own folder structure to organize their functionality.
  • Surface Energy Balancing (SEBS) has been extended and improved.
  • Improved installation program
  • Bug fixes

ILWIS 3.5.2

The following functions and parameters now work properly:

  • the interactive color composite,
  • the parameters %r, %k, and some other '%' parameters,
  • the MapIter parameters.

ILWIS 3.5.1

The following bugs were fixed:

  • the expression errors is now properly communicated,
  • the MapIterProp has been reintroduced (was ommitted during the original conversion of the applications to a plugin model),
  • the SimpleCalc has been reintroduced (was ommitted during the original conversion of the applications to a plugin model),
  • the History works properly again.

ILWIS 3.5 extends the functionality offered by ILWIS Open 3.4. New user features include:

  • ILWIS as an OGC compliant WMS client. It can now process GetCapabilities requests and make the WMS layers (or combinations of them) available as raster maps in ILWIS (domain color). These can be combined with any local data.
  • Surface energy balances with preprocssing functionality (SEBS). ILWIS is now able to produce Surface Energy Balance maps and carry out the chain of preprocssing to create the products needed for processing.

New developer features include:

  • ILWIS is now a MS Visual 2008 project.
  • ILWIS applications and applications user interface now form a plug-in system. One can extend ILWIS applications without changing anything to ILWIS.
  • ILWIS user interface and ILWIS analytical functionality have now been completely seperated making it easier to write server side applications for ILWIS.

ILWIS 3.8.5

ILWIS 3.8.5 contains several new features and a number of bug fixes.

The following features were added:

  • Map Window selections: added the option to select polygons (previously only points and segments could be selected)
  • Ellipsoidal Plate Carree coordinate system added
  • Table Join operation: added the missing option to join a column of type Coord, making it possible to e.g. join the coordinates of a pointmap to its attribute table
  • Space Time Cube: added the 3D windrose option; added XT, XY, YT lines
  • Applications: added Parallax Correction of clouds for MSG images (under Image Processing), and Probability Density raster generation (frmprobabilitydensity)

Bug fixes:

  • Improved compatibility on computers with Intel HD Graphics or combo-graphics hardware (potential crashes when opening a Map Window). Therefore the "Software Rendering" option in the ILWIS Preferences can be disabled for those who enabled it as a workaround.
  • Restored Epipolar Stereopair functionality (both creation and viewing in the stereoscope window)
  • Restored Import->ILWIS->TIFF functionality (message DATUM.DEF was not found)
  • Improved stability and usability in the Import functionality for both maps and tables, and recognition of more projections (all Import methods, including ILWIS, GDAL and PostgreSQL)
  • Improved stability in the Export functionality (both ILWIS and GDAL)
  • Calling external commands works again (message Exit Code 1)
  • Restored rectangle-based Zoom-Out functionality
  • Restored No-Zoom option for raster images that maps each raster pixel to an on-screen pixel. Use the "Global Tools->Geometry->GeoReference" tool and select the georeference that corresponds to the raster image, in order to display it unprojected.
  • Improved table Window summary statistics for boolean columns and for selected records
  • Improved interactive slicing application
  • Solved the problem whereby the Representation Editor showed a wrong color ramp in the preview
  • Solved potential crashes and wrong results in the vector operations Union and Intersect
  • Solved "vector<T> too long" error when opening corrupted polygon maps
  • Improved per-class hatching and transparency for polygon layers
  • Solved potential crashes when opening "Use As" data
  • Color Composite: the application now creates 24 bits files when this option is selected (previously it was always 8 bits)
  • MapGlue: gluing large images is now possible
  • Open Street Map: corrected the zoom level making the labels readable, and solved potential deadlocks and crashes. Known issue: OSM may not show in 3D-view, depending on the viewing angle.
  • DEM Hydro-Processing functions: solved potential "vector <T> too long" and "Find Error" problems, and the menu is now arranged in the recommended workflow order.
  • Maplist Statistics: solved the "Encountered an improper argument" error so it works again
  • Solved inconsistent behavior in iff statement when one of the parameters is undef (?): iff (a,b,?) is now the same as iff (not a,?,b)
  • Solved crashes or empty results in copying a map to the clipboard when using WMS and Open Street Map, or when using Software Rendering
  • Solved crashes and inconsistent behavior in the Cross Section, Hovmoeller and Track Profile tools
  • Solved many random crashes in ILWIS

ILWIS 3.8.4

ILWIS 3.8.4 contains a number of bug fixes, as well as a few new features.

Bug fixes include:

  • improvements in the SEBS application set
  • improvements to real time animations
  • improvements in the SMCE application
  • improved copying of unicode string to clipboard
  • removal of 2 GB limit on rasters
  • improved recognition of projections from the gdal driver
  • export using gdal works properly again
  • solved several issues with the creation of coordinate systems
  • missing edit fields on the script window (parameter tab) are accessible
  • segment maps with real values as segment value are now stored correctly
  • .smc files are now copied correctly
  • use-as original source data is not deleted when a delete command is done on the ILWIS-proxy
  • Due to some licensing issues, the triangulation code used to draw polygons was replaced.

The following new features were added:

  • a break dependency option to dependent georefs (e.g. submap), for proper exporting georeferenced data
  • support for opening/storing data from Postgres/Postgis databases
  • new application PointMapCross
  • new application MapColorFromRpr
  • experimental WFS support (through import form --> OGC option)
  • variable DPI option when copying mapwindow to clipboard
  • copy coordinate value under the mouse through the right mouse menu
  • synchronization between space-time cube and animated mapwindow
  • PCP (Parralel Coordinate Plot), accessible through the display options of a point layer
  • time profile graph for space-time cube
  • Script : Colored hill shade from a DEM

ILWIS 3.8.3

ILWIS 3.8.3 contains a number of bug fixes, as well as a few new features.

Bug fixes include:

  • local mapwindow histogram functions again
  • legend in layer tree updates properly when stretch ranges change
  • map window legend updates properly when stretch ranges change
  • views work again, however the (new) view system is not backward compatible with the earlier version
  • legend remains at the same place when legend property form is opened
  • copy view works properly again, all relevant files are also copied
  • resolved conflicts between point properties by rpr and global point properties
  • resolved conflicts between line properties by rpr and global line properties
  • re-enabled stretching for attribute maps
  • resolved raster visualization problems on low-end Intel on board graphic chip. An option in the preferences now to switch to software-based OpenGL. Although it is slower, it doesn't have the Intel chips' OpenGL problems.
  • proper animation information update to mapwindow
  • solved synchronization rounding bug when synchronizing animations with different index resolutions
  • solved several issues in the interactive representation
  • correct sorting of the columns druing table selections
  • ILWIS skips corrupt polygons when reading data

New features:

  • header information is added to csv/ssv files when importing
  • layer tree now has user defined step and ranges in addition to the auto mode
  • map window legend allows user defined step and ranges in addition to the auto mode
  • legend background (if enabled) incorporates title
  • new Zoom to feature(s) - now it is possible to zoom to selected features in feature maps
  • rpr properties changes in mapwindow are partially copied
  • a track can now be saved as a segment map and tracks can also be loaded as segment map for getting identical tracks on different maps
  • labels added (again) for points and polygons

ILWIS 3.8.2

ILWIS 3.8.2 introduces a few new features and improvements.

New features include:

  • extended selection options for vector maps and attribute tables
  • ID/Unique ID maps may have their own color scheme when rendering
  • new IsoCluster application

Improvements:

  • improved import shape file multi shapes
  • removal of import errors about coordinate system
  • improved focus of drawer tools status: active/inactive
  • corrected storage of user options for point symbolization
  • improved map view save function
  • largely increased performance for clean up/close large vector maps
  • increased performance for displaying vector maps with attributes
  • removed several 3D grid issues
  • fixed 3D panning

ILWIS 3.8.1

ILWIS 3.8.1 has a few new features for ILWIS 3.8, as well as a number of bug fixes.

New features include

  • access to OpenStreetMap (Internet access required) - add OSM layer to ILWIS layer
  • hatching for polygons,
  • Space Time Cube - tool for 3D analysis of spatial, temporal events,
  • coupling of attribute table selection and map selection - selection of attribute table rows also selects corresponding feature,
  • batch import (use wild cards in import names).

Problems solved

  • fixed various bugs when importing any vector file (including shape files),
  • improved handling of WMS servers,
  • resolved bug when importing raster file (crashed when opening the file, but was fine when ILWIS was reopened),
  • resolved bug when two display tools where trying to capture the mouse at the same time,
  • removed layers from the pixel info when the layer is removed from the layer tree,
  • dates are now correctly read in the date form.

more information...


ILWIS 3.8

ILWIS 3.8 represents a major upgrade from ILWIS 3.7. Changes and improvements have mainly focussed on visualization, however, additional issues have been addressed.

Changes in ILWIS 3.8

Visualization

General

  • Display options form has been replaced by an extended and improved Layer tree on the left side of the map window.
  • Pixel info has a permanent location on the lower left side of the map window.
  • The map window has a command line which works the same as the main window’s command line. Maps calculated in this command line are automatically added to the map window.
  • Map window menus have been substantially reduced. Much of their functionality has been moved to the Layer tree.
  • LatLon maps can show their coordinates as decimal coordinates. This toggle can be found in the Options/Metric Coordinates menu.
  • Visualizations can be shown full screen without any UI elements. This toggle can be found in the Options/Full Screen menu.
  • Automatic reprojection and resampling is available. The map window can display maps of different geometries (both raster and vector) and will automatically morph the maps to a target geometry. The geometry of the map can be changed on-the-fly.
  • Annotation is available in the map window for legends (per layer), boundaries and scale bar.
  • The tree node "Display Tools" has a context menu that controls the visibility of tools.
  • Base maps have been added to the system folder. This (small) set of maps can be used as background/context layers. Each base map acts as a system object.
  • Map backgrounds and surroundings can be changed with respect to color and transparency.
  • The distance measurer can be used on paths (multiple line segments) with the help of the the ctrl button.

Layer tree

  • The previous layer tree has been massively extended. It now replaces part of the main menu. "Tools" that control a coherent subset of visualization properties are available at all levels of the tree. They can be global or have effect on only one layer.

2D maps

  • Raster maps
    • Enhanced performance
    • Interactive representation value creation
  • Polygon maps
    • Enhanced performace. The first time a polygon map is shown it generates a support file (triangulation) which it uses subsequently.
    • Boundaries and Areas are separate entities with separate properties.
  • Segment maps
    • Enhanced performance. All vector maps now use a spatial indexing scheme to quickly retrieve the relation between a coordinate and its features. This speeds up the retrieval of segment values at a particular location.
  • Point maps
    • Symbolization has been completely changed. There is now one consistent system that uses small "svg-like" text files to define the symbolization.
  • Object collections
    • An object collection of maps of the same type and domain can function as a single layer. As a result, all maps are stretched in the same way.
  • Map lists
    • Dedicated tools for map lists. Apart from animations, a set of dedicated tools has been implemented specifically for map lists.
    • Cross section. A graph can be displayed for a point location. It shows all the values of the map list for that point. Multiple points can be defined with the help of the ctrl button.
    • Hovmoeller diagram. A pattern detection representation of lines drawn on a map can be combined with a map list to produce a Hovmoeller diagram.
  • Tools
    • Track profile. This displays a profile graph of a path on the map. A multi-segment path can be created with the help of the ctrl button. Multiple maps can be added to the profile graph to demonstrate relationships between the profiles of these maps.
    • Transparency. This can be added at many levels and mostly on-the-fly. Transparency follows a 0 (no transparency) to 100 (fully transparent) scale. It can be applied to the following objects/properties:
      • Layers: raster, polygon, segment, point
      • Areas and/or boundaries of polygons
      • Lines of grid
      • Extrusions (3D)
      • partial transparent interactive representation ???
      • Selections of polygon maps based on class
      • Selections of raster maps based on numerical value
    • Interactive value stretching. Dymamically adapts stretch values based on a set of sliders (min,max).
    • Attribute tool. The display attribute (column) can be changed on the fly.
    • Layer applications. All applications relevant for a certain layer type can be started from the Layer tree. Any maps produced here are immediately added to the map window.
    • Point editor and segment editor. These tools have been rewritten and are now part of the Layer tree.

3D Maps

  • All layers can be shown in 3D via a simple toggle.
  • Z coordinates can be any numerical value source; e.g. raster maps, attribute columns.
  • Rotation can be carried out by pressing the ctrl button and the left mouse button simultaneously, zooming via ctrl button and the mouse wheel, and panning with the ctrl button and the right mouse button.
  • All 3D properties are controlled by the 3D properties tool which is activated by the context menu of the display options node.
  • 3D grid creation is possible.
  • Tools
    • 3D properties. Controls Z-data source, scaling and offsets and the use of extrusions (and properties).

Animations (formerly slide show)

  • Animations can be made from map lists (raster) or object collections (vector).
  • Animations function as a normal layer in the map window. Tools applicable for single layers, work for animations.
  • Animations work in 3D
  • Multiple Animations can run in one or more map windows (however, there may be performance issues).
  • Animations may use index information or real time information. Real time information is derived from a time column in a map list's attribute table.
  • Several animations may be synschronized according to index information or real time.
  • Animations can be saved as .avi files.
  • Tools
    • Highlight tool. Singles out a selection on the map to highlight during animation
    • Threshold tool. Changes display colors of pixels above and/or below a certain threshold based on an attribute table. This tool can be accessed from the animation management form.


New applications

  • MapListCondense: Condenses a map list into a smaller map list, i.e. aggregates maps into one map according to a step size and specific aggregation rules.
  • MapListExpand: Expands the map list and creates intermediate maps based on certain interpolation rules, i.e. the reverse of MapListCondense.
  • MapListChangeDetection: Makes use of a number of simple change detection schemes to determine changes in map lists.
  • MapAggregateMaplist: Aggregates a map list in a single map based on certain aggregation rules.
  • TableAttributeFromMapList: Creates an attribute table for a map list based on aggregated numbers from maps in a map list
  • ColumnAttributeFromMapList: Creates an attribute column for a map list based on aggregated numbers from maps in an existing map list table
  • TableCreateTimeColumn: Creates a time column in a table. The time column is derived from a map list based on a (user-defined) pattern in the name of the map list.


General

  • Map list and Object collection can have an attribute table. Each record matches the corresponding index in the list/collection.
  • The Operation list has been extended to include a "finder" which filters the list.
  • A Spanish UI translation has been included.
  • The help system has been decompiled and now uses html files instead of the bundled (chm) format.
  • The domain "time" has been included. This handles date/time information based on an ISO standard.
  • ILWIS now has a server component that can run as an (ILWIS-specific) application server. A WPS server has been implemented.

Change log archive...

ILWIS 3.8 represents a major upgrade from ILWIS 3.7. The main focus has been on visualization though some other issues have also been addressed. Please download the ILWIS 3.8 Visualization Reference Document.

New applications

  • MapListCondense : condenses a maplist into a smaller maplist. Aggregating maps into one map according to a step size and aggregation rules
  • MapListExpand : reverse of MapListCondense. Expands the maplist and creates intermediate maps based on certain interpolation rules
  • MapListChangeDetection : A number of simple change detection schemes to determine changes in maplists
  • MapAggregateMaplist : Aggregates a maplist in a single map based on some aggregation rules.
  • TableAttributeFromMapList : Creates aggregation numbers for maps in a maplist in a table that can be used as maplist
  • ColumnAttributeFromMapList : Same as previous but for existing tables
  • TableCreateTimeColumn : Creates a time column in a table from a maplist based on a (user-defined) pattern in the name of the maplist

Applications in ILWIS 3.7

Geospatial Sensor Webs Conference 2017

Upcoming Events

Affiliations

The 52° North affiliations:

OGC logo

Cooperation Partners

The 52°North principal cooperation partners

IfGI Logo con terra logo
esri Logo ITC logo