Places API Web服务的查询限制与JS限制不同 [英] The query limit on the Places API web service is different from the JS limit

查看:92
本文介绍了Places API Web服务的查询限制与JS限制不同的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在开发一个应用程序,该应用程序通过Javascript库使用Places API( https:/ /developers.google.com/maps/documentation/javascript/places ),尽管我在任何时候都用它进行了数百次搜索,但我似乎没有超过这个限制。



我决定将我的应用程序的搜索方面移到服务器端,因为我正在开发一个移动版本,并且不希望移动浏览器一次执行超过100个请求。所以,我转而使用Web服务API( https://developers.google.com/maps / documentation / places /

这样做似乎突然间会超出查询限制。这是什么原因?有没有什么办法可以解决这个问题,而不必增加我的查询限制?

谢谢!

解决方案

我相信使用Google Maps JavaScript API v3,您的通过此政策
并使用Google Places API,您可以这些限制。我认为您应该通过验证,以便将限制从1000到100000美元

I was developing an application which uses the places API through the Javascript Library (https://developers.google.com/maps/documentation/javascript/places), and although I was making hundreds of searches with it at any given time, I never seemed to go over the limit.

I've decided to move the search aspect of my application to the server-side, though, because I was developing a mobile version and didn't want mobile browsers doing 100+ requests at a time. So, I switched to using the Web Service API (https://developers.google.com/maps/documentation/places/)

In doing so I seem to be going over the query limit all of a sudden. What is the reason for this? Is there any way I can solve this without having to increase my query limit?

Thanks!

解决方案

I believe that using the Google Maps JavaScript API v3 you are limited with this policy and by using the Google Places API you have these limits.I think you should go through verification so you raise the limit from 1000 to 100000

这篇关于Places API Web服务的查询限制与JS限制不同的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆