You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lubridate is an extremely good package for handling dates and date conversion. However, it does not accept perhaps one of the most common forms of date data: dates from Excel. Thankfully, many Excel-file-reading functions do this conversion for you, but when they don't it's always one more time Googling to figure out how to convert properly (or, worse, not realizing how oddly Excel handles dates and getting things 70 years off).
The actual task here is very easy, since it just requires setting origin = "1899-12-30". There are many ways this could be implemented, but one simple approach would be, since there is already lubridate::origin, to also have lubridate::excel_origin set to as.POSIXct('1899-12-30').
Maybe this is a bit left-field, but after Googling the correct date for the fiftieth time it occurs to me that this would be a useful convenience function.
The text was updated successfully, but these errors were encountered:
but when they don't it's always one more time Googling to figure out how to convert properly (or, worse, not realizing how oddly Excel handles dates and getting things 70 years off).
I don't particularly mind having excel_origin in the package, but the actual use case is not clear to me. How exactly is supposed that value to help and in which circumstances?
but when they don't it's always one more time Googling to figure out how to convert properly (or, worse, not realizing how oddly Excel handles dates and getting things 70 years off).
I don't particularly mind having excel_origin in the package, but the actual use case is not clear to me. How exactly is supposed that value to help and in which circumstances?
The use case is when you have a data file that, upon import, gives Excel-date-format-integers for numbers (i.e. 45123 or '45123') instead of dates. This sometimes occurs when reading in Excel data directly, or if a file passed through Excel at some point and was exported to another format that did not preserve the date formatting of the date column. I run into this quite frequently when using Excel sheets or CSVs prepared by others or downloaded from the internet.
lubridate is an extremely good package for handling dates and date conversion. However, it does not accept perhaps one of the most common forms of date data: dates from Excel. Thankfully, many Excel-file-reading functions do this conversion for you, but when they don't it's always one more time Googling to figure out how to convert properly (or, worse, not realizing how oddly Excel handles dates and getting things 70 years off).
The actual task here is very easy, since it just requires setting
origin = "1899-12-30"
. There are many ways this could be implemented, but one simple approach would be, since there is alreadylubridate::origin
, to also havelubridate::excel_origin
set toas.POSIXct('1899-12-30')
.Maybe this is a bit left-field, but after Googling the correct date for the fiftieth time it occurs to me that this would be a useful convenience function.
The text was updated successfully, but these errors were encountered: