Could you provide some examples of working and failed ones, along with
where they're supposed to be? I'll see if I can recreate and come up
with a fix or bug.

Thanks,
Matt Ray
Zenoss Community Manager
community.zenoss.com
mray@zenoss.com



On Feb 15, 2009, at 6:27 AM, davetayl wrote:

 

 

just having a bit of an issue with maps when using gps coordinates,
I've managed to get the gps coordinates for some locating using
google earth (decimal notation as opposed to degrees, minutes and
seconds). when I pop them into google maps, no problem I get the
exact location however when I use them as the address in the the
locations sub-sections I get some odd results, occasionally they
land where they should but often they keep landing on common
locations ie if I change the coordinates a bit the dot stays on the
same map location, I've tried clearing the geocache and even
removing and readding the locations but no luck. Any ideas?

Cheers
D







_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
zenoss-users@zenoss.org
http://lists.zenoss.org/mailman/listinfo/zenoss-users

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

These locations show up on the streets closest to the actual locations. They show up fine in google maps and in google earth.

39.751036 -94.840482
39.734567 -94.790720

I haven't tried many but will let you know if I find some that work before applying the patch as described for 2.3.2.

Put a comma between lat and long:

39.751036, -94.840482

If I could somehow get a hold of the regex Google uses to identify coordinates, that'd be sweet. As it is, I'll modify what we're using so that it doesn't require a comma.

thanks ian that seems to have fixed my issue. grin

Ian,

The mapped point showed up correctly for a couple of days/weeks (wasn't paying that close attention and got busy doing other things for the boss) and yesterday/today the situation is this:

=>on the locations tab->select a location-> select the map tab --> the point is in its proper location and everything is groovy
=>click on the dashboard link and two things happen on the Google Map Portlet 1) it reloads ALL of the points every time 2) the points it does reload are located on major roads close to the location (close being relative; a point in Wathena KS doesn't show up in CA or NY but on a major street close to the proper point in KS.)

Zenoss version is Stack 2.3.3 installed on Ubuntu Desktop version 8.10. have 30 different locations mapped and approx 200 items being monitored.

Rod