luminfire

Michael Moore

Cimbura.com

Brilliant Geocoder for Gravity Forms is a powerful and flexible geocoder field 
for Gravity Forms. The Geocoder field is easily be configured to capture geocoder 
input values from other form fields.
It comes with the <a href="http://wiki.openstreetmap.org/wiki/Nominatim" rel="nofollow ugc">OSM Nominatim</a> 
geocoder enabled by default and supports <a href="https://geocod.io/" rel="nofollow ugc">Geocod.io</a> 
and the <a href="https://developers.google.com/maps/" rel="nofollow ugc">Google Maps API</a> once you’ve entered 
API keys for those services.
The geocoder field can be displayed as a map, as latitude and longitude 
fields, as the raw GeoJSON data, or hidden.
This plugin supports WP-GeoMeta, so if you create posts or users with geocoded 
data, their location will be stored as spatial metadata.
NOTICE: This plugin uses 3rd party services to provide geocoding results. 
The default geocoder, OSM Nominatim, requests that you include your email address 
in API calls if you are making a large number of requests. We send the WP admin 
email address by default. You can change what is sent on the Gravity Forms settings 
page, under Geocoder..
<h4>What is Geocoding?</h4>
<a href="https://en.wikipedia.org/wiki/Geocoding" rel="nofollow ugc">Geocoding</a> is the process of turning 
text (an address) into coordinates (latitude and longitude). With coordinates 
you can display data on a map and do location based searching.
<h4>Support for Other Geocoders</h4>
Brilliant Geocoders for Gravity Forms includes hooks so that you can add 
support for other geocoding services.
OSM Nominatim support is built into the plugin, but Geocod.io and Google Maps 
API support is written the same way that you would add support for another 
service. The Geocod.io example in particular has extensive comments.
Please see geocoders/geocodio.php and geocoders/geocodio.js for details.

Brilliant Geocoder for Gravity Forms

Capture location information in Gravity Forms by geocoding user's input into other form fields.

GeoMeta for ACF is an easy way to store location information about posts, pages, 
users or other content types that ACF supports. The default input is a map 
with drawing tools to let the user draw markers, lines and polygons. 
Alternatively you can accept latitude and longitude values, or raw GeoJSON 
text.
GeoMeta for ACF supports for both ACF version 4 and 5.
Why use GeoMeta for ACF instead of one of the other map inputs for ACF?
GeoMeta for ACF uses WP-GeoMeta under the hood, which means that you’re 
actually storing spatial meta data, not just text. With the WP-GeoMeta library 
you have access to all of the spatial functions MySQL supports to search and 
filter your WordPress posts and users.
<h4>Compatibility</h4>
This ACF field type is compatible with:
<ul>
<li>ACF 5 / ACF Pro</li>
<li>ACF 4</li>
</ul>
Note
Metavalues for terms (Categories/Tags) were stored in wp_options up until ACF 
Pro 5.5.0. GeoMeta for ACF will still display a map or other input field for 
terms in previous versions of ACF, but since the values aren’t stored in the 
wp_termmeta table, they won’t be picked up for inclusion in the spatial table 
and spatial searches on them will fail.

GeoMeta For ACF

Store real spatial data with Advanced Custom Fields, using the WP-GeoMeta library.

Brilliant Geocoder for Gravity Forms vs GeoMeta For ACF