maemo.org - Talk - [Announce] modRana: a flexible GPS navigation system

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

- - [Announce] modRana: a flexible GPS navigation system (https://talk.maemo.org/showthread.php?t=58861)

Re: [Announce] modRana: a flexible GPS navigation system

Quote:

Originally Posted by MartinK (Post 1242509)

If modRana won't find the file, it will generate a new one, which might (temporarily ?) fix the issue.

(sidenote) I don´t have the same issue. But happened to notice that with every boot ModRana starts the same map layer and language etc. (whether or not I had changed them during last run).
So I looked for options.bin as well, but it wasn´t there to be found. I had [Show hidden files] on btw.

Re: [Announce] modRana: a flexible GPS navigation system

Quote:

Originally Posted by MartinK (Post 1242185)

Thats a good point and I really do want to integrate HDOP in the rerouting-check calculation. But as there might be another causes for false-alerts, namely routes that were mapped with a slight offset or routes that were mapped correctly, but then reduced in point count to reduce storage space (eq. you might get a straight line for a slightly curved route in the routing result), I would still like to let the user to set the rerouting distance to some arbitrary number manually, to get rid of excessive reroutes in some cases.

IMHO, just using a HDOP multiple won't work - if you have a very good HDOP (say <1 m), the real route differing just 3 meters from the computed one would trigger rerouting. A very bad HDOP (>100m) would result in a 300+ m corridor.

...

Possible algorithms that take HDOP into account:

Algorithm nr. 1
...

Algorithm nr. 2
...
Algorithm nr. 3:
...
Algorithm nr. 4:

check if HDOP < (1/3)*rerouting_threshold (in meters)
if its larger, them rerouting threshold = 3*HDOP

I think there's no real solution for the case that the route is offset or the route has been compressed by reducing the point count. Those problems may lead to unneeded reroutings however the threshold is set. The only solution is to not let the threshold get too small, no matter how it's defined.

I like your algorithm 4. You set a floor below which the threshold cannot fall, and have no discontinuity at the point where you start using HDOP information. If the HDOP is a one standard deviation radius, then 3 standard deviations is a good threshold.

It's nice that you're adding more parameters for us to tweak. One little advantage our poor orphaned OS has is that at this point it is likely that nearly all N900 owners are geeks. Somebody writing an Android app can't assume his users like to fiddle with the app's parameters, but we can.

Re: [Announce] modRana: a flexible GPS navigation system

Is it possible to store downloaded tiles somewhere else then in .maps folder? (i do not want them to be shared with mappero)

Re: [Announce] modRana: a flexible GPS navigation system

MartinK, were you able to find anything out using the file i sent?

Re: [Announce] modRana: a flexible GPS navigation system

Quote:

Originally Posted by sup (Post 1248707)

Is it possible to store downloaded tiles somewhere else then in .maps folder? (i do not want them to be shared with mappero)

I believe you can change where the maps are stored in the settings area. The default is the shared location for several apps (mappero and others). Why would you not want to share tiles across mapping programs?

Re: [Announce] modRana: a flexible GPS navigation system

Quote:

Originally Posted by woody14619 (Post 1248766)

Because of this. And since I opted for sqlite, it does not share maps anyway.

Well, I did not find it in the settings. Just option to use sqlite or not. Am I being blind? If so, could you be more specific where in the settings it is hidden.

Re: [Announce] modRana: a flexible GPS navigation system

Storage location for the map tiles is defined in an editable configuration file.

I can't remember the name of the file or its location, but it's mentioned somewhere in this thread.

Re: [Announce] modRana: a flexible GPS navigation system

Quote:

Originally Posted by rotoflex (Post 1248999)

Storage location for the map tiles is defined in an editable configuration file.

I can't remember the name of the file or its location, but it's mentioned somewhere in this thread.

Ah, I see, it is in ~/.modrana/user_config.conf and the option is map_folder

Thanks!

Re: [Announce] modRana: a flexible GPS navigation system

Quote:

Originally Posted by Ken-Young (Post 1243056)

I like your algorithm 4. You set a floor below which the threshold cannot fall, and have no discontinuity at the point where you start using HDOP information. If the HDOP is a one standard deviation radius, then 3 standard deviations is a good threshold.

OK then, looks like I'll implement number 3. :)

Quote:

Originally Posted by Ken-Young (Post 1243056)

It's nice that you're adding more parameters for us to tweak. One little advantage our poor orphaned OS has is that at this point it is likely that nearly all N900 owners are geeks. Somebody writing an Android app can't assume his users like to fiddle with the app's parameters, but we can.

Yeah, thats quite nice ! :) Still, good applications should be usable (in their default state) even for non-geeks but be configurable enough to satisfy advanced users.

Quote:

Originally Posted by shady (Post 1248760)

MartinK, were you able to find anything out using the file i sent?

Sorry, I haven't got to it yet - I was on vacation + was rewriting track logging + testing the new track logging & rerouting (while on vacation - both work just fine with 130 km/h+ on the Autobahn :) ). I'll check it out right away.

Quote:

Originally Posted by sup (Post 1249011)

Ah, I see, it is in ~/.modrana/user_config.conf and the option is map_folder

There are other useful options in this configuration file:

tracklog storage path
placement of map-screen buttons (per mode)
widget configuration (per mode)

user_config.conf
(It's quite heavily documented)

There is also another configuration file, used for configuring map layers:
map_config.conf