Request to allow for choice of routing algorithm to be used

[piyush280504]

Is there an existing issue for this?

• I have searched the existing issues

Feature/Enhancement Proposal

It would be really nice if the choice of routing algorithm is not restricted while accessing your API from the cloud. It is much easier to create an API key and access the API as compared to running my own instance. I used your API to route EV vehicles from one city to another. I could use Dijkstra by using optimized=False but I also want to try A* andd Genetic algorithms to use AI in my work.

Additional context

No response

Possible Implementation

No response

Forum Topic Link

No response

[aoles]

Thanks for reaching out!

Such functionality is not planned for the foreseeable feature, at least not until APIv3 is published.

May I ask, which ORS API endpoints and which vehicle profiles are you currently using? I think the Dijkstra routing algorithm is only used by the matrix service once optimized = false is set. The directions service uses at worst A*. Unfortunately, there is no interface to use your own routing algorithm implementations in ORS.

Cheers,
Andrzej

[piyush280504]

start = (77.2090, 28.6139) # Delhi
end = (75.5762, 31.3260) # Jalandhar
These are the end points and the vehicle profile is driving-car

[sfendrich]

To me, this sounds like two seperate things:

1. Choose algorithm in request (e.g., Dijkstra, CALT, CH, ...), which would be a relatively easy extension of the API, and
2. Extend with your own algorithm such as GA and AI, which would require major external contributions.

Both cases are unlikely to be activated on the public API for reasons of security and resource consumption.