NEON products consist of several individual components, which are in turn broken up by site and sampling month. By storing these individual files, neonstore enables more reproducible workflows that can be traced back to original, unaltered input data. These atomized files can be quickly and easily combined into unified tables, see neon_read.
neon_index(
product = NA,
table = NA,
site = NA,
start_date = NA,
end_date = NA,
type = NA,
ext = NA,
hash = NULL,
dir = neon_dir()
)
Include only files matching this NEON productCode(s)
Include only files matching this table name (or regex pattern). (optional).
4-letter site code(s) to filter on. Leave as NA
to search all.
Download only files as recent as (YYYY-MM-DD
). Leave
as NA
to download up to the most recent available data.
Download only files up to end_date (YYYY-MM-DD
). Leave as
NA
to download all prior data.
Should we prefer the basic or expanded version of this product? See details.
only match files with this file extension(s)
name of a hashing algorithm to check file integrity. Can be
"md5"
, "sha1"
, or "sha256"
currently; or set to NULL (default)
to skip hash computation.
Location where files should be downloaded. By default will
use the appropriate applications directory for your system
(see rappdirs::user_data_dir). This default also be configured by
setting the environmental variable NEONSTORE_HOME
, see Sys.setenv or
Renviron.
File names include metadata such as the file productCode,
table name, site, and sampling month, as well as timestamp of creation.
neon_index()
parses this metadata from the file name string and returns
the information in a convenient table, along with a path to each file.
# NOT RUN {
# }
# NOT RUN {
neon_index()
## Just bird survey product
neon_index("DP1.10003.001")
# }
# NOT RUN {
# }
Run the code above in your browser using DataLab