Make Initial Appearance of Gpx Tracks a Profile-Default

Dollarius commented 9 months ago

Describe the idea (required)

It would be nice to be able to set the default appearance of gpx tracks upon import. Every time I import a gpx file, I manually set the following track appearance according to the profile I will use it in:

Cycling: Split interval = 1km, Colour = blue, width = Medium
Hiking: Split interval = 500m, Colour = slope, Width = Thin

Tell us about the expected behaviour (required)

It would be nice if these defaults could be automatically set according to the profile upon import, so that every time a gpx is imported the wanted track appearance is automatically applied. Please note that this would not affect the specific appearance of each single track, that could be customised afterwards, but only the settings for initial appearance.

Tell us about alternatives you've considered (required)

In a past version of OsmAnd (several months ago), imported tracks were automatically inheriting the colour of the profile (i.e., Cycling = blue, Hiking = red), but this functionality has now disappeared.

Context (optional)

No response

yuriiurshuliak commented 9 months ago

The bug has been reproduced. After setting Track Appearance on iOS and transferring it to Android, all settings are saved. This means that the track will be displayed with the previously configured appearance. This appearance remains consistent across all profiles; hence, different Track Appearance settings (interval, color, width) for a single track across various profiles (Cycling, Hiking, Car) cannot be set .

OsmAnd~ 4.6.0#1126m, released: 2023-11-30

Android		iOS

Dollarius commented 9 months ago

@yuriiurshuliak thank you for checking this point! The behaviour you describe is, from my perspective, correct: each track should be allowed to have track-specific custom appearance.

My proposal is only about the DEFAULT appearance of a NEW track. I would change profile BEFORE importing a new track so that, for example:

If imported under "Cycling", it could default to: Split interval = 1km, Colour = blue, width = Medium
If imported under "Hiking", it could default to: Split interval = 500m, Colour = slope, Width = Thin

Per-track appearance should be changeable after import, and it is great that is saved into the file. I modified my original post to include this point.

DmitryAlexei commented 8 months ago

To summarize:

when you import a track, it retains its appearance, no matter using which profile you will import it
there is no dialogue about the specific appearance depending on the profile when importing a track
it seems possible to customize the track appearance in the Configure map menu for each profile - see screenshot - but it doesn't work that way
configured in one profile, track appearance remains consistent across all profiles
the track appearance, configured in Browse map profile, can be changed in, for example, in driving profile

latest nightly	4.3.12

Dollarius commented 8 months ago

Let me re-describe my intended behaviour with also a screenshot:

BEFORE importing a gpx track, select the profile of use (cycling/hiking, in my case)
Import the gpx and get the "profile defaults" automatically applied to it (i.e., cycling: 1km splits, blue, medium thickness; hiking: 500m splits, slope, thin thickness)
Allow extra customisation of the track, if necessary (sometimes it is useful to have different colours for different tracks)
Retain the track-specific appearance in all profiles, also if enabling/disabling the track.

The new step is ONLY 2. Please note that a similar behaviour for colour/thickness (not for the splits) was already possible up to few months ago, but it has been removed in the latest versions. Point 1. is my proposed workflow: choose the profile "for which" the track will be used befor importing, and the track will get the profile defaults applied upon import. Points 3. and 4. are the current behaviour, which is OK in my opinion.

The "change appearance" pointed out by @DmitryAlexei is to modify many tracks at the same time, AFTER import, which is not the point of my suggestion.

DmitryAlexei commented 6 months ago

This issue seems closely related with https://github.com/osmandapp/OsmAnd/issues/16943. The last one will be implemented in the nearest future.

osmandapp / OsmAnd