v17.3.1

Further developments related to round-trip floating point representation and scanning, see #894
#775, #757: polygon operators *, +, &, |, -, ^are now implemented by geos_intersection, geos_union, geos_difference, and geos_symmetric_difference, as the geos versions of these boolean mapping operations have been found to be the most reliable and effective versions.

Full Changelog: v17.3.0...v17.3.1

v17.3.0

This minor release has:

• round-trip string representations for Float32, Float64,, FPoint, and DPoint values: #894
• fixed bg_union issues: #882, #857
• use the GEOS variants for binary polygon set operators: GEOS_Intersection, GEOS_Union, GEOS_Difference, GEOS_SymmetricDifference.
• improvement in the annotation of calculation rules with scoped sub-expressions: #905
  Full Changelog: v17.2.5...v17.3.0

GeoDms 17.2.5

Patch history:
17.2.5 fixed #897 jo #901 causing GeoDmsGui to exit early on Windows 10, introduced in v17.2.3 by Qt 6.9.0. Qt has been reverted to 6.8.2.
17.2.4 fixed #899 introduced in 17.2.2
17.2.3 fixed a dead-locks caused by the added lock for fixing #884; all locks are checked again for preserving a global ordering of mutexes.

What's Changed since 17.0.3:

Correct reading of OGR 3D point types by @eoudejans in PR #893, which implemented #656

FenceContainer improvements:

• allow for fencing inherited visible items, such as in Vesta and Hestia
• allow for Fencing unit as direct results.
• Fences in regression test and ActivateAll branch of Hestia now work (again)
• Fixed memory leaks in order to release all fenced intermediate results before calculating with fenced output.
  • in TravelTime calculations per Corop (FenceContainer), see #889
  • in TravelCost calculations per tariff-chain: ObjectVision/NetworkModel_PBL#37
  • in RSOpen ObjectVision/RSopen#230

Fixed issues:

• #883
• #850
• join_near_points improvements: #866 and #885 results are ordered now,
• unsynchronized thread communication caused the GUI thread to pick up new tasks only after a time-out when waiting for results: #884

Affine transformation determination is unified which resolves a mismatch between gdalwrite.grid and tif storage managers by @eoudejans in #886 which fixes writing TIF files with gdalwrite.grid that are dislocated when viewed in (other) GIS software.

Furthermore, the target platform is now Windows 10 (was: Windows 7 in 17.0.3)

Full Changelog: v17.0.3...v17.2.5

GeoDms 17.0.3

Prerelease for testing the effects on #854 and #884 of avoiding the notification of item destruction, see #883

Full Changelog: v17.0.1b...v17.0.2
Full Changelog: v17.0.2...v17.0.3

GeoDms 17.0.1

What's Changed

• new operator: join_near_points(A->P, B->P, Dist: Float64) -> ResultSet: unit< UInt32 > { ResultSet->first_rel; ResultSet->second_rel }, see #866
• get_x, get_y: #689
• Fix issue #878, added debug mode checkbox to GuiOptions window by @eoudejans in #881
• Adapted FenceContainer that has been seen to effectively separate fenced calculations in RSOpen and Network calculations, see #879, #877
• .MMD fixes: #870, #875
• race condition: #831
• improved diagnostics: #874, #878, #880

Full Changelog: v17.0.0...v17.0.1b

GeoDms 17.0.0

GeoDMS v17 has

• stricter diagnostics:
  • error on having an item with a calculation rule that is different than the one specified by a for_each instantiation, and also when an itemname occurs more than once in a for_each, with different calculation rules. see #812
  • inadequate number of values in a data value block, i.e. less than the domain of the attribute indicates, now results in a diagnostic errro.
• TableView can group-by on null values, see #848
• usage of FenceContainer
• .MMD

Different default storagetypes, see #847

• gdal.grid is now the default storage type for StorageNames ending with .tif. One has to configure StorageType = "tif", or StorageType = "gdalwrite.grid" if exporting to a new tif file is intended.
• gdal.vect is nwo the defaulkt storage type for StorageNames ending with .shp. One has to configure StorageType = "shp", or StorageType = "gdalwrite.vect" if exporting to a new tif file is intended.

Full Changelog: v16.0.5...v17.0.0

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