Releases: ObjectVision/GeoDMS
v14.15.4
Added griddist variants that include a boundary impedance.
griddist_zonal(impgrid, startlocations, zonalgrid, boundaryImp)griddist_zonal_maximp(impgrid, startlocations, zonalgrid, boundaryImp, maxImp)griddist_zonal_untiled(impgrid, startlocations, zonalgrid, boundaryImp)griddist_zonal_maximp_untiled(impgrid, startlocations, zonalgrid, boundaryImp, maxImp)griddist_zonal_latitude_specific(impgrid, startlocations, zonalgrid, boundaryImp)griddist_zonal_maximp_latitude_specific(impgrid, startlocations, zonalgrid, boundaryImp, maxImp)griddist_zonal_untiled_latitude_specific(impgrid, startlocations, zonalgrid, boundaryImp)griddist_zonal_maximp_untiled_latitude_specific(impgrid, startlocations, zonalgrid, boundaryImp, maxImp)
Note that Zonalgrid must have the same domain ans impgrid and UInt16 values and boundaryImp must have a void domain and be values compatible with impgrid.
Aded in v14.15.3 (hotfix for gridist issues and inclusion of new variants for latitude specific factors for distances between raster cell centers)
griddist_latitude_specific(impgrid, startlocations)griddist_maximp_latitude_specific(impgrid, startlocations, maxImp)griddist_untiled_latitude_specific(impgrid, startlocations)griddist_maximp_untiled_latitude_specific(impgrid, startlocations, maxImp)
Note that get_x and get_y functions have been temporarily disabled since https://github.com/ObjectVision/GeoDMS/releases/tag/v14.15.3 in preparation of implementation of #689.
Full Changelog: v14.15.3...v14.15.4
GeoDms 14.15.3
Hotfix for gridist issues and inclusion of new variants for latitude specific factors for distances between raster cell centers:
griddist_latitude_specific(impgrid, startlocations)griddist_maximp_latitude_specific(impgrid, startlocations, maxImp)griddist_untiled_latitude_specific(impgrid, startlocations)griddist_maximp_untiled_latitude_specific(impgrid, startlocations, maxImp)
get_x and get_y functions are temporarily disabled in preparation of implementation of #689. The get_x and get_y functions were defined as synonyms for point_col and point_row respectively in v14.12.0, but future implementation are planned to result in base coordinates. Current usage of get_x and get_y, if any, will have to be replaced by point_col and point_row.
Full Changelog: v14.15.2...v14.15.3
v14.15.2
Hotfix of a too strict check on the SpatialReference of a gdal data source (which failed when either no SR was configured or the data source didn't specify any), introduced in v14.15.1, which affected the 2Up and CUSA regression tests.
Full Changelog: v14.15.1...v14.15.2
GeoDMS 14.15.1
In 14.15.0, an issue was introduced in GridDist , see also #673
Furthermore, it was found that the TileUnit function did not result in regular but non-default tiling, which caused the Tiled variants in the operator test to have only one tile, which made the aforementioned GridDist issue undetected in the Unit test; this has been resolved.
Furthermore, a merge was done with the Qt, GDAL, and Python branches, resulting in the following fixes and/or new features:
Qt:
Python:
- renamed GeoDms python bindings to comply to PEP8: geodms.pyd
- added python functions: item.update
GDAL:
- #170: export geometry
- diagnostic on spatial reference mismatch
Full Changelog: v14.14.0b...v14.15.1b
GeoDMS 14.15.0
MapControl issues
- overlapping polygons can now all be selected by mouse-clicking on a location. Open the thematic attribute in a table and press the "show selected only" tool, see #129
- Header row in layer control #631
Fixes
#673 fixes for new griddist options
Diagnostics:
- GeoDmsVersion() is no longer depreciated.
GeoDms 14.14.1
Update of 14.14.0 with the following fixes:
- Fix of #687: connect_info/cut values were {0, 0} since version 9.1 when connecting to arcs with only one point.
- warnings for the use of some depreciated functions were't emitted as intended.
- better diagnostics for multiple ring detection, see #685
- Better visual sink-indication of invisible layers, see #676
Full Changelog: v14.14.0b...v14.14.1
(visual sink-indication of the invisible "grijs" layer).
GeoDms 14.14.0
Hereby the 14th minor upgrade of the v14 series with:
- some variants of the griddist function, see #673
- some extra aggregation functions, similar to modus: unique_count, modus_count, entropy, and average_entropy, which can be selected for numeric columns when TableView is in aggregation (group-by) mode, see #556
- #included now can contain more than one item, for example a bunch of attributes and units which are directly included at the container that enclosed the include directive, see #586
- a fix of the statistics view for linestring and/or polygon data, see #680.
https://github.com/ObjectVision/GeoDMS/milestone/46?closed=1
Full Changelog: v14.13.2...v14.14.0b
GeoDms 14.13.2
Fixed an issue of processing point sequences with composition type polygon (such as with partitioned_union_polygon) with small island touching the starting point as last ring that was skipped as it had to few remaining points for a connecting line and area because there is no connecting line.
This fix resulted in our test dataset for 8 of the 6.6 million BAG panden in a different residential type. In these cases the first and second point of the geometry of the BAG panden were the same. We consider the fix as an improvement.
v14.13.1
Hotfix of issue #670
Full Changelog: v14.13.0...v14.13.1
v14.13.0
New operators:
- district_uint8, district_uint16, district_uint32, district_uint64 (and similar versions for district_8)
- bitxor
Fixed issues:
- #211 BasisGrid beter vindbaar
- #598: close ValueInfo on ConfigClose
- #643, #648: TIFF projection issues
- #661: Dataset information for storages without StorageReadOnly = "True"
- #662: export van boolean naar TIFF
- #664, #668: better diagnostics for incompatible value compositions
- GUI issues: #665, #666:
Full Changelog: v14.12.0...v14.13.0