Messages

Pomohlo by, kdybys detailneji napsal, jak mas nastavene v Locus  Nastaveni - Jazyky , Nastaveni-Navigace ( navigacni service a nastavani relevantni k hlasove navigaci.).

Jaky je puvod GPX ?
Zkousel j si BRouter ?

Protoze hlasova navigace podle GPx je mozna, a pokud GPS funguje bez vypadkum lze podle ni jet dlouhe hodiny.

[fast]

Uff, all are in good health at home .
I still found few issues in routing with car profile(s). Are you interesting in tunning these profiles at all? I'm asking mainly because You and Arndt focus mainly on hike & bike, so I'm not sure if you are interested in perfect "Car / moto" navigation as well.
If so, I may post again some start/end coordinates where profiles fail.

Welcome home at locusmap.eu   

Sure, I am interested in the car profile tuning, I consider all feedbacks I get.
If you provide data, best if as Permalinks from Brouter-web, I can improve it.

But be aware that Brouter car/moto navigation will probably never be near perfect, and always will stay as a plan B, or fallback solutions, for several reasons :

• There are good, fast, free and fully offline car navigations with simple interface like e.g. MapsFactor Navigator.
• BRouter does not offer some map info special features the dedicated car navigation software uses, like turn restrictions or lane choosing
• BRouter uses in its RD5 files, and exposes them to profiles via lookups.dat just selected subset of OSM tags
• BRouter ( at least in near future ) will always be handicapped not being optimized for fast routing over long distances, like using e.g. Contraction hierarchies, used in GraphHopper or OSRM
• Brouter cannot provide extra hint info like e.g. streetnames

Hm, I guess a countdown till sunset a/o citizen twilight can be very useful for outdoor usage, for on-road-planning of save travel or a camp breaking.

The Brouter-web above runs locally as a front-end over the local back-end BRouter.
BUT
1/ Brouter-web is for now intended for desktop browsers, support for mobile ones is in progress. Aside if that, resolution can be the issue for convenient use..
2/ BRouter-web uses online tile servers for OSM maps, it is not designed for full offline use.
3/ The main advantage I had in mind is ability to set the custom profiles as the "standard ones" in choices of the BRouter.

4/ As you have hinted, long routes may find the use for faster desktop CPUs.

It gives some advantage to run the BRouter-web locally....
https://github.com/nrenner/brouter-web

Message for @menion: please do developing for Brouter Addon in Beta versions not in publish. Thanx.

Menion mentioned he does it in public version intentionally, as too few Locus users are simultaneously Brouter users and beta testers.

Google> Minion erwähnt er es in der Öffentlichkeit Version tut absichtlich, da zu wenige Locus Benutzer gleichzeitig Brouter Benutzer und Beta-Tester.

[Avoid route that may be difficult in wet weather.]

For the explanatory text, maybe "Avoid route that may be difficult in wet weather."

nicely worded, purpose is clear, or Avoid sections that may be more difficult in wet weather?

But it does not avoid them. Just shifts the point of switching the decision.
Section can be misleading, as it is unclear what it means. Why not just the old good  (OSM) ways ?
The shift of preferences can be justified by either of being difficult(skills) and being unpleasant(perception).

[Wet conditions]

[...]In the Locus UI, may I suggest: "Wet conditions".  That means, in a general sense, things are wet right now.  "Is wet" implies knowledge of the route, but you haven't been there specifically yet.

For the explanatory text, maybe "Avoid route that may be difficult in wet weather."  (In North American English, the term "road" doesn't include trails, which are part of this.)[...]

"Wet conditions" seems good. "Iswet" followed the naming of my profile variable.  There  is useful to know there are 3 different contexts in BRouter profiles. Global context, way context and node context. Iswet is defined at global context, with no relation to any particular way or route.. There is another related variable ismuddy, at way context, with meaning the particular way has changed surface quality due wet conditions.

For the explanation, I would avoid the verb "to avoid", as the real meaning is just shifting of preferences. E.g.in an illustrative example of 2 alternatives, a primary road and a soil track: The soil track may be chosen in dry conditions if less than e.g. 1.5 times longer than the other one. At wet conditions, the threshold is moved to other value, e.g. 0.3 times longer.

Perhaps rather ways then route.  Like  "Prefer ways not difficult at wet weather"   Difficult may not be fully correct, if related to technical aspects involving skills. But I agree it is hard to choose single verb describing all aspects.

Well Hanka was sometimes well surprised when I 10th time per day silently whispered "grrrr poutniku" .

I was afraid Hanka was going to kill you for such surprises and if she would fail, you were going to kill me.   
In both cases, it would be probably end of Assam software company., so I am glad it did not happen.. 

That's exactly what I thought of! Where is this mentioned by Arndt, I think I missed this?
Is there a corresponding idea in Locus Helpdesk already?

http://forum.locusmap.eu/index.php?topic=5199.msg44479#msg44479

Beachten Sie, dass ich bereits dieses System zu einigen Flaggen in Autoprofilvorlage implementiert Pre.
( Note that I have already pre implemented this system to some flags in Car profile template.)

Edit:   http://help.locusmap.eu/topic/dynamic-brouter-profile-configuration

Now both cases ( terrible roads and tiny streets ) are addressed in v1.0.22 car profile template.

You can use profiles from the respective major car profiles set
https://github.com/poutnikl/Brouter-profiles/raw/master/BR-Car-Profilesmain-V1.0.22.zip
resp. from full list https://github.com/poutnikl/Car-Profile/raw/master/BR-Car-Profiles-v1.0.22.zip
just in case you insist.

For now I have addressed the surface quality issue for the case referred by URL provided by Andrew.

Try the CarFast profile from the archive. When applied  to the route referred, it selects the better road on the left ( with good cost reserve) , without even need to trigger Avoid_unpaved flag.

I will later check the narrow road network issue, regarding initial costs of roads.

I suppose today or tomorrow there will be a fix.

Well, the url route combines highway=unclassified with tracktype=grade2 surface=gravel mtb:scale=1
Wow..  I mean Ouuuuu.

I see I have to test unclassified and perhaps also tertiaries for surface conditions...
I have never seen tracktype to be used for main roads...

Be aware the unbiased profile need some trade off of road preferences.
What is fine here, may be hell in Croatia.
What is fine in Croatia, may be pushing good roads too much.

But if the surface condition info is involved, it can be addressed.

Code Select Expand


Distance WayTags
1106         highway=unclassified tracktype=grade2 surface=gravel
2464          reversedirection=yes highway=unclassified tracktype=grade2 surface=gravel mtb:scale=1

Is this the 2nd route - http://brouter.de/brouter-web/#zoom=12&lat=45.4895&lon=13.8848&layer=OpenStreetMap&lonlats=13.91192,45.5777|13.96209,45.40608&nogos=&profile=car-test&alternativeidx=0&format=geojson

Same route calculated for car-test/ fastbike. Just curious.

In fact, Fastbike is close to car profiles, definitely to moped one. If there are just few reasoable routes, such profiles can provide the same route.