jiayuasu merged PR #749:
URL: https://github.com/apache/sedona/pull/749
--
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:
jiayuasu merged PR #748:
URL: https://github.com/apache/sedona/pull/748
--
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:
umartin opened a new pull request, #749:
URL: https://github.com/apache/sedona/pull/749
## Did you read the Contributor Guide?
- Yes, I have read [Contributor
Rules](https://sedona.apache.org/community/rule/) and [Contributor Development
Yes, there are lots of things to consider when processing large blobs in
Spark. What I have come to learn:
- Do the spatial join (points and the geotiff extent) with as few columns
as possible. Ideally an id only for the geotiff. After that join you can
join back the geotiff using the id.
-
Thanks Martin, it sounds promising. I'll actually give it a try before
going with geotiff conversions.
I'm foreseeing some concerns, though:
- I'm afraid it won't be optimal for a big geotiff - I may have to split
the geotiff into smaller geotiffs
- I wonder how the spatial partitioning
