openrouteservice | 🌍 The open source route planner api with plenty of features | REST library

openrouteservice directions format is not identical to OSRM, so you cannot use OSRMRoadManager. If you really - really - want to use openrouteservice, you will have to develop corresponding openrouteserviceRoadManager.

Alternative: use one among the 3 routing services already accessible with OBP. Pros and cons here.

You need to add a return statement like this:

url encoded arguments should be in the function arguments :

The @Output and @Input directives are only for Components. In order to exchange data between components via a service you have to use Dependency Injection.

So in both your Components you have to inject your Service:
constructor(private apiService: ApiService)

Since your data is coming asynchronous via the httpClient, you will have to use the Observable in your components. Instead of subscribing to it in your service and returning the subscription you can return the observable itself and subscribe to it in your components.

use request.args.get to read the parameter

eg to get the api_key

The API is expecting a JSON object, representing an array of arrays of double values, as the content of the HttpRequest, encoded as an UTF-8 string, sent as a byte array.

This collection can be represented by a List(Of List(Of Double) Property Type of a .Net class:

Solved by creating a new instance of the Directions object each call:

Use a generator/converter to generate Json Classes eg: https://json2csharp.com/

Sample code:

This will be an inherently slow process. If you have 10,000 locations and they are all far apart from each other, then you need to download and model 10,000 local street networks to calculate accessibility around each point. This means 10,000 server calls and data downloads and graph building and topology cleaning, etc, etc.

Accordingly, 100 rows in 3 minutes seems pretty fast to me, especially considering that it means you can complete all 10,000 rows in ~300 minutes (i.e., 5 hours) given your estimated timings. Just start the process before you go to bed, and when you wake up it'll be done. This assumes that this is a one-off computation that needn't be recomputed frequently.

The other alternative would be to parallelize it by dividing it up among say 10 containers or processes, each of which tackles 1,000 locations. This would finish in ~30 minutes, given your estimated timings.

Last question, what are the limitations of OSMnx request, especially for large data ?

The limitation for working with massive network models with OSMnx is the amount of RAM on your computer.