Thanks for the explanations, especially the comment that " if you feed the geocoder some text that looks like a long/lat it will return the nearest address or locality that it knows about ... NOT the long/lat you started with. ". That helps me understand why it works sometimes and not others. Obviously Google Earth has some code that interprets the input and comes up with the right LatLng.
Now I have to do what was suggested: "Write some code to parse lat/ longs input from a form if thats what you want. There'll be plenty of examples out there. That allows you to add, for example, meaningful error messages for latitudes bigger than 100 etc." Unfortunately that's going to take quite some effort given my lack of experience unless I can find some of those examples. Thanks for your kind assistance. If anyone knows where I can find some examples of pasing code please let me know. On Aug 21, 10:34 pm, Rossko <[email protected]> wrote: > > That calls the geocoder, which is a service that looks up postal > > addresses and converts to lat/long. > > If you are feeding that lat/longs its not really the appropriate tool > > for the job. > > I should have elaborated on why it isn't appropriate ; if you feed the > geocoder some text that looks like a long/lat it will return the > nearest address or locality that it knows about ... NOT the long/lat > you started with. -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
