App: Multiple route profiles

thanks for your consideration. yes I agree it would make things complicated.

I need to do some more reading to understand how the profiles and the avoidances relate to each other.

In Kurviger 2.0.11 (Beta) the route color is used in navigation.
(the multiple profile colors are used in route planning)

A simple workflow for more freedom with future improvements:

Perhaps it would be better to change Settings ¦ Routing ¦ Route color to “Route color in navigation mode”, German : “Routenfarbe im Navigationsmodus”.

My first search for this setting started in Settings ¦ Navigation, because this option has only influence on navigation mode. Therefore I thought that it would be useful to shift that option to Navigation.

Meanwhile I am not sure - this setting is similar to the other color settings, so perhaps the placement in “Routing” might be better…

In addition, it is a shared option available to unsubscribed users too.

I wrote a post concerning adding waypoints to routes with multiple routing profiles in March 2021 in the lounge (restricted access): https://forum.kurviger.de/t/kurviger-2-0-6-beta/5043/85?u=rumbrummer

Due to restricted access I copy it here:

If I add a waypoint to a route with multiple routing profiles, on website the new waypoint gets the profile of the segment where it is inserted ( :+1:).
In the app the new waypoint seems to get the main profile set in routing options - from my point of view it would be better also to use the system of the website.
Example:

The base route segment from viapoint #1 to shapingpoint #2 has the profile “curvy” - so after inserting the new viapoint #2 the segments from viapoint #1 to viapoint #2 and from viapoint #2 to shaping point #3 should be both curvy (as on website) - but in app the segment from viapoint #1 to new viapoint #2 has the profile “fastest”.

This topic has been solved, I tested it in March and wrote a comment (https://forum.kurviger.de/t/kurviger-2-0-6-beta/5043/93?u=rumbrummer). I also tested the case in the link above just now - it still works fine, also in app!

But now I have an other case, where website works well, but - from my point of view - app does not:

Base (Routing: Curvy, but Routing profile of 1st and only segment: Fastest):

Add shapingpoint in app → 1st segment “curvy” (but should be “fastest”), 2nd segment “fastest”:

Base, add shaping point on website → both segments “fastest” :+1: :

I use Kurviger 2.0.11 app (with subscription) and Kurviger Tourer on website.

1 Like

Implemented in Kurviger 2.0.12.

Thanks for the report, I will check it.

1 Like

There was a missing check, it will work as you describe in next app update.

1 Like

Improved implementation in Kurviger 2.0.13.

1 Like

Thanks - works correctly also on my device :+1:

1 Like