Dan Baston

I've added many of these docstrings and referenced the NumPy guidelines in https://gdal.org/development/dev_documentation.html#python-api-documentation

Switching from `SnapOverlayOp` to `OverlayNGRobust` in `BufferBuilder` causes three test failures: ``` 368 - misc-safe-16595 (Failed) 369 - misc-safe-16596 (Failed) 371 - misc-singlesidedbuffer (Failed) ```

Not fully. @dr-jts , does it make sense to you to rework `BufferBuilder` so that it uses `overlayng::Edge` and `overlayng::PolygonBuilder` ?

The original motivation here was to better position `LineIntersector` to handle multiple coordinate dimensions, but since that functionality has since been added and this PR no longer applies to `main`,...

Updated to revert changes to the default union strategy. Instead, `GEOSDisjointSubsetUnion` is exposed to the C API so clients can use it if they like.

Not to my mind. I looked into it a while ago, and to my untrained eye this looked like a reasonable way to do the implementation: https://github.com/aws/aws-sdk-cpp/tree/bb1fdce01cc7e8ae2fe7162f24c8836e9d3ab0a2/aws-cpp-sdk-core/include/aws/core/utils/memory

I can reproduce the `ogr_tiledb.py` crash locally (using the Ubuntu 20.04 container). It appears to crash when loading `pyarrow`: ``` Thread 1 "python3" received signal SIGSEGV, Segmentation fault. 0x00007fefb5218f6b in...

I'm going to propose closing this in favor of a separate PR that includes this batch of test changes but does not enable random ordering or parallel tests for CI....

Closing this in favor of #9698

> Is the issue still valid? For Java, yes: https://github.com/OSGeo/gdal/blob/e187124a8462439d7a94581bc1cb062d9df51ac8/.github/workflows/doc_build.yml#L131-L132