OK, I can reproduce now with geo fix.
telnet localhost 5554
geo fix 1 1
Then the location sent to my app is 1.0016, 1.0016. Note
that it's off by 1/600.
It works OK when manually entering locations via the DDMS UI.
--
You received this message because you are subscribed to the
@Mathias Lin- No, that is not the issue. Look, I'm telling you the
latitude/longitude received in the Location object in
onLocationChanged event, have different values than the latitude/
longitude that was sent from DDMS or from command line geo fix
command. The values are close, but off in the
I have the same problem. It started about a month back. All lat/lon is
off by 0.001 ish. Also new is that sometimes I see some lat=0.0,
lon=0.0 showing up which goes away if I restart Emulator most of the
time. I thought this was because my *.gpx file is wrong somehow.
Perhaps someone could post a
@celluri- Not sure if thats the same issue or not. My issue has
nothing to do with GPX file. I can cause same problem to occur from
command line using 'geo fix'.
The amount numbers are off follow some weird pattern I can't quite
decipher. If I enter lat=1.0 , the app receives lat=1.00163, if
Hey guys, I finally got around to trying this out myself. I've been working
on a little utility app to understand the location services.
I haven't been able to reproduce any of the discrepencies you mentioned.
My app registers an update listener and sets a Text view with this:
I am also using same Android 2.0.1 API level 6.
One thing for me is I do:
float distance= (float)10.0;
Global.lm.requestLocationUpdates(LocationManager.GPS_PROVIDER,
0, distance, locationListener);
Not sure if distance creates some error??
-jim
On Oct 25, 9:46 pm, Frank Weiss
hiii
i also got the same problem
if i put distance zero than also this problem coming.
so i dont think this is problem for distance.i also want to know the
solution of this problem.
thanks
nimi
On Tue, Oct 26, 2010 at 9:00 AM, cellurl gpscru...@gmail.com wrote:
I am also using same
This is not an app coding problem. I'm just calling toString on
Location object. I can reproduce using Google Maps app on the
emulator. Send emulator a known location (found using Google Maps web
for example), and then use My Location on Google Maps app to see where
it thinks that point is.
The map data in the Google Maps app and the maps that are available
for developers to use via API (i.e. a MapView in Android SDK) come
from different providers/sources, therefore the geo coordinates differ
and the same lat/lng pair might pinpoint another location on both
maps.
You can see my post
I have to admit I was probably wrong about my check your math comment. I'm
working on trying to reproduce the OP's complaint and provide a more
informed response.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send
10 matches
Mail list logo
