stopping. Additional messages reporting the internal state of the application. DEBUG The log level for messages printed to the console window can be chosen from a drop-down list in the dialog [1]. The log will include all events of the indicated severity as Console well as events of greater severity (default: can be optionally enabled INFO). Word wrapping for long message texts that otherwise exceed the width of the console window. The log output in the is truncated after 10,000 log messages in order Note: console window to prevent high main memory consumption. If log messages shall additionally be stored in a log file, simply activate the option Write The log file is named per messages to log file. log_3dcitydb_impexp_<date>.log default, where is replaced with the current date at program startup. The <date> Importer/Exporter creates the log file if it does not exist. Otherwise, log messages are appended to the existing log file. The user can choose a location where to store the log file by enabling the option and by providing a corresponding path Use alternative path for log files [2]. Either enter the path manually or click on to open a file selection dialog. The log Browse level can be chosen independent from the console window through the corresponding list [2] (default: INFO). Log files are per default stored in the of the Note: home directory operating system user running the Importer/Exporter. Precisely, you will find the log files in the subfolder However, the location of the 3dcitydb/importer-exporter-3.0/log. home directory differs for different operating systems. Using environment variables, the location can be identified dynamically: (Windows 7 and higher) (UNIX/Linux, Mac $HOME/3dcitydb/importer-exporter-3.0/log OS families) Language selection The Importer/Exporter GUI has support for different languages. Use the Language preference dialog shown below to pick your favourite language. selection Figure 119: General preferences Language selection. –
stopping. DEBUG Additional messages reporting the internal state of the application. The log level for messages printed to the console window can be chosen from a drop-down list in the Console dialog [1]. The log will include all events of the indicated severity as well as events of greater severity (default: INFO). Word wrapping can be optionally enabled for long message texts that otherwise exceed the width of the console window. Note: The log output in the console window is truncated after 10,000 log messages in order to prevent high main memory consumption. If log messages shall additionally be stored in a log file, simply activate the option Write messages to log file. The log file is named log_3dcitydb_impexp_<date>.log per default, where <date> is replaced with the current date at program startup. The Importer/Exporter creates the log file if it does not exist. Otherwise, log messages are appended to the existing log file. The user can choose a location where to store the log file by enabling the option Use alternative path for log files and by providing a corresponding path [2]. Either enter the path manually or click on Browse to open a file selection dialog. The log level can be chosen independent from the console window through the corresponding list [2] (default: INFO). Note: Log files are per default stored in the home directory of the operating system user running the Importer/Exporter. Precisely, you will find the log files in the subfolder 3dcitydb/importer-exporter-3.0/log. However, the location of the home directory differs for different operating systems. Using environment variables, the location can be identified dynamically: (Windows 7 and higher) $HOME/3dcitydb/importer-exporter-3.0/log (UNIX/Linux, Mac OS families) Language selection The Importer/Exporter GUI has support for different languages. Use the Language selection preference dialog shown below to pick your favourite language. Figure 119: General preferences – Language selection.
3DCityDB_Documentation_v3.3.docx