Releases: MazamaScience/MazamaCoreUtils
Releases · MazamaScience/MazamaCoreUtils
0.5.3
0.5.2
MazamaCoreUtils 0.5.2
initializeLogging()
now creates aWARN.log
file to complete the suite of
TRACE
,DEBUG
,INFO
,WARN
andERROR
.
0.5.1
MazamaCoreUtils 0.5.1
- Addressed CRAN check error.
- Added
precision
argument tocreateLocationID()
.
0.5.0
MazamaCoreUtils 0.5.0
- Updated dependencies to R 4.0.0 and rlang 1.1.0.
initializeLogging()
now properly usesfilePrefix
argument.- The
timeStamp()
function now defaults tolubridate::now("UTC")
when
nodatetime
is provided. This supports common use cases such as:
> timeStamp(unit = "hour")
[1] "2023102618"
> timeStamp(style = "clock")
[1] "2023-10-26T18:25:55"
- Updated imports from futile.logger to avoid error messages like this:
WARN [2023-08-29 14:06:58] Oops: object 'flog.appender' not found
- Added
createLocationMask()
to identify invalid locations. createLocationID()
now defaults toalgorithm = "geohash"
.createLocationID()
now returns the user specifiedinvalidID
for invalid
locations rather than stopping with an error message.
0.4.16
MazamaCoreUtils 0.4.16
- Addressed CRAN package documentation issue.
0.4.15
MazamaCoreUtils 0.4.15
parseDatetime()
now supports data formats with UTC offset: "2018-10-16 12:00:00+00:00".
0.4.14
MazamaCoreUtils 0.4.14
- Added
algorithm
argument tocreateLocationID()
to select between "digest"
and "geohash".
The "geohash" algorithm is preferred but the "digest" algorithm is retained (and the default) because several existing databases use the "digest" algorithm as a unique identifier.
0.4.13
MazamaCoreUtils 0.4.13
- Updated
stopOnError()
function documentation and associated vignette.
0.4.12
MazamaCoreUtils 0.4.12
- Updated
stopOnError()
with the following additional arguments:prefix
,
code
,maxLength
,truncatedLength
,call.
. - Corrected documentation for
timeStamp()
.
0.4.11
MazamaCoreUtils 0.4.11
- Changed examples in
html_getLinks()
andhtml_getTables()
to explain any
errors with:try({ ... }, silent = FALSE)
.