Feature request/roadmap inquiry: preference: "shortest" for Matrix V2

openrouteservice matrix
1

Hi openrouteservice team and community,

I’d like to ask about the availability (and roadmap) of preference: "shortest" for the Matrix V2 endpoint.

Context
I often need one‑to‑many and many‑to‑one matrices that use the same “shortest” routing logic already available in Directions V2 (as opposed to the default/recommended weighting). With Directions, we can set preference: "shortest" and get the expected behavior for single routes; we’re looking for parity on the Matrix endpoint.

Questions

  1. Is preference: "shortest" currently supported in Matrix V2 (or any equivalent — e.g., a parameter, profile setting, or custom model — that guarantees shortest‑path weighting for the matrix computation)?

  2. If not, is Matrix support for “shortest” on the roadmap? Any indicative timeline/version would help our planning.

  3. Is there a recommended workaround meanwhile to emulate “shortest” in Matrix (e.g., via configuration, custom models, or other API options)?

Thanks in advance for your guidance, and thanks for all your work on openrouteservice!

Kind regards,
Joao Martins

2

Hi Joao,

thanks for reaching out! :heart:

Unfortunately, preference = "shortest" is currently not supported by matrix and there is no workaround to force the computations with the shortest‑path weighting via a configuration hack or similar.

In fact, you are not the first one to ask about such functionality, see issue #1178. Sadly, things are taking longer than originally anticipated. For the time being I cannot give you any update on the timeline.

Cheers,
Andrzej

1 Like