bp kernel-suffix variants documented (48 names: d/i x 4/8/16/X x D/HV per bp set operation); worklist: complete coverage including the for_each family (2276 of 2276 tested and documented on 20.8.0, worklist empty)
Documentation complete for all tested operators: variant bullets on category pages (argmax/argmin/sum/reg_count/select_uint*/null_*/corr/cov/unique_with_null/asExprList_with_null/dyna_segment_with_ends/discrete+greedy+needy_alloc family), links for existing pages (mid, outer_single_polygon, geos_buffer, sqrdist, exp, log, Void, subitem), new pages (needy_alloc, DocData, DocStorageManagers, sequence_element_count, ordererd_union_data, canyon, ClassifyNonzeroEqualCount, ClassifyNonzeroEqualInterval); worklist: 455 of 455 documented operators covered on 20.8.0
Document ordered_union_data (GeoDMS #1168)
New page for the union_data variant with which the modeller states that all
values of all unioned attributes are non-decreasing: monotone increasing, but
not strictly, so equal successors are allowed, also across the boundary of two
arguments. Describes what the GeoDMS does with that statement, that it is
verified when the result is calculated and how a violation is reported, that
only the numeric value types are supported, and that the GeoDMS generates
ordered_union_data itself in the calculation rules it derives for attributes
whose values are known to be sorted.
Linked from Relational functions and from the union_data page, and dropped the
(misspelled) ordererd_union_data entry from the operator coverage worklist.
Refresh operator coverage worklist: two-level harvest + bp,bg,cgal variant tests (374 of 386 documented covered on 20.8.0)
Operator coverage worklist (generated from GeoDMS-Test t010, 20.8.0)
75 tested operators whose page exists but is not linked from any
*-functions category page; 59 tested operators without a page;
211 registered groups neither tested nor documented (after collapsing
the 1632-member for_each_* suffix family).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>