Nothing
#' @export
#' @importFrom rlang .data
#'
#' @title Date filtering for \emph{mts} time series objects
#'
#' @param mts \emph{mts} object.
#' @param startdate Desired start date (ISO 8601).
#' @param enddate Desired end date (ISO 8601).
#' @param timezone Olson timezone used to interpret dates.
#' @param unit Units used to determine time at end-of-day.
#' @param ceilingStart Logical instruction to apply
#' \code{\link[lubridate]{ceiling_date}} to the \code{startdate} rather than
#' \code{\link[lubridate]{floor_date}}.
#' @param ceilingEnd Logical instruction to apply
#' \code{\link[lubridate]{ceiling_date}} to the \code{enddate} rather than
#' \code{\link[lubridate]{floor_date}}.
#'
#' @description Subsets an \emph{mts} object by date. This function
#' always filters to day-boundaries. For sub-day filtering, use
#' \code{mts_setTimeAxis()}.
#'
#' Dates can be anything that is understood by \code{MazamaCoreUtils::parseDatetime()}
#' including either of the following recommended formats:
#'
#' \itemize{
#' \item{\code{"YYYYmmdd"}}
#' \item{\code{"YYYY-mm-dd"}}
#' }
#'
#' Timezone determination precedence assumes that if you are passing in
#' \code{POSIXct} values then you know what you are doing:
#'
#' \enumerate{
#' \item{get timezone from \code{startdate} if it is \code{POSIXct}}
#' \item{use passed in \code{timezone}}
#' \item{get timezone from \code{mts}}
#' }
#'
#' @note The returned data will run from the beginning of \code{startdate} until
#' the \strong{beginning} of \code{enddate} -- \emph{i.e.} no values associated
#' with \code{enddate} will be returned. The exception being when
#' \code{enddate} is less than 24 hours after \code{startdate}. In that case, a
#' single day is returned.
#'
#' @return A subset of the incoming \emph{mts} time series object.
#' (A list with \code{meta} and \code{data} dataframes.)
#'
#' @seealso \link{mts_setTimeAxis}
#'
#' @examples
#' library(MazamaTimeSeries)
#'
#' example_mts %>%
#' mts_filterDate(
#' startdate = 20190703,
#' enddate = 20190706
#' ) %>%
#' mts_extractData() %>%
#' dplyr::pull(datetime) %>%
#' range()
#'
mts_filterDate <- function(
mts = NULL,
startdate = NULL,
enddate = NULL,
timezone = NULL,
unit = "sec",
ceilingStart = FALSE,
ceilingEnd = FALSE
) {
# ----- Validate parameters --------------------------------------------------
# A little involved to catch the case where the user forgets to pass in 'mts'
result <- try({
if ( !mts_isValid(mts) )
stop("first argument is not a valid 'mts' object")
}, silent = TRUE)
if ( class(result) %in% "try-error" ) {
err_msg <- geterrmessage()
if ( stringr::str_detect(err_msg, "object .* not found") ) {
stop(paste0(err_msg, "\n(Did you forget to pass in the 'mts' object?)"))
}
}
# Return the mts if it is empty so pipelines don't break
if ( mts_isEmpty(mts) )
return(mts)
# Remove any duplicate data records
mts <- mts_distinct(mts)
if ( is.null(startdate) && is.null(enddate) )
stop("at least one of 'startdate' or 'enddate' must be specified")
# Use internal function to determine the timezone to use
timezone <- .determineTimezone(mts, startdate, timezone, verbose = TRUE)
# ----- Get the start and end times ------------------------------------------
dateRange <- MazamaCoreUtils::dateRange(
startdate = startdate,
enddate = enddate,
timezone = timezone,
unit = "sec",
ceilingStart = ceilingStart,
ceilingEnd = ceilingEnd
)
# ----- Subset the 'mts' object ----------------------------------------------
# NOTE: When processing lots of data automatically, it is best not to stop()
# NOTE: when no data exist for a requested date range. Instead, return a
# NOTE: valid 'mts' object with zero rows of data.
if (dateRange[1] > mts$data$datetime[length(mts$data$datetime)] |
dateRange[2] < mts$data$datetime[1]) {
message(sprintf("mts does not contain the requested date range"))
data <- mts$data[0,]
} else {
data <-
mts$data %>%
dplyr::filter(.data$datetime >= dateRange[1]) %>%
dplyr::filter(.data$datetime < dateRange[2])
}
mts$data <- data
# ----- Return ---------------------------------------------------------------
return(mts)
}
Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.