Skip to content

Releases: ObjectVision/GeoDMS

GeoDms 8.6.1

07 Dec 10:08
Compare
Choose a tag to compare

8.6.1 brings two significant performance improvements over 8.6.0:

  • better management of data-tiles of intermediate resuls with /S3, avoiding repeated calculations, issue 329
  • faster unique sequence implementation eantis see mantis issue 194

Furthermore, it contains a clean-up of the Generic Detail Page, see mantis issue 322

GeoDms 8.6.0

30 Nov 20:35
Compare
Choose a tag to compare

This release extends two families of functions:

  • select_many(container, condition); select_afew(container, condition) result in tables with all container's attributes with the same domain as condition taken by select_data (seldomain, condition, attr) respectively lookup(org_rel, attr) to support table selection with either a dense or a sparse representation of the selection condition. see PblTrello#69
  • certain_argmin, certain_argmax, known_argmin, known_argmax with optional suffices _uint16 and _uint8 that result in null if any respectively all given values are null, and similarly certain_max_elem, certain_min_elem, known_max_elem, and known_min_elem that result in null if any respectively all given values are null. Note that from v8.6.4 these functions have been renamed to:
    • certain_arg[min|max][|_uint8|_uint16] -> arg[min|max]_alldefined[|_uint8|_uint16]
    • known_arg[min|max][|_uint8|_uint16] -> arg[min|max]_ifdefined[|_uint8|_uint16]
    • certain_[min|max]_elem -> [min|max]_elem_alldefined
    • known_[min|max]_elem -> [min|max]_elem_ifdefined

Fixes:

  • Drawing issue in palette editor, see mantis issues 101 and 146.

Performance:

  • poly2grid now works again filling raster tile-by-tile (with faster throughput, but more total processing time)

GeoDms 8.5.2

25 Nov 16:46
Compare
Choose a tag to compare

This release improves diagnostics and has stricter checks on the usage of calculated values as indices to domains by checking for matching calculation rules.

improved diagnostics:

  • v8.5.1 checks that a non-default formal values unit of a data item with a calculation rule with a categorical result matches with the derived values unit. The results of the following operations are considered as categorical:
    -- rlookup, classify, invert
    -- id
    -- subset, select: nr_OrgEntity, org_rel
    -- combine_unit: first_rel, second_rel
    -- point_in_polygon, point_in_all_polygons, point_in_ranked_polygon
    -- connect_info
    -- dyna_point: SequenceNr
    -- discr_alloc: landuse
    -- dijkstra: OrgZone_rel , DstZone_rel, etc.
    -- sequence2points: segment_rel,
  • v8.5.2:
    -- when data-items are compared or presented as comparable in the iif operation, their values units are checked for having matching calculation rules.
    -- the results of a lookup of categorical values is also considered categorical.
  • TrelloPBl129: when units don't match, diagnostic info will now indicate better what was compared with what.
  • F2 mantis issue 326
  • Shift-F2: usage of F2 transitively to search for an ultimate source of a failure.
  • eventlog now contains fail reasons as they apppear.

Fixed mantis issues :

  • 320 non-zero JenksFischer issue with 2 classes
  • 324 FutureTileFunctor were sometimes constructed without m_ValueRangeDataPtr because source data could be read without the range of the values unit being determined first.
  • 325 TableView tool show only selected rows
  • 327 crash on indirect expressions with 'null' result.

GeoDms 8.5.1

18 Nov 14:49
Compare
Choose a tag to compare

Fixes:
Diagnostics

  • mantis issue 47: values that result from calculation rules that produce categorical values, i.e. referring to an entity, are now required to indicate the same domain as the formal values unit of an attribute with such calculation rule.
  • mantis issue 321

GeoDms 8.5.0

15 Nov 10:17
Compare
Choose a tag to compare

From now on, we apply semantic versioning.
This release is compiled with MSVC 17.4.0 compiler flags: no debugging info

Fixed/implemented mantis issues:

  • 272 & 261: Error Messages and Failures are cleaned up: a source of an error is more consistently found with F2.
  • 315: mitigate/adapt stack overflows
  • 318 & 319: MapView error, introduced in 8.045

Breaking change since v8.043:

  • gdal_vect column names with special characters are now translated using as_item_name. Earlier versions may have resulted in double occurrences of the underscore character. Dependent code should be adapted.

GeoDms 8.045

08 Nov 19:06
Compare
Choose a tag to compare

Fixes Mantis issues:

  • 262: ZoomToExtent,
  • 307: getting ViewPortInfo for raster domains that were created with for_each resulted in Illegal Abstract Error (aka Trello PBL GeoDMS #127)
  • Diagnostic improvements.
  • 317 Diagnostics on invalid ExplicitSupplier references.

Known issue:

  • Mantis issue 319: Requesting raster-data in MapView sometimes doesn't complete while data is read correctly according to TableView and statistics representation; this did work in 8.044.

Breaking change since v8.043:

  • gdal_vect column names with special characters are now translated using as_item_name. Earlier versions may have resulted in double occurrences of the underscore character. Dependent code should be adapted.

v8.044

07 Nov 14:08
Compare
Choose a tag to compare

Fixes:

  • issue 46: large strings ( > 4 GB) in TableView -> Clipboard
  • issue 103: UrlDecode
  • issue 169: template instantiations with missing domain/values units
  • issue 311: Dijkstra fix in too eagerly linking visited network nodes to destination zones.
  • issue 316, 307 (WIP), 46, 103, 312, 249,
  • column names longer than 64 chars are now allowed in gdal storages and column names with special characters are translated using as_item_name

Implemented:

  • issue 157: optional installation for all users
  • issue 164: has_any function that reports for each part if it occurs in a given partitioning relation
  • issue 173, 313
  • %datetime% placeholder.

Diagnostics:

  • FailReason reformatted (see issue 307)
  • issue 179: failure to resolve DialogData reference to a base projection unit

Breaking change since v8.043:

  • gdal_vect column names with special characters are now translated using as_item_name. Earlier versions may have resulted in double occurrences of the underscore character. Dependent code should be adapted.

GeoDms 8.043

27 Oct 14:59
Compare
Choose a tag to compare

Fixed issue 311: the dijkstra function greedily assigned DstZones to the first committed endPoint node, discarding later endPoint Nodes with lower impedance.
This affected only dijkstra calls with endPoint impedances and multiple endPoints per DstZone.

GeoDms 8.042

26 Oct 15:58
Compare
Choose a tag to compare

Fixes:

  • mantis issue 179,
  • mantis issue 164
  • mantis issue 169: template instantiation with missing units now continues to instantiate other items.
  • gdal ReadDouble 'null' or 0, fss read dataset with 0 rows
  • trello issue 142

Includes preview of GeoDmsImGui.exe

dijkstra now has optional verboseLogging

Known issue: https://geodms.nl/mantis/view.php?id=311 results of dijkstra are under investigation.

GeoDMS 8.041

25 Oct 14:52
Compare
Choose a tag to compare

New functionality:

  • large palettes with random colors for the unique values of categorical thematic attributes.
  • thematic attributes can now be represented by multiple aspects, work in progress.

Fixes:

  • mantis issue 283
  • mantis issue 291
  • mantis issue 309
  • mantis issue 310

Known issue: https://geodms.nl/mantis/view.php?id=311 results of dijkstra are under investigation.