After much research we decided to display results based on straight line distance instead of calculating driving distance. Even driving distance API has restrictions on the number of elements we can use per day. We will run in to this issue when we go live.
This is our approach as we don't want to run in to the 2500 quota limitation when we go live; Would aprreciate if you can point out any concerns we should be aware of in the below approach We will be using client-side Geocoding. so when a user does a search for a hotel on the website, all requests will be counted against the user's IP address Example: if there are say 3000 searches done in a second by 3000 different users, and if we use clientside geocoding then that 3000 requests will be counted against the client's IP addresses. Our hosting server will not hit any quota limitations We will be displaying the results in a map to meet Google's terms of Use On a separate page, when a user clicks on a hotel, we display the hotel's address as a marker in google Map. This is again client side geocoding. Anything else we should be aware of? all answers/help greatly appreciated. Thanks! -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-maps-js-api-v3/-/68WEir9p2jsJ. 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.
