From fbe681918cdae26519ae2140bb12dfcdc4e2d366 Mon Sep 17 00:00:00 2001 From: Daniel Herszenhut Date: Wed, 10 Aug 2022 15:04:51 -0300 Subject: [PATCH] bump dev version --- DESCRIPTION | 2 +- NEWS.md | 8 ++++++++ codemeta.json | 4 ++-- vignettes/accessibility.Rmd | 22 ++++++++++++---------- vignettes/decay_functions.Rmd | 5 +++-- 5 files changed, 26 insertions(+), 15 deletions(-) diff --git a/DESCRIPTION b/DESCRIPTION index 9aa26f8..53e0e05 100644 --- a/DESCRIPTION +++ b/DESCRIPTION @@ -1,7 +1,7 @@ Type: Package Package: accessibility Title: Transport Accessibility Measures -Version: 1.0.09 +Version: 1.0.0.9000 Authors@R: c( person("Rafael H. M.", "Pereira", , "rafa.pereira.br@gmail.com", role = "aut", comment = c(ORCID = "0000-0003-2125-7465")), diff --git a/NEWS.md b/NEWS.md index 8bfd38e..23e16de 100644 --- a/NEWS.md +++ b/NEWS.md @@ -1,3 +1,11 @@ +# accessibility (development version) + +## New features + +## Bug fixes + +## Notes + # accessibility 1.0.0 The package has been to tremendous changes. Basically, there's not a single diff --git a/codemeta.json b/codemeta.json index acc1b44..4225a7a 100644 --- a/codemeta.json +++ b/codemeta.json @@ -7,7 +7,7 @@ "codeRepository": "https://github.com/ipeaGIT/accessibility", "issueTracker": "https://github.com/ipeaGIT/accessibility/issues", "license": "https://spdx.org/licenses/MIT", - "version": "1.0.0", + "version": "1.0.0.9000", "programmingLanguage": { "@type": "ComputerLanguage", "name": "R", @@ -187,7 +187,7 @@ }, "SystemRequirements": null }, - "fileSize": "1893.881KB", + "fileSize": "1893.982KB", "releaseNotes": "https://github.com/ipeaGIT/accessibility/blob/master/NEWS.md", "readme": "https://github.com/ipeaGIT/accessibility/blob/main/README.md", "contIntegration": ["https://github.com/ipeaGIT/accessibility/actions", "https://app.codecov.io/gh/ipeaGIT/accessibility?branch=main"], diff --git a/vignettes/accessibility.Rmd b/vignettes/accessibility.Rmd index 1f7d137..6dc6127 100644 --- a/vignettes/accessibility.Rmd +++ b/vignettes/accessibility.Rmd @@ -63,7 +63,8 @@ You may have noticed that we've mentioned a few times that the functions calculate accessibility using travel *cost*, and not travel *time*. That's because we're treating *costs* here in its generic sense: anything that increases the impedance from an origin to a destination, such as travel time, -monetary costs, distances, risk perception, etc., can be considered a generic *cost*. +monetary costs, distances, risk perception, etc., can be considered a generic +*cost*. The `gravity()` and `floating_catchment_area()` functions can use different decay functions when estimating accessibility levels. These decay @@ -198,13 +199,13 @@ to calculate both active and passive accessibility. ## Interval-based cumulative opportunities `cumulative_time_interval()` calculates the interval-based cumulative -opportunities measure. This measure, developed by @tomasiello2022interval, mitigates the impacts of arbitrary choices of cost -cutoffs, one of the main disadvantages of the traditional threshold-based -cumulative opportunities measure. Given a cost interval, it calculates several -accessibility estimates within the interval and summarizes it using a -user-specified function. In the example below, we calculate the average number -of accessible jobs considering multiple minute-by-minute time thresholds -between 40 and 60 minutes. +opportunities measure. This measure, developed by @tomasiello2022interval, +mitigates the impacts of arbitrary choices of cost cutoffs, one of the main +disadvantages of the traditional threshold-based cumulative opportunities +measure. Given a cost interval, it calculates several accessibility estimates +within the interval and summarizes it using a user-specified function. In the +example below, we calculate the average number of accessible jobs considering +multiple minute-by-minute time thresholds between 40 and 60 minutes. ```{r, message = FALSE} cum_interval <- cumulative_interval( @@ -281,8 +282,9 @@ head(bfca) ## Visualize results -If you have the spatial data of your origins/destinations you can easily merge it with the accessibility to create spatial visualizations of the results. -The example below quickly shows how to create a simple map using `{ggplot2}`. +If you have the spatial data of your origins/destinations you can easily merge +it with the accessibility to create spatial visualizations of the results. The +example below quickly shows how to create a simple map using `{ggplot2}`. ```{r, eval = requireNamespace(c("sf", "ggplot2"), quietly = TRUE), out.width = "80%", fig.width = 6, fig.height = 6} grid <- system.file("extdata/grid_bho.rds", package = "accessibility") diff --git a/vignettes/decay_functions.Rmd b/vignettes/decay_functions.Rmd index 2edc4db..dd7b60a 100644 --- a/vignettes/decay_functions.Rmd +++ b/vignettes/decay_functions.Rmd @@ -21,7 +21,8 @@ continuously discount the weight of opportunities as travel costs become larger. For convenience, the package ships with some of the most frequently used functions in the accessibility literature, which are discussed below. Additionally, users can pass custom functions to convert travel costs into -weights to be applied the opportunities, which is discussed further down in this the vignette. +weights to be applied the opportunities, which is discussed further down in +this the vignette. # Currently available decay functions @@ -235,6 +236,6 @@ calculates travel costs exactly as we want. When we create our own custom decay function, we don't have to think about general cases, just the cases that matter for us. Creating a simple function -that converts one vector into another, therefore, suffices our for needs. In both +that converts one vector into another, therefore, suffices our needs. In both examples above, therefore, we're passing a function to `decay_function` - one we created ourselves and another created by `decay_power()`.