I'm looking at incorporating geoarrow-rs geospatial algorithms as a performance optimization compared to vanilla JTS / a webassembly build of JTS when they're available, which, as I understand it, wraps the core operations from georust/geo.
I'm noticing that JTS can generally operate on coordinate sequence/buffers with extra dimensions (XYZ, XYM, XYZM), and can always pass them through.
Simplify and SimplifyVw have their SimplifyIdx and SimplifyVwIdx variants, so geoarrow-rs can just nab the relevant indices from those and pull the extra dimensions through in their output.
SimplifyVwPreserve and ConvexHull, however, don't have idx variants, and so geoarrow-rs has no way to route the Z/M values through.
Would a PR to add this be welcomed?
I'm looking at incorporating geoarrow-rs geospatial algorithms as a performance optimization compared to vanilla JTS / a webassembly build of JTS when they're available, which, as I understand it, wraps the core operations from georust/geo.
I'm noticing that JTS can generally operate on coordinate sequence/buffers with extra dimensions (XYZ, XYM, XYZM), and can always pass them through.
SimplifyandSimplifyVwhave theirSimplifyIdxandSimplifyVwIdxvariants, so geoarrow-rs can just nab the relevant indices from those and pull the extra dimensions through in their output.SimplifyVwPreserveandConvexHull, however, don't haveidxvariants, and so geoarrow-rs has no way to route the Z/M values through.Would a PR to add this be welcomed?