Some thoughts on rerouting – app only about brouter HOT 5 OPEN

@afischerdev thanks for the detailed description.

1 + 3 are very important as many users need routing with forward direction and use many via points.

• So now we must set engine mode 6 for rerouting and 0 for routing?

• About the heading, is nogo now added automatically?

  • Can the weight be parameter?
    (9999 may seem safer, but motor tests prefer 10000)

from brouter.

@devemux86

So now we must set engine mode 6 for rerouting and 0 for routing?

No, routing and rerouting goes as always engine mode 0
The idea behind engine mode 6 was to precalculate the RAW track to get the time benefits from this logic.

About the heading, is nogo now added automatically?

Yes

Can the weight be parameter?
(9999 may seem safer, but motor tests prefer 10000)

Could you please explain this motor tests?
The reason for the weighted nogo is to avoid entering a dead end.

from brouter.

@afischerdev

The idea behind engine mode 6 was to precalculate the RAW track to get the time benefits from this logic.

How does it work for the users, who sets the engine mode to 6?

The reason for the weighted nogo is to avoid entering a dead end.

BRouter with 9999 might return a backward route even when there is a valid forward route (returned with 10000).
Perhaps when the backward route is significantly shorter than the forward route.

At least this is what I found when I implemented nogo for heading in Cruiser (#589 (comment)).
I do not have examples right now, need to review the BRouter routing in such cases.

from brouter.

How does it work for the users, who sets the engine mode to 6?

This is not transparent for the user. It is just a call from the routing app, that started routing, to inform BRouter this is what I'm doing and please preload a RAW track.
The caller is the routing app - just inform to BRouter (BRouter has nothing to do at this time), not a must, but then the user have to wait for rerouting a longer while.

May be we find a sample on this weighted nogos later on. If the future brings us a public server with the current traffic situation for our areas.

from brouter.

This was reverted with #679

from brouter.