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 ... 32 33 [34] 35
496
[CZ&SK] - diskuze o Locusu / Re: Preddefinované nastavenia
« on: November 24, 2015, 18:06:35 »
No vida, to mě nikdy nenapadlo, je vidět, že věkem nepřibývá jen moudrost... Tak mě dodatečně napadlo, že by se ty zálohy asi v podstatě daly využít jako profily. Stačilo by si je nějak pojmenovat a pak před použitím Locusu nahrát tu správnou zalohu se jménem třeba chůze nebo kolo. Budu se na to muset podívat.
Já už jsem to udělal - mám car / bike /foot profily. Akorát je škoda, že se tenprofil nemůže natáhnout hned při startu, ale musí se restartovat. Viz též Backup manager - autoload / autosave of chosen settings defined by icon/widget

497
[CZ&SK] - diskuze o Locusu / Re: Preddefinované nastavenia
« on: November 22, 2015, 08:56:43 »
OsmAnd používá systém View profiles ( Browser, car, bike, Foot)  kde je definovany styl (vektorove) mapy a další zobrazovací charakteristiky, které jsou obvykle navázány na car/bike/Foot navigační profily. Globální nastavení stojí mimo profily.

Sent from Sony Xperia M Dual


498
[CZ&SK] - diskuze o Locusu / Re: Preddefinované nastavenia
« on: November 22, 2015, 08:01:30 »
Profile pro úplně všechna nastavení může mít nevýhodu tam, kde chci, aby některá nastavení byla společná. Pak musí dávat člověk pozor, aby nějaký globální parameter v jednom profilu nezměnil. Parametry typu "globální nastavení" by součástí profilu být neměla. Líbí se mi přístup OSMAndu.

499
Troubles & Questions / Re: Low-power tracking
« on: November 16, 2015, 18:42:12 »
You may also want to try GPSlogger application.
https://play.google.com/store/apps/details?id=com.mendhak.gpslogger&hl=en

BTW by minimal accuracy is usually meant that the point is discarded, if reported accuracy is worse than x metres. It helps to avoid jumps in logged tracks, if GPS fails and location determination falls back to GSM location. Such location can be wrong even few kilometres out of the cities and can ruin the track logging..

500
Troubles & Questions / Re: Low-power tracking
« on: November 16, 2015, 12:53:57 »
The solution could be closely related to the way how Kalman filters work, i.e. evaluating predictor and corrector terms.

The application would predict, based on the position history patterns, the future position. If the prediction-correction difference*)  was less than a given lower limit, the position determining interval would be increased. OTOH, if the difference would be higher than given upper limit, the interval would be decreased. The absolute maximum/minimum interval values could be optionally provided.
*) ( or perhaps better the relative difference wrt passed distance betwen points )

But I guess this is very specialized use case, so enough could be using the current solution of GPS ON/OFF management, manually using  long  wakeup GPS intervals.

501
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

502
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 ).

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

Sent from Sony Xperia M Dual


504
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.  :)

505
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.

506
Tools / Re: Experimental Car profiles for Brouter offline routing
« on: November 11, 2015, 08:41:47 »
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.

507
Tools / Re: Experimental Car profiles for Brouter offline routing
« on: November 11, 2015, 08:36:13 »
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

508
Tools / Re: Experimental Car profiles for Brouter offline routing
« on: November 11, 2015, 07:55:09 »
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 )

509
[DE] - deutschsprachiger Forumsbereich / Re: BRouter Version 1.4.8
« on: November 09, 2015, 19:31:14 »
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...)

:-)

510
Tools / Re: Experimental Car profiles for Brouter offline routing
« on: November 09, 2015, 17:57:27 »
The Github versions updated - see the 1st threadd post.

Pages: 1 ... 32 33 [34] 35