-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use generic CSV parser #1
Comments
Ok, thanks. Currently the data is being parsed through an awkward combination of non-general control flow. It works, but only for one value column and I'm not capturing the column name at present. |
Brain storm
Where the first column is parsed as a Calendar object. Should I open an issue? |
If we start to do automatic time series conversion, I think we shouldn't hardcore which columns are time series, but either (a) guess from the inputs or (b) require that a list of column names be specified by the user. |
> args(read.zoo)
function (file, format = "", tz = "", FUN = NULL, regular = FALSE,
index.column = 1, drop = TRUE, FUN2 = NULL, split = NULL,
aggregate = FALSE, ..., text) The |
The Currently, |
We still need to finish integrating a generic CSV parser into Base, but it seems that you'd be better off using a general-purpose parser than doing comma-splitting by hand. There's probably a while before the generic parser works well enough for your use, but I thought it would be good to raise the idea now while you're working on your package.
The text was updated successfully, but these errors were encountered: