View Single Post
Posts: 214 | Thanked: 140 times | Joined on Aug 2010
#91
Originally Posted by rlinfati View Post
@MasterZap

the agps need about 15s in optimal condition to get your position in good condition (in a park)
I normally get a position in less than that, but lets say that's a number.

Originally Posted by rlinfati View Post
, in a poor condition (inside of a house/office) maybe never get yours position...
Sure, then give it 30 seconds to try? User-definable setting for timeout?

I have a simple python script that gives me GPS coordinates. I don't understand it (partially since I don't understand the location API in the Python code) but it seems to always, in a reasonable way, figure out the current GPS coordinate, and it's always pretty accurate.

I live out in the country, and by celltower it locates me sometimes 6 kilometers from where I am! I hope you understand that isn't even a little bit useful?

Actually, for me, "last GPS coordinate" is probably of more use than cell tower.

Originally Posted by rlinfati View Post
then, the problem is when stop the gps... if i stop early the accuracy will be worst of the cell-tower. if i wait a lot of time the battery drain...
Ideally, make it configurable:

#1 - how long it tries
#2 - what it does when it fails, i.e. "keep last GPS point" or "revert to Celltower"

As said, for me, celltower is almost worse than useless.

Originally Posted by rlinfati View Post
tip: if you open another app using the gps ( nokia maps, location test, chat, etc ) the google latitute will get the gps position ( by design )
So if I set up a cron job that every 30 minutes runs my gps.py (which gives the proper GPS position), that wil cause your tool to give the accurate coordinate? But what about all the times in between - your tool will fallback on the inaccurate coordinate?

I wouldn't want that.

I actually tried to extend the Python code I had to do latitude, but something went wrong in the auth stage (even though I seem to be doing exactly what everyone else is doing... very strange).

Here's my suggestion:

You give the user these options:

UI = Update interval (seconds):
GO = How long to keep the GPS on (seconds):

So you update every UI seconds.
If GO is zero, then DO NOT USE GPS AT ALL, use celltower.
If GO is nonzero, but less than UI, turn on the GPS for GO seconds every interval, then turn off.
If GO is nonzero but equal to or greater than UI, then keep GPS on constantly.


That's easy, and not so many user interface controls, and gives the total flexibility, and saves YOU the problem of deciding how long to try the GPS.

The only remaining question is, what to do when GPS doesn't lock, fall back to celltower, or use the last working GPS position. Personally I suggest give the user an option for that too, i.e.

When no GPS Lock use:
[ ] Celltower position
[ ] Retain last GPS position

Please?

Pretty please?

I'll send flowers!

/Z