I'm encountering issues when generating isochrones using r5r, specifically with the WALK and TRANSIT modes. Regardless of the dataset size, approximately 40–50% of origin points fail, returning the error:
Error in r5r::isochrone(r5r_core, origins = originPoints, mode = c("WALK", : Problem in the following origin points: X, Y, Z...)
When debugging in RStudio, I noticed that even when a specific cutoff time is provided (e.g., 20 minutes), the function always generates an additional isochrone category with a 0-minute travel time. For example, in the attached screenshot, I specified a 20-minute cutoff and received 1076 results for that time range — but an unexpected second isochrone was also created for 0 minutes, with just 2 results.
This 0-minute isochrone seems problematic, as it would only include results exactly at the origin location. I suspect this phantom 0-minute isochrone might be causing many points to fail, especially if at least 3 points are needed for the isochrone to be constructed successfully.
Has anyone else encountered this behaviour? Is this a known issue or bug, and is there a recommended fix or workaround?
This seems related to issue #430.
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
