Is this the Christmas Troll ? > > >> getLatLng() doesn't have its own interface to the server. It simply > > >> makes a .getLocations() call and extracts a GLatLng from the > > >> Point.coordinates of the first Placemark. > > > >It'd have been nice if the reference doc said that.
Why? it's a "black box", you give it a string, it returns a single point. http://code.google.com/apis/maps/documentation/reference.html#GClientGeocoder.getLatLng "In case of ambiguous addresses, only the point for the best match is passed to the callback function." > Is the source available? I don't see any references to it. Do you have > access to info that we mere mortals don't? Non-compressed source not available. Mike takes the trouble to investigate the compressed (obfuscated) code to see what it does. Anyone could do that if they're clever/persistant enough. > I know it may strike people as odd to hear this, but nowhere does it > say that the geocoder is specifically for *postal addresses*. This is true. It says - http://code.google.com/apis/maps/documentation/services.html#Geocoding "Geocoding is the process of converting addresses (like "1600 Amphitheatre Parkway, Mountain View, CA") into geographic coordinates" http://code.google.com/apis/maps/documentation/services.html#Geocoding ".. obtain geocodes for user specified addresses." They probably don't think anyone is going to use non-postal addresses, whatever they are. The geocoder used by GClientGeocoder is not the only one available, you might investigate others if you don't like it. http://groups.google.com/group/google-maps-api/web/resources-non-google-geocoders Geonames for example is good for non-address points of reference ("Loch Ness") > the gmap2 api is a bit too narrowly focused in its purpose: 1) postal > addresses This API is about mapping displays. For convenience, it offers easy access to a geocoding service. There is nothing to stop you using other servicees as well, that's development and integration. > 2) in the browser's locale. Full stop. Not sure what you mean by that. These might relate - http://code.google.com/apis/maps/documentation/index.html#Localization http://code.google.com/apis/maps/documentation/reference.html#GClientGeocoder.setViewport http://code.google.com/apis/maps/documentation/reference.html#GClientGeocoder.setBaseCountryCode > This engine has the potential > to provide maps for all sorts of world-wide uses, where the "context" > is based on the data, not the end-user. Absolutely. That's why it gives you the flexibility to program the "context" yourself. > Re: Function Closure If you don't like function closure, don't use it. It's a convenient method, but not the only way to keep track of multiple service requests. Simply waiting for one response before firing the next is pretty foolproof. Bear in mind you are using GClientGeocoder in a non-recommended way http://code.google.com/apis/maps/documentation/reference.html#GClientGeocoder "As a general best practice, it is not recommended to use GClientGeocoder functions in a loop." so one might expect to have to use some kind of 'workaround'. -- 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.
