GeoDms 19.0.0

Compiled with Visual Studio 2026.

In this major release, all ambiguous syntax for points with 2 coordinates are obsolete, i.e. no longer supported.
In calculation rules, use either point_xy or point_yx In data blocks, use xy(...) or yx(...).

Furthermore, the internal object inheritance structure has been adapted, and the reference counting mechanism has been updated to better differentiate between unique ownership, and duplication of shared ownership that blocks the further non-concurrent mutability. DataView and GraphicObject are no longer (indirectly) derived from SharedObj and therefore don't have an unused and ambivalent m_RefCount member as their lifetime is managed by std::shared_ptr's

Refix of #976
Fixed #1058

Test results

https://geodms.nl/tests/reports/19_0_0___17_9_2.html Now also Hestia is included in the release testing, including performance results. Hestia will be green in these test results in a near future version after setting and checking reference results, See ObjectVision/GeoDMS-Test#16
See https://github.com/ObjectVision/GeoDMS/wiki/Full-test for context

Full Changelog: v18.2.2...v19.0.0.b

v18.2.2

Full Changelog: v18.1.3...v18.2.0
Full Changelog: v18.2.0...v18.2.1
Full Changelog: v18.2.1...v18.2.2

multi-byte utf8 characters in filenames are better supported now, see #1040

https://github.com/ObjectVision/GeoDMS/milestone/66?closed=1

Test results

https://geodms.nl/tests/reports/18_2_2___17_9_2.html
https://geodms.nl/tests/reports/18_2_1___17_9_2.html
See https://github.com/ObjectVision/GeoDMS/wiki/Full-test for context

GeoDms 18.1.3

backward compatibility issue:
Range Property no longer supported for 2D domains. Convert these to a calculation rule, such as: Range(point_xy(left, bottom), point_xy(right, top)) or Range(point_yx(bottom, left), point_yx(top, right)) to become independent from the ColRowOrder in config.ini, which is no longer read nor used.

Full Changelog: v18.1.2...v18.1.3

https://github.com/ObjectVision/GeoDMS/issues?q=is%3Aissue%20milestone%3Av18.1.3

Test results

https://geodms.nl/tests/reports/18_1_3___17_9_2.html
See https://github.com/ObjectVision/GeoDMS/wiki/Full-test for context

GeoDms 18.1.2

Fixes #976

And a bunch of mmd issues
Minor change: results of PropValue(x, 'DomainUnit') and PropValue(x, ,'ValuesUnit') now provide a specific relative path.

See also:
https://github.com/ObjectVision/GeoDMS/milestone/64?closed=1

and
Full Changelog: v18.1.0...v18.1.2

Test results

https://geodms.nl/tests/reports/18_1_2___17_9_2.html
See https://github.com/ObjectVision/GeoDMS/wiki/Full-test for context

GeoDms 18.1.1

New splash screen for v 18

Full Changelog: v18.1.0...v18.1.1

GeoDms 18.1.0

Example dms code included in setup

dms code is now installed in the subfolders example and library in the GeoDms program files folder, see #1017 and #1018.

After installation, you can open c:\Program Files\ObjectVision\GeoDms18.1.0\examples\grid_to_polygon.dms and double click on the item resulting_polygons:

Data formats

• added as known and managed GDAL drivers:
  • Arrow: Apache Arrow defines a language-independent columnar memory format for flat and nested data, organized for efficient analytic operations.
  • Parquet: an open-source, columnar storage file format designed for efficient data storage and fast analytical queries on large datasets.
• #991 support for PolygonZ features that GDAL 3.11.3 presents when reading polygon data formats with z-component support.

New functions

• #723 as_unique_list
• #1016 geos_buffer_point
• #757 geos_simplify_linestring

Fixed issues

• #993 less internal inconsistent use of case
• #996 added outer_single_polygon and outer_multi_polygon
• #939 removed renamed operators
  • EXEC -> EXEC_EC
  • FenceContainer -> PhaseContainer
  • subset -> select_with_org_rel
  • ...
• removed depreciated renamed composite results
  • select_with_org_rel
    • nr_OrgEntity -> org_rel
  • connect
    • nr_OrgEntity -> arc_rel
    • UnionData -> geometry
• #1000 fixed regression on the display of thousand separators
• #989 Deadlock
  minor fixes: #772, #774, #377, #1014, #1008, #1006,
  *MMD: #986, #1012

GUI

• #987, #994 URL in green in detail pages, Descr of Domain and Values units in green in detail pages

Python code

fixes in regression.py and profiler.py

Code documentation

• DiscrAlloc.cpp
• Dijkstra.cpp
• nth_element.cpp
• Potentiona.cpp and OperPot.cpp
• Poly2GridOper.cpp
• OperationContext.cpp

Code maintenance

• removed the usage of boost::mpl and replaced by C++23 facilities for type_list folding and application in ValueClassVisitors and UnitProcessors

Backward compatibility issue

• This release doesn't allow any ambiguous point data of point function syntax.
  In data blocks, use: [ xy(100000.0, 350000.0 ), ..] or [ yx(350000.0, 100000.0 ), ..]
  In calculation rules, use point_xy(100000.0, 350000.0 ) or point_yx(350000.0, 100000.0 )
• See #939

Added diagnostic

a diagnostic is added on a starvation situation, see #1021

Test results

https://geodms.nl/tests/reports/18_1_0___17_9_6.html
See https://github.com/ObjectVision/GeoDMS/wiki/Full-test for context

Full Changelog

See v18.0.0...v18.1.0

GeoDms 18.0.1

Fixes #991

Full Changelog: v18.0.0...v18.0.1

v17.9.8

Hotfix for #991: shape files with 2.5D polygons are now again read as 2D polygons.

Full Changelog: v17.9.7...v17.9.8

GeoDms 18.0.0

The 18.0.0 update provides a step into getting all string comparisons, including item identification case sensitive.
Each identified difference in case will now issue a warning in order to encourage modellers to be more aware and consistent in the usage of uppercase and lowercase usage. See also related issue #972.

Component upgrades:

• BOOST -> 1.88.0 (was 1.86.0)
• GDAL -> 3.11.3 (was 3.10.0)

Other Fixed issues: #621, #914, #927, #947, #978, #981, #982, #983,

Full Changelog: v17.9.7...v18.0.0

GeoDms 17.9.7

Fixes:

• #979 LayerControl appearance in MapView
• updated regression.py to support testing projects.

Full Changelog: v17.9.6...v17.9.7