Open ellisvalentiner opened 5 years ago
Hi Ellis, I'm interested in working on your issue... checking out the pain points now. Have you started a repository to work on this?
Perhaps we can start a repository and invite Ian
On Mon, Apr 15, 2019 at 10:23 AM Nooreen Dabbish notifications@github.com wrote:
Hi Ellis, I'm interested in working on your issue... checking out the pain points now. Have you started a repository to work on this?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/uncoast-unconf/uu-2019/issues/10#issuecomment-483297676, or mute the thread https://github.com/notifications/unsubscribe-auth/AJeNu5-eGzDBuacz8tohzo40DTxH1prgks5vhJlZgaJpZM4bmQii .
Just to note that I had a great conversation with @ellisvalentiner on this - it's a super-interesting topic - we all just need more... time...
There are a few things I run into when I am plotting time that are much easier when plotting datetime/date data. This pain points might be specific to my work but maybe someone else is interested in these as well:
scale_*_time
with data fromstrftime
, you have to use something likelubridate::hms(strftime(x, format = "%X"))
orhms::as.hms(strftime(x, format = "%X"))
scale_*_time
limits are a numeric vector (e.g.limits = c(0, 86400)
to specify the full 24-hour day) which is not very human-readable. However for datetime/dates you can specify limits likelimits = c("2019-04-14", "2019-04-16")
. It would nice if there was something similar for time (e.g.limits = c("12:00 AM", "11:59 PM")
.scale_*_time
breaks with something likeseq(0, 86400, 60*60*4)
(every 4 hours) butscale_*_date
/scale_*_datetime
allows the user to specify breaks as a string giving the distance between breaks (e.g.2 weeks
). It would be nice if there was something similar for time (e.g.4 hours
).One suggestion is to write documentation/examples for how to do each of these things.