@c-voulgaris and I were just troubleshooting a travel-time matrix computation that was giving an out of bounds error here—saying that j was out of bounds for travel_times. It turned out the issue was that everything in this analysis was unreachable and unlinked (because the input data were in projected coordinates rather than lat-lon). I'm not exactly sure why this caused the out-of-bounds error, but maybe r5 short-circuits internally in this situation and returns an unexpected result. In any case, we should handle this case gracefully.
I'm also confused as to why the loop on the above-linked line starts from 3.
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