New functionneon_cloud() leverages NEON’s migrationto Google Cloud Storage (GCS). This function provides direct access toNEON csv data without downloading the data first.
neon_table() gains the optional argumentlazy. Set to TRUE to return a “lazy” table as a dplyrconnection directly to the table induckdb. This issuitable for working with any tables that would be much to large tointeract with directly in R.
neon_index() to run on read-only filesystemsneon_store() [#50]neon_store() importterminates prematurely, [#48])show_deprecated_data(), shows which ifany local data files have been updated in the NEON API. Such files havechanged both the timestamp in their filename and changed content, andolder versions are no longer returned by the NEON API. The warning onlyappears if the deprecated data files are still available in the localstore.neon_store()) is now pluggable:you can pass any validDBIConnection to a SQL database ofyour choice in favor of the defaultduckdb connectionprovided byneon_db(). This may be valuable in cases whereconcurrent write access to the database is desired. ([#39]).zip file packaging infavor of requests to individual files. ([#34])neon_download(),neon_index(),neon_read() gain arelease argument ([#36]).Release tags associated with each file are recorded in the database, butdatabase functionsneon_store() andneon_table() do not directly filter by release tag sincethe database holds all current data.neon_download() now creates and maintains a ‘manifest’tracking the release tag associated with each file by content hash.neon_index() gains arelease column, aswell as displaying NEON’smd5 (non-AOP data) orcrc32 (AOP only) hashes recorded in the manifest. Note:With the.h5.gz files we record the hash of the compressedfile even though we don’t keep the .gz version around, which is a bit ofa slight-of-hand. This means that consecutive calls to neon_download()will no longer perform any downloads whenever the data remainsunchanged.neon_db() handle multiple connectionsbetterneon_db_dir(). Note that in multi-user environments, usersmay prefer to share a file store but utilize separate databases thatthey can write to independently.neon_read() gains the argumentkeep_filename, to always add a column with the filename ofthe original source data. Filenames may contain important metadata (suchassiteID) that is not always included in the tablesthemselves.neon_store() (somemore)neon_store()neon_store()neon_store(),neon_table(), andneon_db() (see README and docs for examples) [#23]neon_index() defaults to includehorizontalPosition andverticalPosition &samplingInterval metadata from filename for sensor data[#11]?neon_readneon_store() [#10]neon_export() andneon_import() for importing/exporting a whole neonstore[#9]neon_read() now parses additional columns intoInstrumental Systems (sensor data) by default: DomainID, SiteID,horizontalPosition, verticalPosition, and publicationDate.neonstore now handles this change.neon_read() will now check if a file requested hasidentical product, site, month, & table names. If it does, then itwill use only the more recent timestamp instead of reading the same filein twice.initial release to CRAN