mkaravel commented on PR #13227: URL: https://github.com/apache/iceberg/pull/13227#issuecomment-2949506693
> @rdblue I think it makes sense to drop `xmin > xmax` wraparound in `geometry` if we don't expect CRS to have an effect. > > On the other hand, I'd like to also add `linear` interpolation to `geography` if we want to drop this. This is an idea proposed by @mkaravel before. Because there will be use cases that needs linear interpolation (cartesian mathematics) on antimeridian crossing geometries on geographic CRS. @jiayuasu I am obviously (since I have suggested it in the past) totally on board with this plan. This will make the semantics of the types very clean (geometry always Cartesian, calculations independent of the CRS) and allow geography to have an easy, practical, and meaningful way to deal with the antimeridian geometries (also very clean IMHO). > I am fine adding the sentence to disallow wraparound here and create another PR to add linear interpolation although I think the 2 issues are interconnected. Or, I can put everything in this PR instead so we can solve these issues together My thinking when I proposed the changes above in this PR was to make it self-consistent and self-contained regarding the `geometry` type. We can follow up with a separate PR for `geography` or add the changes here. Either way is fine with me. Maybe a single PR is just simpler. @rdblue Are you okay with this? Thoughts? -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
