View Single Post
Posts: 44 | Thanked: 28 times | Joined on Mar 2010
#199
Originally Posted by MasterZap View Post
<SNIP>
As for GPS, all the changes I did were the following:

#2: Tell it to ignore any gps point with an accuracy worse than 150 meters (actually, variable "acclimit" in the code is set to this, I was actually planning to make it an option, but never did, you could change "acclimit" to whatever accuracy you think is appropriate by just editing line 112 in the code)

Frankly, I don't know the GPS api well enough to know exactly what happens and if it will try endlessly to find satellites or not. Probably. There is, most certainly, no clever code in this snippet to try to do anything intelligent here, for sure.

For me, I have a low wooden house so I have quite OK GPS signal also indoors, and since I deem non-GPS coordinates to be useless, for me it is a "feature" that it never uses cell tower locations at all (then "last known good" GPS coord is better, IMHO).

But you are quite right about that if you are in a bunker, it will quite probably try for way too long. Especially since my extremely simplictic implementation of the "once" option, is that it stops after the first successful fix (with successful being "better than 150 meter accuracy").

So I'm guessing it will never actually exit properly for a cell tower location.
</SNIP>
/Z
I for one work in a bunker type building, and my GF lives in a bunker type house

This results in the GPS trying to get a fix , and what seems like, never quits... alarmed keeps on firing up new processes that keep on running.. is there a smart way to set a time out somewhere?
f.i. that if no suitable fix is found within say 120secs the --once option quits?