You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when only MTB routes (mtb scale) enabled (menu > configure map > MTB routes > mtb scale), these two ways are displayed the same in all map styles according to map legend (https://osmand.net/docs/user/map-legend/osmand#routes). Screenshot was made in OsmAnd (default) map style
when in addition to MTB routes, cycling routes are enabled (menu > configure map > cycle routes), the second route (Dirty little secrets) is rendered differently. This is probably because of incorrect tagging: Munns track https://www.openstreetmap.org/way/245154534 has joined the relation a week ago, and it is tagged differently, than DLS.
Ahh - thankyou - can now see my lack of understanding 🤔.
Having cycling routes enabled (menu > configure map > Cycle routes)
means that the Network->lcn tag has precedence over the mtb:scale (menu > configure map >Mountain bike routes)
I created some test segments to investigate, results are:
Having both Cycling and MTB enabled yields as below, - Colour overridden if Network defined.
Deselecting Cycling and having only MTB enabled - Colour is not modified by having Network defined.
Description
Have a case where the track colour doesn't reflect mtb:scale, or mtb:scale:imba correctly
Investigation of effects shows that adding the tag pair network=lcn seems to correct to expected colour
Steps to reproduce
Observe settings for Way: Ant Logic (313202038).
Where mtb:scale and mtb:scale:imba are also set to 2
Actual result
However 'Ant Logic is rendered in pink (wrong) and 'DLS' is rendered in mauve (correct)
Expected result
Adding the tag Network=lcn seems to correct the colour to be the same (correct)
Your Environment (required)
Testing done by Exporting a small area from an edit made in JOSM, and creating an obf file via OsmMapCreator.
The text was updated successfully, but these errors were encountered: