User Guide GeoDMS GUI

introduction

This guide focuses mainly on the user, who views the primary data, calculates model results, initiates new cases and makes limited extensions and edits to the configuration. A detailed description of the structure of the client application, the different viewers and the composers is, therefore, given. This user guide does not contain sufficient information for modelers to set up a new configuration or a new calculation scheme. For this purpose, we refer to the section How To Model, describing the basics on how to configure a model with the GeoDMS.

The GeoDMS GUI is a Windows-based application. This user guide does not describe the generic Windows functionality like how to close, maximize or minimize a window. For more information on these topics refer to your Windows user guide. An Internet connection and installed browser are preferred, as the most current help can be found on this wiki.

topics

• Desktop components
• TreeView
• Main menu
• Detail pages
• Map View
  • Layers
  • Tools
  • Legend
• Table View
• ValueInfo
• Eventlog
• Classification and Palette editor
• Export primary data
• GUI Options dialog
• Local machine Options dialog
• Config Options dialog

code analysis (clean-up support)

Configurations, especially for continuing projects with multiple contributors, tend to expand to a level that the overview on the whole configuration gets lost. Configuration parts are added, but less attention is given to removing unused parts of the configuration/source data, partly because it is not always clear which items/data are still 'in use'.

The GUI helps the user in finding out unused parts of the configuration/source data. From the TreeView pop-up menu or the main menu (Tools > Code analysis...) items can be set as:

• source (set source, Alt-K): to find out which other items are using this item.
• target (set target, Alt-B): to find out which other items are used to calculate this item. Additional targets can be added with add target (Alt-N); the selection is reset with clear target.

The items involved are indicated in the TreeView. The aim of this tooling is not to be a fully automatic clean-up procedure, as:

• there is no objective manner to find out if configuration parts/data are not useful anymore.
• cleaning up configuration files automatically would also mean reformatting, which we think can better be done by the modeller.

Furthermore, the Source Descr tab of the Detail pages can be used to find all data sources used for a certain result or container.