Andre, The API call names may be the same, but are the underlying API calls and versions the same?
Just a thought Jack On Mon, Feb 9, 2009 at 4:45 PM, Andrè <[email protected]> wrote: > > Hey Jack, > thanks for your suggestions. > > I had a look on iGoogle latitude gadget code ( > http://www.google.com/ig/modules/friendview/fv-canvas.js ) and it > seems it is using normal API, like a call to getCurrentPosition and > then watchPosition to track position. > > Strange... I've got no clue on what else could be! > > Thank you anyway! > > Andrè > > > > On 9 Feb, 22:37, Jack Chadowitz <[email protected]> wrote: > > Andre' > > > > It appears that iGoogle Lattitude which I am not familiar is using a > > different method than gears. > > > > In one location there is a match between the methods, in another there is > > not. > > > > I suggest understanding what lattitude uses for geolocation > > > > Jack Chadowitz > > > > tel +1 339 230 0268 (US & Canada) > > mobile +1 339 2063583 > > + 44 (0)161 408 0557 (UK & Europe) > > Skype: jackchadowitz > > > > On Mon, Feb 9, 2009 at 4:31 PM, Andrè <[email protected]> wrote: > > > > > Hello Jack, > > > my problem is different. I'm using just a laptop for my tests. > > > > > When I'm at home my position is accurate with iGoogle Latitude gadget > > > and Geolocation API. > > > > > Today I'm in another city. iGoogle Latitude Gadget is accurate, > > > Geolocation API report me to be in downtown with accuracy = 25000. I'm > > > wondering why there are such differences? > > > > > Why I get such differences between difference between iGoogle Latitude > > > Gadget and Geolocation API in the second location, and everything is > > > fine in the first location? > > > > > Any clue? > > > > > Thank Andrè > > > > > On 9 Feb, 21:58, Jack Chadowitz <[email protected]> wrote: > > > > Andre' > > > > > > Your problem may be similar to mine. > > > > > > I use google maps on my AT&T tilt. Accuracy is 2400m unless I ask it > to > > > use > > > > the GPS, the I get 30' accuracy. > > > > > > With gears, I get about 2000m accuracy as its using the cell towers > which > > > > are realy sparse where I am. > > > > > > In your case I believe that gears is using the cell towers and the > > > > difference in accuracy is your location relative to the towers. > > > > > > So a solution may be to use a GPS > > > > > > I can't get gears to use the GPS. > > > > > > Information on that is in a separate posting. > > > > > > Jack > > > > > > On Mon, Feb 9, 2009 at 3:34 PM, Andrè <[email protected]> > wrote: > > > > > > > Hello, > > > > > I found some difference between the two on topic and I act just > > > > > surprised because I didn't read it anywhere. > > > > > > > Let's skip maps and latitude on Cell Phones by now. Let's focus on > my > > > > > laptop. > > > > > > > I added Latitude to my iGoogle and it's working very good, without > any > > > > > GPS. I then created a facebook app that use google gears ( > > > > >http://apps.facebook.com/locate_me) but it just seems to be > > > > > inaccurate. > > > > > > > Here's two example: > > > > > - yesterday I was @ home. Google Latitude and Geolocation showed > the > > > > > same exact location, that was good. > > > > > - today I'm on a biz mission. Latitude displays my location with > good > > > > > accuracy, while geolocation on gears shows results with accuracy of > > > > > 25000. > > > > > > > Is there anything I can do to obtain better results using gears > > > > > geolocation api? > > > > > > > Thank you! > > > > > Andrè >
