1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
|
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/geodist.R
\name{step_geodist}
\alias{step_geodist}
\alias{tidy.step_geodist}
\title{Distance between two locations}
\usage{
step_geodist(
recipe,
lat = NULL,
lon = NULL,
role = "predictor",
trained = FALSE,
ref_lat = NULL,
ref_lon = NULL,
log = FALSE,
name = "geo_dist",
columns = NULL,
skip = FALSE,
id = rand_id("geodist")
)
\method{tidy}{step_geodist}(x, ...)
}
\arguments{
\item{recipe}{A recipe object. The step will be added to the
sequence of operations for this recipe.}
\item{lon, lat}{Selector functions to choose which variables are
affected by the step. See selections() for more details.}
\item{role}{or model term created by this step, what analysis
role should be assigned?. By default, the function assumes
that resulting distance will be used as a predictor in a model.}
\item{trained}{A logical to indicate if the quantities for
preprocessing have been estimated.}
\item{ref_lon, ref_lat}{Single numeric values for the location
of the reference point.}
\item{log}{A logical: should the distance be transformed by
the natural log function?}
\item{name}{A single character value to use for the new
predictor column. If a column exists with this name, an error is
issued.}
\item{columns}{A character string of variable names that will
be populated (eventually) by the \code{terms} argument.}
\item{skip}{A logical. Should the step be skipped when the
recipe is baked by \code{\link[=bake.recipe]{bake.recipe()}}? While all operations are baked
when \code{\link[=prep.recipe]{prep.recipe()}} is run, some operations may not be able to be
conducted on new data (e.g. processing the outcome variable(s)).
Care should be taken when using \code{skip = TRUE} as it may affect
the computations for subsequent operations}
\item{id}{A character string that is unique to this step to identify it.}
\item{x}{A \code{step_geodist} object.}
\item{...}{One or more selector functions to choose which
variables are affected by the step. See \code{\link[=selections]{selections()}}
for more details. For the \code{tidy} method, these are not
currently used.}
}
\value{
An updated version of \code{recipe} with the new step added
to the sequence of existing steps (if any). For the \code{tidy}
method, a tibble with columns echoing the values of \code{lat},
\code{lon}, \code{ref_lat}, \code{ref_lon}, \code{name}, and \code{id}.
}
\description{
\code{step_geodist} creates a \emph{specification} of a
recipe step that will calculate the distance between
points on a map to a reference location.
}
\details{
\code{step_geodist} will create a
}
\examples{
library(modeldata)
data(Smithsonian)
# How close are the museums to Union Station?
near_station <- recipe( ~ ., data = Smithsonian) \%>\%
update_role(name, new_role = "location") \%>\%
step_geodist(lat = latitude, lon = longitude, log = FALSE,
ref_lat = 38.8986312, ref_lon = -77.0062457) \%>\%
prep(training = Smithsonian)
bake(near_station, new_data = NULL) \%>\%
arrange(geo_dist)
tidy(near_station, number = 1)
}
\concept{preprocessing}
\keyword{datagen}
|
