Thursday, June 6, 2013

OVER_QUERY_LIMIT


http://maps.google.com/maps/api/geocode/xml?address= 台北市中華路&sensor=true

#Problem:

註明感應器的使用狀況

使用 Google Static Maps API 時,您必須指出您的應用程式是否有使用「感應器」 (例如 GPS 定位器) 判斷使用者的位置。這對行動裝置尤其重要。應用程式必須傳送必要的感應器參數,指出您的應用程式是否有使用感應器裝置。
如果您的應用程式是透過感應器判斷使用者位置,就必須在 Static Maps API 要求網址內傳送 sensor=true。如果您的應用程式沒有使用感應器,請傳送 sensor=false

#Problem:


This XML file does not appear to have any style information associated with it. The document tree is shown below.
<GeocodeResponse>

<status>OVER_QUERY_LIMIT</status>
</GeocodeResponse>


Geocoding Strategies#


Server-side geocoding through the Geocoding Web Service has a quota of 2,500 requests per IP per day


Client-side geocoding through the browser is rate limited per map session,


When to Use Client-Side Geocoding

The basic answer is "almost always." As geocoding limits are per user session, there is no risk that your application will reach a global limit as your userbase grows. Client-side geocoding will not face a quota limit unless you perform a batch of geocoding requests within a user session. Therefore, running client-side geocoding, you generally don't have to worry about your quota.



Google Maps API Web Services

This document discusses the Maps API Web Services, a collection of HTTP interfaces to Google services providing geographic data for your maps applications. This guide serves only to introduce the web services and host information common to all of the different services. Individual documentation for each service is located below:
business API -
http://maps.googleapis.com/maps/api/geocode/json
  ?address=1600+Amphitheatre+Parkway,+Mountain+View,+CA
  &sensor=true_or_false
  &client=gme-YOUR_CLIENT_ID
  &signature=YOUR_URL_SIGNATURE
#http://googlegeodevelopers.blogspot.tw/2012/06/lower-pricing-and-simplified-limits.html



#必看文章
http://www.webstutorial.com/google-server-side-geocoding-php-infobox/website-tweaks/google

No comments:

Post a Comment