Thanks Marzia,
That's excellent, and I'm glad to know that I'm not overlooking
something obvious! For now "geo-coding" is a point-on-the-map
process :-) I'll keep my eyes open for the update.
On Mar 30, 11:45 am, Marzia Niccolai wrote:
> Hi,
>
> The Maps team is working on this so that it shouldn't be an issue for App
> Engine apps in the future.
>
> -Marzia
>
> On Mon, Mar 30, 2009 at 5:09 AM, Barry Hunter
> wrote:
>
>
>
> > On 30/03/2009, bFlood wrote:
>
> > > I think its because everyone shares the same group of ip addresses so
> > > everything from the GAE servers are triggering some daily limits on
> > > the google maps servers. the same thing is happening when too many gae
> > > apps hit the twitter api.
>
> > > the gmaps keys are based on the domain name but I think there might be
> > > another ip based limit since this issue comes and goes.
>
> > The geocoding limits are based on the IP address of the request. There
> > is both a requests per day and a rate limit.
>
> > The key just needs to match the domain but no throttling is based on it.
>
> > > the gmaps team
> > > would probably need to whitelist the GAE ip addresses for this to work
> > > as expected.
>
> > Perhaps someone should suggest it here:
> >http://code.google.com/p/gmaps-api-issues/
>
> > > cheers
> > > brian
>
> > > On Mar 28, 1:28 pm, Donnie Demuth wrote:
> > > > Hi Ehmo, did you find the solution for this? I'm running into the
> > > > same problem. I know the key is correct but the geo-coding service is
> > > > throwing the 601. Are you still using the proxy or did you ditch the
> > > > app engine completely?
>
> > > > On Feb 17, 4:54 am, ehmo wrote:
>
> > > > > I did register it for API key but it's not working. I tried almost
> > > > > everything, and now i just made another script on another domain,
> > > > > which is doing all this thing instead of GAE. But it's annoying if i
> > > > > can't use google service in google service.
>
> > > > > ehmo
>
> > > > > Barry wrote,
>
> > > > > > I beleive you need to register the key for the {appid}.
> > appspot.com
> > > > > > domain, due to the way urlfetch sends the HTTP referer header.
> > (even
> > > > > > if you
> > > > > > However appengine is a shared system and urlfetch uses a proxy and
> > the
> > > > > > API geocoder limits requests by IP address. For that reason
> > Jarek's
> > > > > > advice to use the ajax method is probably best - that way the
> > request
> > > > > > comes from the users IP which is less likly to be throttled.
> > > > > > On 17/02/2009, ehmo wrote:
>
> > > > > >> Hey guys,
> > > > > >> i'm trying to use Google Geocoding service
>
> >http://code.google.com/apis/maps/documentation/geocoding/index.html
> > > > > >> via http.
> > > > > >> I generated API key for actual domain and it's not working
> > {u'Status':
> > > > > >> {u'code': 610, u'request': u'geocode'}, u'name': u'Brno'}.
> > > > > >> 610 mean it's not good key for this domain. I tryied it on
> > another
> > > > > >> hosting with php, it's working. I tryied it on another hosting
> > with
> > > > > >> same python lib and it's working too. I tryied to use urlfetch
> > and
> > > > > >> urllib2, nothing works.
> > > > > >> Any idea?
>
> > > > > >> Maybe it's because of header restrictions, but i really don't
> > know.
> > > > > >> That link, which is called is ok, coz if i'll try it in browser,
> > > > > >> everything works. All data are encoded before posting, there is
> > 100%
> > > > > >> not problem.
>
> > > > > >> Thnx for help
>
> > --
> > Barry
>
> > -www.nearby.org.uk-www.geograph.org.uk-
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine?hl=en
-~--~~~~--~~--~--~---
