GeoDms 16.0.5

This patch

• fixes direct_index on attributes with UInt64, IPoint, or UPoint domains, used when sorting such attributes in the TableView.
• avoids Suspension (with S0) while executing posted main-thread operations, such as event-log processing
• fixes selecting cells in a raster with a compacted domain, related to #840 and #845.

Furthermore, interactions between worker threads and the main GUI thread have been streamlined to avoid starvation and deadlocks.

Full Changelog: v16.0.3...v16.0.5

GeoDms 16.0.3

The v16 major version

• has support for binary storing results into a memory mapped storage, a.k.a. .MMD, which is similar to a .FSS combined with schema information.
• no longer creates and renames .tmp version of files to be overwritten that only replace the original files when a project run or gui session completes. This avoids difficult to avoid issues related to the intermediate state of stored data and inconsistencies with the opaque GDAL. See #582 and #820.

Functional additions:

• poly2allgrids: #295
• discrete_alloc_np, discrete_alloc_sp
• #827: LayerControl: DubbelClick now only requests ValueInfo when Layer is Visisble and its control not greyed.

Fixes

• #840 (and #845)
• #831
• #832

Minor fixes:

• #824, #766, #808
• #817, #815, #763

Depreciated function, triggering warnings with provided replacements, which will become errors in a future release. See also #826:

• subset -> select_with_org_rel
• polgyon_inflate/deflate variants

Breaking changes compared to v15:

• an attribute with configured block data with less elements than the domain of the attribute now signals an error, as in most cased where this is seen, the intended assignment was indeed different.
• Indirect expression in Calculation rules and StorageNames now trigger a diagnostic error when they result in an attribute with a non-void domain (a.k.a parameter).
• exp and log now trigger a diagnostic error when its argument have a non-unitary metric. Arguments must be dimensionless.

Simplifications:

• #641 Tools/NrGroups in config.ini no longer determines the visibility of selection tools on the Toolbar in GeoDmsGui.exe

Known issue:

• we planned to make several functions depreciated (triggering warnings) in the 16 series and obsolete (triggering errors) in a later major release, including subset, to be replaced by select_with_org_rel. This depreciation has yet to be implemented in a later minor release. See also #826.

Full Changelog: v16.0.2...v15.10.2

GeoDms 15.10.2

Known issues: #838 and #841: consider using v16.0.3 or later, or v15.4.0 when aggregating values of an empty domain

This version contains the new functions poly2allgrids and poly2allgrids_uint64, see also #295.

Both require a polygon dataitem poly as first argument and integer point unit rasterDomain as second argument and they result in a unit<uint32> or unit<uint64> respectively, both with the follwing two sub-items:

• attribute<domain of poly> polygon_rel;
• attribute<rasterDomain> grid_rel;
  The polygon_rel is omitted when the domain of poly is void.

Full Changelog: v15.9.0...v15.10.2

Furthermore, the Nono Sans Medium Font used by Qt and DataViews, that was no longer loaded into the Windows GDI by Qt since version 6.8.0, is now loaded explicitly into the Windows GDI, see #814.

The 15.10.2 patch fixes a race condition issue found in 15.10.1 (withdrawn) with poly2allgrid (introduced in 15.10.0) when then number of polygon data tiles allows for parallel processing. Furthermore, it contains some diagnostic and progress reporting improvements.

GeoDms 15.9.0

This release has simpler versions of discrete_alloc that allows for allocating land use with claims that have the same partitioning:
discrete_alloc_np or no partitioning at all discrete_alloc_sp

Also, Qt is upgraded to 6.8.0
Known issue: #814, fixed in v15.10.1
Known issues: #838 and #841: consider using v16.0.2 or later, or v15.4.0 when aggregating values of an empty domain

GeoDms 15.8.0

Known issues: #838 and #841: consider using v16.0.2 or later, or v15.4.0 when aggregating values of an empty domain

Fixed issues related to progress messages

• #766, #769, #782, #802, #770, #536

polygon operation:

• #757, #775

Full Changelog: v15.7.1...v15.8.0

v15.7.1

Known issues: #838 and #841: consider using v16.0.2 or later, or v15.4.0 when aggregating values of an empty domain

GeoDms 15.7 offers many improvements and alternatives for polygon functions using the alternative libraries for boost polygon, prefix: bp_, which are:

• boost_geometry, prefix: bg_
• https://www.cgal.org/, prefix: cgal_
• https://libgeos.org/, prefix: geos_

See #757 for a compete list:

Polygon processing improvements:

• Accelerated bp_union_polygon and bg_union_polygon by reordering the associative union operations from sequential to a balanced tree collection.

GeoDms 15.7.1 has a fix for a new error related to #783

Since 15.5.0, all operations that were scheduled after scheduling operations required for the contents of a FenceContainer can only start once all the latter operation have completed. This is to be implemented in the RuimteScanner and Hestia in order to reduce memory usage due to too many started sub-tasks.

Known issue:

• bg_union_polygon seems to loose some rings, see #775
• other bg_ functions are still being tested, see #756 and #767

Polygon related issues:

• #604, #757, #768 #773, #756, #761, #778

Other performance issues:

• #684, #275

GUI issues (DataView)

• #762, #771

Diagnostics / Eventlog

• #763

Memory / FenceContainer issue

• #759 and #127: RuimteScanner implementation requires further investigation.

Fixed Crash

• #778

Full Changelog: v15.4.0...v15.7.1

v15.4.0

The 15.4.0 version introduces:

• binary operations for multi polygons with floating point coordinates, see #604
• faster summations and modus-like operations, see #275 and #684
• enhanced functionality: #742
• Fixed calculation bug: #741, #745, #751
• UX Fixes: #686, #688, #744, #750, #752
• Build optimization: #462
• Support for a Silent Instalation option: #747
  Full Changelog: v15.2.0...v15.4.0

v15.2.0

This pre-release contains changes to the use of the GDAL and PROJ libraries such that they are only loaded when GeoDMS actually uses any of their functions, aka delayed loading. This enables python users that had already loaded modules that linked to a different version of GDAL or PROJ, such as in GLOBIO, to use GeoDMS anyway.

Furthermore, GUI tweaks: #719, #733, #688

Fixed are: #731, #655, #710, #675, #110, #737

Full Changelog: v15.1.0...v15.2.0

v15.1.0

This upgrade of 15.0.x introduces a transpose function for the TableView.

New functionality:

• Implemented a Transpose function for TableViews, see #675

Fixes:

• fixes a slow down when requesting a calculation result from the GUI, #729

Furthermore, since pre-release 15.0.1:

• unintended consequences of fixing #669 have been reverted
• the implementation of the new operator split-multi_linestring has been completed and tested
• stricter enforcement of not using obsolete operators, as was intended to be part of the v15 changes, more specifically, select_data must be renamed to collect_by_cond, as part of our road-map to arrive at a consistent set of selection and collection related operator names.

GeoDms as Python 3.9 module:

• the geodms.pyd that is placed in the selected Program Files folder, has been tested with Python 3.9.18 installed from Conda, see also here

Full Changelog: v15.0.0b...v15.1.0

GeoDms 15.0.1

This patch fixes some issues with unintended rounding off point coordinates, introduced due to fixing #669 including clipping wpoint domains to no more than 32767 rows and columns, representing null_wp as 2^16-2, and similar artifacts.

Furthermore:

• the implementation of the new operator split-multi_linestring has been completed and tested
• stricter enforcement of not using obsolete operators, as was intended to be part of the v15 changes, more specifically, select_data must be renamed to collect_by_cond, as part of our road-map to arrive at a consistent set of selection and collection related operator names.
• the geodms.pyd that is placed in the selected Program Files folder, has been tested with Python 3.9.18 installed from Conda, see also here

Full Changelog: v15.0.0b...v15.0.1