Conversation
supportHi, I can see from your GitHUb posts that you’ve added the radius feature to the plugin. Just wondered if you could give me some guidance on how to implement it and get it working? Thanks https://wordpress.org/plugins/wp-geoposts/
you should use the github, there are a couple small updates and bug fixes there. https://github.com/fyaconiello/wp-geo-posts in the bottom of the readme there is an example w/ a radius. A couple known unsolved issues: If you use shared hosting this probably won’t work well. Geoencoding addresses uses Google’s geoencoding service which limits how many geocodes can be done per day PER IP. So if other people are geoencoding on your shared environment there may not be enough encodes for you. If you have a huge number of geoposts, you will run into another issue. calculating distance on EVERY post before limiting on radius is going to take forever. You can modify my plugin using this: http://www.plumislandmedia.net/mysql/haversine-mysql-nearest-loc/ look at the optimization header to pre-filter before records you are calculating distance on.
Seems to work with the new files – Awesome! We’ve been using this plugin for a while with no issues (before we needed the radius feature). What would you call a ‘huge’ number of geoposts? Google recommends Client-Side Geocoding, is this a possibility?
you should use the github, there are a couple small updates and bug fixes there. https://github.com/fyaconiello/wp-geo-posts in the bottom of the readme there is an example w/ a radius. A couple known unsolved issues: If you use shared hosting this probably won’t work well. Geoencoding addresses uses Google’s geoencoding service which limits how many geocodes can be done per day PER IP. So if other people are geoencoding on your shared environment there may not be enough encodes for you. If you have a huge number of geoposts, you will run into another issue. calculating distance on EVERY post before limiting on radius is going to take forever. You can modify my plugin using this: http://www.plumislandmedia.net/mysql/haversine-mysql-nearest-loc/ look at the optimization header to pre-filter before records you are calculating distance on.
Seems to work with the new files – Awesome! We’ve been using this plugin for a while with no issues (before we needed the radius feature). What would you call a ‘huge’ number of geoposts? Google recommends Client-Side Geocoding, is this a possibility?