O/D Matrix - Network search always optimizes for “Total cost”, ignoring selected criteria

[aiAdrian]

What is the input mode?

Mouse

What type of issue is it?

Functionality

What happened?

The shortest path (network search) currently runs exclusively using the criterion “Total cost”.
The shortest “Travel time” or “Number of transfers” are merely derived from that result, but can't be used as cost function.

This leads to edge cases such as the following:
The travel chain ZF → GD via BAA is faster (5 minutes / Connection time at BAA OK) than the “direct” ZF → GD connection (6 minutes).
However, when the filter is set to “Travel time”, this faster option is not shown, because the “best connection” is still defined by Total cost.

Additionally, the color coding of the individual O–D Matrix cells is also based on Total cost, regardless of which criterion the user selected.

Solution: The search logic and color coding must respect the user‑selected criterion (Travel time, Transfers, Total cost).

What did you expect to happen?

The business owner like to change with the right down button the travel cost:

• total cost
• real travel time
• number of changes

Thus the botton-left button -> changes the O/D Matrix cost (-> when switching: re-compute)

Thus the top-right button -> changes the O/D Matrix display (color and text)

How can we reproduce it (as minimally and precisely as possible)?

networkGraphic (12).json

chrome-capture-2026-02-19.10.webm

On which environments the bug occurs?

Local

On which browser the bug occurs?

Firefox

Netzgrafik-Editor version (top left corner Version x.yy.zz)

2.10.15

[shenriotpro]

That sounds like a feature to me.

Here's how I would approach it

• real travel time: set connectionPenalty to 0 https://github.com/OpenRailAssociation/netzgrafik-editor-frontend/blob/main/src/app/services/analytics/origin-destination/components/origin-destination.service.ts#L67
• number of changes: set cost to 1 for connection edges, 0 elsewhere

  netzgrafik-editor-frontend/src/app/view/util/origin-destination-graph.ts

  Line 397 in a32cacc

  const edge = new Edge(arrival, departure, cost);

  (there's a simpler algorithm, but we probably don't want to extract a less generic version)

re: colors, did you try the selector on the right hand side?

[aiAdrian]

I fully understand your point. This means we suggest to switch this user reported bug into a feature. Then we can simply close this bug and we will add a new feature request.

I understand the user perspective what they like to get. Thus the value is given and we should implement this new approach.