Update from Deb Harms:

Sorry, I have been in the field. Our data editor should of caught this. It is due to a site visit. When that happens, we do not have a consistent 24hrs of readings for the midnight values. Because we have interrupted the data collection. It is not unexpected. The data editor usually catches it, but I just hired a new guy and he hasn’t gotten thru some of the edits.

This kind of error shouldn't be all that common.

Excuse me？
I'm a novice for R. I would like to use fetchSCAN to query some data but it seems a problem when using this order. I tried to solve this problem by different versions of soilDB packages (2.0-1 and 2.0-3). It didn't work.

x <- fetchSCAN(site.code=c(356, 2072), year=c(2015,2016))
Error in as.Date.default(x$Date) :
do not know how to convert 'x$Date' to class “Date”

table(x$SMS$depth)
Error in table(x$SMS$depth) : object 'x' not found

check the results

str(x, 1)
Error in str(x, 1) : object 'x' not found

Sorry to disturb you!

Thanks for reporting this, however, the specific error (a big one) is unrelated to this issue.

Fixed with 7b11d5b.

TLDR: SCAN data are now returned from the webservice with an extra line at the top of the file.

You will have to update to the latest version of soilDB, then fetchSCAN() should work as expected.

I have updated the tutorial.

Thank you so much. I appreciate it！