zeroshade commented on PR #960: URL: https://github.com/apache/arrow-go/pull/960#issuecomment-5024606982
> @C-Loftus I believe we had decided that the full geoarrow types should remain outside of this repo, but I believe it does make sense to have the Geometry/Geography types for Parquet in this repo, which necessitates WKB encoding. I think there's a bit of a chicken/egg situation to deal with here that it would be good to get @zeroshade's call on. We don't need to actually perform the WKB encoding/decoding in here, the parquet Geography and Geometry logical types are just byte-array primitives. So as long as we can use a registered extension type and go from the extension type -> parquet logical type (this interface already exists) then writing will work. For reading, we'll need to add a new interface to go from parquet physical type + parquet logical type -> instantiated extension type. In both cases, we'll need to add methods to the extension types in geoarrow-go to do the conversion between the type and parquet logical type which should allow us to generically handle it without needing to actually perform WKB encode/decode in here -- 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]
