You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the requested improvement
As of now, sits_cube_copy() requires a local directory. I would request that sits_cube_copy() can write to a storage container. In the same fashion, sits_cube_apply() or sits_cube_regularize() should be able to retrieve data from a storage container.
An example would be the AzureStor package. The workflow would look like this:
Associated sits API function
sits_cube_copy(), sits_cube_apply(), sits_cube_regularize()
Additional context
Of course, other similar packages could be supported, which implement different types of storage, like S3-compatible backends or GCP.
The text was updated successfully, but these errors were encountered:
Dear @felixg3 There are many differences between the different storage containers. Therefore, implementing a general solution in "sits" will require solutions that work in Azure, Amazon, Google, Dropbox and other solutions. We will consider all the implications and try to implement this function whenever possible.
Describe the requested improvement
As of now, sits_cube_copy() requires a local directory. I would request that sits_cube_copy() can write to a storage container. In the same fashion, sits_cube_apply() or sits_cube_regularize() should be able to retrieve data from a storage container.
An example would be the AzureStor package. The workflow would look like this:
Associated sits API function
sits_cube_copy(), sits_cube_apply(), sits_cube_regularize()
Additional context
Of course, other similar packages could be supported, which implement different types of storage, like S3-compatible backends or GCP.
The text was updated successfully, but these errors were encountered: