| Problem | 2026-09-08 |
| Applies to | LASAT up to 3.5.7 |
|
Title |
Incomplete writing of very large DMN files with a binary
data section (typically DTBA files) |
| Beschreibung |
DMN files with a very large binary part (unpacked size greater than approximately 2.1 GB) may or will certainly (unpacked size greater than approximately 4.3 GB) be written out only incompletely, without an error message. This typically applies only to DTBA files (used to calculate percentiles and exceedance frequencies, e.g. dtba000.dmna) that were generated for many substances and many vertical layers (Nzd > 1 or not set in grid.def). These files cannot be read by LASAT-JAVA routines (such as Lopxtr and IBJdis) and they give an according error message. LASAT-C routines (such as Lopqtl) read them only partially and an error message is not necessarily given. The size of the binary file section is determined by the byte length of a data record and the ranges of the indices i, j, k, l (nx, ny, nz, number of substances nl). Example: For DTBA files and when using the option MAXIMA in param.def, the length of the data record is 224 bytes (2 times 28 floating-point numbers, each 4 bytes long; see the "size" entry in the file header). Therefore, nx*ny*nz*nl should be less than (2^31-1)/224 or approximately 9.5*10^6 to prevent an incomplete writing. For example, with 200 meshes each in the x and y directions and 20 materials, the number of output vertical intervals should be set to less than 12. |
| Workaround | If necessary, reduce the number of written vertical intervals (Nzd in grid.def; Nzd=1 is the default for files generated with AUSTAL and usually sufficient) or reduce the number of materials or meshes. |
| Resolved |
| Problem | 2026-01-14 |
| Applies to | Lopzet with nested grids |
|
Titel |
No modification of the set of nested grids with option -f |
| Description |
Lopzet reads the grid information from file grid.def and then attempts to read the concentration files for all these grids and the concentration value from the finest grid containing the monitor point. This mechanism may not be bypassed by specifying the name format (option -f). When using this option, it is important that the placeholders for the grid indices (and the time intervals) are retained in the format specification (as in the standard setting), for example -fcon%04da%d%d.dmna. Otherwise, Lopzet will become confused and assigns the grid indices for the monitor points incorrectly. |
| Workaround | Note this information. |
| Resolved |
| Problem | 2026-01-10 |
| Applies to | LTool AddIm 2.0.0 |
|
Titel |
Comment string |
| Description |
The optional comment that can be specified for the output file must not contain a comma, otherwise AddIm will get confused when counting the comma-separated parameters. |
| Workaround | Don't use a comma. |
| Resolved |
| Problem | 2025-08-14 |
| Applies to | LTool AddIm 2.0.0 |
|
Title |
Help text in the console |
| Description |
The help text in the console (option -h) states as parameter separator for call options a semicolon instead of the required comma. |
| Workaround | Use the program documentation in the reference book. |
| Resolved |
| Problem | 2020-07-31 |
| Applies to | GeoMapper / GeoOsm up to 1.0.0 |
|
Title |
Access to OSM server |
| Description |
The interface to the tile server of OpenStreetMap has changed in the first quarter of 2020. No tiles can be downloaded with the old interface. |
| Workaround | - |
| Resolved | 2020-01-28 (GeoOsm 1.0.2) |
| Problem | 2020-07-08 |
| Applies to | LTdefcheck up to 1.3.5 |
|
Title |
LTool DefCheck with meteo.def without time series |
| Description |
If no time series is defined in meteo.def, the LASAT tool DefCheck hangs on checking the project. |
| Workaround | Insert a short dummy time series, e.g. ! T1 T2 dummy Z -inf +inf 0 |
| Resolved | 2020-07-31 (LTdefcheck 1.3.6) |