Author Topic: [APP] - version 3.18.x (27. 6. 2016+)  (Read 74707 times)

Offline poutnikl

  • Padavan of Locus
  • ***
  • Posts: 439
  • Thanked: 41 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6-128G) / And9-Pie / LocusMap Pro
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #180 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.


https://github.com/poutnikl/Brouter-profiles/wiki
When a user digs profiles up from the GitHub repositories,
they will be hopefully wrapped in some wiki knowledge....  :-)
 

Offline poutnikl

  • Padavan of Locus
  • ***
  • Posts: 439
  • Thanked: 41 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6-128G) / And9-Pie / LocusMap Pro
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #181 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 )
https://github.com/poutnikl/Brouter-profiles/wiki
When a user digs profiles up from the GitHub repositories,
they will be hopefully wrapped in some wiki knowledge....  :-)
 
The following users thanked this post: Andrew Heard

Offline LocusUser#1

  • Apprentice of Locus
  • **
  • Posts: 126
  • Thanked: 63 times
    • View Profile
  • Device: Samsung A5 (2017)
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #182 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
 

Offline T-mo

  • More than Newbie
  • *
  • Posts: 23
  • Thanked: 1 times
    • View Profile
  • Device: One+3
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #183 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
 

Offline abrensch

  • More than Newbie
  • *
  • Posts: 86
  • Thanked: 16 times
    • View Profile
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #184 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
 

Offline john_percy

  • Master of Locus
  • ****
  • Posts: 636
  • Thanked: 89 times
    • View Profile
  • Device: MotoG
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #185 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.

 

Offline poutnikl

  • Padavan of Locus
  • ***
  • Posts: 439
  • Thanked: 41 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6-128G) / And9-Pie / LocusMap Pro
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #186 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.
https://github.com/poutnikl/Brouter-profiles/wiki
When a user digs profiles up from the GitHub repositories,
they will be hopefully wrapped in some wiki knowledge....  :-)
 
The following users thanked this post: Jencek

Offline Viajero Perdido

  • More than Newbie
  • *
  • Posts: 93
  • Thanked: 11 times
    • View Profile
  • Device: Samsung Galaxy Tab S2 (Android 7), Blackview BV6000s (Android 6), Nexus 7 (2013) for Alpha/Beta testing.
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #187 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.
 

Online menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11231
  • Thanked: 271 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #188 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
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline Christian

  • Premium
  • Master of Locus
  • ****
  • Posts: 798
  • Thanked: 9 times
    • View Profile
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #189 on: August 17, 2016, 19:17:43 »
Pitty.
:(
 

Offline poutnikl

  • Padavan of Locus
  • ***
  • Posts: 439
  • Thanked: 41 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6-128G) / And9-Pie / LocusMap Pro
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #190 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, 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

https://github.com/poutnikl/Brouter-profiles/wiki
When a user digs profiles up from the GitHub repositories,
they will be hopefully wrapped in some wiki knowledge....  :-)
 

Offline john_percy

  • Master of Locus
  • ****
  • Posts: 636
  • Thanked: 89 times
    • View Profile
  • Device: MotoG
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #191 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.
 

Online menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11231
  • Thanked: 271 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #192 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.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline balloni55

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 2452
  • Thanked: 94 times
    • View Profile
  • Device: Motorola G3 MM 6.01
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #193 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
Locus PRO 3.38.3
 

Online menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11231
  • Thanked: 271 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.18.x (27. 6. 2016+)
« Reply #194 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?
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!