Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - poutnikl

Pages: [1] 2 3 ... 29
1
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 15, 2019, 12:15:57 »
I have noticed several times something similar, redrawn after forced zooming in/out. 

Odesláno z mého Mi A2 pomocí Tapatalk


2
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 15:19:15 »
Confirming beta.13 runs fine, without crashing anymore.

Odesláno z mého Mi A2 pomocí Tapatalk

3
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 13, 2019, 11:11:56 »
Even reinstalling of beta does not help. The beta, after displaying the news and receiving file access privilege, immediately crashed again.

I have sent the debug log recently via Google dusk sharing to locus.map@asamm.com, I hope it arrived.

Odesláno z mého Mi A2 pomocí Tapatalk

4
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 20:13:21 »

My crashing mentioned above may be related to the V4 map deletion as well, as I had previously installed both V3 and V4map of Austria from OAM, with the Elevate theme.  About the time I deleted V4 map, keeping just V3., the problems started.

Odesláno z mého Mi A2 pomocí Tapatalk


5
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 12, 2019, 05:24:23 »
While previous beta was perfectly stable for me while crashing for others, now 3.37.2.12 is exactly the opposite.

I was successful to launch and use it several times,  but now it has periods of reproducible crashing at the moment of appearing of the start checklist and periods of reproducible running.

I have not found patterns yet when they switch.

Odesláno z mého Mi A2 pomocí Tapatalk

6
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 11, 2019, 11:39:41 »
Interesting.
The beta from yesterday have not crashed yet on my Xiaomi MI A2 with Android 9.

Odesláno z mého Mi A2 pomocí Tapatalk


7
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 10, 2019, 20:19:16 »
Interesting, as it does run on Android 9. Could the issues be related to incidental parallel running both Pro and Beta ?

Odesláno z mého Mi A2 pomocí Tapatalk


8
Troubles & Questions / Re: Problems with navigating a route
« on: May 10, 2019, 19:00:23 »
The new beta route priority recalculation seems working fine, doing deviations along a precalculated city walking route.

For both GPX based and directly calculated routes.

Odesláno z mého Mi A2 pomocí Tapatalk

9
Troubles & Questions / Re: Problems with navigating a route
« on: May 10, 2019, 18:25:36 »
Hmm, I guess I have asked @Menion by other words about this possible undesired tailing recently as well. :-) ( not having opportunity to test it yet.)

Odesláno z mého Mi A2 pomocí Tapatalk


10
Themes - Vector maps / Re: [Theme] Waymark
« on: May 09, 2019, 11:33:35 »
It is still as a free item in the Locus Store / Graphics, to be installed directly within LocusMap.

Odesláno z mého Mi A2 pomocí Tapatalk

11
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 22:57:18 »



This is what I thought. I just asked to be sure because 100 trackpoints isn't much for activities like car and even not much for bike in rural area.

When I analyzed GPX files of multiple bike routes, generated by BRouter, I realized, that as a "rule of thumb", the is in average 1 trackpoint about every 50 m. I suppose less dense for car routes, more dense  for hiking routes.

Trackpoints from recorded tracks will be probably much denser, depending on the recording settings.


Odesláno z mého Mi A2 pomocí Tapatalk


12
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 03, 2019, 20:31:53 »


@Menion
You talk about trackpoints, not sharp/via points, right.

I see you repeatedly use the term "sharp points", possibly because they are displayed as triangles, that are sharper then squared via points.

But AFAIK, Menion has coined for them the term "shaping points", giving to the route a particular shape between start/destination/viapoints., being e.g. a manual correction of the computed route between those points.

Just for completeness, they do not count as points in context of the point priority recalculation,  in contrary to the via points you "must visit".


Odesláno z mého Mi A2 pomocí Tapatalk


13
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 01, 2019, 11:39:13 »
[

@poutnikl
You think that using some "projected" point will work always? Imagine your situation. The route may after these 10 km turn sharp left or sharp right or even u-turn and in all these cases, projected point 3 km from "meeting point" should really not be what you want.

As I do not know what Locus passes to BRouter, I neither know how it is managed. I would just guess it would be treated as an ordinary short route.

I mean projecting along the route, not geometrically. So it would lead me to a route point 3 km forward from the closest point on the route.

If we consider both route and deviation segments of the same length,
and if the recalculation happens at km5, 3km off the route,
it would point me to the route km8, still 2km before route/deviation meeting point.

My whole idea was optimizing the track length, to return to the route in a relaxed way, as trade off between route following and passed distance. Sure, it would need testing.

Thanks for the tip, I forgot/never knew it is there.

Odesláno z mého Mi A2 pomocí Tapatalk

14
Versions / Re: [APP] - version 3.37.+ ( 18. 3. 2019 )
« on: May 01, 2019, 08:38:45 »
I have thought notes about incoming improvement of route priority recalculation.

Lets imagine route priority autorecalculation , strict following off.

I go along 10 km deviation from the route, that goes in parallel to the planned route and then rejoins.

Both ways are equivalent in sense of routing preference and there are no shortcuts along the deviation.

As it is supposed to aim navigation recalculation toward closest route point, then after 5 km on deviation, it would point (generally) to 5 km point of the planned 10km segment.

Q1: Does it mean it would try to turn me back in first 5 km, as that way to the respective point on the route would be shorter ?

Q2: When recalculation aims me forward, with chosen closest route point, and I finally get on the route somewhere ahead, I guess it will be reasonable enough not going after that point. :-)

Additional note:
It may be good not to choose the closest route point, but project it ahead, along the route, depending on route deviation. (I guess something similar is applied for guidance, but not sure)

E.g., if I am 3 km off the route, it may project the route meeting point a x 3=3 km     
ahead of the closest point., if a=1.

Odesláno z mého Mi A2 pomocí Tapatalk

15
I guess many users are rather against paying transactions themselves than against paying itself.

Also, many people are against suspicious at subscription philosophy as seen at big SW players like Microsoft or Adobe, that tend to draw a lot of money per small amounts.

Odesláno z mého Mi A2 pomocí Tapatalk


Pages: [1] 2 3 ... 29