I spoke to soon.  Using Firebug, i determined that 'callback'
parameter is not the issue, therefore moving key in front of it does
not necessarily fix it.

What does fix it is having the '_' parameter at the end of the URL.
This appears to happens with $.ajax, but only happens with getJson if
'callback' is at end of string.

Here's my working URL i use as an option to my $.ajax() call:

        geoUrl = 'http://maps.google.com/maps/geo?'
                                + '&key='+ googleApiKey
                                + '&q='+ escape(addr)
                                + '&sensor=false&output=json'
                                + '&callback=?';

cheers,
chad

On Nov 18, 12:00 pm, Chad Norwood <[email protected]> wrote:
> Yep, mine broke too, getting 400 error msg from google.   What fixed
> it for me was just moving my api key to be the first parameter in URL.
>
> Before (worked this summer, now broken)
>
>   $.getJSON('http://maps.google.com/maps/geo?callback=?',   { q: addr,
> key: googleApiKey,  ... }
>
> Fix (works as of now)
>
>   $.getJSON('http://maps.google.com/maps/geo?key='+googleApiKey
> +'&callback=?',  { q: addr, ... }
>
> cheers,
> chad
>
> On Nov 6, 12:23 pm, lily <[email protected]> wrote:
>
> > I think the problem is not the callback=blahblah itself, I think the
> > problem is the _=blahblah.   But since that parameter is created by
> > jquery, it would be nice if the google API could handle it.
>
> > On Nov 4, 11:55 am, lily <[email protected]> wrote:
>
> > > Hi!  MyJSONPcalls suddenly stopped working too!  However, I do have
> > > callback=?  at the end of the query string - your solution didn't work
> > > for me!
>
> > > Here's an example of my problem, note the missing 
> > > map:http://www.pic.tv/local/resource-locator/index.php?__language=en&__te...
>
> > > On Oct 30, 5:27 pm, Hugo <[email protected]> wrote:
>
> > > > You nailed it. Thanks!
>
> > > > On Oct 30, 4:19 pm, Adam Schneider <[email protected]> wrote:
>
> > > > > I discovered this problem earlier today.  If you rearrange your URL so
> > > > > that "callback" is the LAST parameter, it will work.  This seems like
> > > > > a bug on Google's end; the order of key/value pairs in a query string
> > > > > shouldn't make one whit of difference.
>
> > > > > Adam
>
> > > > >http://adamschneider.net/http://www.gpsvisualizer.com/
>
> > > > > On Oct 30, 12:40 pm, Hugo <[email protected]> wrote:
>
> > > > > > As of yesterday aJSONPcall to get reverse-geolocationdata worked
> > > > > > just fine - no longer seems to be the case today.
>
> > > > > > If you paste this link (w/ jsonpcallbackarguments) in your browser
> > > > > > it will return a 400 "Bad request"
>
> > > > > >http://maps.google.com/maps/geo?callback=jsonp1256888593627&_=1256888...
>
> > > > > > If you take out thecallbackarguments, leaving the rest of the URL
> > > > > > unchanged, all is good (200 http code, json data returned)
>
> > > > > >http://maps.google.com/maps/geo?q=37.758199,-122.394628&key=ABQIAAAA-...
>
> > > > > > Havejsonpcalls been banned? That would seem...surprising...

--

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=.


Reply via email to