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
1
Hmm, I do not think it was discussed, aside of the nogo iniciative at Locus side and private discussion of LocusMap and BRouter developers. I do remember Arndt, the BRouter author, once mentioned he was working on the new kinematic routing model.

A big part of changes are rather BRouter internal things. For an end user, the important features are these:

- completely new kinematic routing for cars(car-fast, car-eco)(*). It looks like a big thing. This routing  does not use the costfactor, so It currently bypasses the profile developer effort based on costfactor calculation. The routing is tuned by the parameter of maximal target speed vmax(90 for eco, 160 for fast, probably 130 or 110 for non Germans ).It could be tweaked by changing of max default speed for highways classes to change priorities..  I see I will have to rename my car profiles to avoid confusion. Probably by adding P as Poutnik.

- compatibility with the new LocusMap nogo point interactive management   ( for now in Locus beta)

- 2 minor things for profile developers

(*) seems to me as optional, depending on presence of the kinematic model context line in a profile. So in my understanding, both new kinematic car profiles and my old car profiles should be, after renaming, usable side by side.
The following users thanked this post: menion, Andrew Heard

2
Navigation & Guidance / Re: Offline navigation - BRouter v1.2+
« on: September 23, 2017, 18:02:23 »
Published new BRouter release 1.4.9  -  may not be in Google Play yet.

(current revision, 24.09.2017)

    tweaked distance calculation
    new car profiles, kinematic model based
    basic travel-time/energy support
    modular cost models
    lookup extensions (+conrcete:lanes/plate code-side-hack)
    fix for interface provided nogos
    access to way-context vars from node-context
    removed size limit for encoded tags

http://brouter.de/brouter/revisions.html
The following users thanked this post: Bucky Kid, Andrew Heard

3
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

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

5
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

6
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

7
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

8
Troubles & Questions / Re: BRouter (cycling) profile question
« on: September 25, 2016, 19:33:32 »
See the new profile set based of template v2.5.5
https://github.com/poutnikl/Trekking-Poutnik

The above mentioned bug is fixed, and there is introduced new parameter
Code: [Select]
assign   StrictNOBicycleaccess  0 # 0 allows but penalizes foot only access / 1 forbides foot only access.
there is n ot yet an extra profile set to use the flag, will be introduced later.
It must be changed manually for now.
The following users thanked this post: jusc

9
There is missing TTS option in Settings - Guidance - Notification  Doc page
http://docs.locusmap.eu/doku.php?id=manual:user_guide:functions:guidance
The following users thanked this post: Michal

10
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« 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.
The following users thanked this post: Andrew Heard

11
Themes - Vector maps / Re: Server problem for LoMaps...?
« on: August 31, 2016, 19:33:50 »
Hmm, and why do you think you should be able to do any Locus LoMaps routing when off-line ?

I originally missed the off-line mode in your  first post, thinking you had just troubles with online routing service.
In off-line mode you obviously cannot access any network servers.

Do you have installed and properly configured any 3rd party off-line router, like BRouter or GraphHopper ?

As Locus does not have any off-line routing capabilities itself.
It does not have any own routing engine.
Additionally, used format of MapQuest vector map and Mapquest map manipulation libraries
do not allow using the LoMaps vector data for routing.
The following users thanked this post: sbouju

12
[CZ&SK] - diskuze o Locusu / Re: Navigace podle trasy
« on: August 30, 2016, 18:29:12 »
No, prozatim na konfiguraci Brouteru ve smyslu vlastniho vyberu profilu v Locusu zapomen, to bude az v dalsich verzich nekdy v pulce.rijna, podle Meniona.

Mas-li v Locusu vypnutou vlastnii konfiguraci Brouteru, zustava v pro Locus v platnosti nastaveni v BRouteru.

Mas-li vlastni konfiguraci Brouteru v Locus zapnutou , prozatim tam Menion nastavil natvrdo

Auto rychle -  Car-FastEco  ( doporucuji do budoucna Car-Fast )
Auto kratke -  Car-short  ( nedoporucuji pouzivat, doporucuji do budoucna Car-EcoFast nebo Car-Eco )

Kolo rychle -  Trekking-Fast ( je nekde mezi trekkingem silnickou, na cistou silnicku je lepsi standardni Fastbike, nebo Fastbike-lowtraffic )
Kolo kratke -  Trekking-MTB-medium   ( je nekde mezi trekkingkem a (lehci) MTB. )
Pesi          -   Walking

Takze ti zbyvaji pouze modifikace
pro auto  Placene/Neplacene  a Dalnice/Bez dalnic
pro ostatni za sucha a za mokra.
The following users thanked this post: Bucky Kid

13
[DE] - deutschsprachiger Forumsbereich / Re: BRouter Version 1.4.8
« on: August 30, 2016, 18:21:01 »
!The issue is no method  "from,via,nogo,to"  / Das Problem ist, keine Methode "von, über, nicht gehen, auf"

Google Übersetzung
Aah, ich sehe. Dann ist es in der Regel 50 bis 200 km, es hängt sehr auf OSM Wege Dichte, verwendet passcoefficients und schließlich verbot kleine Wege.

Nach dem Check ist der angezeigte Fehler die pass0 den 60er Jahren mit der Empfehlung eines anderen Routing-Dienst Timeout überschritten. Die msg disppeared zu schnell zu erfassen.

  Längere Strecken müssen als Vorstufe des brouter Timeout freien Server-Modus von-bis Strecke Vorkalkulation. (Ich frage mich, warum es nicht einige am Leben Ping-System in der API halten implementiert)

Original message
Aah, I see.  Then it is typically 50-200 km, it very depends on OSM ways density, used passcoefficients and eventually forbidding small ways.

After check, the displayed error is the pass0 crossed the 60s timeout with recommendation of another routing service. The msg disppeared too quickly to capture.

 Longer routes need as the pre-step the BRouter  timeout-free server mode from-to route precalculation. ( I wonder why there is  not implemented some keep alive ping system in the API )
The following users thanked this post: strcat

14
Pokud máš v nastavení Konfiguracce BRouteru Vlastni profily vypnute, tak nijak - vse je jak pri starem, porad se pouziva  mapovani v BRouteru.

Pokud máš v nastavení Konfiguracce BRouteru Vlastni profily zapnute, tak Locus pouziva vlastni mapovani a posila kod profilu primo do Brouteru. Mapovani profilu v BRouteru se obchazi. 

Vyhledove bude mozne toto mapovani rucne nastavit,
ale zatim - udajne vyhledove asi do puky rijna - je tam natvrdo

  Mode            Profile
  Car-fast        Car-FastEco
  Car-short       Car-Short
  Bicycle-fast    Trekking-Fast
  Bicycle-short   Trekking-MTB-Medium
  Foot            Walking

Takze pro Tebe to zatim nama vyznam zapinat.
The following users thanked this post: Dan S.

15
Versions / Re: [APP] - version 3.18.x (27. 6. 2016+)
« 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.
The following users thanked this post: Jencek

Pages: [1] 2