Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable sits_cube_copy() to write data to a storage container #950

Open
felixg3 opened this issue Apr 17, 2023 · 1 comment
Open

Enable sits_cube_copy() to write data to a storage container #950

felixg3 opened this issue Apr 17, 2023 · 1 comment
Assignees

Comments

@felixg3
Copy link

felixg3 commented Apr 17, 2023

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:

bl_endp_key <- storage_endpoint("https://mystorage.blob.core.windows.net", key="access_key")
cont <- storage_container(bl_endp_key, "myfilesystem")


cube_local <- sits_cube_copy(
  cube = s2_L8_cube_MPC,
  output_dir = cont,
  roi = shape,
  multicores = 8
)

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.

@OldLipe OldLipe self-assigned this Apr 17, 2023
@OldLipe OldLipe added this to the version 1.4.0 milestone Apr 17, 2023
@gilbertocamara
Copy link
Contributor

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.

@gilbertocamara gilbertocamara modified the milestones: version 1.4.0, version 1.5.0 Apr 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants