The advantage of
stars_proxy objects,
is that they do not contain any data. They are therefore fast to handle
and consume only limited memory. You can still manipulate the object
lazily (like selecting slices). These operation are only executed when
calling stars::st_as_stars() or plot() on the object.
Usage
cms_native_proxy(
product,
layer,
pattern,
prefix,
variable,
...,
username = cms_get_username(),
password = cms_get_password()
)Arguments
- product
An identifier (type
character) of the desired Copernicus marine product. Can be obtained withcms_products_list.- layer
The name of a desired layer within a product (type
character). Can be obtained withcms_product_services(listed asidcolumn).- pattern
A regular expression (regex) pattern. Only paths that match the pattern will be returned. It can be used to select specific files. For instance if
pattern = "2022/06/", only files for the year 2022 and the month June will be listed (assuming that the file path is structured as such, see examples)- prefix
A
characterstring. A prefix to be added to the search path of the files. Only the matching file (info) is downloaded (generally faster then usingpattern)- variable
The variable name for which to create the
stars_proxy. If omitted it will include all variables in the layer.- ...
Ignored
- username
Your Copernicus marine user name. Can be provided with
cms_get_username()(default), or as argument here.- password
Your Copernicus marine password. Can be provided as
cms_get_password()(default), or as argument here.
Details
For more details see vignette("proxy").
Examples
if (interactive()) {
native_proxy <-
cms_native_proxy(
product = "GLOBAL_ANALYSISFORECAST_PHY_001_024",
layer = "cmems_mod_glo_phy_anfc_0.083deg_PT1H-m",
prefix = "2022/06/",
pattern = "20220621"
)
plot(native_proxy["zos", 1:1000, 1:500, 1, 1], axes = TRUE)
}