nnow accepts a numeric vector, instead of being restricted to a single number.
cutoffnow accepts a numeric vector, instead of being restricted to a single number.
intervalnow accepts a list of numeric vectors, instead of being restricted to a single vector.
weightscan take a
numericvectors as input, instead of being restricted to a single
NAvalues when filling missing ids (which should be filled with
Inf, since they cannot reach any opportunities). This was also responsible for the warning reported in #27, which was also fixed.
The package has been to tremendous changes. Basically, there’s not a single part of it that remained untouched: documentation, vignettes, function names, parameter names, extra functionality, performance improvements, etc. While it is impossible to highlight everything that has been done, we’ll try to summary some of the key points in the following topics.
data. Now they require two input datasets:
activenow takes a
logical, instead of a string (which
summary_functionnow takes a
function, instead of a string (which
cumulative_interval(), used to specify how many travel cost units separate the cutoffs used to calculate the accessibility estimates which will be used to calculate the summary estimate within the specified interval.
group_byparameter, that allows accessibility estimates to be grouped by one or more columns present in
cumulative_interval()) gained a
fill_missing_idsparameter, that includes in the results origins whose accessibility would be 0 but, due to some commonly overlooked implementation details, are usually left out from the output.
cumulative_interval()doesn’t have this parameter because its result will always include all origins, otherwise the summary measure wouldn’t be calculated properly.