Track Route on Smartwatch are too thick

Johannes Waldmüller shared this idea ago

Gathering feedback

I have a Smartwatch (Casio WSD F20) and navigate with it. Your Smartwatch app is really great!

Though if I look on my watch, it seems that the selected route and the recorded track lines are much too thick. They overlap other information. In my opinion there is no need for that thick lines. If they were thinner they still can be clearly seen.

Especially when you navigate by foot e.g. in a city (where you maybe cross your own track more than one time), you can't recognize anything else anymore after a few rounds of walking.

Thanks in advance for commenting this feedback 🙂

I like this idea 0

Replies (1)

Milan Cejnar ●

Hello Johannes,

could you please maybe post one or more screenshots so we could see how bad it is in your case?

The thickness is directly affected by the track line thickness that you have configured in Locus Map and should be corrected by the DPI difference between your phone adn the watch. So the track thickness should be approximately proportional to how you see things on your phone. Of course this might not be ideal approach for your configuration or there might be bug so the screenshots and also your phone model and a value of track thickness you have configured in Locus Map could help us understand the problem better.

Best Regards

Milan

Reply URL

Johannes Waldmüller ●

Hey Milan,

thank u for your answer. I've made a few Screenshots with my watch and one for comparison with my smartphone. The thickness of the route/track line is set to 5px. For me, it appears to be perfect when navigating with my bike by smartphone. But the lines are disproportionately thick on the watch 🤔⌚ give it an analysis, thanks to u! 👍

Files:

URL

Johannes Waldmüller ●

Yesterday I recognized, that I can configure the thickness of the recorded track within an own profile. I think that's the solution of the problem even though the thickness of the route cannot be configured this way... 😉

URL

Milan Cejnar ●

Hello Johannes,

I am glad that track thickness configuration has helped, but you might have really found a bug there. There are indications that when watch and phone's DPI differ significantly then track width might not be computed correctly while rendering map for the watch.

I have added this problem on my issue list and I will investigate more soon when I'll be working on either of Locus Map Watch add-ons and will try to come up with some solution together with Menion.

Anyway thank you very much for letting us know!

Best Regards

Milan

URL