NEON's tabular data files are separated out into separate .csv
files for each site for each month of sampling. In principle,
each file has identical columns. vroom::vroom can read in a
data table that has been sharded into many files like this much
much faster than other parsers can read in each table iteratively,
(and thus can greatly out-perform the 'stacking" methods in neonUtilities
).
Unfortunately, not all datasets are entirely consistent in their use
of columns. neon_read
works around this by parsing such tables in
groups of matching schema, which is still reasonably fast.
For convenience, neon_read
takes the name of a table in the local store.