Change of the meaning for 'dynamic range'

[afischerdev]

The dynamic range was introduced with PR #729 and #747 and enabled the issue #387 - this also carries the description.

The work on the round trip (#759) shows that the dynamic range could be useful in other contexts as well.

But this reduces the meaning to the original meaning of the words:
find the next point that is connected to a way.

The current meaning has the addition
and add a beeline

To play with the problem I added a test library to the test server.

New is the parameter for the profile in global section:

assign add_beeline          = true    # default is false

Please see this sample 2 points or sample 3 points

Now if you add the new beeline parameter above, you will see it in the result.

To get all examples used in #387 running there is one more parameter:

# car profile
assign use_offroad          = true       # default is false

This is because we used use_dynamic_range also to enable some other roads

assign caraccess ...
    switch and highway=track use_offroad     1
    switch and highway=road use_offroad      1

Should be clearer now.

[devemux86]

@afischerdev Thanks, very nice improvement. 👍

Will you also include it in a pull request?

[afischerdev]

@devemux86
Yes, that is the plan. Because it is also needed for roundtrip #759 to avoid ambiguity.

But there should be a little time for testing.