Author Topic: [APP] - version 3.45.+ ( 14. 4. 2020 )  (Read 3969 times)

Offline balloni55

  • Global Moderator
  • Professor of Locus
  • *****
  • Posts: 2673
  • Thanked: 125 times
    • View Profile
  • Device: Samsung XCover 4s Android 10
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #15 on: April 24, 2020, 19:04:51 »
@ Petr
and how can user terminate subscription??
Locus PRO 3.46.1
 

Offline poutnikl

  • Master of Locus
  • ****
  • Posts: 607
  • Thanked: 63 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6G/128G) / A10 / LM3 Pro + LM4 alpha
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #16 on: April 26, 2020, 17:51:15 »
ETA in route planner:

If I use BRouter bicycle profiles in the route planner, it is my understanding the stats bar uses the ETA ( estimated time of arrival ) provided by Brouter, or by some internal defaults.

But if I make LocusMap calculate ETA by ETA estimation from the planner menu, none of ETA estimation profiles fits the stats ETA.

I think it could be good to optionally allow binding a particular ETA estimation profile to a particular Locus transportation mode.

Eventual votes at https://help.locusmap.eu/topic/consistence-of-eta-in-the-route-planner


Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
« Last Edit: April 26, 2020, 17:59:46 by poutnikl »
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....  :-)
Try also https://github.com/poutnikl/Brouter-profiles/wiki/Determining-optimal-bicycle-profile
 
The following users thanked this post: Andrew Heard

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 170
  • Thanked: 53 times
    • View Profile
  • Device: THL4000 CM12.1 (A5.1.1) SM-T235 (A5.1.1) MI A2 Lite (A9)
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #17 on: April 26, 2020, 18:54:35 »
ETA for the "universal person"  ?
Or a more optimal, so a realistic ETA expectation, by personalised Locus setting.
Suggestion: https://forum.locusmap.eu/index.php?topic=5953.msg49935#msg49935
« Last Edit: April 26, 2020, 19:32:46 by 0709 »
Locus Pro 3.46.2
 

Offline poutnikl

  • Master of Locus
  • ****
  • Posts: 607
  • Thanked: 63 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6G/128G) / A10 / LM3 Pro + LM4 alpha
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #18 on: April 26, 2020, 19:43:12 »
Well, the ideal case would be to be able to create and assign custom Route planner ETA profiles, tailored for your performance and various activities.

But as we do not live in an ideal world, for now just the Menion's predefined profiles from the Planner.

Note that I mean in this context just planned ETA, not the real time ETA on the road, but that should be obvious.

For now, I can observe the bicycle Router stats ETA fluctuates between fast and slow trekking ETA profiles. It would be better if you knew how it is calculated, no matter how good it fits your best fit.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

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....  :-)
Try also https://github.com/poutnikl/Brouter-profiles/wiki/Determining-optimal-bicycle-profile
 

Offline 0709

  • Apprentice of Locus
  • **
  • Posts: 170
  • Thanked: 53 times
    • View Profile
  • Device: THL4000 CM12.1 (A5.1.1) SM-T235 (A5.1.1) MI A2 Lite (A9)
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #19 on: April 26, 2020, 20:32:26 »
Quote
Note that I mean in this context just planned ETA
hmm...the suggestion is about the planned ETA (inclusive all expected arrivals onto the medium Via Points (for example a mountain top), of course only in Locus map. (Not by any external web source). So..to say the expected timespan ETA as generated in your personalised installed Locus

Quote
ETA (inclusive all expected arrivals onto the medium Via Points (for example a mountain top)

Time to next Via...
https://help.locusmap.eu/topic/timedistanceeta-to-next-via-point#comment-71695
« Last Edit: April 28, 2020, 08:58:45 by 0709 »
Locus Pro 3.46.2
 

Offline poutnikl

  • Master of Locus
  • ****
  • Posts: 607
  • Thanked: 63 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6G/128G) / A10 / LM3 Pro + LM4 alpha
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #20 on: April 26, 2020, 20:38:53 »


hmm...the suggestion is about planned ETA, of course only in Locus map..to say in your personal installed one.

I know it is, just not to confuse not involved users, as there was much of discussions about real time ETA.

I would prefer rather customizable than personal installation.



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

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....  :-)
Try also https://github.com/poutnikl/Brouter-profiles/wiki/Determining-optimal-bicycle-profile
 

Offline poutnikl

  • Master of Locus
  • ****
  • Posts: 607
  • Thanked: 63 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6G/128G) / A10 / LM3 Pro + LM4 alpha
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #21 on: April 26, 2020, 21:09:52 »
But customisation could do exactly that. Setting your own flat, climbing and descending speed rates, that may decrease over the time.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

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....  :-)
Try also https://github.com/poutnikl/Brouter-profiles/wiki/Determining-optimal-bicycle-profile
 

Offline Andrew Heard

  • Master of Locus
  • ****
  • Posts: 779
  • Thanked: 46 times
    • View Profile
  • Device: Samsung Galaxy A5 Oreo/8, Lenovo Note 4 Nougat/7.1
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #22 on: April 27, 2020, 01:17:32 »
I *think* you are both in agreement! I agree too. Instead of the current 14 Estimated Travel Time profiles (track > More), none of which meet my requirements, it would be much better if a user could define their own. And for @0709 these could be updated over time to reflect "physics". I've always been curious (annoyed) why there is no car profile too, which is inconsistent with default routing profiles.
 

Offline voldapet

  • Administrator
  • Padavan of Locus
  • *****
  • Posts: 493
  • Thanked: 12 times
    • View Profile
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #23 on: April 27, 2020, 09:44:44 »
@balloni55
thank you. You can cancel it anytime in the detail of the item in the Locus store. I updated the description of this item to improve it.
Thanks Petr
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11779
  • Thanked: 409 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #24 on: April 27, 2020, 09:52:56 »
Hi guys,

the best to start with a small explanation.

1. ETA visible directly in route planner
Compute ETA should match ETA computed during navigation (at least when navigation starts). It really internally start navigation feature in some kind of "simulation" and just compute time to target and finish it.

Here are two options:
- routing service supply times between navigation points, than app only sum these times
- or does not supply them, then Locus Map use average speed and distance. Speed is internally computed over time (1 hour block) for you based on activity in three categories: walk, cycle, car.

2. Time visible in "Compute trip" feature
In this case, it is a completely independent feature. Every profile has hardcoded a few parameters (more below). Use-case of this feature is to simulate real travel experience together with breaks on snacks etc.

Code: [Select]
        // basic horizontal speed in m/s
        var speed: Double = 1.0
        // speed to uphill (in vertical metres per hour)
        var speedUp: Double = 1.0
        // speed to downhill (in vertical metres per hour)
        var speedDown: Double = 1.0
        // container with breaks
        var breaks: Hashtable<Int, Int> = Hashtable()

So for example "Bike trekking easy" looks like:
Code: [Select]
        tripCycle1.speed = 14.0 / 3.6
        tripCycle1.speedUp = 500.0 / 3600
        tripCycle1.speedDown = 1000.0 / 3600
        tripCycle1.breaks[60 * 60] = 10 * 60
        tripCycle1.breaks[180 * 60] = 30 * 60
Among speeds, it also define 10 minutes break every 1 hour and 30 minutes big break every 3 hours.

Hope my explanation is clear.

Space for improvements I see:
- in case routing service return time, keep some kind of internal modification that modify even these time based on users real speed (discussed here on for maybe the year before)
- for "Compute trip" feature, allow to modify/create customized profiles
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 
The following users thanked this post: Andrew Heard

Offline joeloc

  • Premium
  • Padavan of Locus
  • ***
  • Posts: 331
    • View Profile
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #25 on: April 28, 2020, 10:34:42 »
Locus exports/imports track color to gpx in a standard extension... and locus activity as custom locus extension. However, the rendering pattern and color (arrows, dots, whatever) is not exported/imported. Could you maybe make this work too?

I remember this working already at one point, that's why I post it here in the versions thread. But maybe I am mistaken, it's been a long time that I tried to import properly colored tracks with patterns.

Code: [Select]

<extensions>
<line xmlns="http://www.topografix.com/GPX/gpx_style/0/2">
<color>0D9B0D</color>
<opacity>0.83</opacity>
<width>8.0</width>
</line>
<locus:activity>cycling_mountain</locus:activity>
</extensions>
 

Offline poutnikl

  • Master of Locus
  • ****
  • Posts: 607
  • Thanked: 63 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6G/128G) / A10 / LM3 Pro + LM4 alpha
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #26 on: April 28, 2020, 10:52:28 »
@menion Thank you for the thorough explanation. I have approximately already understood what you have explained.

What I had in mind was, that for user convenience, the user could decide, what should be there.

 The summary ETA value on the stats bar could be

either as is now, as is or modified internally
either as the trip  ETA result from a chosen  particular ETA profile(built-in or custom),

It would have advantage of not to have to go there.

Sent from my Xiaomi MI A2 / Android 10, via Tapatalk
« Last Edit: April 28, 2020, 13:04:04 by poutnikl »
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....  :-)
Try also https://github.com/poutnikl/Brouter-profiles/wiki/Determining-optimal-bicycle-profile
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11779
  • Thanked: 409 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #27 on: April 28, 2020, 19:49:53 »
@0709
- invisible short segments > thanks, fixed
- recalculate all > hmm, may you give me a screenshot? Are you sure, it is an old track? Isn't it an alternative route provided by online GraphHopper in the Alpha version?

@joeloc
This never worked yet. I was already thinking about it, but because no global standard exists, I left it as is now. How you may use this? Just to share tracks from your Locus to other Locus instance right?
There is quite a lot of parameters, but I'll look at it ...

@poutnikl
This is definitely not a task for one evening ... I'm now little pushed by time to finish some less or more cosmetic improvements for LM4. Once it will be out, I really really wants to focus mainly on many incorrect algorithms on background so please remind me (again, sorry), this serious topic maybe half an year later. Thanks!
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline poutnikl

  • Master of Locus
  • ****
  • Posts: 607
  • Thanked: 63 times
    • View Profile
    • My Brouter Profiles
  • Device: Xiaomi MI A2 (6G/128G) / A10 / LM3 Pro + LM4 alpha
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #28 on: April 28, 2020, 20:16:23 »


@poutnikl
This is definitely not a task for one evening ... I'm now little pushed by time to finish some less or more cosmetic improvements for LM4. Once it will be out, I really really wants to focus mainly on many incorrect algorithms on background so please remind me (again, sorry), this serious topic maybe half an year later. Thanks!

Sure :-) No big deal. Just nice to have.
I wish you being just pleased by the user feedback, not being frustrated by it.
Thanks for all your great work.



Sent from my Xiaomi MI A2 / Android 10, via Tapatalk

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....  :-)
Try also https://github.com/poutnikl/Brouter-profiles/wiki/Determining-optimal-bicycle-profile
 

Offline menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11779
  • Thanked: 409 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: [APP] - version 3.45.+ ( 14. 4. 2020 )
« Reply #29 on: April 28, 2020, 21:43:38 »
Feedback is amazing all these years ... and most probably it's the main reason I do this day by day for more than 10 years now :).

The only problem I see > my own on my working speed ... unfortunately, it won't be better :)
« Last Edit: April 28, 2020, 21:45:26 by menion »
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 
The following users thanked this post: tramp20, tapio, Andrew Heard