Since GeoDMS 20.23.1: the version labels of the interim builds name the release
The changes since 20.20.0 were labelled with the version of the build they first came in: 20.21.0,
20.22.0, 20.22.1 and, on one page, 20.23.0. None of those was published as a release that stayed;
20.23.1 is the first in all four flavours, so a reader on a released version could not tell from
the label whether their build has the change. Every "Since GeoDMS 20.21.0" and the like, also in
the forms "since 20.22.0", "*(since 20.21.0)*" and "_(20.22.0+)_", now says 20.23.1: 153 labels on
89 pages, replaced by one exact pattern and checked word by word in the diff, which holds only
version numbers.
By hand, where a version was named without "since": the order of the spatial index changed in
20.23.1 (Connect, Connect_neighbour, Deterministic-and-unspecified-results); Python-bindings says
"before 20.23.1" and "20.23.1 and later"; Arc-visualisation says the wide dashed pens were drawn
solid from 20.0.0 on and before 20.23.1; the "since version" of pareto_optimal and
pareto_optimal_eps is 20.23.1, and the epsilon of Impedance-options and impedance_matrix lost its
"relative since" that now named the same version twice. Left as they are: the two sentences on
what the interim builds 20.21.0 to 20.22.1 did with an epsilon, which is what someone who ran
those builds needs to know.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Python bindings: asDataItem and asUnitItem raise for another kind or a null item
They returned a wrongly cast object for an item of another kind, and the result for the null item of find() crashed on first use. Engine commit 86c1eeba1.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Features first built in the 20.21 interim builds are dated 20.22.0
20.21.0 and 20.21.1 were interim builds; the release notes of 20.22.0 cover everything since 20.20.0 and
fold their changes in. The range check of modus_weighted, the imp2_epsilon argument of the pareto option
and the Python bindings fail_reason(), update_metainfo(), in_template() and is_template() were labelled
with 20.21.0; they now say 20.22.0, the first release a modeller can install them from.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Python bindings: set_values_from_float_list and _int_list take one value per element
The dated note for what a modeller notices of the engine change 986df78be "Python set_values_from_float_list / _int_list: one value per element, written tile by tile" in ObjectVision/GeoDMS, doc/code-audit-2026-09-27.md.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
#1279 Listing the red items of a configuration from Python
Since GeoDMS 20.21.0 a script can ask an item for its meta info without calculating it, which
is what makes an item red in the GUI tree-view, and can read the fail reason of an item that
has not failed without the process dying.
Python-bindings.md gains a "Listing the red items of a configuration" section with the walker,
says why update_metainfo() and not update() (the latter reads the primary data of the item and
of all its suppliers, which for a raster attribute is a full calculation), and records what
changed about fail_reason(): before 20.21.0 calling it on a valid item took the whole Python
process down, so the only safe use was on an item already known to be bad. update_metainfo(),
in_template() and is_template() are added to the API reference, and GeoDMS-through-Python.md
points at them from its summary of the module.
Also corrected on the same page, unrelated to the above: the regular Windows setup stopped
carrying CPython 3.9 in 20.19.0 and now carries 3.12, 3.13 and 3.14; 3.9 is only in the GLOBIO
flavour. The page still named 3.9 among the four and asked release builders for PYTHON39_ROOT.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Document Python ABI matrix and GDAL limits
Fix migration artifacts, typos and dead links across the wiki
Sweep of all 867 pages: MediaWiki-to-GitHub migration damage repaired
(wikilink artifacts, reversed link order, broken code blocks, image
links restored as embeds), 2200+ typo/grammar/dead-link fixes, and
remaining CalcCache references removed or marked version-historical.
Factual example errors corrected where unambiguous (a.o. Boundcenter,
Ge_or_rhs_null, Capacitated_connect, Dpoint, Modus).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Updated Python bindings (markdown)
Updated Python bindings (markdown)
updated doc wrt indirect expressions, https://github.com/ObjectVision/GeoDMS/issues/1142 and using pythion
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Updated Python bindings (markdown)
Created Python bindings (markdown)