Releases: MazamaScience/MazamaCoreUtils
Releases · MazamaScience/MazamaCoreUtils
0.6.2
0.6.1
MazamaCoreUtils 0.6.1
- Fixed
setIfNull()so that it doesn't ever convert type if the user provides
a value. - Removed the
algorithmargument fromcreateLocationID(). Now always using
geohash. - Updated documentation throughout.
- Added all lubridate functions to
timezoneLintRules. - Addressed several minor edge cases.
0.6.0
MazamaCoreUtils 0.6.0
- Refactor to use logger rather than futile.logger.
- Time stamps in log files are now vertically aligned for easier scanning.
- Additional tests of logging functionality.
0.5.3
MazamaCoreUtils 0.5.3
- The
loadDataFile()function now includes apriorityargument so that
eitherdataUrlordataDircan be prioritized with the other as a backup
if initial loading of data fails.
0.5.2
MazamaCoreUtils 0.5.2
initializeLogging()now creates aWARN.logfile to complete the suite of
TRACE,DEBUG,INFO,WARNandERROR.
0.5.1
MazamaCoreUtils 0.5.1
- Addressed CRAN check error.
- Added
precisionargument tocreateLocationID().
0.5.0
MazamaCoreUtils 0.5.0
- Updated dependencies to R 4.0.0 and rlang 1.1.0.
initializeLogging()now properly usesfilePrefixargument.- The
timeStamp()function now defaults tolubridate::now("UTC")when
nodatetimeis 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 specifiedinvalidIDfor 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
algorithmargument 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.