Accessing TEMPO data with R

[ateucher]

This is a tutorial for accessing TEMPO data with R using terra. It is a direct fork of the Python notebook from the ASDC Data and User Services Tutorials Cookbook, illustrating the same workflow.

@danielfromearth I'd love it if you could look this over and see if you see anything jump out compared to the ASDC Python notebook.

@cboettig and/or @eeholmes you are much more fluent in this work than me, so if you have the time to look it over I'd appreciate it very much!

The deploy preview for the tutorial is here.

[github-actions]

🚀 Deployed on https://deploy-preview-405--openscapes-org-preview.netlify.app

[github-actions]

🚀 Deployed on https://deploy-preview-405--openscapes-org-preview.netlify.app

[ateucher]

/deploy-preview

[github-actions]

🚀 Deployed on https://deploy-preview--openscapes-org-preview.netlify.app

[github-actions]

🚀 Deployed on https://deploy-preview-405--openscapes-org-preview.netlify.app

[eeholmes]

@ateucher I get this error with earthdatalogin 0.0.3 (the one on cran) from code below. Your 3 or so box

Error in vapply(elements, encode, character(1)) :
values must be length 1,
but FUN(X[[4]]) result is length 4

dlat <- 5.0 # deg
dlon <- 6.0 # deg

bbox_results <- earthdatalogin::edl_search(
  short_name = short_name,
  version = version,
  temporal = c(date_start, date_end),
  bounding_box = c(
    POI_lon - dlon,
    POI_lat - dlat,
    POI_lon + dlon,
    POI_lat + dlat
  ), # search by bounding box
  parse_results = FALSE
)

length(bbox_results)

[ateucher]

Right, yes! PR here: boettiger-lab/earthdatalogin#25.

You can install with remotes::install_github("boettiger-lab/earthdatalogin@fix-search-bounding-box")

[danielfromearth]

@ateucher, first question (sorry for the very long delay before commenting!): I'm a bit confused, why are there so many files in this PR?

[ateucher]

@danielfromearth no worries, thanks for having a look! As for the number of files, it's the _freeze directory, which holds the computation results from .qmd files, as well as the javascript libraries for the rendered site... I think this PR adds so many js libraries because of the interactive data table using DT. You can ignore everything in the _freeze directory in your review (unless you think the benefits of the interactive tables are not worth adding so many js dependencies to the cookbook).

[danielfromearth]

This is great @ateucher!

I added some comments to the .qmd file with the underscore prefix (the 'stars' one) – is that alright? It looks like that (mostly) duplicates the qmd without the underscore, but I'm not sure what is the relationship between the two.

[ateucher]

Thanks @danielfromearth! The two notebooks demonstrate the same workflow using the two main geospatial (raster) packages stars and terra. I think I will try to combine them into one, using tabs to toggle between stars and terra so people can compare.

These are great suggestions! I'll update to V04 as well, and update the date range