You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sedona.apache.org by "paleolimbot (via GitHub)" <gi...@apache.org> on 2026/08/07 02:30:32 UTC
[I] Consider polar projections in Raster spatial join bounding box calculation [sedona-db]
paleolimbot opened a new issue, #1130:
URL: https://github.com/apache/sedona-db/issues/1130
Filing this as an issue so we don't forget!
> Extent reprojection requires internal points across the whole domain, not just the boundary. I can demonstrate if desired, my approach is in reproj::reproj_extent
_Originally posted by @mdsumner in [#1126](https://github.com/apache/sedona-db/pull/1126/changes/13f834a1ee048e97f894ba016bb25e50a0e1c87b..497e36bdfa8b7f757fb3b49cf653006e81adb1f4#r3732660054)_
This is a great point...in addition to the example in the linked thread, any polar projection when converted to lat/lon falls in this category (e.g., the south pole is directly in the middle of some projections, so even densifying the edges is not going to work, and even including points in the middle is not going to necessarily catch the minimum). Some of the minimum values it covers might also not be coverable by the other projection (e.g., mercator projections with a sigularity at the south pole).
Probably a geography covering is more accurate than a bounding box.
--
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: issues-unsubscribe@sedona.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Consider polar projections in Raster spatial join bounding box calculation [sedona-db]
Posted by "mdsumner (via GitHub)" <gi...@apache.org>.
mdsumner commented on issue #1130:
URL: https://github.com/apache/sedona-db/issues/1130#issuecomment-5212671993
a coverage is a great idea ... nice convergence of problem spaces here. If we consider the polar case of mine as 1) then
1) The pole inside a polar raster -> longlat
2) The antipode inside the source when targeting an azimuthal projection (the global EPSG:4326 boundary has nothing to do with the global Azimuthal Equal Area boundary), and many others
3) Antimeridian/seam crossing
4) Boundary points that are invalid but the interior is fine: Geostationary full-disk (Himawari, GOES), Sinusoidal (MODIS), or any of Mollweide/Robinson/HEALPix/Goode Homolosine etc
Certainly interested to spin up a few as examples 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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Consider polar projections in Raster spatial join bounding box calculation [sedona-db]
Posted by "paleolimbot (via GitHub)" <gi...@apache.org>.
paleolimbot commented on issue #1130:
URL: https://github.com/apache/sedona-db/issues/1130#issuecomment-5217762803
> Certainly interested to spin up a few as examples here.
Examples are great! We can use them as test cases.
--
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: issues-unsubscribe@sedona.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org