On Nov 11, 10:07 am, nianwei <[email protected]> wrote: > The goecoder object itself is using JSONP with cross domain capability > already. If you are talking about sending to Google's geocoding > service directly without through the API, then it's a Term of use > issue, and it appears the server did some checking on the callback > method name and will reject if the call is not from the API
What I was doing was using the Gmaps4JSF library, which currently doesn't support reverse geocoding. Please note that the page that describes reverse geocoding (the URL is below) makes no mention that you have to use it through the API. It simply says here is how to form a request URL with your key. This works -- I can hand code a URL in a browser and I get a JSON object back. There doesn't seem to be any server authorization issues. However it doesn't have the "padding" and that is what I was asking for. If the only way of doing what I want is via the API that's fine. http://code.google.com/apis/maps/documentation/geocoding/index.html#ReverseGeocoding --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
