On Dec 28, 4:47 pm, argv01 <[email protected]> wrote: > (Moderators: this is a resubmission from an attempt of the same two > days ago; there may have been a problem with my network connection. > Since it hasn't come up, I assume you haven't seen it. Hence, this > repost.) > > -------------------- > The fact that these two functions, getLatLng and getLocations, are > passed different params is causing me no end of frustration. > > Because there's no "singular" version of getLocations (ie., > "getLocation"), I can't pass it strings like "london, england" just to > get a marker for that location. As you can imagine, it returns a great > number of Placemarks. > > Because there's not a "getLocation()" (where the parser would only > view it as a single address), I am forced to use getLatLng(). But the > params passed to its callback function are not as full-featured as > those passed to the getLocations() callback, which I need for all > sorts of error-handling and other general diagnostics, not to mention > useful UI feedback.
My understanding is that getLatLng() just returns the first result from getLocations(). -- Larry > > getLatLng only gets a single Point variable, and in order to preserve > which address is used, I have to use the callback as an in-line > function, which is inelegant, not to mention clumsy when you have to > incorporate many other things. It also gets unnecessarily lengthy when > you're passing multiple addresses in a loop. > > Context: > > My photography websites hosts about 50,000 images, and there are many > toplevel pages that now contain maps indicating where the photos were > taken. The maps are NOT based on the geographical region of the client > browser, but on the specifics of the photos themselves. So, when > passing information for each image, I have to pass country information > as well as others to reduce ambiguity of the geocoder. I often have > to actually include the continent name as well to keep names like > "Scotland" being confused with "Scotland, Ohio", which is what the map > will show me because MY browser happens to be in the US. > > All the maps on the site are automatically (dynamically) built using a > series of perl scripts. In order to place a marker on the map > representing the location indicated for each photo, I use the city/ > state/country fields of the EXIF or IPTC data, whichever may have it. > A dynamically-generated javascript function is produced according to > the API reference. > > An example ishttp://www.danheller.com/windows.html > (Note that the map only displays markers for a few places--the > geocoder fails to parse arbitrary names like "buenos aires, argentina" > and many others. But that's a different issue that will get a separate > thread.) > > You can look at the javascript that my perl code generated by looking > at the html source. Notice the params passed to getLatLng as example > locations extracted from photos' EXIF/IPTC data. (Note that addMarker > () is commented out because it's only used as the callback for > getLocations(), which I'm not using due to the problems noted in this > posting.) -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
