FreespeedFactorRoutingModule not creating NetworkRoute
Is there any reason behind FreespeedFactorRoutingModule creating a generic route instead of a NetworkRoute? We were experimenting with network-routed walk trips, so I was expecting that setting the teleportedModeFreespeedFactor would do the routing (which it does), but also write the route into the plans. All the path information to do so would be there.
-> We could change this either by default, or add a flag that allows to write out the route or not.
Second question: The FreespeedFactorRoutingModule works differently than the NetworkRoutingModule in terms of unknown links. The specific use case is with the intermodal SwissRailRaptor. Let's say all my stop facilities are connected to a network of links with the mode pt, and then I have a separate network with the mode walk. If I use networkModes="car,walk" the NetworkRoutingModule will notice that the link of the stop facility provided by SRR is not in the walk network. It then selects the closest link on the walk network. In contrary, the FreespeedFactorRoutingModule will just throw an error indicating that the link does not exist in the walk network (meaning we'd either need to move the transit stops to walk links, or build some kind of connector links between the networks).
-> Should we adapt the behaviour of the FreespeedFactorRoutingModule to the NetworkRoutingModule?
-> We could change this either by default, or add a flag that allows to write out the route or not. I would make it the default, with the possibility to disable it (that might be useful to reduce memory usage).
-> Should we adapt the behaviour of the FreespeedFactorRoutingModule to the NetworkRoutingModule? I'm in favour of this. Probably the FreespeedFactorRoutingModule was simply forgotten when the NetworkRoutingModule became multi-modal.