openeo-r-client
openeo-r-client copied to clipboard
R client package for working with openEO backends
In https://github.com/Open-EO/openeo-python-client/issues/264 @soxofaan had the nice idea of a layered config approach across the clients so that a single config file would be available for all clients. See the issue...
Another convenience function would be to have a function like `view_extent(collection_name)`. It could take the coordinates from the metadata and create a mapview for example. Would be helpful for researchers...
In JS I can do something like: ```js let builder = await connection.buildProcess(); // Set the metadata for the process builder.description = "# Moisture Stress Index\nCalculate MSI for an area...
At some point we may want to consider using rstac for everything related to STAC: https://github.com/brazil-data-cube/rstac
Closes #148
Closes #144 Tested with client credentials on the openeo-dev.vito.be backend.
The `describe_collection()` gives the same output as[ `collection_viewer()`](https://open-eo.github.io/openeo-r-client/reference/collection_viewer.html). However, both of these also throw an error: `No or invalid collection id(s)` prior to the result. example: with `collection_viewer(x="SENTINEL2_L2A")` in rstudio...
Would it take much time for you to translate the python code for accessing Awesome Spectral Indices into R? Thank you for consideration!