Locus Map - forum

Development => Versions => Topic started by: menion on June 27, 2016, 20:21:08

Title: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 27, 2016, 20:21:08
27.06.2016 - Locus 3.18.0/3.18.1 - new version
- Blog post about major version: blog post (http://www.locusmap.eu/news-version-3-18-0)
- Detailed list of news: list of news (http://help.locusmap.eu/announcement/version-3-18-0-3-18-1-27-6-2016)

30.06.2016 - Locus 3.18.2 - bug-fix version
- news after app start.

04.07.2016 - Locus 3.18.2.1 - beta version
- news after app start.

12.07.2016 - Locus 3.18.2.6 - beta version
- news after app start.

15.07.2016 - Locus 3.18.3 - more new version then bug-fix, but numbered as bug-fix
- news after app start.

16.07.2016 - Locus 3.18.4 - more new version then bug-fix, but numbered as bug-fix
- news after app start, as usually

22.07.2016 - Locus 3.18.4.1 - beta version
- news after app start.

28.07.2016 - Locus 3.18.5 - new version minor/bug-fix
- news after app start, as usually

03.08.2016 - Locus 3.18.6 - new version minor/bug-fix
- news after app start.

11.08.2016 - Locus 3.18.6.2 - beta version
- news after app start.

18.08.2016 - Locus 3.18.6.5 - beta version
- news after app start.

19.08.2016 - Locus 3.18.6.6 - beta version
- news after app start.

25.08.2016 - Locus 3.18.7 - new version minor/bug-fix
- news after app start.

26.08.2016 - Locus 3.18.7.1 - unofficially beta version
-

27.08.2016 - Locus 3.18.7.2 - unofficially beta version
-

29.08.2016 - Locus 3.18.9 - new version minor/bug-fix
- news after app start.

01.09.2016 - Locus 3.18.9.1 - beta version
- news after app start.

03.09.2016 - Locus 3.18.9.2 - beta version
- news after app start.

23.09.2016 - Locus 3.18.9.4 - beta version
- news after app start.

30.09.2016 - Locus 3.18.9.5 - beta version
- news after app start.

04.10.2016 - Locus 3.18.9.6 - beta version
- news after app start.

08.10.2016 - Locus 3.18.9.8 - beta version
- news after app start.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on June 27, 2016, 23:11:11
V 3.18.1.
Same problem: (Locus map stopped).
http://forum.locusmap.eu/index.php?topic=5113.msg43695#msg43695

Strange: Display only(not import): Start Navigation = Succes/no such problem.
Failure happens when Importing a file (set: view on map after import) then directly start Navigation.
There is No failure if the Navigation track was already in the database, then start Navigation.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 28, 2016, 07:02:57
Hello Willy, thanks. I tried also direct start after import as You wrote, but no problem on my side. May you please create for me a log right after crash? Thank you!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on June 28, 2016, 10:00:28
- Detailed list of news: list of news (http://help.locusmap.eu/announcement/version-3-18-0-27-6-2016)
Link doesn't work.
Looking forward to the new version.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Bucky Kid on June 28, 2016, 12:58:14
Link doesn't work.
Looking forward to the new version.
It is already at Play Store..try here: http://help.locusmap.eu/announcement/version-3-18-0-3-18-1-27-6-2016
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on June 28, 2016, 13:20:51
on "news" i read following sentence
Quote
Don’t worry, you won’t be left without geotagged photos nor Panoramio. You can set the Map layers as individual tags to the left screen edge or add it as a button to the upper or right panels (Settings >Maps >Panels & Buttons > Set functions panels > Add function to panel).
and exactly that is what i and others ;) want to do, but i can´t find buttons for Panoramio or geotagged photos to put them to upper/right panel  :-[

EDIT: upps sorry i ignored the word without while translating

using FREE "MAP LAYERS" i get different info if i click on PRO features "Map overlays" "Map shading/ Geotagged photo", clicking on "Panoramio" i get no info ?! ???
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 28, 2016, 13:22:16
@Geotagged photos:
I'm either doing something wrong, or there's a bug.
I wanted to try out the new "Geotagged photo" layer, so I opened the new sidebar, tapped on the entry, added my ExtSdCard directory with all my photos, and then activated the layer. Nothing happened. Thought I might have to wait, because I got a lot of pictures (>23K, >5K of them with tags), but nothing changed.
Now I know the tags are ok, because I use F-Stop as my gallery, and there the map view with the pictures works flawlessly.
Any idea?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 28, 2016, 13:29:56
@0709: thanks for a log, I'll check it

@Christian: link fixed, thanks

@balloni55: I think that Michal spoke about ability to place whole "Map layers" button to side panel, not the individual item in list. "No info" ... I'll check it, thanks

@slarti76: hmm maybe give it a few more seconds. If layer is enabled and directory is correctly set, it should work. And 5+k photos, may really take a while for the first time.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 28, 2016, 14:23:41
@Geotagged photos:
OK, will keep an eye on it ;)

Another thing:
I don't find the new "Nearest Points" to be working intuitively. When I open it, it shows me all enabled points, really all, even if they're half around the world. Now we can argue about what's "nearest", but I would've at least expected disabled points to show up, too. For me, that would be the main use, finding a point I have somewhere in the DB, but not currently displayed. Right now, I can only hide points from that list, that are shown - when I open the list next time, they're gone...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 28, 2016, 14:28:46
Tiny thing:
Thanx for the activity "Snowshoeing" - but as the icon now exists, it should be no problem to offer the icon also for tracks folders, or not? It's missing there...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on June 28, 2016, 15:37:39
@menion a month ago maybe you made a change so that if satellite signal drops out you now automatically stop GPS then restart it. I have now seen this restart a few times, it works perfectly, thanks.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on June 28, 2016, 16:04:53
@menion we've discussed GPX trkpt not containing a time element a few times. I can see in 3.18.1 that nearly all saved tracks are now displayed correctly. BUT I have one track where list view shows huge total time, but detail statistics now show I guess the proper time. How can I upload screenshot with Android phone? It ignores the upload button. Hope you understand anyway.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 28, 2016, 16:11:15
@slarti76: yep limitation of "nearest points". I'll look on it later. And snowshoeing is missing in track icons? Hmm should not, thanks

@Andrew Heard glad that GPS restart works. I always like to read such positive response:). And track ... best - in Locus do export to GPX and check "share". After that choose email and send me track as attachment on jiri.mlavec@asamm.com.  Thank you

Sent from my SM-G930F using Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on June 28, 2016, 16:55:04
Another thing:
I don't find the new "Nearest Points" to be working intuitively. When I open it, it shows me all enabled points, really all, even if they're half around the world. Now we can argue about what's "nearest", but I would've at least expected disabled points to show up, too. For me, that would be the main use, finding a point I have somewhere in the DB, but not currently displayed. Right now, I can only hide points from that list, that are shown - when I open the list next time, they're gone...

100% support. I do not need much help by database search for what I can already see. I need help re. what I cannot see on the map, but is in the POI database. At least in my own DB, so start with.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on June 28, 2016, 19:46:25
for now it´s possible to add different folders where geotagged photos are stored,
disadvantage all photos are displayed at once   :-[
please make it possible to select/activate one and/or more folders whose content should be displayed,
for now user has to delete folder link and add another one in order to keep the overview ???
(https://s32.postimg.org/rahzdsnrl/geo.jpg) (https://postimg.org/image/rahzdsnrl/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 29, 2016, 08:09:05
@slarti76: hmm maybe give it a few more seconds. If layer is enabled and directory is correctly set, it should work. And 5+k photos, may really take a while for the first time.
I've waited the whole day now, some time with Locus active and screen on, too - nothing happened. Then I removed my picture root dir and just added one sub dir with not so many pictures, but definitely with geotags - still nothing.
Is there anything I can try?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on June 29, 2016, 08:26:39
Quote
Is there anything I can try?
just an idea
copy for test a few photos you know their position to internal SD and zoom in  on map
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 29, 2016, 11:33:13
Quote
Is there anything I can try?
just an idea
copy for test a few photos you know their position to internal SD and zoom in  on map
Yeah, works. Turns out, the problem is simple: It doesn't work recursively, i.e. subdirectories are not searched! Is that on purpose? Hope it's a bug, because I don't think it's very useful if you have to add all your picture directories separately...

PS: A few posts above, I wrote "added one subdir with not so many pictures" - I was still talking about a directory with more subdirectories, just deeper down the hierarchy. If you must know, my pictures are ordered in directories-by-year, and under that in events. So only 2 levels deep, nothing fancy ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on June 29, 2016, 16:48:49
@Geotagged photos:
OK, will keep an eye on it ;)

Another thing:
I don't find the new "Nearest Points" to be working intuitively. When I open it, it shows me all enabled points, really all, even if they're half around the world. Now we can argue about what's "nearest", but I would've at least expected disabled points to show up, too. For me, that would be the main use, finding a point I have somewhere in the DB, but not currently displayed. Right now, I can only hide points from that list, that are shown - when I open the list next time, they're gone...

Additional: all i can see in "Nearest Points" are the huge number of nav commands of the track (left, right, straight a.s.o.).
So a filter for different purposes is needed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on June 29, 2016, 21:50:16
Energy value

i´ve played a little with my 10 KM jogging course ;)
if activity is
- not specified i burn 357 KJ
- walking 2011 KJ
- nordic walking 1322 Kj
- running 2162 KJ

why i get a value for not spezified? and i cant belief the difference between nordic walking and walking

now i played with my wight and hight, more wight more KJ but more lenght (longer legs) more KJ ????

and best of all, if i am 10 years jounger i burn more KJ 8) 8) 8) 8)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on June 30, 2016, 00:55:08
Search menu does not scroll sufficiently to clear the on screen system buttons in portrait mode on MotoG 2.
(http://uploads.tapatalk-cdn.com/20160629/dce6327eb0afb687388b2e6d432064c6.jpg)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on June 30, 2016, 00:58:39
Actually the system buttons should not really be there in full screen view. They just appear with the search menu.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Diddi on June 30, 2016, 07:22:09
Nice new update.  Love the map item buttom.  But please make ik possible to hide it, like the other bars
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 30, 2016, 08:33:04
@slarti76: ah, "funny" problem with subdirs. I personally think that current system is better. Mainly because it gives you the flexibility to select really only directories you wants. Also Locus needs to register a "observer" - feature that watch certain folder for every change. If you now add photo to your directory while Locus is running, it will be automatically placed on the map. And this should not be possible with included sub-directories. And what happen if anyone select root directory? Heh, that will be complete disaster :).

@Christian: filter is already possible with top tools menu in this "Nearest points" screen

@balloni55: nice test, thanks for it.

- value without activity: it¨s currently done mainly because it was a lot easier then create something that notify that "no activity is selected". So it compute energy with activity equal sitting in sofa :).
- nordic walking is considered as faster walk around 6 km/h, while walk or run more depend on your speed. If your difference is so huge, then your walk was really fast and this difference is really possible. In your case it looks like jogging with average speed around 8 km/h.
- compute of energy is based on "basal metabolic rate". There exists many methods how to compute it. Method I use is similar to this http://www.bmi-calculator.net/bmr-calculator/bmr-formula.php. As you may see, height increase this value, age decrease. I asked Hanka (she is a nutritionist) - about weight, she do not know exactly. But age is correct. Older = a lot slower regeneration of everything in body, so body needs less and less energy for it's main functions (reason why older people sometimes get fat = because they eat still same amount of energy as younger).

@john_percy: thanks, I'll try to improve it

@Diddi: please check menu > settings > maps > panels > left actions panel to define content. Anyway if you wants a hike/show based on double-tap, this is not currently possible.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on June 30, 2016, 08:45:04
@slarti76: ah, "funny" problem with subdirs. I personally think that current system is better. Mainly because it gives you the flexibility to select really only directories you wants. Also Locus needs to register a "observer" - feature that watch certain folder for every change. If you now add photo to your directory while Locus is running, it will be automatically placed on the map. And this should not be possible with included sub-directories. And what happen if anyone select root directory? Heh, that will be complete disaster :).

Give users a choice - they are not silly kids ... :-)
You could allow for ONE directory to be monitored (no recursion), and allow for each directory recursion no/yes (with warning, if you prefer).
All of your concerns addressed, users happy - what do you think ?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 30, 2016, 09:02:04
Not happy :). Extra work for me, extra complication for UI and no big usage I think. How many directories with photos you have on your device? I have ... wait ... hmm ... one. Oki, slarti76 has for every year one directory, this means around four extra taps every year. Someone wants to display photos from Locus in data/media/photos ... well.
Petr even wanted to completely remove this directory selection and let Locus automatically pick photos from default android camera directory. But I was aware that there will be some other needs ...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 30, 2016, 09:12:31
Not happy :). Extra work for me, extra complication for UI and no big usage I think. How many directories with photos you have on your device? I have ... wait ... hmm ... one. Oki, slarti76 has for every year one directory, this means around four extra taps every year. Someone wants to display photos from Locus in data/media/photos ... well.
Not quite correct, in my "year directories", there are subdirectories again for single events. Ca. 2 dozen per year, so overall a 3-digit number of directories - unfeasible.
But I do get your point, Menion, and I'm absolutely OK with it - after all, F-Spot does this very well for all my pics, and for Locus, this is just an extra. So I can use it to just show some pictures I need right now.
But you should make that clear somewhere in the UI. I'm pretty sure I'm not the only one who expects it to work recursively. Constraints like this should be indicated in the UI, e.g. with a message box with "Don't show this again".
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Diddi on June 30, 2016, 12:50:59



@Diddi: please check menu > settings > maps > panels > left actions panel to define content. Anyway if you wants a hike/show based on double-tap, this is not currently possible.

Hope to see Double tap based option in future.

One bad thing of update this day is that ALL Points of ALL lists are shown.  Thats confusing.  Would be nice to have it chooseable.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on June 30, 2016, 12:58:01
@slarti76: thanks for extra feedback. I'll think about it

One bad thing of update this day is that ALL Points of ALL lists are shown.  Thats confusing.  Would be nice to have it chooseable.
That's what I was worried. Things cannot be simple ...   :(
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on June 30, 2016, 13:39:55
Filter in Nearest Points found. Thanx for the hint. Too much new features ;)

But no points (normal poi's) are displayed. Which poi's are meant?
When i have a look in POI DB, choose a category and close GUI of POI DB, than points from within this category are listed in menu "nearest points". Thats all. No automatic update if i move the map.
Why am i wrong?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on June 30, 2016, 15:31:55
3.18.2:
Thx for disabled points in "Nearest points" and snowshoeing icon! :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on June 30, 2016, 19:35:24
all old geotagged photos from locus/data/media/photo are displayed on map  8)

new geotagged photos are not displayed on map :-[

- i create a new POI, take a photo and save it
- POI with attached photo can be displayed  :)
- photo is stored with correct exif coords in  locus/data/media/photo
- new start of device, new created link to folder nothing help, geotagged photo is not displayed  :(
- i copy this photo to e.g. extSD, now this geotagged photo from extSD is displayed on map

additional question:
if i remember right, in the past locus stored a photo i have added from gallery to POI also in  locus/data/media/photo and wrote also coords to exif
currently if i add a photo from gallery, locus dont copy it,  locus use it from gallery folder without any exif modification (geotag)
So if user change his device and follow the manual "create backup" and "copy complete locus folder" a.s.o he miss these photos :-[
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on June 30, 2016, 19:39:45
Energy value

i´ve played a little with my 10 KM jogging course ;)
if activity is
- not specified i burn 357 KJ
- walking 2011 KJ
- nordic walking 1322 Kj
- running 2162 KJ

why i get a value for not spezified? and i cant belief the difference between nordic walking and walking

now i played with my wight and hight, more wight more KJ but more lenght (longer legs) more KJ ????

and best of all, if i am 10 years jounger i burn more KJ 8) 8) 8) 8)

I confirm that the values are not real.
Especially running and road biking are much to small (factor 2-3). Not sure if elevation gain and pace are computed.

And the small arrow in track details are gone. I liked the shortcut back to the tracklist :(

Still crowling through the amount of new features and not tested in the wild,
Christian

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on June 30, 2016, 21:04:32
V 3.18.2 report. Confirm In both Samsung TAB 4 and THL4000 phone, chrash problem solved. Tnks.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 01, 2016, 07:38:47
@Christian: which normal points are not visible? Do you have enabled at top tools menu to display also the common map points? And update when map is moving thanks to GPS is not implemented for now.

@slarti76: you are welcome

@balloni55: hmm, have to check it next days. And about copy .. to be true I do not remember that Locus made a copy of picked photo. Are you really sure it worked that way?

@Christian: Elevation gain and pace are not used for energy values. In case, you use HR monitor, Locus computes energy values by HR values, otherwise "track activity" + "speed" is used.
And values are not real ... well I had quite nice discussion on this topic here help.locusmap.eu/topic/locus-pro-3-18-1-and-track-new-statistics and in the end it showed that Locus compute values correctly.
If you give me GPX track and your parameters, I'll gladly explain why computed values are as are.

@0709: glad to hear it! Thanks for report and test

And excuse me today, I'm out of office (but will be on Live Tracking whole day ;) ). Enjoy Friday + weekend!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: joeloc on July 01, 2016, 11:36:32
Is there a new secret but horribly misguided gps auto pausing mode in Locus?

I am recording a track. I have a break for a few minutes (not moving... not touching the smartphone at all). I continue riding.

No more points will be recorded from here on, even though there is a perfect gps fix and everything!

That's very bad... I need to manually pause and unpause the recording whenever I stop a bit longer. Otherwise I will lose the days track.

This behaviour is reoroducable with latest Betas and latest pros. No difference. Please investigate... losing track data is serious business.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: joeloc on July 01, 2016, 18:25:33
Here is proof... break at restaurant... phone was not touched... not even turned on display... continue riding... blam... no more points recorded. And there never will be... unless you manually pause and unpause the track. I can reproduce that every time. Android 5.1.1, wasn't changed in a year. Only Locus changed... and some time in the last weeks it turned from a reliable work horse into a random fun house :)

(https://s32.postimg.org/j371dgoy9/Screenshot_2016_07_01_16_53_51.png) (https://postimg.org/image/j371dgoy9/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: tommi on July 01, 2016, 19:20:38
Someone shared his position via Whatsapp, several apps are offered to process the position information including Locus Free, but Locus Pro is missing
(https://s32.postimg.org/e0x0hgu01/Whatsapp_Share_Position_Locus_Pro_missing.jpg) (https://postimg.org/image/e0x0hgu01/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 01, 2016, 21:22:07
@Christian: which normal points are not visible? Do you have enabled at top tools menu to display also the common map points? And update when map is moving thanks to GPS is not implemented for now.
No points at all are displayed. tool menu is set up properly: common map points only.

@Christian: Elevation gain and pace are not used for energy values. In case, you use HR monitor, Locus computes energy values by HR values, otherwise "track activity" + "speed" is used.
And values are not real ... well I had quite nice discussion on this topic here help.locusmap.eu/topic/locus-pro-3-18-1-and-track-new-statistics and in the end it showed that Locus compute values correctly.
If you give me GPX track and your parameters, I'll gladly explain why computed values are as are.
Not sure that i compared my values properly. I will check this later more carefully. Sorry for confusion.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 02, 2016, 09:19:55
Quote
And about copy .. to be true I do not remember that Locus made a copy of picked photo. Are you really sure it worked that way?
no, i´m not ??? perhaps it is a daydream from me :P
but it would be a good solution i think ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 02, 2016, 16:59:33
@joeloc: are you using any special settings? GPS Auto-off? Record only when moving? Hard to solve without ability to simulate on own device. This "break" happen only when you stop for a while on one place? What about some battery optimization on your device? Is Locus excluded? Balloni, you have send me a recorded track and log, thanks for it, but I see no problem in log. This won't be some error that will be printed to log.

@tommi: hmm I have no idea :). Both versions of Locus has exactly same parameters for sharing, sorry.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 02, 2016, 17:26:37
Quote
Balloni, you have send me a recorded track and log
sorry, i havn´t send you anything ?!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on July 02, 2016, 18:57:30
@ balloni was for me I think.
 
Set: Record only when moving.  If unset: no such problem.
No gps auto off. Kit Kat  (no battery optimalisation ;-)  Recording active track. Then put phone on a table in free air. Not moving. After about 15 minutes, restart moving, and there is no restarting trackrecord.The gps indication is ok, with arrow indication  in the moving direction.
EDIT: New tests: Trackrecord is autorestarting, but only after 2 a 3 minutes.(bikespeed).
On old phone Locus V 3.15.3 recording resumes in about 1 second. 
(https://s31.postimg.org/71jf1ans7/Panorama.png) (https://postimg.org/image/71jf1ans7/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: tommi on July 02, 2016, 21:03:41
Seems to be related:
http://help.locusmap.eu/topic/gaps-in-recording-after-pause
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 02, 2016, 21:35:17
Guys, joeloc ... sorry, my bad! Please keep "Only when moving" disabled till next version. I'm sorry, issue found. It really happen only when you pause for a few more minutes.

EDIT: ah sorry willy, I though it was balloni :). Thanks willy for a report, as I wrote .. in log no issue, because all were correct. Issue was in algorithm.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on July 02, 2016, 22:08:30
Tnks. Algoritm ? Maybe by some other improvement ? http://forum.locusmap.eu/index.php?topic=5176.0
Expected to see some more testdrive reports and experiences from 'mountain' region bikers, as in my flat country the moving speed is mostly relatively too 'stable'. But it seems to me that this new 'dynamic' adaption and so the correct in time navigation announcements are really improved. (switching from bike speed to walking speed and back is fast adapting now).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 02, 2016, 22:34:07
Nono this was caused by system that computes average calories, hr values and energy requirements. I needed here to know if user is moving or not, so I've improved previous simple test little bit. Unfortunately this caused a problem: if there were huge gap between last stored point and new point (because of "no movement"), Locus considered all new points as invalid (time between points was too long so computed speed was below minimum speed considered as movement).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 03, 2016, 14:04:23
please open nearest point with two clicks less, similar as it work in point tab

if i click on  "map preview" in point detail, i expect to see next this point on map and not two clicks later
https://www.dropbox.com/s/bjh5gzbw82u53l8/nearest.mp4?dl=0
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: zigzag on July 03, 2016, 16:22:08
Hello menion,

There is a problem in periodic update system since last Locus update.
Some data have not got to my addon. I have got the log below.
For example the distance stay "0.0" in the track recording in my addon. (Pebble addon)
I try it with "Locus API Android (sample)" and there is the problem in it also.
What do I wrong?

The log:
Quote
07-03 15:22:36.181 23591-23591/menion.android.locus.api.sample W/Bundle: Key 1204 expected Double but value was a java.lang.Float.  The default value 0.0 was returned.
07-03 15:22:36.182 23591-23591/menion.android.locus.api.sample W/Bundle: Attempt to cast generated internal exception:
                                                                         java.lang.ClassCastException: java.lang.Float cannot be cast to java.lang.Double
                                                                             at android.os.BaseBundle.getDouble(BaseBundle.java:902)
                                                                             at android.content.Intent.getDoubleExtra(Intent.java:5046)
                                                                             at locus.api.android.features.periodicUpdates.PeriodicUpdatesFiller.intentToUpdate(PeriodicUpdatesFiller.java:97)
                                                                             at locus.api.android.features.periodicUpdates.PeriodicUpdatesHandler.onReceive(PeriodicUpdatesHandler.java:87)
                                                                             at menion.android.locus.api.sample.receivers.PeriodicUpdateReceiver.onReceive(PeriodicUpdateReceiver.java:38)
                                                                             at android.app.ActivityThread.handleReceiver(ActivityThread.java:2673)
                                                                             at android.app.ActivityThread.access$1700(ActivityThread.java:156)
                                                                             at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1428)
                                                                             at android.os.Handler.dispatchMessage(Handler.java:102)
                                                                             at android.os.Looper.loop(Looper.java:211)
                                                                             at android.app.ActivityThread.main(ActivityThread.java:5389)
                                                                             at java.lang.reflect.Method.invoke(Native Method)
                                                                             at java.lang.reflect.Method.invoke(Method.java:372)
                                                                             at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1020)
                                                                             at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:815)
07-03 15:22:36.187 23591-23591/menion.android.locus.api.sample I/PeriodicUpdateReceiver: onUpdate(locus.api.android.utils.LocusUtils$LocusVersion {
                                                                                             mPackageName: menion.android.locus.pro
                                                                                             mVersionCode: 500
                                                                                             mVersionName: 3.18.2
                                                                                             $change: null
                                                                                         }, locus.api.android.features.periodicUpdates.UpdateContainer@854e8ec)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 03, 2016, 22:23:34
@balloni55? side menu will be closed when you tap on "map" button or map preview, in next version, thanks

@zigzag: my bad, sorry!! In next version of Locus & API, this will be fixed. Expect that all track record parameters will be removed and instead of this will be available one bigger object "TrackStats". You will see ...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 05, 2016, 13:40:30
V 3.18.2.1
Quote
side menu will be closed when you tap on "map" button or map preview, in next version
and
Quote
new geotagged photos are not displayed on map
solved, thanks :)

my first impression of "share track as screenshot"

- why only share with FB?
- "track preview" is stored in locus/export as "track-preview.jpg" and always overwritten if user view next "track preview" :-[ why it´s not named identically track?
- some, not all tracks are not scaled enought and trackline is out of mapview
- visible information is different depending original/reimported .gpx or .kmz
for me activity should be shown always.
(https://s31.postimg.org/n2h3ylriv/image.jpg) (https://postimg.org/image/n2h3ylriv/)

and here screenshot of track tab
(https://s32.postimg.org/j82b0pkqp/tab.jpg) (https://postimg.org/image/j82b0pkqp/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 05, 2016, 17:37:42
Helllo balloni55, thanks for feedback!

1) Locus generates JPG image and send simple "Share it" request to system. If there is more apps that may handle it, it should be offered. If it automatically starts facebook for you, then you probably some time ago set "JPG" association for facebook. For me, it offer two picture browsers, email, hangout and few others

2) name of track > good point, I'll improve it

3) tracks that are not fully visible ... give me some GPX so I may try it, thanks

4) export, import ... well since begin, Locus never exported and imported tracks in 1:1 ... so there was always something lost. There was always a problem with attachments, that are lost, now also "activity" that is not exported. Time in GPX export ... I'll check it too, thanks. In case of KML > KML file is not usable for export of recorded tracks. Except coordinates and elevation, all other values are lost.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: joeloc on July 05, 2016, 19:47:23
menion.android.locus folder and thus the image caches are always created on /externalSd/Android/data on my system. Is there any reason to put these on external sd card? I would assume writing to internal memory is orders of magnitude faster and much more suited for things like caches.

Can I can somehow influence this folder? Or does Locus want to be on externalSd specifically?
 
Locus folder itself is on internalSd obviously.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: joeloc on July 05, 2016, 19:54:16
I just noticed Locus mobile data usage for the first time. In the last seven days, it was 60MB "foreground data" and 5MB "background data" according to Android. Can you explain what this means? Is this with the app in front and screen on? And background is with screen off or app in background? Or does it have to do with separate tasks inside Locus... like live tracking and online maps?

60MB feels a lot to me, since I normally never use online maps. Is it possible that the new Panoramio layers eats loads? Then again, I used that just for testing :-).

Live tracking traffic should be miniscule, right?

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 05, 2016, 20:14:46
Quote
For me, it offer two picture browsers, email, hangout and few others
for me it offer  only two picture browser, nothing else available like gmail or whatsapp. "share a track" is an extra button with FB and so i ask for. I never used FB i have no account ;)

Quote
now also "activity" that is not exported
activity is also not visible in original track preview, or i´m blind?

 tracks attached

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 06, 2016, 17:44:10
@joeloc: well "cache" usage is to be able to temporary store data, that otherwise take more time. Cache on SD card is slower then in internal memory (in most cases), but still a lot faster then internet connection. Benefit of cache on SD card is that it do not consume a lot more precious space in internal memory, which I decided is more important then few percent of speed benefit.

Mobile usage ... hard to say what consumed you 60 Mb when I wasn't standing next to you, but from what you wrote, online tiles will be the "problem" here. Live tracking - I was thinking about some "data counter". We will see later ... anyway tested now and with 7 active people, one event (send your location and receive 7 users) took around 1.3 kB. So count it by your "refresh frequency" a in case of 15 seconds, you get around 310kB per hour.

@balloni55: thanks, I think generated preview will be "shared" better now. I found a one more method to offer more options after preview is generated.
And activity: is activity really defined for these tracks? And I tried to import both your tracks and when I created preview, both tracks were completely visible on this preview, hmm.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on July 06, 2016, 18:27:45
Information. Sharing on THL4000.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 06, 2016, 18:32:42
Hi Willy, what you see is sharing from a photo viewer that already opened generated preview. I'm improved sharing of generated "preview" directly in Locus so in next version you should see very similar list of options directly when "preview" is generated.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 06, 2016, 19:33:06
Quote
And activity: is activity really defined for these tracks?
take a look at my post #50
- left SS is from original track named "Jo ZH" with 1936 KJ but no aktivity and in SS of track tab you see the blue runner icon at "Jo ZH", so aktivity is set

please share us a SS from track preview where aktivity is visible

Quote
both tracks were completely visible on this preview, hmm.
- in middle SS of #50 you see preview of track not complete visible "Jo ZH.gpx" i have shared in #54 "Jo ZH.zip"
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on July 07, 2016, 07:58:57
Hello,
After the update to 3.18.2.1 I noticed a an icon on the right at vertical center that gives access to the settings of function panel.
(http://uploads.tapatalk-cdn.com/20160707/eaed8060c813fb745aaddce51683c1c2.jpg) (http://uploads.tapatalk-cdn.com/20160707/6a84e7ce8e383e7f4dd42dab574d241a.jpg)

I think that is not a new function but a little bug.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 07, 2016, 08:12:20
Quote
I think that is not a new function but a little bug.
i think it should only apeare if user has minimum one icon visible on right side, below it
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on July 07, 2016, 09:20:21
Quote
I think that is not a new function but a little bug.
i think it should only apeare if user has minimum one icon visible on right side, below it
I do not use right panel and the cited icon is related to top menu. In pro version there is no icon only in this beta after the update.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 07, 2016, 10:02:01
@balloni55: as I wrote, activity is now missing on generated "Track preview". Also this "preview" is not a simple screenshot. Method how to generate it is quite complex anyway extension is possible. I'll think about option to add there activity as well.

Hmm indeed, you track is not fully visible. Interesting as this do not happen on my device. I'll test it little bit.

@lor74cas: not a bug, rather a feature. I expected stronger offense against this button  (from more people), so result is quite positive to me :).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on July 07, 2016, 10:36:36


@lor74cas: not a bug, rather a feature. I expected stronger offense against this button  (from more people), so result is quite positive to me :).

OK this the first offense.  I like a clear interface and not always more is better.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Bucky Kid on July 07, 2016, 12:20:38
Hello, I have tried the screenshot share from beta 3.18.2.1 and the track profile is convenient but if mixed with map background, it's almost unreadable.
I suggest to place the profile either under the map (or cut the map rectangle to cover only shared track) or under the stats on the right.
When the current raster map has only one zoom level which is not sufficient for the scale of exported image, vector map is used instead. I'd wish to filter all available of offline maps and give user a choice to select one (+whichever from online maps)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 07, 2016, 12:33:45
@lor74cas: I'll try to improve it little bit and allow to hide this button

@Bucky Kid: you see a raster map as background of this feature? Surprise, because only vector maps should be used here! And with chart > I'll try to do something with it, thanks.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on July 07, 2016, 14:35:24
@Bucky Kid: you see a raster map as background of this feature? Surprise, because only vector maps should be used here! And with chart > I'll try to do something with it, thanks.
Only vector map? Please change that! The best map for Switzerland, for example, is the official SwissTopo map, for all higher mountain tours everything else is just useless (the vector maps are sometimes mainly a light green background). So for this feature to be any use in the Alps, it must be possible to use it with the best map, which usually won't be a vector map.
I also agree with Bucky Kid about the chart - in principle it looks nice as overlay, but there are so many cases when it will interfere with the map content, it should be put separately on white background.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 07, 2016, 15:59:53
No improvements for map rotating after display wake up during guiding :(
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on July 07, 2016, 18:11:04

(https://s31.postimg.org/flj0rrtvr/2016_07_07_174647.jpg) (https://postimg.org/image/flj0rrtvr/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on July 07, 2016, 18:31:34
Quote
For me, it offer two picture browsers, email, hangout and few others
for me it offer  only two picture browser, nothing else available like gmail or whatsapp. "share a track" is an extra button with FB and so i ask for. I never used FB i have no account ;)
Few month ago (yes, that's not a new idea) i wrote same objection on G+
Why F*book has so high priority? Don't need this feature too.
So thanks for your post Wolfgang  ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 07, 2016, 19:12:39
Hello menion,
official PRO didnt display "tracktime movement" correct, pause time is ignored :-[
With BETA its better but not perfect ;)
see attached screencast,
at start of screencast i stop my car
-tracktime "movement" and "all" pause at that time, i expect time "all" count on.... ???
sec 12
- after ~3.45 min i drive on, both times are identically  i expect less "tracktime movement" :-[
sec 53 i stop recording
sec 58 now in statistic "tracktime movement" is displayed well :)
https://www.dropbox.com/s/vyjpezqr0op0oq0/time%20movement.mp4?dl=0
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 08, 2016, 08:43:01
@slarti76: understand anyway it's technically problematic as raster maps do not have precisely defined it's coverage. There is also a problem with license where mainly paid maps like swiss topo may have some problems with such terms of use > have to check this later. So for now, only vector maps will be possible.

@Christian: surprising, I was almost sure that this "problem" is solved.

@gynta: thanks, I also noticed not-refreshed icon, I'll check it. And Facebook ... you are right, it's almost everywhere now. It's ... one button in track bottom menu and one button in "share" screen, so almost everywhere. This is your "so high priority"? I'm glad that you otherwise use all other 268 buttons in Locus ;). Well, some people use this feature, some not, some are alergic on this feature. I also do not use it (even I have FB account), but I'm aware that it is also useful tool for propagation of Locus itself, sorry guys.

@balloni55: hmm still a problems with speed detection (detection of movement). I rather rewrote this from scratch and will test it in the filed this week. Thanks for inform me!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Bucky Kid on July 08, 2016, 22:59:22
I have this graphical bug sometimes. The transparent sidepanel handlers are touch sensitive, after opening and closing side panel, they're placed correctly.

I have verified on two phones

(http://i.imgur.com/eEjkcFJ.png)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on July 08, 2016, 23:35:11
Me too
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 09, 2016, 06:27:40
Me too :)

Sent from my SM-G930F using Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 09, 2016, 08:22:39
Locus last final version: not active for at least one day. No active task...
Then this message appeared: "Locus is not responding". Whats going on in the background?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 12, 2016, 23:57:45
@Christian: sorry for a delay ... but how may I help here? I have no idea what happen in your device.

Unfortunately for me, issue with track recording affect more people then I expected, so I'll need a new version sooner. Together with disabled MapQuest maps ... a lot sooner. So I've just published new Beta version. Tomorrow I'll be out of office for a day anyway during Thursday I'll try to manage all feedback and if all goes well, I'll publish on Google Play a new version.

Have a nice evening.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 13, 2016, 20:40:32
V 3.18.2.6
- track preview with activity in headline 8)
- track preview now with multible share options :P
- track time all/movement inside track panel and statistic tab with correct time  :)

New Locus themes:
- for me the waymark icons are displayed a little bit too small
- tracks on yellow ordinary roads are concealed
for  comparison
(https://s31.postimg.org/bs84the1j/theme.jpg) (https://postimg.org/image/bs84the1j/)

Edit:
render problem with summer and winter theme
https://www.dropbox.com/s/1illojoqxlefer5/render.mp4?dl=0
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 13, 2016, 22:35:36
@Christian: sorry for a delay ... but how may I help here? I have no idea what happen in your device.
Spooky. Mystic.
Are you sure that nothing is running in background not even the widget when Locus is closed?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 15, 2016, 14:19:56
New version 3.18.3 on Google Play!

@balloni55: thanks for issue. Hope it will be fixed now. About style ... it's on @voldapet

@Christian: next time when this happen, try to create a log. Maybe there will be something useful.

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 15, 2016, 14:25:01
Quote
About style ... it's on @voldapet
is behavior forwarded to him ?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 15, 2016, 15:03:40
@balloni55
Wrong tiles should be fixed in the new 3.18.3.

When it comes to offset for hiking routes. Please consider that internal themes use different approach then HiLo theme. The hiking route is not rendered over highways but along the highway. Due to different thickness of highways can be sometimes hidden like on your screenshot. The tricky part it to find the correct offset for hiking routes. Such offset that can be used for small path, tracks or bigger highways. I'm sorry but this is maximum what I can do. The solution is to make the yellow highways litter bit smaller but from my point of view has the highway bigger priority then hiking route.
However is it complication for usage of summer theme in the field?

The size of the symbols: I have sometime the map overcrowded with symbols but I can understand that they are little bit small. Well, what others think?
Title: Lomap themes
Post by: radobyl on July 15, 2016, 17:54:13
Too bad, the new vector theme misses a lot of important Symbols. No more Campsites for instance. If this is not enough, the sea is white now (Holland and Belgium). The Old theme, with the ability to select from a wide range of topics what is shown on the map wasmuch better. Please fix this until next Friday, when I will need it 😎.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 15, 2016, 22:07:01
@radobyl
Thank you for report! The missing sea areas - really stupid mistake. It'll be fixed in next version. Current version really doesn't display some camp site (also fixed). Please feel free to post what other symbols are missing (for example viewpoint)

Quote
The Old theme, with the ability to select from a wide range of topics
Would please give me some example, please?
Thank you
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Bucky Kid on July 15, 2016, 23:00:20
I'm trying latest version on my old phone and observe that POIs from map items folders now load remarkably slower. Also the list of all categories load time seems remarkably longer.
Especially on app startup the wait time is limiting.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on July 16, 2016, 10:49:59
V 3.18.3 - Black tile issue: confirm fix.  Thank you Menion

Gesendet von meinem SM-N9005 mit Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: radobyl on July 16, 2016, 11:47:05
@radobyl
Thank you for report! The missing sea areas - really stupid mistake. It'll be fixed in next version. Current version really doesn't display some camp site (also fixed). Please feel free to post what other symbols are missing (for example viewpoint)


I just compared the map of Belgium (still have an Old Version on a Tablet).  Besides from Campsites and viewpoints  I haven't found more missing points so far. Zoos are new, i Found.

Quote
The Old theme, with the ability to select from a wide range of topics
Would please give me some example, please?
Thank you
[/quote]

My mistake. I thought, it was here, where one could choose from different poi groups. But this is actually possible up to a certain point in the new theme.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: jusc on July 16, 2016, 12:14:09
I wonder about the numbers within the grey dots... Where do they come from?
(https://s32.postimg.org/j9vb01qu9/Numbers.jpg) (https://postimg.org/image/j9vb01qu9/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Kona on July 16, 2016, 12:29:39
Hi guys,


As we know sea water bodies are missing but also beautiful creamy f4f3e9 colour.

I'm not sure about the Themes names, you are trying something new but for me Spring and Autumn is missing ;P
Be aware as only small part of the world has snow during a winter (also there is no snowing over there some years).
When I have purchased Locus Pro it was clear, I'm going e.g. to Italy for skiing and that Theme shows me pistes, clear, makes sense.
Winter name is misleading now, especially Summer one. ;)

Church icon looks like female upside down.  ;D

Main roads are much thinner so hard to recognize hierarchy.


Anyway I'm sure work is in progress so it will look stunning soon!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 16, 2016, 12:39:42
Share track :(

(https://s32.postimg.org/saupas2rl/PE_20160716_123707.jpg) (https://postimg.org/image/saupas2rl/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 16, 2016, 12:43:46
One more version with few quick fixes - 3.18.4

@michaelbechtold: you are welcome!

@jusc: this is my older attempt to reduce number of points from vector maps. Grey dots are grouped points from Db POI. Useless? I still consider this better then map overloaded with icons.

@Kona, very nice summary, thank you. I'm sure @voldapet will comment every single feedback after a weekend.

@Christian: ehm ... problem? :) EDIT: the completely black image is your result of "Track preview" feature?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 16, 2016, 13:07:33
text render problem with germany south map < ZL20
(https://s32.postimg.org/vdffv9075/render.jpg) (https://postimg.org/image/vdffv9075/)

Quote
but from my point of view has the highway bigger priority then hiking route
sorry, i dont think so :-\
if user select hike/bike trials, he want to see on display outdoor with bright sun always clearly the trails to know where to go!
and not to stop and puzzle next direction ???
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 16, 2016, 13:38:18
@Christian: ehm ... problem? :) EDIT: the completely black image is your result of "Track preview" feature?
Yes, black out(put) :o
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: HtV on July 16, 2016, 15:39:00
I don't know if it's a bug or feature:
When in theme-options, I can select or unselect several options e.g. Eat/Drink or Hiking routes or MTB-routes. At first the choices I made would  not stick. Then I found out that I should not use the back arrow to go back to the previous screen but I should just put my finger next to the window to make it disappear, then the changes I made would happen on the map.
I hope you understand what I'm trying to say. :D
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: LeeDee on July 18, 2016, 00:43:08
Locus automatically updated and now it no longer can import a GPX file.  I goes through the process like everything is OK but then says "No data in list!".  My GPX routes are made with Garmin's Basecamp and I'm using OSM maps.  I rebooted my device and uninstalled/reinstalled Locus Pro.  It all worked great before the upgrade.

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 18, 2016, 09:00:22
Hello guys,
@balloni55: text problems are in Locus for quite long time, sorry, I cannot help here now. And priority of symbols ... well I also prefer visible hike/bike trail as "it's a main point of Locus, right"?

@Christian: hmm complicated task. Anyway has same problem? I've tried it on many devices and everywhere it worked fine. What device are you using now?

@HtV: thanks for a bug-report, understand. This really should not happen. Problem is, that it works fine on my device. You are using latest 3.18.4 version of Locus and internal Locus themes?

@LeeDee: what a complicated GPX. Inner route points and total mess in times. You are right that Locus has troubles with this file now, sorry for this. Issue will be fixed in next version .. seems it will need one more bugfix version at start of next week.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 18, 2016, 09:32:54

@Christian: hmm complicated task. Anyway has same problem? I've tried it on many devices and everywhere it worked fine. What device are you using now?
Still using Galaxy Note(1) running exotic stock rom A4.1.1., not rooted, not spoiled.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: HtV on July 18, 2016, 12:06:33

@HtV: thanks for a bug-report, understand. This really should not happen. Problem is, that it works fine on my device. You are using latest 3.18.4 version of Locus and internal Locus themes?

Yes I have version 3.18.4 installed on my Sony Z5 Compact on Android 6.1
I tried a few different settings: automatic hide top and bottom panels on/off but that makes no difference.
I restarted my phone: no difference.

Edit: I am using Locus maps with the internal themes.
It's not a big deal. :) Good luck with it.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 18, 2016, 16:31:25
@Christian: I'm sorry. I'm fighting with it for more then hour. "Fortunately" on my device with Android 4.0.4 it do exactly same problem. No matter what I do, result is always only black image with blue thin border. Android completely ignores my attempts to render whole screen into simple image. From what I was able to find about similar problems, it looks like generated preview is too big on this Android version. So I'll have to disable this feature for all 4.0, 4.1 Android versions, sorry.

@HtV: ah perfect, I got it! You tap twice on back arrow, so it returns you to root menu of "Map content" panel, not just to list of map themes. Perfect, thank you, issue fixed!

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 18, 2016, 17:10:59
The track charts in 3.18.4 are a big improvement over 3.18.2. Thanks @menion
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 18, 2016, 17:37:39
Sometimes small change do a lot. Except few tiny improvements with placing texts, only bigger change was twice more "fat" lines. Nothing more. Anyway I was also surprised how clearly chart is visible on sun, compare to before :).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on July 18, 2016, 19:26:35
@Christian: I'm sorry. I'm fighting with it for more then hour. "Fortunately" on my device with Android 4.0.4 it do exactly same problem. No matter what I do, result is always only black image with blue thin border. Android completely ignores my attempts to render whole screen into simple image. From what I was able to find about similar problems, it looks like generated preview is too big on this Android version. So I'll have to disable this feature for all 4.0, 4.1 Android versions, sorry.
Great that you found the problem. Sad not to have the feature in 4.1 :(
May be you will find a way to solve it later.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 18, 2016, 20:35:32
The town names are very clear to read on the new lomap road theme in 3.18.4. Nice. Will there eventually be a cycling theme and a greater number of tick boxes for hiding map features?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on July 19, 2016, 09:26:57
Black map tiles on changing theme still occur.
(http://uploads.tapatalk-cdn.com/20160719/115213080fb19da60b2de4962ac52bb9.jpg)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 19, 2016, 09:34:52
Hi Guys,
thank you for comments about themes. I've prepared testing theme - please download and try. However:
@kona
-  creamy f4f3e9 colour is back
- Winter/Summer  Is it or it isn't evident for which activities is focused the Winter and Summer theme? At least in European area
- Church icon is the same as used to be. Only the colour is different
- There are no changes in highway thickness for summer theme (only low zoom-levels zoom < 12 are different). Note that the highways were quite wider internal themes probably two years ago. But I've made them narrow based on gynta's suggestion...

@balloni55
- I've tried to little bit improve it (attached testing theme). However I'm still convinced that offset for marked trails is the best approach how to highlight any route in the map. Paper and also some web map use this approach. I can remember the old issues when users complained that they can not see the type of track/path because is covered by highlighted hiking line (even transparent). Offset approach offers both - the background track and also highlighted route. Unfortunately in some situation is offset solution "broken". It's needed to decide what approach is better..

@Andrew Heard
What features you'd like to hide? Please write me also some use cases, why, etc. I'd like to know the reason why is important to have more options.

Thank you!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 19, 2016, 13:44:14
Hello Petr
Quote
I've tried to little bit improve it
a little bit, yes.... ???

my suggestion:
- keep offset off trials
- display trials always ontop
Quote
It's needed to decide what approach is better..
please diskuss it with your complete team ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: HtV on July 19, 2016, 18:21:46
@HtV: ah perfect, I got it! You tap twice on back arrow, so it returns you to root menu of "Map content" panel, not just to list of map themes. Perfect, thank you, issue fixed!

Glad you found and fixed it. :)
Off topic: I'm very fond of Locus, so many options with such a clear/clean screen, great work.
Before I used Osmand but I never really got to understand/like it.
And very important: it uses very little battery. A few weeks ago I walked for about 4 hrs with my wife and the dog, I take a look at the map probably every 10 mins, took a few photographs, had tracking on of course, In that 4 hrs my battery went from 95% to 80%. I have a fairly new Sony Z5 Compact. :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 20, 2016, 12:48:31
@balloni55: without thinking too much about it, from my point of view, theme focused on hiking/biking, should have hiking/biking trails as highest priority. Theme for a car, should have roads as main priority.

And if offset yes/no ... I think they looks quite good :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on July 20, 2016, 13:48:31
About new Locus theme structure Sommer/Winter
Seriously?
I hope this is only an interim solution.
Please reconsider again the logic behind it.
Just waiting for negative feedback soon.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 20, 2016, 15:29:55
Agree with @gynta, can't see point of season-based themes.

I observe I can no longer merge a track with a route - the route points are completely ignored. I guess because no timestamps. But I really hope you consider this a bug because many times if I forget to reenable track record so I "patch" by adding in a route for my records.

And on this subject I see you have again supported a function panel track record button. This is great. Now fully obvious if track recording NOT enabled. But I think it's been working/ not working/ wanted/ not wanted many times now. Please leave it.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 20, 2016, 17:51:35
Quote
About new Locus theme structure Summer/Winter
Seriously?
Seriously? Yes, at least for now :-) Honestly I'm not sure if winter/summer is the best solution. But what's the better name for summer theme?
1. General topo & hiking & cycling & mtb  theme ?
2. Summer theme ?
I'm still convinced that "Summer" is the best name for all activities. However I can imagine "Bike & Hike" name.  Give me some reasons or ideas why to rename, please.



Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 20, 2016, 19:04:16
I disagree. Those activities don't necessarily happen just in that season. Confusing. Why not just individual activity based themes like Elements LE? Seems consistent with recording profiles, maybe.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 20, 2016, 20:02:21
Agree with @gynta, can't see point of season-based themes.

Why, if there are season-based paper maps ? E.g. summer/winter outdoor maps for highlands or mountains.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 20, 2016, 22:53:44
Season based maps probably exists, but what we have here is not a Summer theme for hiking and winter theme for hiking.
Truth is, that winter theme may evoke using this theme for hiking in winter, which is of course not correct. Maybe some "Base theme" name should be better as it do not specify exactly usage.
As I read some discussion somewhere, guy complain about road theme and Petr suggested to use "Summer" theme with disabled hike & bike tracks. It's perfect, it's different use for this theme. And well, "summer" make no sense here. Sorry, have to agree.

@Andrew Heard: hmm broken merge, I'll check it, thanks
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 21, 2016, 07:19:05
Agree with @gynta, can't see point of season-based themes.

Why, if there are season-based paper maps ? E.g. summer/winter outdoor maps for highlands or mountains.
maybe for some countries, but weird concept for others.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 21, 2016, 13:41:20
maybe for some countries, but weird concept for others.

Hmm. you are probably right - based on supposed activity is better, like Bike/Hiking versus Cross-country skiing.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 21, 2016, 14:09:06
In AUSTRALIA-Tasmania more summer riding, for South Australia more winter, for top end only dry-season, each state is very different. Every culture is different. Viva la difference.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on July 21, 2016, 14:50:30
In some countries there are ice roads in winter in place of ferry crossings, for example. But I don't know if any of the maps show them as such.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 21, 2016, 20:52:08
i think unskilled users didn´t know where to enable kml/kmz files
(https://s31.postimg.org/f66dir58n/data.png) (https://postimg.org/image/f66dir58n/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on July 21, 2016, 22:03:01
i think unskilled users didn´t know where to enable kml/kmz files
I agree.
I think in that menu we'd find all the elements and set up the transparency for each one.
Full transparency = disabled
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 21, 2016, 22:09:45
Thank you for comments about names of themes. I'll discuss it with team - "Hike & Bike" / "Ski" could be ideal solution. BUT you gave me another idea - "General" theme. What about to remove City theme and create something between City and Hike & Bike. Menion gonna kill me but I like this idea.

@john_percy - interesting idea. I'll add ice roads into next LoMaps
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 22, 2016, 12:46:12
Thank you for comments about names of themes. I'll discuss it with team - "Hike & Bike" / "Ski" could be ideal solution. BUT you gave me another idea - "General" theme. What about to remove City theme and create something between City and Hike & Bike. Menion gonna kill me but I like this idea.

IMHO, I would keep scenario themes as the baseline, with bunch of check-in options to tweak them,
like Elevate theme for OpenAndroMaps ( Hiking / Cycling / City, each with lot of options )
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 22, 2016, 12:52:49
Quote
I would keep scenario themes as the baseline, with bunch of check-in options to tweak them,
like Elevate theme for OpenAndroMaps ( Hiking / Cycling / City, each with lot of options )
exactly +1 8)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 22, 2016, 13:38:38
Quote
I would keep scenario themes as the baseline, with bunch of check-in options to tweak them,
like Elevate theme for OpenAndroMaps ( Hiking / Cycling / City, each with lot of options )
exactly +1 8)
+1
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on July 22, 2016, 15:29:14
Quote
...with bunch of check-in options to tweak them,...each with lot of options
exactly +1 8)
+1
+1
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on July 22, 2016, 15:45:13
Quote
...with bunch of check-in options to tweak them,...each with lot of options
exactly +1 8)
+1
+1
-1
I really do not like so many options
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on July 22, 2016, 15:54:55
Well, no need to toggle the checkboxes 10 times a day
...but IF I want - I can do it ;D
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 22, 2016, 17:12:58
-1
I really do not like so many options

OTOH, 1 option "food and drinks" in the current winter theme is the opposite extreme.
Perhaps a balanced number of themes and options - neither too many themes with too few options neither vice versa.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 22, 2016, 20:57:12
Hi guys,
I'm trying to keep this completely on Petr and because he is extreme minimalist, it ended with one checkbox in winter theme etc. (as I remember he did not want even a this one) :).

Anyway enjoy weekend, I've just published new Beta version mainly with some fixes. Because there is again a few more issues that needs fix (import of GPX, GC Offlinizer), I'll release new version at middle of next week, so few days to tune it!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on July 22, 2016, 21:34:51
...and because he is extreme minimalist...
damn - that means, "Locus Map" is his worst project ;D ;D
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: jusc on July 23, 2016, 12:17:46
Quote
...with bunch of check-in options to tweak them,...each with lot of options
exactly +1 8)
+1
+1
-1
I really do not like so many options
-1
I agree with John.
But everyone should create his own theme and can see how many work it is, to test all these feautures.  ;D
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 24, 2016, 21:39:54
Hi,
well I'm sorry but check-boxes are useless from my point of view and they can cause more harm than good. Current check-boxes exist in internal themes because:
- it's quite complicated to create one Hiking & Cycling theme because of offset of highlighted routes (more routes in one place)
- overcrowded city centre by icons because there wasn't any intelligent logic how to group the map icon

Mentioned Food & Drink check-box in CAR theme exists only because consistency how theme is changed in app. I'm sorry but I add more check-boxes only when I get direct order from menion. I have strong opinion on it.


@gynta
I've probably wrote it somewhere... We spent hours and hours haggling / arguing with menion about tnes of Locus features, settings, screens, etc. I see lot things in different way.  Unfortunately menion has always lot's of argument why is some setting important. He's the boss and I respect it...sometimes. Maybe is Locus my worst project but the question is how would Locus look like without my comments and complaints. Maybe would it be better ...who knows
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 25, 2016, 07:45:06
Hi,
well I'm sorry but check-boxes are useless from my point of view and they can cause more harm than good. Current check-boxes exist in internal themes because:
- it's quite complicated to create one Hiking & Cycling theme because of offset of highlighted routes (more routes in one place)
- overcrowded city centre by icons because there wasn't any intelligent logic how to group the map icon

Mentioned Food & Drink check-box in CAR theme exists only because consistency how theme is changed in app. I'm sorry but I add more check-boxes only when I get direct order from menion. I have strong opinion on it.


Quote
"Thank you for comments about names of themes. I'll discuss it with team - "Hike & Bike" / "Ski" could be ideal solution. BUT you gave me another idea - "General" theme. What about to remove City theme and create something between City and Hike & Bike. Menion gonna kill me but I like this idea. "

Hm, but it may lead to "one size fits all" extreme, if both theme and option numbers are minimized, especially in context of your idea of general theme combining hiking/bik theme and city theme. ( Unless it is meant as an extra theme and not as replacement )

As you have said, cities are icon crowded. It is natural to want a selective POI filtering.

For outdoor themes, such a filtering is less important. But OTOH there is challenging problem to display all OSM way features important to know for challenging routes. Like  track/path class,  track grade, surface, difficulty ( smoothness, MTB scale, SAC scale, ) trail visibility and along/over it also foot and bike routes. It is difficult to display all at the same time, even if OAM theme Elevate/Elements (http://www.openandromaps.org/en/legend/elevate-mountain-hike-theme) made a very good trial in that. It is hard to see other way but selective feature switching by the theme options.

Fortunately, there is external theme escape path, so there is no need to help Menion killing you.  :D
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: tramp20 on July 25, 2016, 13:53:39
Hi menion,
since the last 2-3 versions the notify icon for automatic backup disappears after ~5 seconds (free and pro).
Is this intended?
Before this the icon remains visible until I clear it.

This happens on two smartphones (5.1.1 and 4.2).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 26, 2016, 08:27:17
I do not understand why the current internal road theme gave up the colour distinguishing of the road classes ( motorways, trunks, primaries, secondaries, tertiaries ) ?  It is quite an important info and I can see no gain in keeping them all similar.

You can see various OSMAnd themes for illustration, that often follow various road atlas conventions.

BTW, does/can a theme distinguish paid/unpaid sections of motorways ?( MapsForge libraries may not provide that.- OSM data contain paid flag for roads and toll points). Some OSMAnd themes use extra dotted line inside motorway line. It is quite important e.g. in France, where you can take either long way along free motorways ( Beziers to Clermond-Ferrand), or pay big money for it ( Mulhouse - Lyon - Avignon ). The router can distinguish that, but visual check is useful as a double measure..
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on July 26, 2016, 09:18:01
OpenAndroMaps maps tag toll sections of roads (not just motorways), and some third party themes (Elevate, Voluntary) show them. LoMaps and internal themes do not.

BTW, does/can a theme distinguish paid/unpaid sections of motorways ?( MapsForge libraries may not provide that.- OSM data contain paid flag for roads and toll points). Some OSMAnd themes use extra dotted line inside motorway line. It is quite important e.g. in France, where you can take either long way along free motorways ( Beziers to Clermond-Ferrand), or pay big money for it ( Mulhouse - Lyon - Avignon ). The router can distinguish that, but visual check is useful as a double measure..
(http://uploads.tapatalk-cdn.com/20160726/67c25b4c7e9cda774b2d3a669c9f8e71.jpg)
Voluntary theme and OAM Great Britain map: toll roads shown by red-orange dots, and red-orange borders on motorways

(http://uploads.tapatalk-cdn.com/20160726/029fa5e9972a9424d265f6b06651df37.jpg)
Elevate theme and OAM Great Britain map: toll roads shown by orange dots

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 26, 2016, 09:43:25
I agree fully with Poutnic on new internal themes. I used on off last few weeks but now other than to view city names more clearly with Road theme I have given up hope. Will stick with OAM.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 26, 2016, 11:59:52
@poutnikl
I often think in Parero's principle 80:20. I really think that for 80% users are options in CAR/WINTER/CITY theme useless. I've performed a series of usability tests with Mapy.cz (czech leading map service) a couple years ago. The tests included also reviews of POI filtering. There was probably 8 groups of options (Restaurants, posts, bus stops,...) The tests show that users didn't click on these options or they thought that POIs are missing in the map.  Bellow is one real comment from participant:
"I can't see the bus stops, so why map does not contain bus stops"

In case that map is icon crowded than it should be solved by application not by the theme. For example using automatic grouping of icons (available in the beta). Lots of users understand the map as invariable "image" - even the themes are for them quite abstract.  We want to collect some stats how users switch themes and pois options. You can also test it - watch your wifes/friends how often they change the pois options and why they change it. 

Outdoors - I want to keep the hiking/cycling routes as simple as possible. Map has to be understable without legend and user has to be able to read map even if all hiking/cycling routes are switched on. I don't really want to create something like openmtbstyle -  https://openmtbmap.org/legend/mtb_highways_clas.png

Quote
I do not understand why the current internal road theme gave up the colour distinguishing of the road classes

Have you tried the latest beta, please. The car theme should be improved.

Toll roads - I thought about toll roads maybe three years ago. I was worried about coverage but it looks quite well now. I have no problem with this idea - although it's related with router, not with the map
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 26, 2016, 19:11:14
My experimental BRouter car profiles (https://github.com/poutnikl/Car-Profile) count with toll roads, toll booths or bridges.

I must check how much is usable UK voluntary theme in Czech area, as it seems well sophisticated. I am for now fond of UniGCCZ Czech specific theme, HiLo theme and Elevate them, all for non car scenario.

I have not remembered well  which OSMAnd themes and Locus themes/maps do use this toll info, so thanks for information.

I have found avoiding toll roads in France and Spain by Mapquest and BRouter routing highly reliable during June/July vacation. We noticed just 2 small mistakes and they bother were a driver error, not wrong routing.

OpenAndroMaps maps tag toll sections of roads (not just motorways), and some third party themes (Elevate, Voluntary) show them. LoMaps and internal themes do not.

Voluntary theme and OAM Great Britain map: toll roads shown by red-orange dots, and red-orange borders on motorways

Elevate theme and OAM Great Britain map: toll roads shown by orange dots.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 26, 2016, 20:00:55
@poutnikl  - I often think in Parero's principle 80:20. I really think that for 80% users are options in CAR/WINTER/CITY theme useless. ......................... We want to collect some stats how users switch themes and pois options. You can also test it - watch your wifes/friends how often they change the pois options and why they change it. 
I quite agree with your 80/20 approach, I seldom fit the 80, regardless the topic.  :) I change themes and options all the time.
I know personally just 1 other Locus user, I will ask him.  I have as well thought - as you mentioned - the POI filtering should be rather matter of the application then of the theme. I was also thinking about positive ( what to display ) and negative ( what to hide ) filtering approaches.

OTOH, filtering of map features may be better done in themes.

Quote
Outdoors - I want to keep the hiking/cycling routes as simple as possible. Map has to be understable without legend and user has to be able to read map even if all hiking/cycling routes are switched on. I don't really want to create something like openmtbstyle -  https://openmtbmap.org/legend/mtb_highways_clas.png

I see. I half agree half disagree with you. As there are needed both simple and advanced paper maps, there are needed both simple and advanced maps/themes. Making trade off between being simple and provide most of relevant info probably cannot lead to anything good.

Personally I am fine with eventually LoMaps hiking/bike themes kept simple, as advanced users can use advanced Elevate theme, eventually with OAM maps, e.g. the map of Alps. there is no need for doubling the effort. OAM elevate theme legend for completness (http://www.openandromaps.org/wp-content/users/tobias/Elevate_map_key.pdf)

Near all paper maps do have legend, so legend IS needed, but it is always handy at the paper map side. Emaps rather sacrifice the easy legend availability, as managing handy access to it is problematic, of course.

Quote
Have you tried the latest beta, please. The car theme should be improved.

Toll roads - I thought about toll roads maybe three years ago. I was worried about coverage but it looks quite well now. I have no problem with this idea - although it's related with router, not with the map

Even if it does not look like that, I still consider myself as a Locus beginner, not having Locus in firm grip, so I rather postpone the fiddling with beta yet :-)  Playing with beta features requires solid experience how it should behave normally. For now, I am patient, looking forward to stable one.

For toll roads, Mapquest and my BRouter car profile routing were highly reliable in avoiding toll roads/booths during my recent vacation in Spain and France. The only errors were driver errors.

As I mentioned above, the toll topic is related to BOTH routers and maps. Either as a secondary real-time visual routing control, either just for the map browsing .
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: tommi on July 26, 2016, 20:26:45
I often think in Parero's principle 80:20.
Peter, Locus users are not part of the 80% of smartphone map users, those 80% simply use Google Maps and are happy with it.
This is my experience in more than 5 years using Locus and showing it to other people who are surprised what I can do with this smartphone app with the strange name (meaning of Locus in German).
But almost all of them stick with Google Maps though I show them that it misses a lot of outdoor information compared to Vector maps in Locus, route planning with brouter, ...
Locus is and should stay a Swiss Army Knife, only then it is useful in the wild.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 26, 2016, 20:49:47
I often think in Parero's principle 80:20.
Peter, Locus users are not part of the 80% of smartphone map users, those 80% simply use Google Maps and are happy with it.... 

+1  Locus is more Swiss knife than a cheap knife for spreading butter. 
But Peter may think about 80% of those 20%...   :-)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on July 27, 2016, 00:16:33
Whatever Petr thinks this 80% group needs - fell free to put those things as the DEFAULT settings.
And give the full power to everyone, as an option. E.g. to grow from the 80% to the 20% group skill level, rather than patronize everybody with ideology.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on July 27, 2016, 07:14:31
It is like with BRouter profiles.

For 80%, the default profiles out of the box are good enough. The rest accepts the benefit, challenge and power of custom profiles, own or shared.

If BR was focused to 80% only, the profiles could be as well hardcoded to binaries, referred just by their names.

The simple and advanced approaches do not exclude each other, but complement each other.

@Peter: I have just noticed at City variant of Elevate theme, that it performs icon grouping for the city icon crowding.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on July 27, 2016, 10:29:01
I often think in Parero's principle 80:20.
Peter, Locus users are not part of the 80% of smartphone map users, those 80% simply use Google Maps and are happy with it.
This is my experience in more than 5 years using Locus and showing it to other people who are surprised what I can do with this smartphone app with the strange name (meaning of Locus in German).
But almost all of them stick with Google Maps though I show them that it misses a lot of outdoor information compared to Vector maps in Locus, route planning with brouter, ...
Locus is and should stay a Swiss Army Knife, only then it is useful in the wild.
+1
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on July 28, 2016, 15:05:11
Hello Guys,

thank you for comments.  I don't want split the users into group 20% skilled and 80% beginners that's nonsense. More over we can not say that Locus users are some geeks are super cartographers. I don't think that there are 300 000 hiking-carto-maniacs in Germany :). Assumption that Locus users are almost some skilled freaks is quite odd. BUT It doesn't matter how experienced the Locus users are, we should offer better UI/design for everyone. And this is my fight ... fight for couple checkboxes that completely change the usage of Locus app. I'm kidding but you've already say it: make it simple but offer more possibilities for enthusiast. You can use different map, different themes, there are no limits.

More options more pain - see this myth http://uxmyths.com/post/712569752/myth-more-choices-and-features-result-in-higher-satisfac
 
Maybe I'm completely wrong. Give us some time to collect stats how Locus users use themes and option. That give us better view.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on July 28, 2016, 19:34:53
question to "Track preview"
- after i click on "Track preview" > preview open :)
 at this moment  this preview.jpg file is stored in locus/Export :o why? can´t see the benefit :-[ and folder content grow unobserved
if user want to store this "preview file" he can share it via file browser to folder destination he want.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on July 29, 2016, 15:05:36
Good day balloni,
well I need to store file somewhere before display. So without longer thinking I've considered this as "export" and result was "export" directory.

But you are correct that in most cases, you do not need to handle with this file directly. So if there is no one against it, I'll change it to some temporary directory in cache, where file will be automatically deleted later. Thanks
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on August 02, 2016, 08:51:30
Good day balloni,
well I need to store file somewhere before display. So without longer thinking I've considered this as "export" and result was "export" directory.

But you are correct that in most cases, you do not need to handle with this file directly. So if there is no one against it, I'll change it to some temporary directory in cache, where file will be automatically deleted later. Thanks
This reminds of something I wanted to ask for a long time: Why are the images created by "Share screen" also saved in data/media/screenshot? Sharing means I do something with them, so if I want to save them, I can do that. But like this, I regularly have to clean the data/media directory, which apart from that doesn't contain any temporary data.
I know that you have to create the file first before it can be shared, but don't you agree that it makes more sense to do that in a cache dir, too?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 02, 2016, 10:56:46
Hmm good point. Btw. surprised that someone still use this feature :). I'm united system with new "Track preview", so exported images will be stored in locus/cache/export (which is from time to time cleared) and also before "share" will be visible small screenshot "preview" dialog. Thanks
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on August 03, 2016, 08:12:58
Hmm good point. Btw. surprised that someone still use this feature :).
Please don't think about removing it! :)
It's perfect for making overviews - for example, I made a great overview with all tracks from my Japan trip. You first select just the tracks and points you need, lock the right zoom and then export the screen - voilà! Perfect e.g. for photobooks. I would even like to see it extended with an option to choose the resolution. Actual screen resolution is ok for me, as I have HD phone, but higher is even better. But I understand if the feature is not used very often, it's too much effort.
Anyway, don't remove it...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 03, 2016, 11:36:06
Hehe, don't worry, it's not planned for now ;). When You use it for this case, don't forget to try new similar feature optimized just for tracks .. tap on track, bottom "share" button > track preview.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Bucky Kid on August 04, 2016, 12:46:11
Hello
did I overlook something? I don't find in current version the top panel button counter, ie. it can't be changed.
Looking up in Settings > Maps > Panels & Buttons > Set function panels
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 04, 2016, 13:18:20
Hi Kid, did You tried simply drag buttons from "right" part to "top" part? ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Bucky Kid on August 04, 2016, 14:47:23
Of course it works, thanks
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: slarti76 on August 05, 2016, 08:11:13
Hehe, don't worry, it's not planned for now ;). When You use it for this case, don't forget to try new similar feature optimized just for tracks .. tap on track, bottom "share" button > track preview.
Yeah, I know - voted for that  8) And like it - but as I said, for connected trips, the screen export is still a great addition.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 07, 2016, 14:10:32
@ Petr
(https://s7.postimg.org/5jmzgi2w7/Villages.jpg) (https://postimg.org/image/5jmzgi2w7/)
while playing with "new" locus themes i´ve noticed different behavior depending on locus version and on used map ::)
on my SGS2 with badenwurttemberg map and V 3.18.5  names of this 5 villages are displayed from ZL 13-17 ;D

on my Moto G3 with badenwurttemberg map and V 3.18.6 name of 4 villages are displayed from ZL 13-17
only village name "Zaisersweiher" isn´t displayed on ZL17 ???

with map germany_south and V 3.18.6
names of this 5 villages are displayed on ZL13
zooming in
"Sternenfels" isnt displayed at ZL14 +17
"Diefenbach" isnt displayed at  ZL14 + 16

this is only an examle, i noticed this also on other parts of the map

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on August 07, 2016, 16:08:08
Just tried the new Share Track feature for the first time. What is the theme used ? The map in the picture is definitely not the map shown in normal Locus display ...

Gesendet von meinem LG-H850 mit Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on August 09, 2016, 12:20:48
@balloni55
I didn't study your issue deeply but it seems that it's our long term issue with text caption and labels. I don't think that menion changed anything in last version so it's only on Mapforge logic if text is shown or not. The main reason will be probably in different resolution of your devices. This causes different size of text and finally influence if text will or will not be shown. I'm sorry but I guess that we can not offer any quick solution...but it's more on menion ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on August 10, 2016, 15:23:47
Just tried the new Share Track feature for the first time. What is the theme used ? The map in the picture is definitely not the map shown in normal Locus display ...

Gesendet von meinem LG-H850 mit Tapatalk
Anybody knows ?

Gesendet von meinem LG-H850 mit Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 10, 2016, 16:04:38
Hi. Map in this preview is best available vector map with last selected theme.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on August 10, 2016, 16:15:50
TXS Menion. I think there is a reason people select a particular map, regardless of vector or tile. And no reason to take any other map for the purpose of screenshot.

Gesendet von meinem SM-N9005 mit Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 10, 2016, 17:02:19
There is a lot of reasons why I do it. Coverage of raster maps (not exactly known in most of cases), zoom range of raster maps (biggest problem), license options (not always exactly known), time necessary to create screenshot (should be problem mainly in case of online maps). Because of all this, currently only vector maps are supported.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on August 10, 2016, 17:39:40
Understand the raster map topic (and license may not be the least of it).
For a vector map, though (and this is the only thing I tested, and just did again), there should be no reason to take another map than the one shown to the user, nor to take another theme than the user chose.
With my test right now, I see a different map and a different theme in the resulting Locus screenshot. Why ?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 11, 2016, 15:35:56
New Beta version 3.18.6.2
Many fixes already reported by users + first attempt to new version of "items" screen (available in menu > more) and first attempt to custom configuration for BRouter profiles directly over Locus.
Locus will now display also profiles stored in Locus/data/brouter (for those who wants to play with it). Such profiles also support "on the fly" definition of "avoid_motorways" and "avoid_toll" parameters. Check sample attached file if interested. Hope you find it useful.

@michaelbechtold: well, reason is currently quite simple ... because I have function "get me best vector map for this area", which is used in this case. Because all maps except LoMaps do not have precisely defined bounding area, it is little bit risky to use just a method "use current map". In such case, there is a chance, then map won't cover required area.

I'm sorry, for now I do not have a better solution. Because of this, it may end, that user itself will be able to manually choose a map, that he wants to use. Just an option ...

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 11, 2016, 19:18:07
btw. thank you for bring back the (right) green GPS Satfix icon...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 11, 2016, 19:29:05
Thanks for possibility to disable left REC-button :)

- no map preview in data track tab

brouter profiles:
- allways long list of available"profiles". I think only meaningfull profiles should be available for selection, or what is the realistic use of  e.g "CAR-SHORT > Walking"  or  "FOOT > Car ECO"
- Where can user find abbreviation of e.g. SAC4 or FCR
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 11, 2016, 20:32:43
@gynta: heh you mean as default content in panels? Well, we realized that it is quite complicated to solve tasks like "check if Locus has GPS fix" :)

@balloni: list of profiles is based on Libor work here: https://github.com/poutnikl/Brouter-profiles . He will help me to choose best of them, that will be included in Locus by default. For now, it is only for testing. And what means FCR? I have no idea :).

And "realistic use" ... well I know that some people set all five options to hike/bike profiles. So question here is, if not to allow rename and re-icon these profiles. Maybe I'll go easier way and offer only few relevant profiles for every type, as you suggest. Thanks for opinion.

And no map preview ... indeed, thanks!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on August 11, 2016, 22:46:52
... first attempt to custom configuration for BRouter profiles directly over Locus.
Locus will now display also profiles stored in Locus/data/brouter (for those who wants to play with it). Such profiles also support "on the fly" definition of "avoid_motorways" and "avoid_toll" parameters. Check sample attached file if interested. Hope you find it useful.

Thanks, and works for me as intended.

However, I think that needs a second thought.

The issue was that the transport-mode mapping in BRouter is too abstract for the average user, and you need something more intuitive. And now you come up with ....... a transport mode mapping....

So everytime the word "transport mode" comes to your mind, just say 3 times:

  "There's nothing like a transport mode - there are just profiles with options"

  "There's nothing like a transport mode - there are just profiles with options"

  "There's nothing like a transport mode - there are just profiles with options"

I know that for MapQuest you have a similar concept: the options (there are 4 options for MapQuest) are configured deep in the configuration, and the transport mode is selected on the navigation screen. This is already dangerous: it's easy to forget such an option, and you will be confused by unexptected results.

But now, things are even worse: while for Mapquest, you have one set of options, now you have a set of options for each transort mode. That's a multiplication of entropy and the way to hell.

So the concept that I have in mind is much simpler: put the profile-selection AND the options directly on the navigation screen.Maybe two lines, the first with a combobox for profile selection + a trigger button, and the second line with checkbox icons for the options. And have the values for the checkboxes shared over profiles, that is, if you change the profile selection, the options keep their values, but the visibilty of the option icons depends on whether the selected profile evaluates that option. Of course that does not offer space for the (multi-language?) option descriptons, so they must be places somewhere else.

I am aware that you need a transport mode also to initialize the voice navigation. But you can take that from the gpx-response, the same way you do it when importing a gpx.

regards, Arndt
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on August 12, 2016, 01:57:46
I agree with Arndt regards new BRouter customization.
Thanks for ability to hide the left track recording button.
Thanks for 2 new track styles and more empty space between icons in other styles. The spacing looks really good now - can see underlying road better.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 12, 2016, 07:46:02
Hello @abrensch, thanks for a nice feedback.

I perfectly understand your point of view. More I think about it, more I agree that current system just "duplicates" settings for BRouter. On seconds side, life is not so easy.

I can imagine how you see it ... similar to what you have on web page, but
- quite weird to have some routing service done in this way, some in different, so it will require to recreate MapQuest and other to look and work same
- I read about no single problem till now, that car-fast, car-slow ... etc. cause problems to anybody. So this system as is, is usable and logical for users. What comes now is a complication - "profiles". You care about "average users". I care currently more about less then average users. They don't care about profiles. I expect, they will use all settings as is, no need to modify it.
- anyway good point is with extra parameters. As I think about it, agree they should be shared and agree they needs to be visible easily directly during creating navigation definition (start/stop). I have something in my mind, so give me one more chance ;).

@Andrew Heard: you are welcome!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 12, 2016, 07:59:41
brouter profiles:
- allways long list of available"profiles". I think only meaningfull profiles should be available for selection, or what is the realistic use of  e.g "CAR-SHORT > Walking"  or  "FOOT > Car ECO"
- Where can user find abbreviation of e.g. SAC4 or FCR

@balloni55: Well, my work on script based generation of profiles (  I have found manual creation of profiles boring ) got ahead of the documentation. There was planned to add during the generation the short legend inside the profile header comment and to create a profile legend list file. Also the Github documentation of the new profiles versions.

At that moment Menion "has caught me off-guard" with this profile initiative, before the documentation was ready.  :)

All profiles for given way of transport come from a signle template, so using Locus options can significantly decrease their number. It could make sense to put them to car/bike/foot subfolders...

4 in SAC4 means maximum allowed value of OSM SAC_Scale (http://wiki.openstreetmap.org/wiki/Key:sac_scale#Values) , what is rating of alpine hiking difficulty of the trail.

FCR stands for Follow Cycle Routes, an analogy to ICR name.
FCR is a functional analogy to the flag stick_to_cycleroutes in the standard reference Trekking.brf, but works differently.

For more, see my Github pages or wait for later provided more elaborated comments.

@Menion: For car profiles, I would recommend added parameter %drivestyle%, modifying it to Fast / FastEco / Eco variants.

Eco is too focused on cost of fuel consuption at steady speed, but drivers would not be usually willing to drive so slow
( Driving distubations influence on time/cost are considered in Fast/Eco profiles as well. )

FastEco is a kind of balancing of speed and cost criteria.

My recommendations for bicycle and hiking profiles will come later. While all comes from the single template, it must be well thought, what to address by %parameter% and what rather by independent profile.

For bicycle, the most often tweaked is iswet, MTB_factor and smallpaved_factor.

https://github.com/poutnikl/Brouter-profiles/wiki/MTB_factor-and-smallpaved_factor (https://github.com/poutnikl/Brouter-profiles/wiki/MTB_factor-and-smallpaved_factor)

Boolean iswet try to guess shifting of preferences in wet weather, avoiding muddy/slicky roads.
MTB_factor and smallpaved_factor are numeric factors with default values 0.0, used for the single place tweaking of road preferences of profiles.   More on Github or later.


                 
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on August 12, 2016, 11:36:43
Locus will now display also [BRouter] profiles stored in Locus/data/brouter (for those who wants to play with it
They must be somewhere but I can't find them in that location on my system
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 12, 2016, 11:49:12
Locus will now display also [BRouter] profiles stored in Locus/data/brouter (for those who wants to play with it
They must be somewhere but I can't find them in that location on my system

(https://s9.postimg.org/cu6jsy8cr/locussettings.png) (https://postimg.org/image/cu6jsy8cr/)

edit
...and you are right.
Locus/data/brouter is somewhere :)
Menion?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: LocusUser#1 on August 12, 2016, 13:15:10
Beta 3.18.6.2
New Item screen: the arrow in the top left corner will not jump back into the list, I always land directly on the map screen, so I can not get to the list.

New Item screen: No items in the folder "GPSies" are displayed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 12, 2016, 14:27:15
@poutnikl: thanks for feedback. Yep, it was quick action, but it's a beta and I think it's better to give you something to play with, then speed week on something, we later consider as useless.

I wanted to set just most used basic "boolean" parameters into optional parameters (like I did with motorways and tolls). More complicated parameters should be handled directly by routing profiles (separate files). Anyway it's on discussion. I think that for most of basic users, one or in worst case, two profiles for every type should be enough. Advanced users may use own profiles loaded in mentioned Locus/data/brouter directory (also possible to prepare pack with profiles to Store).

Btw. this directory is not created automatically. Just create it manually.

@LocusUser#1 and others ... what you expect to happen when you press "left arrow icon" in top left corner of screen? Forget on Locus now, it's a general question. As I read by Google suggestions, this button may move you one step back in activity lists, not just one step back like with "back button".
At start, in new "Items" screen this arrow has same system as hardware "back" button. But soon I realized that everytime I wants to return to map, I have to tap back many times and after return I have to again move to correct folder. This top arrow solve it and it's one tap to map and one tap to exactly same place where I was before.

Btw. I'm going to publish one more Beta now with completely redesigned configuration screen for BRouter and based on @arndt suggestion (and small inspiration from Google Maps), I made a compromise that I'll test next four days (out of office).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on August 12, 2016, 14:31:51
- I read about no single problem till now, that car-fast, car-slow ... etc. cause problems to anybody.

I can help you remember :-)

http://forum.locusmap.eu/index.php?topic=5066.msg42633#msg42633

Quote
So this system as is, is usable and logical for users.

The system, as it is used, is not logical. In my mapping I mapped "moped" -> "car slow". A moped is not a car, so this is not logical, it's just a workaround. When zossebart maps 5 biking-profiles on the 5 transport modes and has a hard time to remember what "car slow" actually is, then there's also a usability problem.


Quote
What comes now is a complication - "profiles". You care about "average users". I care currently more about less then average users. They don't care about profiles. I expect, they will use all settings as is, no need to modify it.

I do not agree. The complication is the fact that there are two "namespaces" with a mapping between them. If there's only one namespace, whether you call it a mode or a profile is just wording. A user seeing a combobox with items like "car" "moped" "roadbike" "velomobil" "bike" "hike" will be less confused than a user that has to learn that a moped is a slow car.

Quote
- anyway good point is with extra parameters. As I think about it, agree they should be shared and agree they needs to be visible easily directly during creating navigation definition (start/stop).

Think about consistency. As poutnik pointed out, it's quite arbitrary where you put the "cut" between having distinct profiles or controlling behavior via parameters (and in current beta there are far too many profiles, because most differnces would be better implemented by parameters).

There's no good reason to treat these two ways of configuring the router on different levels of visibility/reachability. So if I convinced you to put the parameters directly on the Navigation Screen, I will also convice you to put the profile name there. Then you have a layout problem because of the extra space that needs, and convice yourself that you need to remove the transport mode buttons :-)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on August 12, 2016, 14:51:46
I'm very happy about the implementation of more BRouter profiles and even parameters.
This is for me beside guidance the most important functional module in Locus and sure also for other users and may make difference to other apps.
But i would like to ask all responsible and involved persons to create a functional design together before a new beta is released. This may avoid this kind of mailing list here in forum (see above).
Thank you. Looking forward to use this new feature.
And... i totally agree with the opinion of abrensch about users and parameters.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 12, 2016, 15:04:33
By "I read no ...", I was talking about using basic simple separation to "car fast", "car slow" etc. used in MapQuest and other services. Not about BRouter.

If we will talk about BRouter and it's usage in Locus as is now, then of course, system is not best in case you wants to change profiles and use different options.

Anyway I'm not saying that what you wrote does not make sense to me, it does. I just now can't imagine to create completely different UI for all routing engines, because of this. And have some special UI because of BRouter that will be quite different ... hmm ... have to think more about it ...

EDIT: and mailing list/discussion ... well, this is a one of main purposes of this forum I think :).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on August 12, 2016, 15:29:45
Back arrow button and new Items screen
I follow what you say @menion, but I was flummoxed as how to get back to the Items screen when I had drilled down to a collection of pois.
Back arrow returns straight to the map.
(http://uploads.tapatalk-cdn.com/20160812/c407bd1a1ef5e376d0fe45e65f440756.jpg)
(Answer after a lot of trying is to get the title bar and system buttons to appear, then click system button "back". )
Not intuitive.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 12, 2016, 15:52:11
By "I read no ...", I was talking about using basic simple separation to "car fast", "car slow" etc. used in MapQuest and other services. Not about BRouter.

If we will talk about BRouter and it's usage in Locus as is now, then of course, system is not best in case you wants to change profiles and use different options. 

I think one BRouter feature would have to be addressed - Timeout free route precalculation in BRouter server mode.
It serves to prevent 60s routing timeout for the Locus 1st time route calculation or route recalculation with ( distant ) point priority.  At destination distance 50-100 ( OSM data density dependent ) km , the timeouts at normal calculation start to appear.

Either the new Locus system has to address it, either timeout policy has to be changed.
---------------------
@Arndt:
It could make sense, if there is implemented a way of default values if no parameter is provided, to have the common profile version.

E.g., current idea is
assign avoid_toll 0  # profile for BRouter
assign avoid_toll %avoid_toll%  # profile for Locus

What about modifying the profile syntax like

assign  avoid_toll  [%avoid_toll%] 0   # profile for both, [] means optional

where the assign command would take %avoid_toll% value if provided by API.
If no parameter is provided, syntax %avoid_toll% would be ignored and the default value 0 would be used.


Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 12, 2016, 16:04:18
What about - perhaps a crazy idea - general expandable list of "slots" for the Locus Routing

It would have
Slot Name ( like Fast Tollfree - car would be seen from the icon )
Mode, projected to the slot icon ( car, moped, bike, foot, canoe ). For BRouter may be extracted from Profile code
User routing service ( Mapquest, OSRM, GraphHopper, BRouter )
Optional legend - extracted or typed
Dynamic routing  options ( possible ?? ) like
     already available options for existing services ( car/bike/foot, fast/short for OSRM etc,)
     for Mapquest also toll, unpaved ...,
     For Brouter the used profile + extracted list of defined parameters.( or just predefined fixed list )
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: LocusUser#1 on August 12, 2016, 19:46:16
Back arrow button and new Items screen
I follow what you say @menion, but I was flummoxed as how to get back to the Items screen when I had drilled down to a collection of pois.
Back arrow returns straight to the map.

(Answer after a lot of trying is to get the title bar and system buttons to appear, then click system button "back". )
Not intuitive.

+1
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: T-mo on August 13, 2016, 12:27:50
@Menion:
shortly I recognised while driving close to start or end but being busy with the traffic situation due to road works and changed navigation, not much clicks and stuff possible, that the selection of the 'navigation data source' is quite faaar away.
Also studying and comparing of the found navigation-results of different 'data souces' for the same navigation (start-end) is nothing that can be done quickly..with a girl as assistant by my side and having a bit different result with an iphone on unknown tracks ;) Sure, things can be done before, but happened..

Do you think it's possible to rethink some positions of settings?
At least you want to have your best route, which might not be delivered by using only ony data source nowadays..still the same with profiles, where we can quickly change due to situation depending criteria
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on August 13, 2016, 16:49:54
I think one BRouter feature would have to be addressed - Timeout free route precalculation in BRouter server mode.
It serves to prevent 60s routing timeout for the Locus 1st time route calculation or route recalculation with ( distant ) point priority.

Hi,

Both features do work in that constallation. And by the way, that was my main development effort when I implemented the remote-profile option for brouter 1.4.3

Every request with a remote profile saves that profile on the brouter-side as brouter/profiles2/remote.brf

So after a timeout, you can repeat that long-distance calculation using the brouter-app, using the exact same destination point and a close-by starting point. That will automatically store the "reference-track" as brouter/modes/remote_rawtrack.dat, and with the help of that file the next try from Locus is guaranteed not to time out. Same for automatic recalulations (using endpoint priority). Recalculations should always be faster than the initial ones.

Quote
@Arndt: What about modifying the profile syntax like

assign  avoid_toll  [%avoid_toll%] 0   # profile for both, [] means optional

Nice try, but this ball goes back to Menion :-) When using a comment syntax instead, compatibility is not broken, so I don't have to repair. I would go one step further and define a comment-syntax that also provides the label-text and the label description text, and that also allows profile-defined parameters (currently, only build-in parameters work). Like that:

assign  avoid_toll  = false   # %config-option% Toll roads | Allows toll roads

regards, Arndt
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on August 13, 2016, 18:55:38
So, user steps are:
1. Attempt Brouter navigation in Locus but get timeout.
2. Use Brouter app to do same calculation, using remote.brf profile and selecting a to point and a from point.
3. Now it will work in Locus so either import track, or recalculate.
Am I right? If so it's still not very user friendly.

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 14, 2016, 02:51:35
......
Every request with a remote profile saves that profile on the brouter-side as brouter/profiles2/remote.brf

So after a timeout, you can repeat that long-distance calculation using the brouter-app, using the exact same destination point and a close-by starting point. That will automatically store the "reference-track" as brouter/modes/remote_rawtrack.dat, and with the help of that file the next try from Locus is guaranteed not to time out. Same for automatic recalulations (using endpoint priority). Recalculations should always be faster than the initial ones.......

It could be better from user convenience view,
if BRouter, seeing start destination distance bigger than a threshold,
would calculate the reference track and the first route calculation directly,
sending via API some kind of "keep alive ping".until finished.

As if used for cars, ( even if aware of turn restriction issue ), the timeouts may be rather the rule then exception.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Viajero Perdido on August 15, 2016, 07:25:10
When in offline mode and you try to view online map tiles, Locus shows a placeholder tile with directions to the offline mode checkbox.  Brilliant idea, BTW.

With recent changes to the setting structure, it needs to be reworded.  :)  Noticed in the current beta.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 17, 2016, 17:53:31
Hi to all,
hope you had a good days without my responses last days. I had to test BRouter & Locus on moto and it worked pretty well. I was used mainly "FastEco" mode and have to say, that few times track was longer then expected (usually a lot shorter track was over city which was probably considered as "not so eco").

Anyway in the end, I agree with opinion of @abrensch about duplicating of Locus routing profiles & brf selection. So I've removed it for now and Locus will have hardcoded custom profiles. So for car-fast will be used Libor's "Car-FastEco.brf" profile etc. without possibility to change it. You will be anyway still able to disable Locus custom-mapping and use old used system with mapping directly over BRouter. Reason for this is, that creating system with such huge customization of routing profiles needs more then one afternoon, so it's not possible to implement it now. I've decided to allow less features for now. Thanks for understanding.

@T-mo: is it really so often that you change even a navigation routing sources? Hmm, not sure how common use case is this. I for example usually use "recalculate" option from menu and now quite frequently also long click on this option to define how will be recalculation done. Not sure about others ...
@Viajero Perdido: thanks, improved
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on August 17, 2016, 19:17:43
Pitty.
:(
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 18, 2016, 18:16:52
...... I had to test BRouter & Locus on moto and it worked pretty well. I was used mainly "FastEco" mode and have to say, that few times track was longer then expected (usually a lot shorter track was over city which was probably considered as "not so eco"). .........

You may want to try the updated Car-Profile template (https://raw.githubusercontent.com/poutnikl/Car-Profile/master/Car-test-Template.brf), identical to future Car-FastEco.

The above experience may be caused by not well tuned yet evaluation of turn and initial ways costs, that could provide less them optimal results in urban areas. I have tried to address it better in the above template.

I have also added 2 extra boolean flags for Locus, that allow to turn already existing features by ON/OFF flags.
 Avoiding Unpaved and
Fast versus FastEco. Or may be named Balanced .

Code: [Select]
assign fastprofile            0 # default 0=economic, i.e. balanced cost and time, 1=prefers shorter time
                                # implemented for Locus config switch system
                                # fastprofile=0 is equivalent drivestyle=2(FastEco), fastprofile=1 is equivalent drivestyle=3(Fast)
assign avoid_motorways        0 # default 0, 1=like if on moped or on "sightseeing tour", includes motorroad=yes
assign avoid_toll             0 # default 0 / 1=avoid paid ways and toll points like booths or bridges
assign avoid_unpaved          0 # default 0 / 1=avoid unpaved roads, equivalent to road_restriction=2, implemented for Locus confing switches

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on August 19, 2016, 10:41:25
Anyway in the end, I agree with opinion of @abrensch about duplicating of Locus routing profiles & brf selection. So I've removed it for now and Locus will have hardcoded custom profiles. So for car-fast will be used Libor's "Car-FastEco.brf" profile etc. without possibility to change it. You will be anyway still able to disable Locus custom-mapping and use old used system with mapping directly over BRouter. Reason for this is, that creating system with such huge customization of routing profiles needs more then one afternoon, so it's not possible to implement it now. I've decided to allow less features for now. Thanks for understanding.
Trying this on the new beta, I eventually discovered that "custom settings" means menion's settings, and "fast" means "avoid motorways". Neither are all that obvious, and (at least for me) "fast" should mean "use motorways".
If it is to be hard coded, my preference would be "fast" = "use motorways" and "slow" = "fast-eco" and "avoid motorways". Plus use phrasing like "Locus defaults" or "BRouter defaults" instead of "custom settings".
Anyway, I guess this is only one iteration on the route to perfection.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 19, 2016, 11:01:17
aaaaa, there is an issue and there are missing extra settings for "custom settings" ... damn, thanks @john_percy , how may I miss it, hmm :/

@poutnikl : thank you, I'll look at it ...

damn ... hard to test it when settings for custom profiles are missing. I'll do some more fixes and publish one more beta version on weekend. Sorry. And yes, consider this as first iteration.

Plan is to publish one more bug-fix version next week, in middle of September, I'll be out-of-office for two weeks and October will be in name of rewriting handling of profiles + most probably creating ability to define custom profiles for BRouter directly in app.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 19, 2016, 13:43:18
V 3.18.6.5
- map preview in track tab solved :)

- geotagged photos, it´s only one level so please write subdirectory :) > subdirectories is missleading
- item subdirectory
> http://help.locusmap.eu/topic/subfolders-in-item-tab
how to create folder/subfolder inside locus? Folder created with file explorer work, but subfolder isnt availabel in item tab :-[

Fundamental question "visibility of items"
- using items, last state of visible items is stored and displayed on next activation of this item.
Screencast:
sec. 10 > i hide th route
sec. 20 > i hide the poly and one point
sec. 40 > in overview it seams there is no item active item :-[ this is missleading
sec. 44 > 5 points are nevertheless visible
sec. 65. > i hide all points and tracks
sec. 79. > i disable item and after enabling it again no item is visible on map > using last state :-[
https://www.dropbox.com/s/krmkvb88hur5gc6/Item.mp4?dl=0
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 19, 2016, 14:19:54
- subdirectories improved :)

- subfolders ... you create a new subfolder somewhere in Locus/mapItems and it is not visible in new "Items" screen? Old "Items" tab in data manager support only one level of subdirectories as is mentioned in topic

- visibility ...
Understand, good point. Seems that "eye" icon needs three states ... nothing visible, something visible, all is visible. Otherwise restoring previous state seems for me as correct behavior, isn't it?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 19, 2016, 21:43:48
Quote
and it is not visible in new "Items" screen?
after long search i found this "item function" with "+ icon" and it work quite good with subfolders ;D
sorry, i didn´t search for a new function because items tab on old place is furthermore available :P
Quote
Seems that "eye" icon needs three states ... nothing visible, something visible, all is visible.
if you solve it this way, previous state is ok ;)

new questions/ideas:
in item detail window down right "eye button" is always blue, with or without stroke and i think the logic is inverse.
- blue eye with stoke item is visible on map :-[
- blue eye without stroke item is hidden :-[

- if i click on map preview in item detail window and hit a item this item change state, for what´s this??
- click on map preview in item detail window should end in mapscreen, identically POI/track

- back button in map items should end on mapscreen and not jump step by step back from deep subfolder, navigating in folder/subfolders is possible with click in "top folder list"
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 20, 2016, 06:54:27
In new beta version, eye icon is enabled even when single item is enabled, so it may helps little bit for now.

Blue button ... it depend on what you expect. You expect that this icon display current situation. Anyway I had made it that icon display action that happen. So item is not on a map > eye icon say "show it". Isn't it more logical?

"Click on map" ... thanks, I'll fix it

About "back" from "items screen" - don't talk me about it: http://forum.locusmap.eu/index.php?topic=5199.msg44460#msg44460
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 20, 2016, 12:30:36
......
Every request with a remote profile saves that profile on the brouter-side as brouter/profiles2/remote.brf

So after a timeout, you can repeat that long-distance calculation using the brouter-app, using the exact same destination point and a close-by starting point. That will automatically store the "reference-track" as brouter/modes/remote_rawtrack.dat, and with the help of that file the next try from Locus is guaranteed not to time out. Same for automatic recalulations (using endpoint priority). Recalculations should always be faster than the initial ones.
......

Hmm....., Locus can define the startpoint and the endpoint for the route calculations by multiple ways, e.g. by coordinates or screen center position. The above procedure of manually trigerring timeout calculation would fail, if the points are not chosen from already defined Locus waypoints...... It would be good if BRouter exposes the used points to the user so he would use them for timout free calculation.  Perhaps the way of generated points from, [via1,] .... [viaN,]   to would help.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 20, 2016, 13:01:35
Quote
Anyway I had made it that icon display action that happen. So item is not on a map > eye icon say "show it". Isn't it more logical?
logical.... off course ;)
but it is not consistent inside locus, all over locus blue eye means visible and grey eye with stroke means not visible on map.
This is what locus user keep in mind and he do not recognice the difference of a stroke inside a blue eye icon,
just my two cents ::)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 25, 2016, 14:32:42
Thanks balloni, I'll think about it more next week. This change is still not yet ready to publish, but I think, I'm close.

Btw. new version 3.18.7 published. Thanks to many people for ultra-fast translation of texts, that I've uploaded just yesterday on crowdin. And also thanks for many bug reports. I didn't wrote all of them to news, because even without them, list of news is quite long :).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 25, 2016, 18:52:00
"BEGIN" is wrong here, because you want to show a 2nd page.
(https://s16.postimg.org/8owglm7xd/free.png) (https://postimg.org/image/8owglm7xd/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 25, 2016, 18:56:47
main menu vs functions(more)
In "Functions" Locus is able to display whole label.
"Main menu" should do it in the same way.

(https://s4.postimg.org/s5wm36vxl/2016_08_25_152133.png) (https://postimg.org/image/s5wm36vxl/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 25, 2016, 19:38:25
sometimes i am confused which profile is used :-[
https://www.dropbox.com/s/zgjcsgwcy9nt0vb/BR.mp4?dl=0
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 25, 2016, 21:20:29
OOps, accidentally I replaced this my post by the new one below. I have tried to recreate its main points.

To BRouter profiles integration
1/ I suppose BRouter config Own Settings OFF works as the previous mode profile mapping in BRouter.
   ( Already confirmed by Menion in CZ post on HelpDesk )

2/ If Own Settings is ON,and transportation mode is chosen, there is for a fraction of second displayed used profile, mapped diractly in Locus. There is shown some roll out menu probably intended for profiles selection, but cannot be activated.

The profiles in Own settings ON are for now hard coded
  Mode            Profile
  Car-fast        Car-FastEco
  Car-short       Car-Short
  Bicycle-fast    Trekking-Fast
  Bicycle-short   Trekking-MTB-Medium
  Foot            Walking

 Than all disappers and appears a new screen with avoiding switches. Is it intended behaviour for now ?
 ( Menion confirmed that such behaviour is temporary till next versions, should be ignored. Profile choice is planned )

3/ Car-short profile exists rather just for completess, is intended just for e.g. technical emergency of damaged but still operational cars. Most of drivers would not seriously choose such a profile for "production drives".
IMHO, Car fast mode should be Car-Fast and short mode should be some of Eco profiles, Particularly Car-Eco is short enough.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on August 26, 2016, 00:56:05
For car, I think the combination Car-Fast and Car-(Fast)Eco would be better than Car-FastEco(otherwise good) and Car-Short.  As I guess not many drivers would really prefer the shortest routes. Car-Eco is short enough.
+1
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: ta-ka on August 26, 2016, 03:45:02
main menu vs functions(more)
In "Functions" Locus is able to display whole label.
"Main menu" should do it in the same way.
+1
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 26, 2016, 09:24:40
P.S. for integration of the BRouter  profiles:

Iswet flag would be better translated to CZ "Za mokra" rather than "Je mokrý". ( Localizators have difficult job, as needed context for proper translation is often missing.. )

The description ( back translated ) as "to avoid dangerous ways in case of wet weather" is misleading, Most of such ways are not dangerous, just inconvenient. Danger particularly is not evaluated, as such info is not available. Danger must be evaluated visually on the map and terrain.  Better would be something like "It prefers ways that do not become slicky or dirty during wet weather".

Important info is, that ISWET flag DOES NOT avoid/forbid such ways, like e.g. Flag "Avoid motorways". It could lead to serious unnecessery detours. It just gives them various extra penalty, so in case of significant shortcut, they ARE chosen.
( It is possible my comments in profile or on wiki are misleading as well, I will review them. )
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 26, 2016, 23:59:45
'Delete' vectormap inside mapmanager should also delete xxmap.osm.db
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 27, 2016, 20:56:27
Iswet flag would be better translated to CZ "Za mokra" rather than "Je mokrý".
Same for other Languages
"Is Wet" @Crowdin is the quite wrong word.
What ever. If a hiker/biker isn't clever enough to handle wet tracks, he should better stay at home.
So for me this flag is an overdosed feature. just my two cents...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 27, 2016, 21:37:29
Same for other Languages

"Is Wet" @Crowdin is the quite wrong word.
What ever. If a hiker/biker isn't clever enough to handle wet tracks, he should better stay at home.
So for me this flag is an overdosed feature. just my two cents...

Hi Gynta,

Menion just overtook my naming of the flag for consistency. I as the author of the BRouter profile can name it as I want..  :-)

Edit: Using 1-2 flags means replacing 2-4 profiles by a single one, avoiding profile flood. Technically, all my bicycle profiles could be represented by a single one and several boolean flags and numerical settings. Menion has chosen reasonable conservative approach of 1-2 booleans.

BTW, I guess you misinterpreted intention of this flag, probably bacause it was incorrectly commented in Locus config. It is not about technical skills nor about avoiding danger nor about avoiding such roads, like avoid motorways. It just gives different BRouter costfactor preferences to problematic surfaces.

Edit:  E.g. the profile may prefer 6 km of soil but fine track to 5 km tertiary road. In case of iswet=1 it would take the tertiary road, as the track may be muddy and unpleasent, especially for girlfriends. You may want to think twice before taking them into muddy hell, full of track ponds.  OTOH, if it would be 2 km of such track versus 10 km of tertiary, the track  can be chosen in spite of that.

See https://github.com/poutnikl/Brouter-profiles/wiki/Bicycle-Trekking-profiles (https://github.com/poutnikl/Brouter-profiles/wiki/Bicycle-Trekking-profiles)

Trekking Wet is modification of the above. The parameter assign iswet=1 penalizes potencially muddy / slicky surfaces and little promotes paved and main roads. Weather related priority shifts are fixed*), but distinguishing weather effect on different surfaces.

*) in contrary to numerical parameters MTB_factor and smallpaved_factor, where the profile behaviour can be tuned.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 27, 2016, 21:46:15
guys, no need to worry about "is wet" parameter. It's really just "working name". Section around BRouter needs to be improved completely as I mentioned few times and as well these parameters. Anyway thanks Libor for explanation, it helps.

@gynta: deleting *.db files, thanks, agree, I'll look at it ..
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 28, 2016, 15:52:30
graphhopper.app(!) expected his routing files in "..Locus/mapsVector/"
( descripted in Forum (http://forum.locusmap.eu/index.php?topic=4036.msg30647#msg30647) )
(https://s11.postimg.org/xrqk914n3/2016_08_27_234751.png) (https://postimg.org/image/xrqk914n3/)

but Locus navigation settings expected this file in current vector map folder (could be differet)
(https://s11.postimg.org/arjwwp6tb/2016_08_27_234901.png) (https://postimg.org/image/arjwwp6tb/)

- Description in Forum is wrong.
- Checkroutine inside graphhopper app is wrong.

- Locus navigation settings detects the missing files error - but show me wrong start/errorscreen:
(https://s11.postimg.org/lsf21pz27/2016_08_27_235001.png) (https://postimg.org/image/lsf21pz27/)
(here I have selected graphhopper - not brouter)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Sersus2 on August 28, 2016, 21:55:54
I think in the last Pro version from the Google Play the TTS engine doesn't work. Today I tried many combinations of settings to make Locus to voice my custom kml tracks during navigation with no success.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on August 28, 2016, 22:22:11
recognized no problem here in setting.
please check:
settings / language & units / Text-to-speech settings / button "Test text-to-speech"
and
settings / Navigation / Select voice / select Text-To-Speech

what happend?
If there is no problem, please attach your kml track
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Sersus2 on August 29, 2016, 07:21:51
recognized no problem here in setting.
It's a weird thing but after reinstalling the application and restoring all the settings is has started to work.  :-[
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on August 30, 2016, 19:48:40
So, user steps are:
1. Attempt Brouter navigation in Locus but get timeout.
2. Use Brouter app to do same calculation, using remote.brf profile and selecting a to point and a from point.
3. Now it will work in Locus so either import track, or recalculate.
Am I right? If so it's still not very user friendly.

I uploaded a new version with some (60%) Performance improvement, and with a new shortcut to simplify this workflow:
(not yet on play, only here: http://brouter.de/brouter/revisions.html )

After a timeout, if you start brouter-app (within 5 minutes) you see "<repeat timeout>" in the profile list, and this way you can redo the timed-out calculation and update the reference track without any further click.

More user friendly?

BTW, seems that in the current Locus version, the display of timeout-messages (or any other error-messages) is broken.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on August 30, 2016, 20:51:05
Quote
Section around BRouter needs to be improved completely as I mentioned few times and as well these parameters
sure, but it is in official version and after tests with different settings i am sometimes surprised

Example: i want to "route" on an official hike trial "E1"

Setting:
1 Compute Route "Foot" no additional settings
2 Compute Route "Foot" with Custom setting "on"
3 Compute Route "Foot" with Custom setting "on" and "is wet" checked

with "add route&measure"
- result with basic settings (1) is ok  :)
- what is the difference in setting (2) custom??? where get user any info about this?? for me this track could be the wet one
- setting (3) far away ... unusable
(https://s10.postimg.org/8retnxdat/image.jpg) (https://postimg.org/image/8retnxdat/)

with "navigate to"
- why is result with setting (1) different :-[
(https://s17.postimg.org/nvax0eo6z/Nav.jpg) (https://postimg.org/image/nvax0eo6z/)

A checkbox inside custom settings "follow official tracks if possible" would make make more sense ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 30, 2016, 21:45:17
Generally I think, that publishing this Locus direct Brouter mapping feature in public locus version is rather premature, but if it happened, it at least can serve as a wider base user feedback.

Custom settings OFF works with BRouter as before, using Brouter transportation mode-profile mapping, by default the  shortest profile.

Custom settings ON was set by Menion's decision to the foot profile Walking, that is technically my Hiking template (https://raw.githubusercontent.com/poutnikl/Hiking-Poutnik/master/Hiking.brf) with set preferred SAC scale (https://wiki.openstreetmap.org/wiki/Key:sac_scale#Values) 0 ( T0 ) and max SAC scale 1 ( T1 ).

There are 2 important objection notes I have:
1/ Walking profile is aimed rather for general foot usage for walks in easy or even urban areas. Simple stone paths of SAC T2 difficulty are already forbidden.   For Hiking is better rather Hiking-SAC2 profile, or Mountain-hiking SAC3 profile. See also https://github.com/poutnikl/Hiking-Poutnik (https://github.com/poutnikl/Hiking-Poutnik)

2/ iswet flag is good rather for easy walks or trips around hybrid surface OSM way network, to prefer better surface in wet weather, if you want so - what is not always case of hiking.  For hiking on surfaces of similar kind, like all soil / grass or all gravel/stones, it makes much less sense.

My foot profiles uses as default mild foot route preference, that can be increased,given by parameter
hiking_routes_preference =   0.20  ( it cca means 6 km or official track =  5 km of otherwise identical but not offical one.
Strict  "follow official tracks if possible" is not useful in cities and even in terrain may lead to undesired effects like following 20 km detour to avoid 2 km of non marked path. But I agree something like "Strong official track preference" can make good sense. Similarly as  (conditional) Follow cycleroute flag in my bike profiles, or Stick to cycleroutes in standard Trekking.brf profile.

Menion for now decided to support only boolean flags, addressing numerical parameters by different profiles, as I do for bike profiles.

Why there is result for (1) = Brouter foot default shortest different for add route and measure and navigate to, I have no idea.
( Unless different viapoints were used or Alternative BRouter route calculation was triggered. )
There was also some issue with rounding coordinate error in BRouter, but since 1.4.3 it should be fixed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on August 31, 2016, 12:46:18
@abrensch: I'm currently sending "maxRunningTime" set to value 120, does it have any effect on this time-out? Because from what other write, seems that still default 60 seconds is used.

@poutnikl: Generally I think that BRouter over Locus currently use limited number of active users and when I need some feedback, it's usually best to take this risk and publish a  not-yet-perfectly-finished feature directly in public version.

Thanks for extra description for "Foot" profiles. I'll improve it based on your description to next version, that should also solve issue that had @balloni55 with his 2 or 3 option.

I would like to stick with boolean parameters as long as possible. We will see. Is there anything you consider as essential that is currently missing in parameters and that should be easily added?

EDIT: I'll check issue with "add new route" & "navigate to", thanks


Is here anyone active in OSM mapping? If so, may you please look at this topic? Thanks
http://help.locusmap.eu/topic/export-of-manually-drawn-routes-to-openstreetmap
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on August 31, 2016, 14:29:27
@abrensch: I'm currently sending "maxRunningTime" set to value 120, does it have any effect on this time-out? Because from what other write, seems that still default 60 seconds is used.

type mismatch. Expecting "String" but getting "Integer"
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on August 31, 2016, 15:33:00
@poutnikl: Generally I think that BRouter over Locus currently use limited number of active users and when I need some feedback, it's usually best to take this risk and publish a  not-yet-perfectly-finished feature directly in public version.

Thanks for extra description for "Foot" profiles. I'll improve it based on your description to next version, that should also solve issue that had @balloni55 with his 2 or 3 option.

I would like to stick with boolean parameters as long as possible. We will see. Is there anything you consider as essential that is currently missing in parameters and that should be easily added?

Yes, I do understand the reason for publishing to get wider user base. :-)
Sticking to booleans if fine, as the chosen numerical values can be sticked to a boolean as well.

For now, for foot context, I think about hiking router preference management, expressed in the profile by default parameter
assign hiking_routes_preference  0.20 ( 5 km of marked route = 6 km of the same, but non route ) what means a mild penalty for a way not being a hiking route.

I think about 2 booleans, that may be in outdoor Hiking context even more important than iswet parameter.
One boolean would set strong route preference, e.g. 0.60-1.0 ( 5 km of marked route = 8-10 km of the same, but non route )
the other boolean would mean stick to routes, restricting to routes only.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 01, 2016, 09:37:50
Thanks Libor, really appreciate your help with this task.

Preference for "hiking route" sounds logical for me. Other two parameters, not sure about it. Hard to say how much longer route people are willing to go. Maybe we will see based on some feedback from usage?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 01, 2016, 18:34:15
New BETA version 3.18.9.1 is just uploading to Google Play.

Main changes I want to highlight:
- new screen for work with "map items" that replace "items" tab in data manager
- massive rewrite of finalizing generated/created tracks (last step, merging etc.). This change needs to be tested and excuse possible problems that may happen here
- BRouter configuration - I was sitting maybe one/two hours with tea on it and I was not able to find working solution (from my developer point of view) that will satisfy me. Generally I agree with Arndt comments, but I hope this will be usable compromise for all ;). At least till I return at 20. 9. from small vacation ... feedback is anyway welcome.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 01, 2016, 21:21:22
thx for fixing http://forum.locusmap.eu/index.php?topic=5199.msg44648#msg44648
BRouter.. hmm - I think we need more beta versions after your vacation :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 01, 2016, 22:08:45
BRouter.. hmm - I think we need more beta versions after your vacation :)
Not working at all?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 01, 2016, 22:27:38
Locus cover timeout message:
http://forum.locusmap.eu/index.php?topic=4064.msg44797#msg44797
(posting in wrong language but using google translator should help :) )

btw
only first part is a Locus problem.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on September 02, 2016, 00:52:10
New BETA version 3.18.9.1 is just uploading to Google Play.
1. I tried menu > More functions > Map items > (no items in list) > tap big + button at bottom > boom (unfortunately Locus has stopped working).

2. position & content of all 6 user buttons on main menu had changed, a little annoying
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 02, 2016, 06:56:46
@gynta, I'll check it thanks

@Andrew Heard:
1. this button in the end only display "Not yet implemented" :), but this should not happen, thanks, consider as fixed
2. this is weird, should not happen :/. Only main menu has changed? Function panels not? (they share same settings variable).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on September 02, 2016, 10:41:23
2. this is weird, should not happen :/. Only main menu has changed? Function panels not? (they share same settings variable).
yes even weirder, problem happens on Samsung Note 3 tablet, but correct buttons/ positions on Sony Z1.

But now after reboot of tablet it is displaying correct buttons/ positions too. hmmm
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 02, 2016, 10:55:04
#216
Quote
with "navigate to"
- why is result with setting (1) different
no improvement :-[

"Navigate to" and "route&measure" > Navigation
with profile walk and bike created route work :)
but for recalculation is always used car fast :-[ see also icon in recalculation window, on each recalculation logically orange message apeares!
After long click i can change to hike/bike and recalculate again with wanted profile
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 02, 2016, 14:35:13
balloni, may you please share with me exact start/end coordinates and routing profile you have mapped in BRouter application? Because I'm trying to simulate your issue with "navigation" & "add new route" difference, but no success, thanks.

About problem with recalculation - issue in new "merge" feature. Thanks, fixed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 02, 2016, 14:42:12
Quote
may you please share with me exact start/end coordinates
start on  "Hütte",
 target "Mühle"

EDIT: "walk" BRouter profiles "off"
EDIT2: with official BRouter from Googleplay
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 02, 2016, 14:54:04
Thanks, so I've removed BRouter together with it's directory, installed new, downloaded data and here is result

https://nas.asamm.com:443/share.cgi?ssid=0lui0J4
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on September 02, 2016, 17:25:48
New BETA version 3.18.9.1

- BRouter configuration ...  hope this will be usable compromise for all ;). At least till I return at 20. 9. from small vacation ... feedback is anyway welcome.

thanx, yes I think I can get used to it

But here are my bug-reports so far:

- error messages are (still) hidden by the navigation panel, as Gynta pointed out already
  These are not just timeouts, but also the "Island" error messages
  ( "no track found" for startpoint island or "target island detected" ) and waypoint-matching failures
  (  "from-position not mapped in existing datafile" )

  To subtitle them all with "Maybe another service works" is of course not what I want to read there

- you seem to replace the start- and endpoint of the calculated track by the start- and endpoint of the routing request
  this is wrong. It replaces the first and last section of the way by "offroad" sections

- When starting navigation, the voice-announcement ("navigation is started") does not contain the transportmode anymore ( "in bike mode" ). I could not yet test what mode effectivly determines the distances and timings of the voice commands.

- However, you are maybe better of to the the mode from the gpx-response ( "locus:rteComputeType" )
 I derive that from the attributes "validForBikes", "validForCars" etc in the profiles. And I would prefer to have it back in the voice announcement.

 - After changing the mode via long-press on "recalculate", I get back to the screen containing the "recalculate" button.
  Howver, I had expected to return to navigation directly
 
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 02, 2016, 17:44:01
Hello Arndt,
thanks for a feedback.

- error messages are (still) hidden by the navigation panel, as Gynta pointed out already
  These are not just timeouts, but also the "Island" error messages
  ( "no track found" for startpoint island or "target island detected" ) and waypoint-matching failures
  (  "from-position not mapped in existing datafile" )

  To subtitle them all with "Maybe another service works" is of course not what I want to read there
Ah, that's the point. I just get a link from gynta on a German topic, where I wasn't able to understand.

- you seem to replace the start- and endpoint of the calculated track by the start- and endpoint of the routing request
  this is wrong. It replaces the first and last section of the way by "offroad" sections
Well, I don't have better solution on this ... https://groups.google.com/forum/#!topic/osm-android-bikerouting/jcdsVretpbQ ;)

- When starting navigation, the voice-announcement ("navigation is started") does not contain the transportmode anymore ( "in bike mode" ). I could not yet test what mode effectivly determines the distances and timings of the voice commands.
- However, you are maybe better of to the the mode from the gpx-response ( "locus:rteComputeType" )
 I derive that from the attributes "validForBikes", "validForCars" etc in the profiles. And I would prefer to have it back in the voice announcement.
It was just change in translation made by gynta anyway it should have no effect on other functionality. Current type used for compute is visible for example as icon on "recalculate" button in navigation menu. (well not 100% true because of small issue already reported by balloni).

- After changing the mode via long-press on "recalculate", I get back to the screen containing the "recalculate" button.
  Howver, I had expected to return to navigation directly
Long press serve only to change, what type will be used for recalculation. In most cases you then wants to tap on a "recalculate" button ...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 02, 2016, 19:23:38
Quote
so I've removed BRouter together with it's directory, installed new, downloaded data and here is result
ok, looks good :D
but not for me puuh...
i have uninstalled BRouter and deleted complete BR-folder
after new installation of V 1.4.3 with new downloaded segments same result
next i´ve repeated workflow with V 1.4.4 from post #215 same result :-[
is there anything inside locus i´ve to delete additional?
Here my screencast
https://www.dropbox.com/s/dyzhz4gbvzq64ft/Wutach.mp4?dl=0

BTW: with FF and Chrome i get a security warning after click on your link, i had to make a exception before i am able to download your video :-\
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 03, 2016, 08:41:53
balloni, sorry, I have no idea, all seems to be identical :).

And security exception, yep, I was little bit lazy so we have on server currently only selfsigned certificate. Have to purchase so offficial anyway there is no risk, no worry.

And new BETA version 3.18.9.2. Have a nice weekend.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on September 03, 2016, 11:13:58
balloni, sorry, I have no idea, all seems to be identical :).

I do not get what you guys are talking about.

The balloni-screencast shows that for walk/custom-off = "shortest" you get the shortest way. Nothing wrong.

With Libors hiking profile you get the way along the river. Also nothing wrong, because that's the whole idea of that stuff to get a nice hike instead of the shortest way.

The original bug issue was that there were differnt results for custom mode=off whether you use the "measurement tool" or "navigate-to". This cannot be confirmed from the screencast or screenshots.

Or is it mixed with the issue of having car-mode in recalculation? I also encountered ths, but this is fixed in the new beta.

There's a log-option in brouter that can be enabled by placing en empty file "debug.txt" in it's base directory. This file could help to clarify such issues, or see if the cost calculation was just on the edge and the way flipped just because the destination point was a little bit different.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 03, 2016, 12:14:02
After select navigation function a popup show me the location window.
Well, and here i don't see what location Locus need first.
start? destination? viapoint?
So I suggest to change the window title depending on requirements:
(https://s13.postimg.org/xrx4qt6oj/2016_09_03_110843.png) (https://postimg.org/image/xrx4qt6oj/) -> (https://s13.postimg.org/oy689pjpv/2016_09_03_110933.png) (https://postimg.org/image/oy689pjpv/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on September 03, 2016, 12:28:25
After select navigation function a popup show me the location window.
Well, and here i don't see what location Locus need first.
start? destination? viapoint?
So I suggest to change the window title depending on requirements:
(https://s13.postimg.org/xrx4qt6oj/2016_09_03_110843.png) (https://postimg.org/image/xrx4qt6oj/) -> (https://s13.postimg.org/oy689pjpv/2016_09_03_110933.png) (https://postimg.org/image/oy689pjpv/)
+1
This is a difficulty I found took me a while to understand.
What's more, when I press Navigate, the underlying screen has already selected from: GPS to: Screen Centre, so in most cases I just need to dismiss this particular screen. So, could this process be simplified or clarified?
That said, the interface for Brouter is now much much better.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 03, 2016, 16:01:39
currently we have three routing profile sources

1. internal
2. brouter/profiles2/
3. Locus/data/brouter/

So we need three sections:
(http://s16.postimg.org/56qq4yov5/profiles.png) (http://postimg.org/image/56qq4yov5/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 03, 2016, 16:05:50
New function "Map items " includes a wrong blurred icon for calibrated maps:
(https://s21.postimg.org/fbnxwkj8z/2016_09_03_144029.png) (https://postimg.org/image/fbnxwkj8z/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 03, 2016, 19:15:50
Quote
balloni, sorry, I have no idea, all seems to be identical
thanks help from gynta problem is solved ! 8)
- renaming locus folder
- start locus and run the routing between this two points, it work on first attemt as it should ;D
- close locus, delete new created locusfolder and finaly renamed old locus folder
- now routing work also with old locus folder 8)

but for now i didn´t understand what this workflow effect in background ???
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 03, 2016, 20:40:05
BRouter
Locus routing flags are
Avoid highways, Avoid tolls and Wet surface

Wet surface
"Try to avoid muddy or slippery roads"

Not clear for me.
This Roads are muddy or slippery only if it's raining??

or this roads always are muddy or slippery because that's his normal ground conditions (bog path, road through marshland, moore land,...)?

edit
@Wolfgang, my pleasure!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 03, 2016, 20:50:08
BRouter - Locus routing flags:
I'm not able to set different car settings.
Want set car/fast with NO flags
and set car/short with both flags.

edit
same with "Wet surface"
ALL fitting profiles have same setting (flag) after changing.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 03, 2016, 21:02:42
BRouter - BRouter profiles - Locus routing profiles
footnote does not change correctly.
Sometimes Locus show me "...orbert Renner, profiles by Poutnik" but i have disabled Locus profiles.
Sometimes Locus don't show me "...orbert Renner, profiles by Poutnik" but i have selected a Poutnik profile.

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: jusc on September 04, 2016, 16:57:53
I use a custom rom based on CM 13.
After every Locus update I have to edit my /data/system/packages.xml to have the possibilty to read/write on external SD card.  >:( Otherwise Locus stops after start.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 04, 2016, 19:15:36
Map Item screen
if i change orientation of device locus stop :-[
after i confirm "ok" locus start again

question:
why are items handeled as temporary items? > long click on data icon "remove temporary map items" they are removed
for me they are not temporary, if they are visible they are also visible after restart of locus ???
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 04, 2016, 21:44:44
Thanks Libor, really appreciate your help with this task.

Preference for "hiking route" sounds logical for me. Other two parameters, not sure about it. Hard to say how much longer route people are willing to go. Maybe we will see based on some feedback from usage?
The point is, there is wide range of need from no preference at all for city walking, to exclusive walking on marked routes in national parks or similar protected areas. Stronger the preference, longer possible detours.
All topic is similar to already long established route preferencing in standard and my bicycle profiles.
( Edit> with exception there is no hard restriction to bicycle routes only )
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 05, 2016, 08:19:10
[...]

Wet surface
"Try to avoid muddy or slippery roads"

Not clear for me.
This Roads are muddy or slippery only if it's raining??

or this roads always are muddy or slippery because that's his normal ground conditions (bog path, road through marshland, moore land,...)? 

The iswet flag means there is possiblility of being muddy or slippery for  ways that can be - according to OSM surface data -  vulnerable to that.
Iswet could be named as well as "Prefer_roads_that_do_not_get_muddy_or_slippery_if_water_is_applied_on_them". But iswet is shorter. For being muddy as normal condition, there is OSM tag surface=mud.

In trekking bike and bike travelling context, most people would take unpaved soil track shortcut, if it is supposed to be dry, but (not too big ) tertiary road detour instead, if there are/can be muddy ponds on it.

It is generally recommended not to consider things useless until they are understood. Until integrated to Locus, people familiar to BRouter used to got quickly, what iswet flag is good for, as it is an old thing already.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: tommi on September 05, 2016, 08:31:03
@poutnikl I also didn't get the meaning of iswet. Now with your explanation I'd name the flag maybemuddy instead of iswet
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: michaelbechtold on September 05, 2016, 08:33:41
and if considered top long a word, what's about PotMud for potentially muddy ;-) ?

Gesendet von meinem LG-H850 mit Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 05, 2016, 08:58:30
@poutnikl I also didn't get the meaning of iswet. Now with your explanation I'd name the flag maybemuddy instead of iswet

I have never imagined that such a simple name as iswet could cause such troubles ( and I have thought that especialy gynta would appreciate the shortness ;-)  ). It may be not necessery to tell adults that if there is wet outside, there may be muddy as well, and that wetness/muddiness disappers progressively and by different rates.  :-)   

It is on the user's common sense to decide, when the iswet condition stops for him/her  Iswet means that for the particular rider the significant part of way surfaces in the area are at wet condition. This evaluation can widely differ.

I am not sure, how many people really read the Github wiki, readme and comments within profiles. As I have very rarely received any feedback to them. What is strange, as I admit there is a lot to be improved , as I am not a great writer.

maybemuddy or PotMud makes  less sense in areas that do not get muddy even if wet. Also not all effects of iswet are related to being muddy. ..    E.g. it penalizes cobblestone or sett roads a lot, especially in downhill, as it is really dangerous surface at higher speed, if wet. Easy falls under car tyres.

Menion can name the GUI flag whatever he wants, if it follows its purpose.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 05, 2016, 14:29:18
I have created a new github wiki page, dedicated to the iswet flag. Feel free to suggest the description improvement.
Edit> e.g. some EN native speaker can suggest better weather expressions to use in sentences like  "There is wet outside", or "Ways were wet during my ride here."

https://github.com/poutnikl/Brouter-profiles/wiki/Iswet_flag (https://github.com/poutnikl/Brouter-profiles/wiki/Iswet_flag)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Viajero Perdido on September 10, 2016, 18:28:42
Hi.  Just looked at this for the first time, and skimmed the wiki.  (My head is spinning.)

In the Locus UI, may I suggest: "Wet conditions".  That means, in a general sense, things are wet right now.  "Is wet" implies knowledge of the route, but you haven't been there specifically yet.

For the explanatory text, maybe "Avoid route that may be difficult in wet weather."  (In North American English, the term "road" doesn't include trails, which are part of this.)

(In spite of my user name, I'm a native English speaker; Spanish is just a hobby to support travel.)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on September 11, 2016, 01:42:03
For the explanatory text, maybe "Avoid route that may be difficult in wet weather."
nicely worded, purpose is clear, or Avoid sections that may be more difficult in wet weather?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 11, 2016, 09:38:42

[...]In the Locus UI, may I suggest: "Wet conditions".  That means, in a general sense, things are wet right now.  "Is wet" implies knowledge of the route, but you haven't been there specifically yet.

For the explanatory text, maybe "Avoid route that may be difficult in wet weather."  (In North American English, the term "road" doesn't include trails, which are part of this.)[...]

"Wet conditions" seems good. "Iswet" followed the naming of my profile variable.  There  is useful to know there are 3 different contexts in BRouter profiles. Global context, way context and node context. Iswet is defined at global context, with no relation to any particular way or route.. There is another related variable ismuddy, at way context, with meaning the particular way has changed surface quality due wet conditions.

For the explanation, I would avoid the verb "to avoid", as the real meaning is just shifting of preferences. E.g.in an illustrative example of 2 alternatives, a primary road and a soil track: The soil track may be chosen in dry conditions if less than e.g. 1.5 times longer than the other one. At wet conditions, the threshold is moved to other value, e.g. 0.3 times longer.

Perhaps rather ways then route.  Like  "Prefer ways not difficult at wet weather"   Difficult may not be fully correct, if related to technical aspects involving skills. But I agree it is hard to choose single verb describing all aspects.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 11, 2016, 09:56:32
For the explanatory text, maybe "Avoid route that may be difficult in wet weather."
nicely worded, purpose is clear, or Avoid sections that may be more difficult in wet weather?
But it does not avoid them. Just shifts the point of switching the decision.
Section can be misleading, as it is unclear what it means. Why not just the old good  (OSM) ways ?
The shift of preferences can be justified by either of being difficult(skills) and being unpleasant(perception).
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on September 12, 2016, 00:31:12
Section can be misleading, as it is unclear what it means. Why not just the old good  (OSM) ways ?
The shift of preferences can be justified by either of being difficult(skills) and being unpleasant(perception).
I think only people familiar with OSM terminology would understand the meaning of "way" in this context. For the majority of english speaking people it reads quite strange. "Section" was more generic, but in new suggestion below "route" reads better to me. There are plenty of other places in Locus where the text could be improved and/or go round in endless discussions for marginal benefit.

Improving grammar & changing the negative (not) into a positive:
"Prefer easier ways when wet weather"
"Prefer easier route when wet weather"
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on September 16, 2016, 08:11:23
Hi guys,
I'd like to inform you that in the latest beta are available Polish Compass.pl (http://www.compass.krakow.pl )outdoor maps. Please visti the Locus store > Europe > Poland to test the map ( if you're interested in)
Petr
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 19, 2016, 17:16:13
@gynta: title of "request for location" in navigation screen improved, thanks. Btw. Locus always ask for target point. Start is set to GPS
Settings flags for every profile separately was declined after some discussion month or two before. Flags are united for all profiles for now.

@jusc: not sure how may I help here? Code of Locus Map has no effect on some crazy hacks in your device, sorry

@balloni55: rotate of "map items", indeed, thanks! "Temporary" ... all that is not stored in database is in Locus world considered as temporary

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 19, 2016, 20:53:40
hope you're relaxed now - so welcome back in the hard reality :)

thx for answer but i missing some more:

http://forum.locusmap.eu/index.php?topic=5199.msg44647#msg44647

http://forum.locusmap.eu/index.php?topic=5199.msg44695#msg44695

http://forum.locusmap.eu/index.php?topic=5199.msg44845#msg44845

http://forum.locusmap.eu/index.php?topic=5199.msg44851#msg44851

http://forum.locusmap.eu/index.php?topic=5199.msg44852#msg44852
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 19, 2016, 21:09:15
Settings flags for every profile separately was declined after some discussion month or two before.
Flags are united for all profiles for now.
?
Your label was "INTERNAL THEMES" (see shot (http://forum.locusmap.eu/index.php?topic=5199.msg44843#msg44843))
but we use PROFILES

BRouter profiles from ".../brouter/profiles2/" folder are NOT INTERNAL

my profiles from ".../Locus/data/brouter/" are NOT INTERNAL
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 19, 2016, 22:23:43
Well ...
- "begin" should be already changed (not sure but it should be already in Beta version)
- "GraphHopper data" - description is wrong, files have to be in defined root directory for vector maps
- "icon for calibrated maps" - why is wrong? it's icon from "On board calibrator" function. And blurred .. possible
- "Locus routing flags" - on this I made answer before, started with "Settings flags for every profile separately..."
- "attribution below BRouter" - thanks, I'll look at it
- "internal themes" ... this is task in preparation, anyway thanks, I'll fix this
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 20, 2016, 21:00:24
- "icon for calibrated maps" - why is wrong?
blurred .. possible
that's the point. = wrong  ;)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 20, 2016, 21:50:55
Heh, oki, and what image you expect when into this directory are automatically placed all maps from this function http://docs.locusmap.eu/doku.php?id=manual:user_guide:maps_tools:calibrator ? Just ... different, right? :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: gynta on September 20, 2016, 21:55:08
misunderstanding
only "blurred" = wrong
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: jusc on September 21, 2016, 13:35:11
@jusc: not sure how may I help here? Code of Locus Map has no effect on some crazy hacks in your device, sorry

hmm  :o  crazy hacks?
For example my music streaming app stores and caches after an update the music files without any problem on external sd card, if it is set in the app.
Locus is the only app, that doesn´t work with my external sd and custom rom (marshmallow) , if I don´t edit the data/system/packages.xml new installation and after every update. Maybe this is not the best way for Android 6.01, but it works so far.

My question is, if Locus creates the new entry in packages.xml while installing an update? If you know a better way to use the external SD as working directory for storing tracks and so on, please let me know.

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on September 23, 2016, 09:18:15
OS Street View Map for the UK incorrectly appears in the store providers under OpenStreetMap.
OS is Ordnance Survey, linked to the UK government and nothing to do with OSM. This map is however made freely available by OS.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: voldapet on September 23, 2016, 10:23:16
@john_percy
Thank you - fixed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on September 23, 2016, 11:17:27
@voldapet: It now appears in the Store but doesn't appear under Ordnance Survey in the list of online maps in map manager.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 23, 2016, 15:32:01
Whoaa, what a nice Beta version 3.18.9.4 !! Enjoy it ;)

@jusc: crazy hacks because it it not officially supported method and because Locus has absolutely no effect on what happen in this file. It's content is automatically re-generated after every single app install/update. Sorry, cannot help here.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: jusc on September 23, 2016, 16:16:16
@menion,
I just installed fresh Locus free (Beta).
It says external storage is read only. This is not true, because my crazy hack works for Locus Pro at least at the moment. So what can I do?
I wonder, that nobody else uses Android 6.01 with a custom rom?!

(http://s12.postimg.org/lqzx720nt/Screenshot_20160923_160255.png) (http://postimg.org/image/lqzx720nt/)

at Google Play in ratings somebody else wrote the same.

(http://s9.postimg.org/i8nh9ftbv/Screenshot_20160923_155619.png) (http://postimg.org/image/i8nh9ftbv/)

[Edit]
#############################
now after doing my hack the Locus Beta start looks like this:  ;D

(http://s21.postimg.org/5uauka1yb/Screenshot_20160923_163447.png) (http://postimg.org/image/5uauka1yb/)
#############################
[/Edit]

[Edit]
#############################
Quote
Whoaa, what a nice Beta version 3.18.9.4 !! Enjoy it ;)
Is there any changelog? In Beta latest changlog is 3.18.9.2 from 03.September 2016
#############################
[/Edit]
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 23, 2016, 17:34:46
@jusc I do not know how to do this automatically, really. I'm not using any custom rom and about this method I've read few times, but never checked more deeply, why and how it works, sorry. Anyway as I wrote, app itself cannot do anything here (maybe I'm wrong, so please correct me).

About version ...news, weird. Do you have version 3.18.9.4? Maybe it was not yet ready for download in your country so it downloaded previous 3.18.9.2.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 23, 2016, 20:16:39
long click measurement two fingers, nice feature :)
Code: [Select]
map_items_selection_line_value_below=0if this value is set to 2, 3, 4, 5, 6 always elevation is displayed
i noticed that direction - + of elevation value depend on which finger of both hit first on display
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on September 23, 2016, 21:16:29
long click measurement two fingers, nice feature :)
Code: [Select]
map_items_selection_line_value_below=0if this value is set to 2, 3, 4, 5, 6 always elevation is displayed
i noticed that direction - + of elevation value depend on which finger of both hit first on display
I agree, great and simple to use feature.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: john_percy on September 23, 2016, 22:26:18
@voldapet: It now appears in the Store but doesn't appear under Ordnance Survey in the list of online maps in map manager.
It appears under "OSM - Other" even in the new beta, which claims to have corrected the attribution. It's nothing to do with OSM.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on September 24, 2016, 01:14:29
3.18.9.4 beta: Locus/ BRouter Fast & Short car profiles have Unpaved checkbox, but Fast/ Cycle/ Walk profiles only have Wet Conditions checkbox. Unpaved checkbox is absolutely desirable for these latter 3 profiles too. And maybe Walk profile could use Wet Conditions checkbox. Why inconsistency?

"Absolute time when sun will rise/fall" - nice! But why does my tablet display correct sunset time, but phone displays "unknown"?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 24, 2016, 08:21:54
3.18.9.4 beta: Locus/ BRouter Fast & Short car profiles have Unpaved checkbox, but Fast/ Cycle/ Walk profiles only have Wet Conditions checkbox. Unpaved checkbox is absolutely desirable for these latter 3 profiles too. And maybe Walk profile could use Wet Conditions checkbox. Why inconsistency?

Andrew, Locus GUI config for BRouter profiles can offer only parameters, that are exposed by the chosen profiles. Neither standard, neither my bike profiles offer absolute avoidance for unpaved roads like car profiles, for quite good reasons. You may want to stay with Fastbike profile, or my template e.g. with MTB_factor -2.0.

Walking in urban/near urban mixed surface network could make use of Wet Conditions, but generally, the parameter is probably less useful for hiking. See also https://github.com/poutnikl/Brouter-profiles/wiki/Iswet_flag (https://github.com/poutnikl/Brouter-profiles/wiki/Iswet_flag). The parameter is exposed, so it can be used.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 24, 2016, 09:36:51
Quote
Map Item screen
if i change orientation of device locus stop :-[
after i confirm "ok" locus start again
problem in main item screen is solved :)
but with opened item detail locus stop furthermore while changing orientation :-[
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 24, 2016, 17:46:18
observation while playing with 2-finger distance measure
https://www.dropbox.com/s/h7q02erd0fl64yx/2%20finger.mp4?dl=0

sec 7-14 > measure line disapears if line is horizontal

sec 17 > if i leave locus by accident, distance line is visible after i return to locus. When i zoom out, maploading is blockd till i do next 2-finger touch > sec 28
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on September 24, 2016, 23:55:16
3.18.9.4 beta: Locus/ BRouter Fast & Short car profiles have Unpaved checkbox, but Fast/ Cycle/ Walk profiles only have Wet Conditions checkbox. Unpaved checkbox is absolutely desirable for these latter 3 profiles too. And maybe Walk profile could use Wet Conditions checkbox. Why inconsistency?

Andrew, Locus GUI config for BRouter profiles can offer only parameters, that are exposed by the chosen profiles. Neither standard, neither my bike profiles offer absolute avoidance for unpaved roads like car profiles, for quite good reasons. You may want to stay with Fastbike profile, or my template e.g. with MTB_factor -2.0.
OK, so Locus scans each profile for exposed parameters & displays as list . This would explain the Locus delay in changes with the UI - reading/ writing the (pro)file. Clearly, absolute avoidance of unpaved roads is not desirable, and may result in huge detour, although it could be argued the user can also view the proposed route from each checkbox state and make own decision, but surely hint from user for increased cost to selection of unpaved roads would be nice, and operates with similar logic/ consistency to Wet Conditions.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on September 25, 2016, 14:26:39
OK, so Locus scans each profile for exposed parameters & displays as list . This would explain the Locus delay in changes with the UI - reading/ writing the (pro)file. Clearly, absolute avoidance of unpaved roads is not desirable, and may result in huge detour, although it could be argued the user can also view the proposed route from each checkbox state and make own decision, but surely hint from user for increased cost to selection of unpaved roads would be nice, and operates with similar logic/ consistency to Wet Conditions.

AFAIK, Locus for now uses just a priori chosen set of exposed parameters, so it is not dynamic.
The user has wider options to choose profiles with predefined numeric parameters, or tweak the parameters directly if he wants. It provides much finer tuning of profile behaviour than flipping flags. It is like the continuous tuning of radio volume being better than High/Low volume switch.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 25, 2016, 14:27:15
action after "found it"
good solution for users who don´t use FN ;)
one idea to keep better overview, is it possible to use "green marked smiely" for uploaded geocaches also in this folder?

(http://s10.postimg.org/5zif3wx4l/log_icon.jpg) (http://postimg.org/image/5zif3wx4l/)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Christian on September 25, 2016, 17:24:17
If not mentioned yet for last stable version:
Sometimes when using "add route & measure" the route is not computed. I have to change the profile and back than the route is computed. Seems that the choosen profile is not taken properly for computation.

If "advanced setting" in profiles in "add route & measure" is activated (but "iswet" not choosen)  the route is sometimes not computed or in a senseless way.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 28, 2016, 09:00:11
@balloni55: I believe it is solution for all geocachers :). About icons, sorry, this will increase loading time a lot as testing if certain field note is already logged or not, take a while.

@Christian: "sometimes" is a problem. I need to simulate this problem and I never noticed such issue, sorry. Some exact steps for me?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 28, 2016, 09:42:20
@menion, a comment to #274, #279, #280 ??
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on September 28, 2016, 09:45:43
I was not reacting on it, sorry, but all three topics are solved. "Quick measure" line was only beta and settings wasn't working before. Only what I'm unable to simulate is that line hide to you if horizontal. Well you will see in next version as I did some changes in background system. Thanks!
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on September 28, 2016, 09:55:14
Locus V 3.18.9.4 Report.
Recalculate using "GraphHopper" NOK.
Startposition offtrack: (Distance away form track is above the value set in distance for trigger recalculation) 
= No offtrack autorecalculate triggering.
Navigation Button continuously shows Question Mark. 
By Pushing the Question Mark Navigation Button( to activate Manual Recalcalute button): Locus Map Failure and Exit.

Same exercise by Brouter is succesfull.
Start from offtrack position -> Triggers autorecalculate  = Resulting in autorecalculate succes.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on September 30, 2016, 19:58:09
V3.18.9.5
Quote
Only what I'm unable to simulate is that line hide to you if horizontal. Well you will see in next version as I did some changes in background system
#280, unfortunately no improvement of both described (screencast) behaviors
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 02, 2016, 08:32:00
Quote
# values above/below lines:      nothing: '0', distance: '1', bearing: '2', ETA: '3', elevation: '4', time to: '5', ETA & time to: '6'
is it possible to add also bearing&elevation: '7' to config file?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on October 02, 2016, 10:02:32
Hello,
In New beta 3.18.9.5 the two fingers measurement doesn't show altitude value.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 02, 2016, 10:05:44
settings/maps/maps objects/Quick measurement
and additional setting in config.cfg see code in #290
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on October 02, 2016, 18:32:33
settings/maps/maps objects/Quick measurement
and additional setting in config.cfg see code in #290
Thank you,
I have the altitude value back.
I don't know why the "line below info" is disabled in the last beta, and I do not understand why the two fingers measurement is disabled by default.
But the important is to have both back

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 04, 2016, 11:00:34
@balloni55: unfortunately no such problem happen on any of devices I've tried, so for now I have no solution on this weird problem, sorry.
Parameter "6" was created mainly because both are time values that are close to each other. Anyway you wants bearing & elevation that are not quite connected so it make sense to have them separately. There may exist many other combinations, but I would like to stick with current options. Thanks for understanding.
@lor74cas: in previous beta, this option was hardcoded in app. Now it is configurable over config.cfg and may be enabled in Locus settings (disabled by default). That's all ...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on October 04, 2016, 17:02:05
Report Locus V 3.18.9.5
I noticed very serious problems using navigation and recordings with the actual Beta.
In first instance I thought about a serious hardware phone gps problem. 
I never before noticed such serious positioning problems.
But next tests, using the Pro version, all was and still is normal functional in both navigation and trackrecords.

A today's trackrecord:  See track in attached .zip

V 3.18.9.5 Using "Navigate to" function AND "track record".
At start navigation was unstable. Navigating instructions "in the wild" and on map was showing very large position jumps.

I closed track recording by actual Beta.  And had an immediate restart of "track record" by the Pro version.
Result: The Beta version in use for the "Navigate to" function AND at the same time the Pro version  for "track record". 
This parallel operation was resulting in a Normal "Navigate to" functionality by the Beta version,  AND normal "track record" by the Pro version now.

In the attachment:  Trackrecord  (uncleaned)
Tracksegment 1: Trackpoint record from first trkpt point to point 803.  "Navigate to" AND "track record" by V 3.9.18.5
Tracksegment 2: Trackpoint record from point 803 to 12173. "Navigate to" by V 3.9.18.5 AND "track record" by V 3.18.9.

Any idea what was (is) going on here ?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 04, 2016, 19:16:06
Willy, this is almost unbelievable!

No idea, sorry. Mainly because track recording system is only a "consumer" of received locations. It do not promote any changes back to system, so I have absolutely no idea, how may track recording affect coordinates ... technically it is not possible.

I just published new Beta version so try it please if possible. I won't do any bigger changes, so this version is candidate for release to Monday when I plan publishing. I'll do also some more testing. Few hours ago I was just training (running), so only track recording was running and only small problem at start, but simultaneously running different recording application, recorded exactly same track. Weird...
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 04, 2016, 20:51:26
V 3.18.9.6
if i tap near the left side of the screen while 2 finger measure, measurement freeze. Reset can be done with a new two finger touch inside the screen
https://www.dropbox.com/s/z603p9tevsxkdl2/2finger.mp4?dl=0
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: lor74cas on October 04, 2016, 20:58:31
V 3.18.9.6
if i tap near the left side of the screen while 2 finger measure, measurement freeze. Reset can be done with a new two finger touch inside the screen
https://www.dropbox.com/s/z603p9tevsxkdl2/2finger.mp4?dl=0
Confirmed
I think that when you touch the left side of the screen the activation of side panel casue the issue.

Inviato dal mio SM-G800F utilizzando Tapatalk

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 05, 2016, 07:40:14
thanks guys, issue fixed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on October 05, 2016, 11:31:58
Using 3.18.9.6 for navigation I found the usual magenta line was not being displayed. I've never seen this before.
(https://s16.postimg.org/dyijt5p0x/2016_10_05_20_24_27_C_Temp_SHAREit_C6903_photo.jpg) (https://postimg.org/image/dyijt5p0x/)

I then swapped to 3.18.0 Pro & restarted navigation, and the normal magenta navigation line was displayed properly.
(https://s15.postimg.org/akx1887w7/2016_10_05_20_26_06.jpg) (https://postimg.org/image/akx1887w7/)

I then swapped back to 3.18.9.6 & restarted navigation again. Same problem - invisible navigation line. But maybe 10 minutes later I found that the magenta navigation line was again displayed.

Unlike 0709 I didn't find any other problems with navigation. I also performed same navigation with GPS disabled and normal magenta navigation line was displayed properly. Weird.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on October 05, 2016, 23:21:34
05-10-2016
Trackrecord by phone THL 4000 (GPS).  Using Locus Beta V 3.18.9.6 and Locus PRO  V 3.18.9

Track segment 1:  "Navigate to" by Beta AND track record by Beta. "Navigate" result unstable/unreliable !
Track segment 2:  "Navigate to" by Beta AND track record by the PRO version. "Navigate" result stable/reliable.
Track segment 3.  "Navigate to" by Beta AND track record by Beta.  "Navigate " result unstable/unreliable !

A double check recording was made by Locus V 3.18.9.5 and  Samsung tablet TAB 4  (GPS + GLONASS)

Both track recordings in the attached .zip.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 06, 2016, 10:26:31
@Andrew Heard: hmm line is not on the first screenshot visible completely, so even a thin line on part you already passed is not visible. It may only means that Locus a) considered that track is not visible in current view, b) has any problems with rendering of this line. Never noticed something like this on own device, do you have steps to reproduce it please?

@0709: uff. Willy, please find a while and use for a few minutes [ur=https://nas.asamm.com/share.cgi?ssid=0IgvFm5l]this beta version[/url] I made for you. It may be little slower as it will print out few information into Locus/logs/X.log file. Try to simulate this problem and after a while stop it and send me please latest log(s). Maybe if you enable in Locus settings recording of NMEA messages and send me also this message, it will be useful. Thank you and sorry for a complications. I still have absolutely no idea how may something like this happen.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on October 06, 2016, 11:31:53
@Andrew Heard: hmm line is not on the first screenshot visible completely, so even a thin line on part you already passed is not visible. It may only means that Locus a) considered that track is not visible in current view, b) has any problems with rendering of this line. Never noticed something like this on own device, do you have steps to reproduce it please?
@menion - I've been using navigation for the last year. I can tell when it isn't displaying correctly. I've never noticed it before either, and although I don't have great screen captures sorry or steps to reproduce (yet), but as I said, it rendered perfectly on Pro, but not (at times) with latest Beta, on simple road/ route I use a lot for previous testing over the last year. I will try to reproduce next week
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 06, 2016, 11:43:47
Navigate to:
arrow on map "keep left" thats ok, but top left icon advice me to go right ????
(https://s9.postimg.org/4l1ftzswb/Richtung.jpg) (https://postimg.org/image/4l1ftzswb/)

pofile on/off:
sec 0 > locus profile is switched on and i get direction advices
sec 12 > i switch profil off
sec 19 > recalculate, i get no direction advices only destination is visible :-[
sec 37 > i switch on locus profil
sec 44 > direction advices are back
https://www.dropbox.com/s/x5z791h6r708or0/profil%20on%20off.mp4?dl=0

Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 06, 2016, 12:22:41
@Andrew Heard: understand, thanks. If you find something that may helps, let me know. Seems that publishing version next week (and not this one) was a good idea. I'll try to get out for some longer testing because of this and as well, because of Willy's (0709) issues. Thanks

@balloni55: if I remember correctly (@poutnikl corrects me), default BRouter profile do not generated navigation commands for a foot profile. Please try it with cycle/car profile if it works correctly. It was also one more reason, why I was in hurry with creating custom settings for BRouter directly in Locus > because many users wrote us that for cycle it works correctly, but for "foot", Locus do not navigate.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 06, 2016, 15:58:28
Quote
Please try it with cycle/car profile if it works correctly.
work with both :) thanks
any idea to my question in screenshot?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: 0709 on October 06, 2016, 20:13:58
Had a look at my historic records. A first such strange record was at 1/10/2016.
Did not report as I thought this to be a serious hardware phone gps issue.
Back home now. Installed this test .apk Beta version 3.18.9.7.
Had a 11km testdrive. "Navigate to" AND "trackrecord" active.
No problems reported.  Trackrecord attached.
Will do some more test. I keep you informed.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on October 06, 2016, 20:23:03
@balloni55: if I remember correctly (@poutnikl corrects me), default BRouter profile do not generated navigation commands for a foot profile. Please try it with cycle/car profile if it works correctly. It was also one more reason, why I was in hurry with creating custom settings for BRouter directly in Locus > because many users wrote us that for cycle it works correctly, but for "foot", Locus do not navigate.
Correct, the Brouter default foot profile is Shortest, that is for some reasons about a year old, not updated and not aware of the Brouter navigation instructions. The Hiking/Walking should work fine.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 06, 2016, 20:36:00
@poutnikl thanks!

@balloni55: give me please coordinates so I may try it. There should be no problem in Locus anyway, it will be more a "problem" of routing service (BRouter?).

@0709: I'm glad to hear it. I have no idea how this may happen anyway I made one small change on every possible place that may mess coordinates little bit and seems it helped. Perfect, uff :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 06, 2016, 20:57:21
Quote
give me please coordinates so I may try it.
to get the situation from screenshot
start on
N 48°55.350  E 8°51.880
navigate to
N 48° 54.975  E 8°52.470
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: erfi on October 06, 2016, 21:28:16
@balloni55: Du kannst im profile2-Ordner die Original-shortest.brf gegen die im nachfolgenden Link (Beitrag vom 27.05.16) leicht angepasste Version austauschen. Dann sollte BRouter Anweisungen erzeugen. Ich nutze sie seither mit Erfolg.
http://forum.locusmap.eu/index.php?topic=4064.msg43212#msg43212

@0709, @menion: Habe gestern und heute bei Autofahrten die Locus-Navigation bei gleichzeitiger Trackaufzeichnung getestet. Keine Probleme, alles perfekt!  :)  Locus Beta 3.18.9.6 benutzt.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 07, 2016, 07:39:48
@ erfi, thanks works perfect ! 8)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on October 07, 2016, 10:00:11
arrow on map "keep left" thats ok, but top left icon advice me to go right ????

It's the other way round: go left but keep right. It's perfectly reasonable to go left but keep right, if there are two close-by choices on the left side. Unfortunatly, a navigation command can only express one aspect so sometimes you have to decide and in a complex situation there are cases where it's confusing
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 07, 2016, 10:53:53
@ arndt, thanks for your answer i understand what you´ve explained :-[
but in this example it´s only one forest path leading left i have to go
and  not a  multi-lane highway.

I suspect, if i use morse signal with disabeled screen for navigation  i´m lead to the wrong direction :-\
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on October 07, 2016, 13:15:56
@Balloni55: The scenario is same for motorways or paths. The path may be turning left when you are to take the right fork. The only reasonable hint is to keep right.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: abrensch on October 07, 2016, 13:26:45
.. but in this example it´s only one forest path leading left i have to go and  not a  multi-lane highway.

There's a grade5 track going to the east, maybe it's not really visible:

http://brouter.de/brouter-web/#zoom=19&lat=48.919378&lon=8.867397&layer=OpenStreetMap&lonlats=8.866785,48.919824|8.867989,48.919198&nogos=&profile=trekking&alternativeidx=0&format=geojson

Only grade1 tracks get a higher "priority classifier",  your grade2 and this grade5 are considered equal-priority, and therefore you get the keep-right hint.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 07, 2016, 14:13:44
Nice discussion guys, thanks!

With this comes one question from me as well. It happen to me already sometimes then I ride probably similar track in woods like @balloni55 ... thin road for one bike and now I hear "keep right". Isn't in such cases better to say "slightly left" or "left" (based on angle of course) command instead of this, which is more suitable for multi-line highway? I'm asking because in such cases, some hint about expected angle (like now the road will be slightly to left) should be more useful then "keep right", which may also means "ride straight because there is another road to left". Just my two cents.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: poutnikl on October 07, 2016, 19:21:54
Such a hint is not about the turns and angles. It is about the forks, if the one *relatively* more to left or more to right is to be taken.

I do not see "keep right(way) / left(way)" in this scenario confusing..   If I would hear (slight) left because a left turn just before the fork, I would be confused. Should I go left left or right left ?

I remind myself some Indiana Jones scene about carriages on the cave railway. For them was keep right / left quite essential. Sometimes for downhill MTB as well, as the choice cannot often be undone.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 08, 2016, 12:19:11
Thanks Libor! Understand. Maybe I'm just too used to hear "keep right" on a highway and then it sounds little bit funny in thin forest path :)
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: balloni55 on October 10, 2016, 17:27:12
V 3.18.9.8
release notes
"Settings" button on track record widget changed to icon of current profile
perhaps i didn´t understand this note
since now i can´t find icon which change, where i have to look? :-[
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 10, 2016, 19:57:58
Hmm you have a track recording widget with Beta version (Locus Map FREE)? :) Sorry, it is only in Pro version, so in this case it is needed to wait on public version.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: Andrew Heard on October 11, 2016, 13:01:51
@Andrew Heard: understand, thanks. If you find something that may helps, let me know. Seems that publishing version next week (and not this one) was a good idea. I'll try to get out for some longer testing because of this and as well, because of Willy's (0709) issues. Thanks
I tried identical navigation test today as last week (in which navigation line wrongly appeared transparent) but this time worked perfectly. I have no idea why different. Oh well.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: joeloc on October 11, 2016, 14:40:27
Since the latest beta was labeled "release candidate" already if I remember correctly, I once again want to point out the super weird strangeness of the new map items interface:

I'm really not a Locus beginner, but I have a seriously hard time figuring out how this is working. I navigate to some folder with my kmzs in the new map items dialog. Then I load a file by clicking on the "eye". Then Locus blocks and I wait for half a minute while it loads. Then I click on the three dots sub menu of the same file and select "center element" to actually see it displayed on my map. Not really a funny procedure to start with.

It gets even worse when I want to hide the file again though. Because apparently, I need to remember the exact sub directory and name where I loaded it from and navigate there manually(!) from some root folder. Only then I can turn off the "eye icon" to hide. Thats really pure horror if you deal with more than just one overlay and have them sorted in nested directories.

Apparently there is also a separate new "sidebar" menu for map items that shows all the loaded overlays. But strangely, the sidebar thingy cannot unload anything. I can "dive into" a kml/kmz and hide specific elements, but not simply unload the whole thing.

This whole process seems completely unlogical to me. I just cant understand how it's supposed to work. Maybe I am missing something very obvious here?
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 11, 2016, 20:34:35
@Andrew Heard: thanks, but .. you know ... it's needed to simulate this problem, so if you find something useful, please let me know.

@joeloc: thanks for a feedback. You are same as @voldapet . One day before release, he, same as you, write me essay what should be changed in this new "Map items" screen. Well, nice thanks. Anyway I do not understand, why you write it day before release when this feature is in Locus for testing almost two months!!! So sorry, but to next version, there won't be any serious changes.

To your problems ... quick return to map and back on same place ... use small bottom left "home" button. Loading dialog ... yes it's there, same as in previous "items" tab. Neverending story with cumberstone UI that break fluent work etc. ... I know, don't worry.

Anyway feature is in active development so I register these issues, thanks.
Title: Re: [APP] - version 3.18.x (27. 6. 2016+)
Post by: menion on October 13, 2016, 06:43:08
Hi guys, version is out ...
this was looongest time between two major versions ever, I think. Hope list of news will have something interesting for everyone.
Thanks also for a valuable feedback, just please criticize (constructively), but don't take example from joeloc above and crtiticize at least few days before planned release. Better as soon as you discover any problem.
Thanks!

EDIT: ah! and thanks @gynta for neverending updates of first post with published versions. I almost always forget to update it :).