svrooij

<p>The mobile editor app for WordPress has an option to automatically geocode all the posts.<br />
This works great but doesn’t really allow for easy editing or show this information on for instance a map.</p>
<p>Current features:</p>
<ul>
<li>Editing the location provided by the mobile app from the post edit screen.</li>
<li>Showing a widget with the latest x (configurable number) posts that have a geolocation (loads async).</li>
<li>Automatically looking up the locality of a new post.</li>
<li>Exposing a ‘geo’ object for each post in the REST api with ‘latitude’, ‘longitude’ and ‘locality’.</li>
<li>Posts from the mobile app connected through wordpress.com get the geo_public set automatically.</li>
</ul>
<p>Things that are on my wish list are:</p>
<ul>
<li>Manually bulk geocoding old posts.</li>
<li>Displaying the geocoded posts on a map with a shortcode or something.</li>
</ul>
<h4>Notes</h4>
<ol>
<li>If you like the plugin <a href="https://svrooij.nl/buy-me-a-beer/" rel="nofollow ugc">buy me a beer</a></li>
<li>Something wrong with this plugin? <a href="https://github.com/svrooij/wp-geocoded-posts/issues" rel="nofollow ugc">Report issue on Github</a></li>
</ol>
<p>For development we use Github in combination with Grunt for easier deployment. If you run <code>npm install</code> and <code>grunt build</code> in the cloned <a href="https://github.com/svrooij/wp-geocoded-posts/" rel="nofollow ugc">repository</a> it will produce a build folder. This folder contains all the files needed to run the plugin.</p>


Geocoded posts

Better location management with Location posts widget, location editor and location data in the REST api.

Eyal Fitoussi

<p>WP Job Manager Client-Side Geocoder plugin bypass the geocoder function ( server side ) provided by WP Job Manager plugin and instead uses client-side geocoding system.<br />
By doing so the plugin should overcome the OVER_QUERY_LIMIT issue which you might have been experiencing.</p>
<h4>Features</h4>
<ul>
<li>Client-side geocoding system will try to overcome the OVER_QUERY_LIMIT issue which prevents address from being geocoded. </li>
<li>New “Geocode” button added under the location field in the “New Job” ( and “New Resume” for those who use the Resume Manager add-on ) page in the back-end. A click on the button will geocode the address entered.</li>
<li>When creating/updating job ( or resume ) from the front-end the location will be automatically geocoded once the form is submitted. No “geocode” button added to the front-end forms.</li>
</ul>


WP Job Manager Client-Side Geocoder

Use client-side geocoding to overcome the OVER_QUERY_LIMIT ( failed to geocode a location ) issue when updating job's location

Geocoded posts vs WP Job Manager Client-Side Geocoder