I’ve been successfully using GMap2 for a variety of simple things for a year or so.
Somewhere along the way, I discovered that, rather than pass a normal street address query to the geocoder method I could pass a Lat-Long pair and short-circuit a few things I needed to do. (Doing both address coding and bounding rectangle coding in the same dumb kludge.) This has worked fine over the past year, but today I noticed an anomaly. As I was nudging the Longitude in the query to center my point of interest in the bounding box, the returned Latitude leapt. http://www.lakeerietravelguide.com/geocoderanom.htm I hadn’t seen this discontinuity before and was wondering if my friendly “feature” had changed somehow. (I’m keyed for 2.x and this isn’t part of production, but it could be, if the dancing elephants ever decide to sit.) It’s not a big deal, and, yeah, sure, I was flanging the interface a bit by passing Lat-Long, and, yes, I can rewrite the kludge to handle things differently, but I was wondering: Is Lat-Long “addressing” going away? (Anticipated Answer: “Nope! It was never there!”) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
