Messages

[Please note that currently none of the vehicles accounts for turn restrictions.]

Interesting is this note on GraphHopper Github page,
what means similar limitations for proper car navigation, as Brouter admits:

"Please note that currently none of the vehicles accounts for turn restrictions."

https://github.com/graphhopper/directions-api/blob/master/supported-vehicle-profiles.md

Is this the suggestion that you refer to: http://help.locusmap.eu/topic/independent-configuration-of-navigation-services-for-carbikefoot ?
I found the suggestion hard to track down on the help desk!

The help looks like a candy, Yes., that one,. Also closely related
http://help.locusmap.eu/topic/short-fast-pedestrian-navigation-modes-fro-brouter-navigation
http://help.locusmap.eu/topic/global-settings-profiles-for-navigationguidance-settings

Personally, I quite like the OSMand approach. Anytime aOSMAnd user enters the part of configuration related to navigation, he is asked for the context ( car / bike / foot ).

It was already explicitly asked as the idea in Help desk.

Sent from Sony Xperia M Dual

[add-on GraphHopper - 0.1.7]

Hi guys,

new version of add-on GraphHopper - 0.1.7

Requirements: Locus Map 3.9.3.3+

Download from HERE   data/GH addon 'version' - based Y.apk and install.

Download from HERE 'date' - Y/your country/*-gh.zip routing file

It seems the names and the contents of Google drive subfolders is switched. The apk is in data folder, while data are in apk folder. 

Each product has its customers, none is intended to serve all , whatever product domain is considered.

For off-line car navigation, GH is definitely a good choice.

For bicycle and foot navigation, one can have with GH any ice cream flavour whatever one wants, if it is vanilla. Nothing bad with vanilla. For other flavours, there is the Brouter.

We are probably going "off topic" with the direction of this topic, but as a highway motorist you are generally expected to drive at a fairly fast (read non-eco) speed. If you choose to drive at an "eco" speed (what speed would that be?) you will be a hazard to other faster moving vehicles on that highway.

Why offtopic ?

Eco/EcoFast mode does not expect you to run at 70-90 car-dependent optimal eco speed, It takes 110 as trade off.
Cars going 150+ are higher hazard. Cars overtake each other on motorways all the time.

For EcoFast, I may consider to put there 120. Profiles are under development, anything can be changed.

But OSMAnd and later Graphhopper/Locus should be preferred.
OR GPX navigation.

What is wrong with highway choice for cars. Highways are the most eco roads there are. The speed you choose makes the difference.

Highways are very economic only in sense you avoid acceleration that spends a lot of fuel. But high speed is very non-economic. Regarding chosen speed, Eco profile does not count with speed for motorway 130 km/h.

Most economic is steady speed somewhere is interval 70-90 km/h - it is car dependent. But nobody would run at this speed on motorway ( unless perhaps saving Dutchmen, in early 90s they had motorway maxspeed 80 km/h )

The specific fuel consumption at 120-130 km/h is up to 1/3 higher then at 70-90 km/h.
For Fast profile is expected you run on motorways as fast as you can, i.e. e.g. 130 km/h . ( US guys would have to tweak the numbers for now ).
For Eco profile is expected you run slower at 110 km/h to save the fuel.

See also Brouter Car profiles Github wiki

Profiles updated to version 1.0.3.  See the 1st post.
Penaltes for start/stop and slowing events were tweaked, but will  be subject of tuning for some time. Feedback is welcome.

While profiles provide different routes, even Eco now chooses motorways a lot - checked in long Germany routes.

Note that as Graphhopper implementation approaches  mature state, it should be probably preferred for the car. ( Or the off-line car navigation of the OSMAnd )

Entwicklung scheint eine Hälfte der Codierung und eine Hälfte der Öffentlichkeitsarbeit sein ...

( Development  seems to be a half of coding and a half of public relations...)

:-)

The Github versions updated - see the 1st threadd post.

Try rather EcoFast then Eco. Eco is too focused to optimal fuel consuption at steady estimated speeds.

For now, all are very experimental, not all needed features are implemented., and some will be probably never implemented, due Brouter limitations. Remember these initial versions are simply focused rather on steady driving. Point-wise delays will be tweaked later.

But it will never be as good as online routers and they should take priority. E.g. for now, detection of crossroads is not possible directly and is very tricky. It is based on indirect detection by changing road class, traffic light presence and by geometrical turns, that can be penalized.

Eco just try to choose the route with minimal fuel consumption with estimated steady speed. but I see EcoFast as better.
EcoFast balance minimal fuel consumption and minimal time.

Start/stops effects are not implemented well yet, but coming.

All profiles are more useful for now in fully rural, or fully urban scenario. If mixed, they will have difficulties with optimal preferences.

If not downloading from github by direct link, then the is need to press RAW button above the file text.

Then it displays the file content and the address us the direct link, so either can be used.

I don´t know why, but I have difficulties to load from github. Now I opened the link for the template.brf directly and copied the content into a new brf file and it works for me too.
Thank you for the hints.

Sent from Sony Xperia M Dual

i have updated the original post

Sent from Sony Xperia M Dual

I preference rather  linking to the Github repositories/Wikis for development versions, but I can do so for convenience.  The direct links are the latest versions, but template improvements were not ported yet.

I am moving niw, so test for now just the template, it is identical with future profiles.They are just renamed and using particluar value of drivestyle variable.



Sent from Sony Xperia M Dual

[Is possible your download was corrupted or eventually the profile text was not copied properly ?]

Hm, it is interesting.. I admit I tested them previously only in Brouter-web. I usually load my profile to my Android device only the "release versions/candidates", and these are in development yet.  I have limited real testing opportunities, as I even do not have a car, as for a single person it seems to me as wasting of resources.

They definitely do contain global context.

Code Select Expand


---context:global
....
---context:way   # following code refers to way-tags
....


Now, I have tried both  https://raw.githubusercontent.com/poutnikl/Car-Profile/master/Car-test-Fast.brf  and also newer https://raw.githubusercontent.com/poutnikl/Car-Profile/master/Car-test-Template.brf 

and both do work in my instance of Brouter 1.3.2 in direct, GPX generating mode.

Is possible your download was corrupted or eventually the profile text was not copied properly ?

---------------------------------------------------------------------------
Eco/Ecofast/Fast profiles differ each other just in 1 flag number so they should work all or none.
BTW, I recommend rather Ecofast than Eco,  Eco is too much Eco, ignoring travel time. :-)

In the current template they are chosen by variable drivestyle (1=Short, 2=Eco, 3=EcoFast, 4=Fast).
Aside of avoiding motorways, flags for avoiding tolls/toll roads  and unpaved roads are implemented.

----------------------------------------------------------------------------------

As car route are usually longer than bicycle routes, you may notice time outs in Locus fo routes longer than 50-100 km, if navigation is configured to use Brouter. The reason is Brouter is computation intensive and Locus may not be patient enough.

There are 2 solutions>

- Generate GPX file and navigate along it.

- Generate GPX file, but then choose Server mode option, with assigning to Brouter navigation mode (Car fast/short).
It makes Brouter to use just analysed data for the same future destination+profile calculations, So if you use the same destination+profile later in Locus, it will be fast enough to fit the time out limits. The data are volatile, so one must not use other Brouter routing in between.