paleolimbot opened a new issue, #819: URL: https://github.com/apache/sedona-db/issues/819
Most mechanical extractors (e., number of geometries, is empty) that can support geography already do via the `is_geometry_or_geography()` matcher. Transformers (that output the same type they input) aren't quite supported yet in many cases. A few that can be implemented trivially: - st_dump - st_force_dim functions - st_flipcoordinates - st_geometryn - st_interiorringn - st_reverse - st_start_point - st_pointN Some of the GEOS functions are structural (could possibly be reimplemented in sedona-functions for speed but could also be left as is and given a geography matcher) - st_numpoints (maybe this is repeated from sedona-functions? or could be easily ported) - st_numinteriorrings (could probably be easily ported to sedona-functions) - st_nrings (could probably be easily ported to sedona-functions) - st_isring - st_boundary -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
