Well, you've exposed an excellent bug. Here's what was happening: the lat/long would be sent to Google for geocoding. Google would try to /reverse/ geocode it to an address, then /forward/ geocode the result, obtaining a set of coordinates that in no way necessarily correspond to the originals. I have no idea why it would do this, but that's my best guess as to what happened based on the geocoding responses.
Luckily, the fix is simple. There's no reason at all to send lat/lng coordinates for geocoding in the first place, so if the address of the Location is coordinates we can just skip that step. I've put the fix in the trunk: http://dev.zenoss.org/trac/changeset/12202 Unfortunately the Google Maps code is quite a bit different in the trunk so you won't be able to apply the patch directly to an older version. You can manually apply it to the ZenGeoMap.geocode function, though. You'll need to make the change in geomap.js /and/ geomap-2.1.js. OR you can just wait for Blue Crab. Let me know how it works out. --Ian -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=31469#31469 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
