Skip to content

History / dms_split_union_polygon

Revisions

  • #1214 The rest of the dms_ family: six pages, and the statements they make stale dms_polygon, dms_union_polygon, dms_split_polygon, dms_split_union_polygon, dms_overlay_polygon and dms_polygon_connectivity get a page each, in the layout of their geos_ counterparts and leaning on the family page for the shared semantics. The two Minkowski operators are named on the shared minkowski_sum and minkowski_difference pages, where the other four backends already are. Three statements were true when they were written a day ago and are not any more, so they are corrected rather than left to age: the family page said the rest of the family did not exist yet, the operators page said it was to be developed, and Cleaning invalid polygons told the reader to unite an argument with itself because dms_polygon did not exist. That example now calls dms_polygon, and points at dms_union_polygon for cleaning a whole layer at once. The family page also gains the sections the family now has (cleaning, dissolving, splitting, overlay, growing) and says plainly that all six point types are supported throughout, which is wider than any of the libraries. Cross references both ways: the four xxx_overlay_polygon and four xxx_polygon_connectivity pages, Polygon_connectivity and box_connectivity now name their dms_ counterpart, and the pair-finding table on the operators page has a row for each of the two. Since GeoDMS 20.20.0, engine fd3dd0b8. The six pages are new, so they are built and indexed but do not appear in the menu of geodms.nl until nav/geodms.md in the converter lists them. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

    @MaartenHilferink MaartenHilferink committed Sep 6, 2026