Skip to content

Commit

Permalink
bump dev version
Browse files Browse the repository at this point in the history
  • Loading branch information
dhersz committed Aug 10, 2022
1 parent 294c5e2 commit fbe6819
Show file tree
Hide file tree
Showing 5 changed files with 26 additions and 15 deletions.
2 changes: 1 addition & 1 deletion DESCRIPTION
Original file line number Diff line number Diff line change
@@ -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", , "[email protected]", role = "aut",
comment = c(ORCID = "0000-0003-2125-7465")),
Expand Down
8 changes: 8 additions & 0 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -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
Expand Down
4 changes: 2 additions & 2 deletions codemeta.json
Original file line number Diff line number Diff line change
Expand Up @@ -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",
Expand Down Expand Up @@ -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"],
Expand Down
22 changes: 12 additions & 10 deletions vignettes/accessibility.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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(
Expand Down Expand Up @@ -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")
Expand Down
5 changes: 3 additions & 2 deletions vignettes/decay_functions.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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()`.

0 comments on commit fbe6819

Please sign in to comment.