In the accessibility function, max_trip_duration is set to 120 (minutes) by default. So R5 will search routes to really further away places. However, I understand that when a user sets cutoffs = 30, the max_trip_duration should automatically be affected. It seems like this is not happening.
obs. having a max_trip_duration longer than cutoffs does NOT affect accessibility estimates, but it does affect computation time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4