rgeeExtra: An extensions for 'rgee'

[csaybar]

Submitting Author Name: Cesar Aybar
Submitting Author Github Handle: @csaybar
Other Package Authors Github handles: (comma separated, delete if none) @davemlz, @LBautistaB13, @choisy
Repository: https://github.com/r-earthengine/rgeeExtra
Version submitted: 0.0.1
Submission type: Standard
Editor: @maurolepore
Reviewers: @nmorandeira, @zackarno

Archive: TBD
Version accepted: TBD
Language: en

---

• Paste the full DESCRIPTION file inside a code block below:

Package: rgeeExtra
Title: Extensions for 'rgee'
Version: 0.0.1
Authors@R: 
    c(person(given = "Cesar",
           family = "Aybar",
           role = c("aut", "cre"),
           email = "csaybar@gmail.com",
           comment = c(ORCID = "0000-0003-2745-9535")),
      person(given = "David",
           family = "Montero",
	         role = c("ctb"),
	         email = "dml.mont@gmail.com",
	         comment = c(ORCID = "0000-0002-9010-3286")),
      person(given = "Lesly",
           family = "Bautista",
	         role = c("ctb"),
	         email = "leslyarcelly.213@gmail.com",
	         comment = c(ORCID = "0000-0003-3523-8687")),
      person(given = "Marc",
           family = "Choisy",
	         role = c("ctb"),
	         email = "mchoisy@oucru.org",
	         comment = c(ORCID = "0000-0002-5187-6390"))
    )
Description: High-level API to process Google Earth Engine (GEE) raster (ee.Image and ee.ImageCollection) and vector data (ee.Geometry, ee.Feature, and ee.FeatureCollection). Popular Third-party GEE algorithms are re-coded from Javascript and Python to R.
License: Apache License (>= 2)
Encoding: UTF-8
LazyData: true
Roxygen: list(markdown = TRUE)
RoxygenNote: 7.2.3
Config/reticulate:
  list(
    packages = list(
      list(package = "earthengine-api")
    )
  )
Imports:
    reticulate (>= 1.31),
    rgee,
    magrittr,
    crayon,
    cli
Suggests:
    testthat (>= 3.0.0),
    googledrive,
    googleCloudStorageR,
    geojsonio,
    magick,
    stars,
    sf,
    knitr,
    rmarkdown
VignetteBuilder: knitr
Language: en-US
BugReports: https://github.com/r-earthengine/rgeeExtra/issues
URL: https://github.com/r-earthengine/rgeeExtra

Scope

• Please indicate which category or categories from our package fit policies this package falls under: (Please check an appropriate box below. If you are unsure, we suggest you make a pre-submission inquiry.):

  • data retrieval
  • data extraction
  • data munging
  • data deposition
  • data validation and testing
  • workflow automation
  • version control
  • citation management and bibliometrics
  • scientific software wrappers
  • field and lab reproducibility tools
  • database software bindings
  • geospatial data
  • text analysis

• Explain how and why the package falls under these categories (briefly, 1-2 sentences):

rgeeExtra is an extension of the rgee package that enables interaction with Google Earth Engine (GEE). The advantage of rgeeExtra lies in its user-friendly syntax for R users. The package includes operator overloading and access to various functions created by third parties within the ee_extra package.

• Who is the target audience and what are scientific applications of this package?

GEE users and any R user who wants to retrieve data using the GEE API from within R.

• Are there other R packages that accomplish the same thing? If so, how does yours differ or meet our criteria for best-in-category?

There are other packages for connecting to GEE, but they are primarily focused on composite generation and data download. See geedim

• (If applicable) Does your package comply with our guidance around Ethics, Data Privacy and Human Subjects Research?

Yes

• If you made a pre-submission inquiry, please paste the link to the corresponding issue, forum post, or other discussion, or @tag the editor you contacted.

• Explain reasons for any pkgcheck items which your package is unable to pass.

• Package uses global assignment operator ('<<-'). The global assignment operator is used in the .onLoad special function to set the ee_extra Python Package in the R global environment (See here). This approach is similar to other reticulate R packages like keras or tensorflow.

Technical checks

Confirm each of the following by checking the box.

• I have read the rOpenSci packaging guide.
• I have read the author guide and I expect to maintain this package for at least 2 years or to find a replacement.

This package:

• does not violate the Terms of Service of any service it interacts with.
• has a CRAN and OSI accepted license.
• contains a README with instructions for installing the development version.
• includes documentation with examples for all functions, created with roxygen2.
• contains a vignette with examples of its essential functions and uses.
• has a test suite.
• has continuous integration, including reporting of test coverage.

Publication options

• Do you intend for this package to go on CRAN?
• Do you intend for this package to go on Bioconductor?
• Do you wish to submit an Applications Article about your package to Methods in Ecology and Evolution? If so:

MEE Options

• The package is novel and will be of interest to the broad readership of the journal.
• The manuscript describing the package is no longer than 3000 words.
• You intend to archive the code for the package in a long-term repository which meets the requirements of the journal (see MEE's Policy on Publishing Code)
• (Scope: Do consider MEE's Aims and Scope for your manuscript. We make no guarantee that your manuscript will be within MEE scope.)
• (Although not required, we strongly recommend having a full manuscript prepared when you submit here.)
• (Please do not submit your package separately to Methods in Ecology and Evolution)

Code of conduct

• I agree to abide by rOpenSci's Code of Conduct during the review process and in maintaining my package should it be accepted.

[ropensci-review-bot]

Thanks for submitting to rOpenSci, our editors and @ropensci-review-bot will reply soon. Type @ropensci-review-bot help for help.

[ropensci-review-bot]

🚀

Editor check started

👋

[ropensci-review-bot]

Checks for rgeeExtra (v0.0.1)

git hash: 79fde841

• ✔️ Package name is available
• ✔️ has a 'codemeta.json' file.
• ✔️ has a 'contributing' file.
• ✖️ The following functions have no documented return values: [ee_length_ic, ee_length, ee_name_ic, ee_name, ee_subsetting, extra_Initialize, Math-methods, Ops-methods, Summary-methods]
• ✔️ uses 'roxygen2'.
• ✔️ 'DESCRIPTION' has a URL field.
• ✔️ 'DESCRIPTION' has a BugReports field.
• ✔️ Package has at least one HTML vignette
• ✔️ All functions have examples.
• ✔️ Package has continuous integration checks.
• ✖️ Package coverage failed
• ✖️ R CMD check found 1 error.
• ✔️ R CMD check found no warnings.

Important: All failing checks above must be addressed prior to proceeding

Package License: Apache License (>= 2)

---

1. Package Dependencies

Details of Package Dependency Usage (click to open)

The table below tallies all function calls to all packages ('ncalls'), both internal (r-base + recommended, along with the package itself), and external (imported and suggested packages). 'NA' values indicate packages to which no identified calls to R functions could be found. Note that these results are generated by an automated code-tagging system which may not be entirely accurate.

type	package	ncalls
internal	base	71
internal	rgeeExtra	38
internal	graphics	5
internal	stats	2
imports	magrittr	70
imports	rgee	29
imports	reticulate	5
imports	crayon	NA
imports	cli	NA
suggests	sf	2
suggests	magick	1
suggests	testthat	NA
suggests	googledrive	NA
suggests	googleCloudStorageR	NA
suggests	geojsonio	NA
suggests	stars	NA
suggests	knitr	NA
suggests	rmarkdown	NA
linking_to	NA	NA

Click below for tallies of functions used in each package. Locations of each call within this package may be generated locally by running 's <- pkgstats::pkgstats(<path/to/repo>)', and examining the 'external_calls' table.

base

c (13), list (12), length (9), drop (6), for (4), lapply (3), which (3), mode (2), names (2), seq_along (2), sprintf (2), all (1), args (1), basename (1), diff (1), dirname (1), gsub (1), rep (1), scale (1), source (1), system.file (1), tempfile (1), try (1), url (1)

magrittr

%>% (70)

rgeeExtra

ee_get (3), ee_connect_to_py (2), ee_new_list_name (2), ee_source_python (2), ee_check_packages (1), ee_image_getCitation (1), ee_image_getDOI (1), ee_Image_getOffsetParams (1), ee_Image_getScaleParams (1), ee_Image_getSTAC (1), ee_Image_maskClouds (1), ee_Image_matchHistogram (1), ee_Image_panSharpen (1), ee_Image_preprocess (1), ee_Image_scaleAndOffset (1), ee_Image_spectralIndex (1), ee_Image_tasseledCap (1), ee_ImageCollection_closest (1), ee_ImageCollection_getCitation (1), ee_ImageCollection_getDOI (1), ee_ImageCollection_getOffsetParams (1), ee_ImageCollection_getScaleParams (1), ee_ImageCollection_getSTAC (1), ee_ImageCollection_panSharpen (1), ee_ImageCollection_preprocess (1), ee_ImageCollection_scaleAndOffset (1), ee_ImageCollection_spectralIndex (1), ee_ImageCollection_tasseledCap (1), ee_maxValue (1), ee_minValue (1), Math.ee.image.Image (1), Ops.ee.image.Image (1), Summary.ee.image.Image (1)

rgee

ee_as_sf (4), sf_as_ee (4), ee$ImageCollection (3), ee$ImageCollection$first (2), ee$ImageCollection$toList (2), ee$List$get (2), ee$Reducer$max (2), ee$Image (1), ee$Image$abs (1), ee$Image$bandNames (1), ee$Image$pow (1), ee$Image$unmask (1), ee$ImageCollection$getVideoThumbURL (1), ee$List$length (1), ee$List$sequence (1), ee$Number$format (1), ee$Reducer$min (1)

graphics

image (5)

reticulate

import_from_path (4), py_discover_config (1)

sf

st_cast (2)

stats

offset (2)

magick

image_read (1)

NOTE: Some imported packages appear to have no associated function calls; please ensure with author that these 'Imports' are listed appropriately.

---

2. Statistical Properties

This package features some noteworthy statistical properties which may need to be clarified by a handling editor prior to progressing.

Details of statistical properties (click to open)

The package has:

• code in R (100% in 12 files) and
• 1 authors
• 2 vignettes
• no internal data file
• 5 imported packages
• 48 exported functions (median 4 lines of code)
• 60 non-exported functions in R (median 8 lines of code)

---

Statistical properties of package structure as distributional percentiles in relation to all current CRAN packages
The following terminology is used:

• loc = "Lines of Code"
• fn = "function"
• exp/not_exp = exported / not exported

All parameters are explained as tooltips in the locally-rendered HTML version of this report generated by the checks_to_markdown() function

The final measure (fn_call_network_size) is the total number of calls between functions (in R), or more abstract relationships between code objects in other languages. Values are flagged as "noteworthy" when they lie in the upper or lower 5th percentile.

measure	value	percentile	noteworthy
files_R	12	65.5
files_vignettes	2	85.7
files_tests	9	89.6
loc_R	825	62.7
loc_vignettes	120	31.3
loc_tests	477	74.0
num_vignettes	2	89.2
n_fns_r	108	78.4
n_fns_r_exported	48	87.1
n_fns_r_not_exported	60	72.4
n_fns_per_file_r	6	75.7
num_params_per_fn	2	11.9
loc_per_fn_r	5	8.1
loc_per_fn_r_exp	4	7.0
loc_per_fn_r_not_exp	8	22.6
rel_whitespace_R	15	58.6
rel_whitespace_vignettes	50	45.3
rel_whitespace_tests	31	80.2
doclines_per_fn_exp	37	45.3
doclines_per_fn_not_exp	0	0.0	TRUE
fn_call_network_size	13	37.5

---

2a. Network visualisation

Click to see the interactive network visualisation of calls between objects in package

---

3. goodpractice and other checks

Details of goodpractice checks (click to open)

3a. Continuous Integration Badges

![R-CMD-check.yaml](https://github.com/r-earthengine/rgeeExtra/actions/workflows/R-CMD-check.yaml"><img src="https://github.com/r-earthengine/rgeeExtra/actions/workflows/R-CMD-check.yaml/badge.svg)

GitHub Workflow Results

id	name	conclusion	sha	run_number	date
5917635570	Commands	success	887d78	13	2023-08-20
6216302723	pages build and deployment	success	1c6bba	9	2023-09-17
6216295894	pkgdown	success	79fde8	28	2023-09-17
6216295890	R-CMD-check	NA	79fde8	28	2023-09-17
6216295893	test-coverage	failure	79fde8	3	2023-09-17

---

3b. goodpractice results

R CMD check with rcmdcheck

R CMD check generated the following error:

1. checking tests ...
   Running ‘testthat.R’
   ERROR
   Running the tests in ‘tests/testthat.R’ failed.
   Last 13 lines of output:
   ── Error ('test-subsetting.R:6:1'): (code run outside of test_that()) ────────
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-subsetting.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)

[ FAIL 8 | WARN 0 | SKIP 0 | PASS 0 ]
Error: Test failures
Execution halted

R CMD check generated the following note:

1. checking installed package size ... NOTE
   installed size is 6.1Mb
   sub-directories of 1Mb or more:
   doc 4.3Mb
   ee_extra 1.6Mb

R CMD check generated the following test_fail:

1. library(testthat)

library(rgee)
library(rgeeExtra)
library(stars)
Loading required package: abind
Loading required package: sf
Linking to GEOS 3.10.2, GDAL 3.4.3, PROJ 8.2.0; sf_use_s2() is TRUE
library(sf)

if (identical(Sys.getenv("NOT_CRAN"), "true")) {

• test_check("rgeeExtra")
• }
  [ FAIL 8 | WARN 0 | SKIP 0 | PASS 0 ]

══ Failed tests ════════════════════════════════════════════════════════════════
── Error ('test-ee_gif.R:8:1'): (code run outside of test_that()) ────────────
Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
your R session after install miniconda or run ee_install()?
If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-ee_gif.R:8:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-ee_image.R:6:1'): (code run outside of test_that()) ──────────
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-ee_image.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-eeImageCollection.R:6:1'): (code run outside of test_that()) ──
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-eeImageCollection.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-ops-image.R:7:1'): (code run outside of test_that()) ─────────
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-ops-image.R:7:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-raster.R:6:1'): (code run outside of test_that()) ────────────
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-raster.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-subsetting-image.R:6:1'): (code run outside of test_that()) ──
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-subsetting-image.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-subsetting-imagecollection.R:6:1'): (code run outside of test_that()) ──
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-subsetting-imagecollection.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)
   ── Error ('test-subsetting.R:6:1'): (code run outside of test_that()) ────────
   Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/bin/python3
   does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
   your R session after install miniconda or run ee_install()?
   If no do it, please try again:

ee_install(): To create and set a Python environment with all rgee dependencies.
ee_install_set_pyenv(): To set a specific Python environment.
Backtrace:
▆

1. └─rgee::ee_Initialize() at test-subsetting.R:6:0
2. └─rgee:::ee_connect_to_py(path = ee_current_version, n = 5)

[ FAIL 8 | WARN 0 | SKIP 0 | PASS 0 ]
Error: Test failures
Execution halted

R CMD check generated the following check_fails:

1. no_import_package_as_a_whole
2. rcmdcheck_tests_pass
3. rcmdcheck_reasonable_installed_size

Test coverage with covr

ERROR: Test Coverage Failed

Cyclocomplexity with cyclocomp

The following functions have cyclocomplexity >= 15:

function	cyclocomplexity
Math.ee.image.Image	29
Ops.ee.image.Image	22

Static code analyses with lintr

lintr found the following 108 potential issues:

message	number of times
Avoid library() and require() calls in packages	4
Lines should not be more than 80 characters.	88
Use <-, not ->, for assignment.	16

---

Package Versions

package	version
pkgstats	0.1.3.8
pkgcheck	0.1.2.3

---

Editor-in-Chief Instructions:

Processing may not proceed until the items marked with ✖️ have been resolved.

[csaybar]

@ropensci-review-bot

[maurolepore]

@csaybar thanks a lot for your submission.

• Can you confirm you're requesting a review in English?
• Also, this is part of the Champions program, right?

@mpadge kindly noted that coverage and R CMD check failed due to a missing python dependency that our system can't track. I'll need a bit of time to investigate more. Do you know a good/easy way to provide the required Python environment so that the handling editor and reviewers can hit the ground running?

[csaybar]

Hi @maurolepore thank you for your quick response. I just activated the notification button to this issue.

Can you confirm you're requesting a review in English?

Yes, I'd prefer to do it in English

Also, this is part of the Champions program, right?

Yes, I'm part of the program and my mentor is Marc Choisy @choisy.

Unfortunately, I haven't been able to resolve the issues related to Python dependencies. These are the same ones you can find in the pangoling package review. The Python coverage when it is evaluated in an ENV with the Python envs is around 95%. See https://app.codecov.io/gh/csaybar/rgeeExtra/tree/master/R

The flag "The following functions have no documented return values: [ee_length_ic, ee_length, ee_name_ic, ee_name, ee_subsetting, extra_Initialize, Math-methods, Ops-methods, Summary-methods] have been solved in rgee 0.0.1.999.
"

[csaybar]

@ropensci-review-bot

[maurolepore]

Great, thanks for pointing me to pangoling. I'll explore how they handled installation during review.

[maurolepore]

@ropensci-review-bot assign @maurolepore as editor

[ropensci-review-bot]

Assigned! @maurolepore is now the editor

[maurolepore]

@csaybar, I self-assigned to be the handling editor. I think this makes sense because I would like to explore the installation process, I'm part of the Champions program, and I'm available.

I'll start working on the handling-editor's checklist. In the meantime, could you please list three potential reviewers?

Following our guidelines I'll use no more than one of them, but it's useful to have a few options and also to see the range of expertise you think is helpful.

[csaybar]

Hi, @maurolepore,

@zackarno : tidyrgee creator. Experience using GEE and R.

@giswqs: geemap creator. Experience using GEE and R.

@yabellini: Experience using GEE and R.

@ricds: Experience using GEE and R.

[maurolepore]

@csaybar,

I can successfully install rgeeExtra but fail to run the example in README. The reprex below shows a number of helpful error messages. Although I don't show it here, I did put substantial effort in trying to follow the advice but still failed to complete the example :-(

library(rgee)
library(rgeeExtra)

ee_Initialize()
#> Welcome to the Earth Engine client library for R!
#> ----------------------------------------------------------------
#> It seems it is your first time using rgee. First off, keep in mind that
#> Google Earth Engine is only available to registered users, check the
#> official website https://earthengine.google.com/ to get more information.
#> 
#> Before start coding is necessary to set up a Python environment. Run
#> rgee::ee_install() to set up automatically, after that, restart the R
#> session to see changes. See more than 300+ examples of rgee at
#> https://r-earthengine.github.io/.
#> 
#> rgee will need to create the environmental variable "EARTHENGINE_INIT_MESSAGE"
#> in your system to avoid you recieve this message again.
#> Would you like to stop to receive this message? [Y/n]:
#> Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/local/bin/python3
#> does not have the Python package "earthengine-api" installed. Are you restarted/terminated.
#> your R session after install miniconda or run ee_install()?
#> If no do it, please try again:
#> > ee_install(): To create and set a Python environment with all rgee dependencies.
#> > ee_install_set_pyenv(): To set a specific Python environment.
extra_Initialize()
#>  ✔ Initializing ee_Extra module:
#> Error in ee_connect_to_py(path = ee_current_version, n = 5): The current Python PATH: /usr/local/bin/python3
#> does not have the Python package "earthengine-api" installed. Do you restarted/terminated
#> your R session after install miniconda or run ee_install()?
#> If this is not the case, try:
#> > reticulate::use_python(): Refresh your R session and manually set the Python environment with all rgee dependencies.
#> > ee_install(): To create and set a Python environment with all rgee dependencies.
#> > ee_install_set_pyenv(): To set a specific Python environment.

img <- ee$Image("LANDSAT/LC08/C01/T1_SR/LC08_038029_20180810")
#> List of 22
#>  $ python              : chr "/usr/local/bin/python3"
#>  $ libpython           : chr "/opt/python/3.8.17/lib/libpython3.8.so"
#>  $ pythonhome          : chr "/opt/python/3.8.17:/opt/python/3.8.17"
#>  $ pythonpath          : chr "/cloud/lib/x86_64-pc-linux-gnu-library/4.3/reticulate/config:/home/r68453/.local/lib/python3.8/site-packages:/o"| __truncated__
#>  $ prefix              : chr "/opt/python/3.8.17"
#>  $ exec_prefix         : chr "/opt/python/3.8.17"
#>  $ base_exec_prefix    : chr "/opt/python/3.8.17"
#>  $ virtualenv          : chr ""
#>  $ virtualenv_activate : chr ""
#>  $ executable          : chr "/usr/local/bin/python3"
#>  $ base_executable     : chr "/usr/local/bin/python3"
#>  $ version_string      : chr "3.8.17 (default, Jun  6 2023, 15:28:08)  [GCC 9.4.0]"
#>  $ version             : chr "3.8"
#>  $ architecture        : chr "64bit"
#>  $ anaconda            : logi FALSE
#>  $ conda               : chr "False"
#>  $ numpy               : NULL
#>  $ required_module     : chr "ee"
#>  $ required_module_path: NULL
#>  $ available           : logi TRUE
#>  $ python_versions     : chr "/usr/local/bin/python3"
#>  $ forced              : chr "RETICULATE_PYTHON_FALLBACK"
#>  - attr(*, "class")= chr "py_config"
#> Error: Python module ee was not found.
#> 
#> Detected Python configuration:
ndvi <- (img[["B5"]] - img[["B4"]])/(img[["B5"]] + img[["B4"]])**2
#> Error in eval(expr, envir, enclos): object 'img' not found
names(ndvi) <- "pow_ndvi"
#> Error: object 'ndvi' not found

Map$centerObject(img,zoom=12)
#> Error in eval(expr, envir, enclos): object 'img' not found
Map$addLayer(img)
#> The legacy packages maptools, rgdal, and rgeos, underpinning the sp package,
#> which was just loaded, will retire in October 2023.
#> Please refer to R-spatial evolution reports for details, especially
#> https://r-spatial.org/r/2023/05/15/evolution4.html.
#> It may be desirable to make the sf package available;
#> package maintainers should consider adding sf to Suggests:.
#> The sp package is now running under evolution status 2
#>      (status 2 uses the sf package in place of rgdal)
#> Error in eval(expr, envir, enclos): object 'img' not found

^{Created on 2023-09-26 with reprex v2.0.2}

In the installation instructions of rgee I see you point to a posit.cloud project with a file that aims to quickly help a new user set everything up in a fresh environment. That seems like a good idea. Could you please do it also for rgeeExtra, so that I and the reviewers can install the package as quickly as possible?

Note however that on posit.cloud I fail to install rgee because I seem to need gcloud and I can't use sudo to install it because it's password-protected. Here is the project I used. You'll see some FIXME that explain my struggles. As rgeeExtra depends on rgee I guess simplifying the installation of rgee will also help with rgeeExtra?

If posit.cloud limits the system dependencies we can install, how else can we quickly create a working environment for the reviewers? Would it help to have a Docker image on r-hub or a Dockerfile in the repo?