Closed dschlaep closed 2 months ago
Thanks very much for reporting , reprex, and finding a solution @dschlaep. Your fix works for me and is implemented in 03ba0b1e
Thanks for the notification. I'll take a look into it further this afternoon, and let the SCAN folks know the mayhem created by unannounced changes.
Many thanks for fixing this so fast!
Yes, that was fast! Thanks @brownag
It appears that the format of the SCAN data has changed (again). The call by
soilDB:::.get_SCAN_data()
to obtain column headers no longer works correctly. This https://github.com/ncss-tech/soilDB/blob/3ed0bd5b704ce5da5a9e01ff8d399940d9a9974c/R/fetchSCAN.R#L388now results (after further processing) in h being
"California"
(instead of a vector of column names).Then,
names(x) <- h
sets all but the first name toNULL
. And finally,x$Date
ends up beingNULL
which causes the new error "replacement has 0 rows, data has 367".It appears that skipping 5 instead of 3 lines is now required to obtain column headers (see example code below).
Thanks!
Created on 2024-05-17 with reprex v2.1.0