Voting starts in March for the Drupal Association Board election.
We are working with the d7 development snapshot of this module and have got it working well on a site that we're looking to put in production in a few months. It's a website for a large non-profit and the site gets a lot of traffic. We are trying to understand in what instances the proximity module hits the Google Maps Geocoding API and how often.
According to this documention, the geocoding API limits more than 2500 hits a day, and the search we're working on could very possibly be getting more than 2500 searches a day.
Can you help me answer:
- In the case of a view which does a proximity search filter on results, does this module require a site to hit the gmaps geocode api for every single search (ie, every time the view is loaded with a zip code argument)? Or does the search happen within the proximity table that is built upon module install?