On 25 April 2017 at 18:05, Duncan Murdoch wrote:
| On 25/04/2017 5:41 PM, Dirk Eddelbuettel wrote:
| >
| > On 25 April 2017 at 16:04, Jeff Reichman wrote:
| > | R Users
| > |
| > | Having problems converting the following DTG into an R recognized
date/time
| > | field
| > |
| > | 01-01-2016T14:02:23.325
| > |
| > | Would I separate it into a date field and time filed then put it back
| > | together???
| >
| > The anytime package (on CRAN) does this (and other date or datetime input
| > variants) without requiring a format:
| >
| > R> library(anytime)
| > R> anytime("01-01-2016T14:02:23.325")
| > [1] "2016-01-01 14:02:23.325 CST"
|
| How does it decide between MDY and DMY orderings in dates? Doesn't
| matter for this example, but it would for "01-02-2016T14:02:23.325"
See
http://dirk.eddelbuettel.com/code/anytime.html
https://github.com/eddelbuettel/anytime
https://github.com/eddelbuettel/anytime/blob/master/src/anytime.cpp#L43-L106
for overview(s), some comments, notes and in particular the set of formats.
It has a strong preference for sane (ie ISO formats) but in the case of
ambiguity it (grudingly) prefers the (silly) US way:
R> anytime("01-02-2003")
[1] "2003-01-02 CST"
R>
But I try not to miss an opportunity that the format should really not be used.
Dirk
--
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
______________________________________________
R-help@r-project.org mailing list -- To UNSUBSCRIBE and more, see
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.
