Is there an existing issue for this?
Feature/Enhancement Proposal
Hi,
My study requires computing full origin-destination travel time and distance matrices under two routing strategies—minimizing travel time and minimizing distance—as part of a comparative accessibility analysis.
The computational pipeline uses OpenRouteService as the routing backend, with VROOM as the vehicle routing problem solver, both deployed via Docker. The R package openrouteservice is used to query the ORS matrix endpoint from within an analytical workflow. I encountered one issue that currently prevents efficient use of custom routing profiles in this research context - maximum_visited_nodes limit on the matrix endpoint not respected.
With the driving-car-shortest profile (configured with weightings: shortest and turn_costs: true, using EDGE_BASED CH preparation), any matrix request with more than approximately 10–15 total locations fails with the following: message: "Unable to compute a distance/duration matrix: Search exceeds the limit of visited nodes."
I have attempted the following fix, but it did not resolve the issue - setting maximum_visited_nodes: 1000000 under ors.endpoints.matrix in ors-config.yml.
The standard driving-car profile (EDGE_BASED CH with weightings: fastest) works correctly with blocks of 50×50 locations. The driving-car-shortest profile is limited to blocks of approximately 7×7 locations. Any help will be appreciated.
Thank you for maintaining this package and for your time.
Additional context
No response
Possible Implementation
No response
Forum Topic Link
No response
Is there an existing issue for this?
Feature/Enhancement Proposal
Hi,
My study requires computing full origin-destination travel time and distance matrices under two routing strategies—minimizing travel time and minimizing distance—as part of a comparative accessibility analysis.
The computational pipeline uses OpenRouteService as the routing backend, with VROOM as the vehicle routing problem solver, both deployed via Docker. The R package openrouteservice is used to query the ORS matrix endpoint from within an analytical workflow. I encountered one issue that currently prevents efficient use of custom routing profiles in this research context - maximum_visited_nodes limit on the matrix endpoint not respected.
With the driving-car-shortest profile (configured with weightings: shortest and turn_costs: true, using EDGE_BASED CH preparation), any matrix request with more than approximately 10–15 total locations fails with the following: message: "Unable to compute a distance/duration matrix: Search exceeds the limit of visited nodes."
I have attempted the following fix, but it did not resolve the issue - setting maximum_visited_nodes: 1000000 under ors.endpoints.matrix in ors-config.yml.
The standard driving-car profile (EDGE_BASED CH with weightings: fastest) works correctly with blocks of 50×50 locations. The driving-car-shortest profile is limited to blocks of approximately 7×7 locations. Any help will be appreciated.
Thank you for maintaining this package and for your time.
Additional context
No response
Possible Implementation
No response
Forum Topic Link
No response