Replies: 1 comment 1 reply
-
Take a look at some open data cube methods. This and others in the base https://github.com/opendatacube/odc-geo |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
Sorry if this is not the right avenue for this discussion, but I wanted some feedback on best practice/ideas for using STAC/stackstac for wide area analysis. Some context...
I am interested in processing HLS satellite imagery across a large area that encompasses multiple UTM zones (e.g., Canada). I am testing means to split my area into reasonably sized tiles and processing each tile independently. To test, I created a fishnet grid of 120km squares in a national projection and extracted some HLS imagery using stackstac.
In a perfect world, the output cube would have 4000 x 4000 pixels. However, because I need to provide a local UTM bounding box, the output is 4856 x 4856 pixels. This represent approximately 1.47x increase in pixels, which will overlap other fishnet squares and thus not be useful.
Another option that I assume would avoid this would be use MGRS tiles directly, which are already in the local UTM. However that comes with its own set of redundancy issues - especially towards the poles. A nice visual is from this figure in Bauer-Marschallinger 2023:
Maybe there is some combination approach that would limit redundancy? For example, full squares in the center of a UTM zone that transition to slivers along the edge? But it seems like a lot of work to create a robust grid that meets all edge cases etc.
I just wanted to make this post to see if others have worked through this type of issue and have some thoughts or ideas. Maybe I am missing something obvious!
Beta Was this translation helpful? Give feedback.
All reactions