|
1 | 1 | ## R CMD check results
|
2 | 2 |
|
3 |
| -── R CMD check results ───────────────────────────────────────────── r5r 1.1.0 ──── |
4 |
| -Duration: 24m 8.8s |
| 3 | +── R CMD check results ──────────────────────────────────────── r5r 2.0 ──── |
| 4 | +Duration: 29m 21.6s |
5 | 5 |
|
6 | 6 | 0 errors ✔ | 0 warnings ✔ | 0 notes ✔
|
7 | 7 |
|
8 |
| -* This is a minor update with bug fixes |
9 | 8 |
|
| 9 | +**Breaking changes** |
| 10 | + |
| 11 | +- r5r uses now JDK 21 or higher (Breaking changes). Closed [#350](https://github.com/ipeaGIT/r5r/issues/350). |
| 12 | +- r5r now uses the latest version of R5 V7.1. Closed [#350](https://github.com/ipeaGIT/r5r/issues/350) |
10 | 13 |
|
11 | 14 | **Major changes**
|
12 | 15 |
|
13 |
| -- New `isochrone()`function. Closes [#123](https://github.com/ipeaGIT/r5r/issues/123), and addresses requrests in issues [#164](https://github.com/ipeaGIT/r5r/issues/164) and [#328](https://github.com/ipeaGIT/r5r/issues/328). |
14 |
| -- New vignette about calculating / visualizing isochrones with `r5r`. |
15 |
| -- New vignette with responses to frequently asked questions (FAQ) from `r5r` users. |
| 16 | +- r5r now stores R5 Jar file at user dir using `tools::R_user_dir()` |
| 17 | +- New function `r5r_cache()` to manage the cache of the R5 Jar file. |
| 18 | +- By using the JDK 21, this version of r5r also fixed an incompatibility with MAC ARM processors. Closed [#315](https://github.com/ipeaGIT/r5r/issues/315) |
16 | 19 |
|
17 | 20 | **Minor changes**
|
18 | 21 |
|
19 |
| -- The default value of `time_window` is not set to `10` minutes in all functions to avoid weird results reported upstream in R5. Closes [#342](https://github.com/ipeaGIT/r5r/issues/342). |
20 |
| -- Removed any mention to `percentiles` parameter in the `expanded_travel_time_matrix()` because this function does not expose this parameter to users. Closes [#343](https://github.com/ipeaGIT/r5r/issues/343). |
21 |
| -- Updated vignette on calculating / visualizing accessibility with `r5r`. |
| 22 | +- In the `accessibility()` function, the value of `max_trip_duration` is now capped by the max value passed to the `cutoffs` parameter. Closes [#342](https://github.com/ipeaGIT/r5r/issues/348). |
| 23 | +- Updated documentation of parameter `max_walk_time` to make it clear that in walk-only trips, whenever `max_walk_time` differs from `max_trip_duration`, the lowest value is considered. Closes [#353](https://github.com/ipeaGIT/r5r/issues/353) |
| 24 | +- Updated documentation of parameter `max_bike_time` to make it clear that in bicycle-only trips, whenever `max_bike_time` differs from `max_trip_duration`, the lowest value is considered. Closes [#353](https://github.com/ipeaGIT/r5r/issues/353) |
| 25 | +- Improved documentation of parameter `suboptimal_minutes` in the `detailed_itineraries()` function. |
| 26 | +- Updated the vignette on time window to explain how this parameter behaves when used in the `detailed_itineraries()` function. |
| 27 | + |
| 28 | +**Bug Fixes** |
| 29 | +- Fixed bug that prevented the use the `output_dir` parameter in the `detailed_itineraries(all_to_all = TRUE)` function. Closes [#327](https://github.com/ipeaGIT/r5r/issues/327) with a contribution ([PR #354](https://github.com/ipeaGIT/r5r/pull/354)) from Luyu Liu. |
| 30 | +- Fixed bug that prevented `detailed_itineraries` from working with frequency-based GTFS feeds. It should ONLY work with frequency-based GTFS feeds. |
22 | 31 |
|
| 32 | +**New contributors to r5r** |
| 33 | +- [Luyu Liu](https://github.com/luyuliu) |
0 commit comments