diff --git a/R/recipe_sf.R b/R/recipe_sf.R index 5d9a1aa..f1da99a 100644 --- a/R/recipe_sf.R +++ b/R/recipe_sf.R @@ -4,12 +4,12 @@ #' case when `x` is an [sf::sf] object, as commonly #' used in Species Distribution Model, and generates a `spatial_recipe`. #' -#' [recipes] are not natively compatible with [sf::sf] objects. The problem is that +#' [recipes::recipe()] are not natively compatible with [sf::sf] objects. The problem is that #' the `geometry` column of [sf::sf] objects is a list, which is incompatible with -#' the translation of formulae in [recipe]. This method strips the `geometry` +#' the translation of formulae in [recipes::recipe()]. This method strips the `geometry` #' column from the [data.frame] and replaces it with a simple `X` and `Y` columns #' before any further operations, thus allowing -#' the usual processing by [recipe()] to succeed (`X` and `Y` are give the role +#' the usual processing by [recipes::recipe()] to succeed (`X` and `Y` are give the role #' of coords in a spatial recipe). When prepping and baking a `spatial_recipe`, #' if a data.frame or tibble without coordinates is used as `training` or #' `new_data`, dummy `X` and `Y` columns diff --git a/man/recipe.sf.Rd b/man/recipe.sf.Rd index a8a0968..5cca2e9 100644 --- a/man/recipe.sf.Rd +++ b/man/recipe.sf.Rd @@ -25,12 +25,12 @@ case when \code{x} is an \link[sf:sf]{sf::sf} object, as commonly used in Species Distribution Model, and generates a \code{spatial_recipe}. } \details{ -\link{recipes} are not natively compatible with \link[sf:sf]{sf::sf} objects. The problem is that +\code{\link[recipes:recipe]{recipes::recipe()}} are not natively compatible with \link[sf:sf]{sf::sf} objects. The problem is that the \code{geometry} column of \link[sf:sf]{sf::sf} objects is a list, which is incompatible with -the translation of formulae in \link{recipe}. This method strips the \code{geometry} +the translation of formulae in \code{\link[recipes:recipe]{recipes::recipe()}}. This method strips the \code{geometry} column from the \link{data.frame} and replaces it with a simple \code{X} and \code{Y} columns before any further operations, thus allowing -the usual processing by \code{\link[=recipe]{recipe()}} to succeed (\code{X} and \code{Y} are give the role +the usual processing by \code{\link[recipes:recipe]{recipes::recipe()}} to succeed (\code{X} and \code{Y} are give the role of coords in a spatial recipe). When prepping and baking a \code{spatial_recipe}, if a data.frame or tibble without coordinates is used as \code{training} or \code{new_data}, dummy \code{X} and \code{Y} columns