Messages

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 Expand

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 Expand

assign isbadoneway = 0
assign isgoodoneway = 0

Ale druhý způsob moc nedoporučuji.

Generally for me a NOGO is only needed for the life of the route. No longer. As my cycle touring is always to a new area.

I see. But imagine everyday bicycle commuting in big cities with regular municipal announcements about short and long term road closures. There is even Android application to monitor them for my country. They are often not updated in OSM, or with delays, or routers generally do not deal well with time restrictions.

I have a nogo folder in Locus and put their nogos there with target date in name, periodically purging them.

They should not be used as "negative viapoints/shapepoints".

I sometimes find nogo's very convenient for negative viapoints/shapepoints. Sometimes it is the fastest method for shaping my route.

I mean - description of what I want is easier by expressing what I want, not by what I do not want. If I would try to order my dinner by nogo approach.....

The admitted advantage of nogos for route shaping is that it bypasses eventual viapoint count restrictions. Personally I prefer to use the profile that follows my priorities and eventually I choose viapoints that I do want visit or go through.

It not at all about users should act this way, I am just describing my way. That is all.

IMHO when I use the clear route button if I have a pop up to choose to: clear all nogo/profile nogo/current visible nogo points or something similar should be helpful.
I used the nogo points to avoid some sections of a track for a hike but next time  I do not want the nogo still there and to give them all an expieration of a week is tedious.

I do not agree with Arndt - the BRouter author - on nogo usage philosophy. IMHO, nogo points should serve as really nogo points, permanent(e.g. really bad road or always traffic jams or whatever) or temporary ( e.g. road fixing).  They should not be used as "negative viapoints/shapepoints".

Perceptions of using NOGO points.
1) The "ignore NOGO" option should be added to the route planning menu. This option would also be saved with the route. The point is that NOGO will be used mainly where you can not go by car or bike. However, if I plan a hiking trail, I can go through the NOGO areas through the pavement.

Note that the original BRouter nogo system can activate nogos separately for each profile, resp. transportation mode. E.g. all nogos for cars, some for bikes, none for pedestrians.
And yes, they are considered globally, so not limited to a particular route.

Na OSM je to už opravené. Takže nezbývá než počkat na aktualizaci LoMaps.

Anebo si stáhnout mapu z http://osm.paws.cz/, kde je updatují  cca každé 3-4 dny.

@Taras - I'm certainly not fixed on the term "Shaping" point. It is more meaningful & appeared on the face of it to be a more widely used term than "Definition" point. You & @0709 (& like the idea) observe a Shaping point is simply a silent, unnamed, unannounced Via point. So maybe this 3rd type of point doesn't even need a separate name? It's just an unnamed Via point? That could solve the next point...

In some sense, shaping points aka unnamed viapoints are just viapoints, to just go through.
In some sense, viapoints aka named viapoints are not really viapoints, but route POIs to visit..
Both are worthy to be kept when route is saved or exported.

1.4.9? neueste Version ist 1.4.8?

Version 1.4.9 ist wohl noch nicht auf dem Google Play, sondern nur auf http://brouter.de/brouter/revisions.html
Beachten Sie die @utack auf GitHub berichtet ein Bug, verursacht das Hängen der letzten benutzerdefinierten Fahrrad-Profile, die explizit verwendet Turn Restriktion Auswertung (standardmäßig OFF für Fahrrad). @Arndt fixiert für die nächste Version.

Version 1.4.9 is probably not on the Google Play yet, only at http://brouter.de/brouter/revisions.html
Note the @utack on GitHub reported a bug, causing hanging of recent custom bicycle profiles, that explicitly uses turn restriction evaluation.( by default OFF for bicycle ). @Arndt fixed it for next version.

LoMaps jsou založené na mapových datech otevřeného  projektu https://www.openstreetmap.org.    Tvůrci mapy nejsou uzavřená omezená skupina profesionálů, ale může se jím stát každý, kdo se zaregistruje a nastuduje, jak na to. Projekt obsahuje též nástroje, jak zamezit, aby tam někdo nědělal neplechu.

Pro začátečníka může být nejjednodušší použít online ID editor ( EDIT ).

Edit: pomoci může též
http://www.marekp.cz/jak-vkladat-turisticke-informace-na-osm
https://openstreetmap.cz/turistika
https://openstreetmap.cz/komunita

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.

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

@zavinac.eu
OK, beru zpet, chtel jsem rict, ze Locus umoznuje mit na karte vektorove a offline rastrove mapy, ne nutne ze je tam umi sam zapsat. Ja osobne stahuji ( vektorove ) mapy ( Paws, OpenandroMaps ) pres script na mem PC, a pak si je prekopiruji  synchronizaci pres lokalni WiFi.

No, však on neříká, že 5 GB zabírají listingy.

Locus umožnuje vektorové a vlastně i rastrové offline mapy uložit na kartu. Co potřebuje v interní jsou cachované online mapy a některá metadata. Další možnost u Android  6+ je nakonfigurovat kartu jako interní úložiště.

Das Lesen von englischem Text aus englischen Eingeborenen kann den präzisen deutschen Köpfen weniger Schaden zufügen als ein deutscher, der von Google geschlachtet wurde. Die meisten Deutschen verstehen Englisch auf einigen Ebenen und der Rest kann die schmutzige Google-Metzgerei für sich selbst machen. ( butchered as well :-P  )

Is there a limitation on "country file" size? I built the entire US as a routing file and tried it in Locus (it was 3.5GB) and it immediately crashed on opening the navigation screen.

I can imagine the  device dependent  resources demand may depend of the file size, and 3.5 GB may be too brave attempt. I would personally divide the US into several overlapping areas.
Or, I would create a custom area along supposed route, if it is for one time occasion.