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

import_*: Import data from non-API sources #105

Closed
m-mohr opened this issue Dec 13, 2019 · 2 comments
Closed

import_*: Import data from non-API sources #105

m-mohr opened this issue Dec 13, 2019 · 2 comments

Comments

@m-mohr
Copy link
Member

m-mohr commented Dec 13, 2019

This originates from #83: There are probably several processes, which could be useful to import data from "non-API" sources, similarly to load_uploaded_files. Some ideas:

  • import_s3: Load data from Amazon S3 (see example in #83)
  • import_nfs: Import from a network file storage system attached to the back-end. Example from VITO: load_disk_data
  • import_stac: Import from a STAC catalog/API
  • import_external_result: Import a openEO job result from another back-end
  • and more (GCS, Azure, ...)

Similarly, there could be export_* processes at some point.

@m-mohr m-mohr added this to the future milestone Dec 13, 2019
@m-mohr m-mohr changed the title import_* import_*: Import data from non-API sources Dec 13, 2019
@lforesta
Copy link
Contributor

I like the idea. Maybe we could write explicitly in their description that these processes may require a significant (and possibly slow) data transfer. This may not be clear to non-technical users.

@m-mohr m-mohr modified the milestones: future, v1.0 Dec 17, 2019
@m-mohr m-mohr added the help wanted Extra attention is needed label May 28, 2020
@m-mohr m-mohr modified the milestones: v1.0-final, future May 28, 2020
@m-mohr m-mohr added the minor label Aug 4, 2020
@m-mohr m-mohr added the vector label Apr 21, 2021
@m-mohr
Copy link
Member Author

m-mohr commented Feb 15, 2022

More or less encapsulates too many different new processes. There are some separate issues for such processes, e.g. #322

@m-mohr m-mohr closed this as completed Feb 15, 2022
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

2 participants