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 - Žajdlík Josef

Pages: [1] 2
1
Ten nový symbol Lomap vlevo dole asi nepůjde odstranit? Celkem mi tam vadí.

The following users thanked this post: Žajdlík Josef

2
Discussion/New features / Re: What's the "Next Big Thing" in 2018?
« on: February 08, 2018, 17:39:13 »
Good topic :).
Let's discuss basic plans for year 2018

I'll give here, at least, current state in our small team.

Little history:
I had (still have) large hope in live tracking system. Two years ago, I've hired one guy who wrote for me server side solution in nice Clojure language (after more then year of work!). And when first part was finished, he stopped to communicate. Nice .. btw. no one know Clojure :). My mistake ...

In November, some of you probably noticed, that our team had increased to 6 person. Milan > finally developer who should help me with Android. His first task was (still is) Wear add-on. Nice work I think ...
Since January, he work on 1:1 conversion of old Live tracking system to something, we may continue work on it and improve. ETA till middle of March. Then, Milan will work on new UI & various stuff around Live tracking system, also based on feedback. I expect, it will be work on few more months. And then ... sync server? ( most probably ).

Because number of people involved in work on Locus increased and for my suprise, all wants their monthly salary, and also because of number of sold Locus Map is still +- same ( slowly growing ), we needs to invest more work into interesting content, that may bring additional income. Because of this was created and published new Store, because of this I now needs to work on new system for login, new Start screen and third bigger thing will be new Map manager ( which is currently terrible user-experience ).

Most wanted feature: synchronisation. Some users wrote, it's now easy task with some existing stuff. Well, with Petr and Milan, we spend on discussions around this many many hours and we still do not have simple universal solution, that may be done within few weeks. Anyway few ideas are in our heads ... EDIT: and we also have it in list of top priorities!

Except few priorities, that I wrote before and that have to do ( even it's not kind of developement I like ), I really wants to focus in first half of year on:
  • better logging system for geocaching
  • fine-tune route planner
  • fine-tune track editor

And in second half of year
  • new design for main map screen ( close to what is visible in Route planner)
  • new track detail screen with better stats, chart, weather, etc.
  • improve Dashboard system & custom "dashboard" for track screen

My time estimates are really bad, so be aware of it ...
Uff, too long post ... sorry :).
The following users thanked this post: Žajdlík Josef

3
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: January 29, 2018, 16:56:47 »
guys, issue in training found. Recorded track was really incorrectly stored so some post-process and also upload to Strava was not working correctly. Issue fixed ... next version (final) in Wednesday ;)
The following users thanked this post: Žajdlík Josef

4
Michael, you need to check third-party apps such as battery widget (battery saver), or RAM optimizer... a lot of them all done. Something is killing the energy-intensive process... There are no miracles. Samsung makes a good firmware to their devices. (I have a J5 - no problems.)

Look for disguised "optimizer"!
The following users thanked this post: Žajdlík Josef

5
Did Michale manage to solve the run of Locus on the Galaxy A3? I'm thinking of buying it mainly because of a barometer and running Locus is a priority for me.

CZ: Podařilo se Michale nějak vyřešit běh Locusu na Galaxy A3? Uvažuji o jeho koupi hlavně kvůli barometru a provozování Locusu je pro mě prioritou.
Josefe I don't have any feedback so far. Nobody has answered yet.

Sent from my MI 3W using Tapatalk

The following users thanked this post: Žajdlík Josef

6
Versions / Re: [APP] - version 3.28.+ ( 20. 12. 2017 )
« on: December 23, 2017, 12:12:03 »
Thanks, nice to You too, better .. to you all ;).
The following users thanked this post: Žajdlík Josef

7
Versions / Re: [APP] - version 3.26.+ ( 11. 10. 2017 )
« on: October 30, 2017, 21:09:28 »
I have never used the display of a line with a multicolored version. However, I would greatly appreciate if Locus had this feature in a simplified way in the route planner. This could be an option in the Scheduler menu: "Notify X-Percent Tilt". When I activate it, I would set the percentage and Locus would need a reddish part of the track with this slope. This could be used for planning a trip for rides with children, etc.
Currently
a) it is possible to setup width of lines in Route planner, nothing more
b) global line style affect these lines, weird
I was thinking about it, and in the end, I've removed option to set width of line and instead, I've added into menu option to setup full style of lines, thanks

@john_percy:
2. when you tap on "Line coloring" selection, bottom panel completely disappear??
3. it worked in same way also in previous versions, maybe it was not so visible as is not. Point here is to highlight track and it's orientation, as much as possible. Maybe little confusing when we consider that symbols are disabled, on second side, it should allow to see line better.
Hmm should be more logical to just highlight such selected tracks always with simple arrow and inverse  base color? Maybe it worked like this in previous versions and not how I made it now. Thanks
The following users thanked this post: Žajdlík Josef

8
Ahoj,
jak tak koukám,je to založeno na starém profilu. Nějak jsi zkombinoval pěší profil s cykloprofilem. Chybí tam definice proměnné onewaypenalty pro vyhodnocení jednosměrek..

Co jsem to tak porovnával se současnou Hiking templatou , tak se mi jako jediný podstatný rozdíl zdá Tvoje nastaveni Offroad factor na 1.0.  Takže by sis to tam mohl znova nastavit a měl bys to.

Další možnost je ve starém profilu vyhodit
Code: [Select]
assign isbadoneway = not equal onewaypenalty 0
assign isgoodoneway = if reversedirection=yes then oneway=-1
                      else if oneway= then junction=roundabout else oneway=yes|true|1

a nahradit
Code: [Select]
assign isbadoneway = 0
assign isgoodoneway = 0

Ale druhý způsob moc nedoporučuji.
The following users thanked this post: Žajdlík Josef

9
Přijít by jsi nutně nemusel, je důležité dodržet totožné pojmenování souboru, takže když tvoje alternativní mapa bude mít stejné jméno jako LoMaps, mělo by to i tak nadále fungovat ( včetně offline adres )
The following users thanked this post: Žajdlík Josef

10
Nevím o tom. Normalne tam bývá název profilu, ale při uploadu profilu na web tam Web client přihodí profile ID v server cache.  Editovat, nebo si napsat script.
The following users thanked this post: Žajdlík Josef

11
Versions / Re: [APP] - version 3.24.+ ( 31. 5. 2017 )
« on: June 04, 2017, 16:23:52 »
Thanks. Issue is in your database, not in Locus Map itself ( well common question is why database is corrupted .. because of Locus Map? ... ).

Anyway by this method, I was able to fix it. I'll send you download link over PM. Try it, but I believe it will work as expected.
The following users thanked this post: Žajdlík Josef

12
Tady zkus Fastbike - LowTraffic III. třídou
The following users thanked this post: Žajdlík Josef

13
MTB_factor  -0.5  a  smallpaved_factor      -0.4 Ti udělá zhruba tohle
Co je pod čarou upřednostní, co je nad ní, potlačí
Code: [Select]

                                                                                  ------------------------
                                                    ------------------------ 
                                              /                                 
                                       /
                                  /
I.tř------II.tř-----------III.tr------Ulice-----C-e-s-t-y---a p-ě-š-i-n-y--------------  Preference pru MTBfactor 0.0 a smallpaved factor 0.0
                        /
                    /
               /
           /
      /  .
  /.

Kdežto dole je to např pro MTBfactor -0.75   a smallpaved factor 1.0
Vše jen ilustračně.

Code: [Select]

                                                                                              /
                                                                                         /
                                                                                    /
                                                                                /
                                                                           /
------------                                                        /
               -------------                                  /
                               ---------------          /
I.tř------II.tř-----------III.tr------Ulice-----C-e-s-t-y---a p-ě-š-i-n-y--------------





The following users thanked this post: Žajdlík Josef

14
Díky za pomoc, nakonec jsem asi nejlepších výsledků dosáhl s níže uvedenými těmito hodnotami. Hodnota: assign   isbike_for_mainroads   true se neosvědčila. Přeci jen už to pak hodně preferuje jedničky, které jsou u nás strašně přeautované. Přesto zatím zůstanu u starší verze vycházející z 2.4.3 výpočty trojek jsou o dost lepší.

assign   MTB_factor             -0.5 # default 0.0, *)
assign   smallpaved_factor      -0.4 # default 0.0, *)

Code: [Select]
assign   isbike_for_mainroads   true se osvědčit ani neměla, má být false, což 
udržuje costfactor hlavních silnic vysoký.

Já jsem radil MTB_factor = cca  -smallpaved_factor , zapomněl jsi na znaménko.
MTB_factor  -0.5  a  smallpaved_factor      -0.4 preferuje silnice I. třídy a penalizuje malé asfaltové cesty
smallpaved_factor  měj kladný a MTB_factor podobné hodnoty záporný.

Další nesystémová, ale účinná možnost je, posunout hodnoty
pro preferované typy cest směrem k nule.

Code: [Select]
assign univ_factor_coef
    switch  highway=motorway|motorway_link|trunk|trunk_link 1.0 switch highway=primary|primary_link   0.9
    switch  highway=secondary|secondary_link                0.7 switch highway=tertiary|tertiary_link 0.4
    switch  highway=unclassified                            0.25
    switch  or not istrack highway=footway                  ( switch ispaved 0.25 switch isunpaved -0.25 0.0 )
    switch  or ispaved tracktype=grade1                     0.1
    multiply rough_coef   
    add ( switch  highway=path -0.25 0.0 )
        switch ( nosurfacenortracktype ) ( switch isbike 0.0 -0.25 )
        switch nosurface  ( switch or isbike tracktype=grade2|grade3 -0.25 -0.5 )
        switch surface=compacted|fine_gravel -0.25 switch surface=cobblestone|sett  -0.4
        switch surface=ground|mud|dirt       -0.6  switch surface=grass|sand        -0.6   
        switch surface=gravel|pebblestone    -0.75   -0.6
The following users thanked this post: Žajdlík Josef

15
Ahoj,

Když 2 dělají totéž, není to totéž. MTB a smallpaved factors byly už dávno zcela předelány, s větší granularitou podle typu a stavu cesty, se společným hodnocením cest. 

Dříve měl MTB factor na silnice I. a III. třídy silnější a navíc stejný efekt. Naopak smallpaved factor měl na silnice I. a III. třídy sice různý efekt, ale slabší než teď a hlavně slabší než MTB factor.

Stejný MTB factor a  smallpaved factor mají ted u hlavních silnic stejný efekt, takže vlastně dvojnásobný..
Naopak u nezpevněných cest se navzajem rusí.

Opačný MTB factor a  smallpaved factor se naopak ruší u hlavních silnic a zdvojují u nezpevněných cest .

Obecně má teď na hlavní silnice smallpaved factor větší effekt než dříve a MTB factor naopak nižši, zvlast pro třetí třídu.

Doporučuji MTB factor = cca  -smallpaved factor,   címž hlavní silnice budou mít cca neutralní posun.
Cim větší bude ( smallpaved factor  - MTB factor ) , tím víc budou nezpevněné cesty potlačeny.

Dále doporučuji zmenit
Code: [Select]
assign   isbike_for_mainroads   true na
Code: [Select]
assign   isbike_for_mainroads   false
Cimz se zruší "bike friendly" penalty pardon pro hlavni silnice .

Taky možná sniž cycleroute_pref, pokud je moc silný, protoze byl předělaný.

Tady lehko uvidiíš, co oba faktory delají. MTB faktor bere hodnotu jak je a vynásobí sebou.
smallpaved factor napred spocte absolutní hodnotu.
Code: [Select]
assign univ_factor_coef
    switch  highway=motorway|motorway_link|trunk|trunk_link 1.0 switch highway=primary|primary_link   0.9
    switch  highway=secondary|secondary_link                0.7 switch highway=tertiary|tertiary_link 0.4
    switch  highway=unclassified                            0.25
    switch  or not istrack highway=footway                  ( switch ispaved 0.25 switch isunpaved -0.25 0.0 )
    switch  or ispaved tracktype=grade1                     0.1
    multiply rough_coef   
    add ( switch  highway=path -0.25 0.0 )
        switch ( nosurfacenortracktype ) ( switch isbike 0.0 -0.25 )
        switch nosurface  ( switch or isbike tracktype=grade2|grade3 -0.25 -0.5 )
        switch surface=compacted|fine_gravel -0.25 switch surface=cobblestone|sett  -0.4
        switch surface=ground|mud|dirt       -0.6  switch surface=grass|sand        -0.6   
        switch surface=gravel|pebblestone    -0.75   -0.6
The following users thanked this post: Žajdlík Josef

Pages: [1] 2