Fixes #121

[tomschenkjr]

• Add ability to handle date/time formats as YYYY-MM-DDTHH:MM:SS -- fixes NA's from date fields when reading JSON's #121
• If the date/time format is not properly converted, RSocrata returns the data as chr strings instead of NA. This will let the user manually convert if necessary and will reduce the severity of errors like these in the future (there are several date formats we are not handling right now)
• A warning has been added to alert users they will not have a POSIX-formatted column.

[coveralls]

Coverage increased (+0.2%) to 96.407% when pulling b0ce826 on issue121 into 7714a0e on master.

[geneorama]

@tomschenkjr I'm curious why this change incremented the dependency from R 3.0 to R 3.1

[tomschenkjr]

The `anyNA()` function became available in 3.1 https://journal.r-project.org/archive/2014-1/r-changes.pdf While the function itself is simple and we can replicate it (http://www.renjin.org/blog/2015-12-30-a-critical-look-at-the-anyna-function-in-r.html), 3.1 seems old enough where it is unlikely to impact users. _ Tom Schenk Jr. Chief Data Officer Department of Innovation and Technology City of Chicago (312) 744-2770 tom.schenk@cityofchicago.org | @ChicagoCDO data.cityofchicago.org | opengrid.io | digital.cityofchicago.org | chicago.github.io | dev.cityofchicago.org On Fri, Mar 3, 2017 at 10:41 AM -0600, "Gene Leynes" <notifications@github.com<mailto:notifications@github.com>> wrote: @geneorama commented on this pull request.

________________________________ In DESCRIPTION<#123 (comment)>:

Author: Hugh Devlin, Ph. D., Tom Schenk, Jr., and John Malc

Maintainer: "Tom Schenk Jr." <developers@cityofchicago.org> Depends: - R (>= 3.0.0) + R (>= 3.1.0) @tomschenkjr<https://github.com/tomschenkjr> I'm curious why this change incremented the dependency from R 3.0 to R 3.1 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#123 (review)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ABkC0Vno1Gkl1uSA3OnpyVWp6ho34Or8ks5riELAgaJpZM4MK0c3>.

…

________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail (or the person responsible for delivering this document to the intended recipient), you are hereby notified that any dissemination, distribution, printing or copying of this e-mail, and any attachment thereto, is strictly prohibited. If you have received this e-mail in error, please respond to the individual sending the message, and permanently delete the original and any copy of any e-mail and printout thereof.