How-to usecase? Add optional geocoding to map input widget

Hi JB,

If you install the openlayers module along with geofield and geocoder, you should see the widget "OpenLayers Map" for geofield, within that widget settings, you should see options to enable geocoding as part of the map widget.

Marking as fixed.

Hello Boabjohn,

Being that I'm a relative newb to Geofield, I had setup a geofield with all of the available features and created an issue where users could create more than one point and draw on the map and NOT reset the point currently on the map. So first I recommend checking your content type's fields' settings (Addressfield and Geofield).

Please note that your setup may vary.

Go to Administration->Structure->Content Types->[ContentTypeHere]->Manage Fields

Review Addressfield settings

Label:Address, Field Type: Postal Address, Widget: Dynamic Address Form

Review Geofield settings

Label: Geofield, Field Type: Geofield, Widget: OpenLayers Map
Click "edit" to check your geofield's settings
OpenLayers Map: Geofield Widget Map
Storage Options: Store each simple feature as a separate field.
Available Features: Point
Allow Shape Modification: Checked

Geocoder settings

Enable geocoding of location data: Checked
Geocode from field: Address
Geometry Type: Point

Geofield Field Settings

Number of Values: 1

2 important setting changes I made to geofield were:

1. uncheck Available Features: Path and Polygon
2. and set Number of Values to 1

I hope you made the same mistake that I did and enabled too much.

Have fun!
Jeremy

Hello @boabjohn,

can you clarify where you're selecting the Geocoder settings

I'm referring to your content type's Geofield field's settings.

I apologize as I thought you had already setup your content type with an Addressfield field and Geofield field. The Geocoder project page has a link to an instructional video on using OpenLayers, Geofield, Addressfield and Geocoder produced by DrupalOverEasy.com

Geocoder will default to using Google's geocoder API v3 which does not require an API key (See https://developers.google.com/maps/faq#geocoder_limit). In other words, you don't need to enter an API key at Administration->Configuration->Content Authoring->Geocoder settings.

I do recommend the book, Mapping with Drupal to get more familiar with mapping and Drupal. Though it is probably out of date by now, it is a quick read and a great start to understanding mapping with Drupal.

Is there a way to make the map geocode on node save, just as the geofield does? THis was the funtionlity for geofield map in Drupal 6. In cases such as ours, were we import hundreds of nodes at a time, we need to be able to geocode on node save.

correct minor typos

the setup works till a certain point.
When a user enters an address into the address field and than uses the "find using Address field" the map has to be huge to show the point on the map - because there is no zoom to layer option for the found result. It is a show stopper as you can't expect people to search the hole map for the point ...

Question: the open layers library is pretty large, do I need all of it for this use case?

I followed the "right way" method of getting the library shown here: https://www.drupal.org/project/openlayers The entire library folder (OpenLayers-2.13.1) is 74.2 MB unzipped.

Do I need everything that is in there for this use case? I want to be able to use local JS instead of this: http://openlayers.org/api/2.13/OpenLayers.js (see settings: admin/structure/openlayers). By the way the main reason I need to do that is that http://openlayers.org/api/2.13/OpenLayers.js won't load when I am https on my Drupal site, maybe there is another way around that? It works fine on http.

This is error on https:

Mixed Content: The page at 'https://www.mysite.com/node/1720/edit' was loaded over HTTPS, but requested an insecure script 'http://openlayers.org/api/2.13/OpenLayers.js'. This request has been blocked; the content must be served over HTTPS.

My use case is only to be able to have an open layers widget for geofield to set a location of a node in case the geofield module cannot get the coordinates from the address field (the subject of this issue).

Or, should I not worry about it and just put the whole 74MB up there in the libraries folder? Seems like a lot of bloat is all.

Thanks,

Rick

UPDATE:
OK I realized that a huge part of the size of the open layers library is the docs folder which was 50.5 MB. I got rid of that folder as well as these others:
examples folder (4.1 MB)
tests folder (5.8 MB)
tools folder (147 KB)
It all works fine without those folders, so all set.
Open Layers library running locally now, so no https problem anymore.

Geolocation Field provides a Google Maps input widget for Geofield.
https://www.drupal.org/project/geolocation

The comments by GreenSkunk got me really close to accomplishing my goal of using the openlayers map option for allowing admins to fine tune the Geocoder results. Unfortunately, that broke auto-geocoding on programmatic node creation. It turns out the Geocoder module only updates fields that are using the 'geocoder' field widget. Even after setting the 'geofield_openlayers' widget to Geocode From A Field, and selecting my Addressfield field.

A workaround I found was to copy Geocoder's hook_field_presave function into a module, and change which widget it is looking for:

/**
 * Implements hook_field_attach_presave().
 *
 * Geocoding for the geocoder widget is done here to ensure that only validated
 * and fully processed fields values are accessed.
 */
function MYMODULE_field_attach_presave($entity_type, $entity) {
  // Loop over any geofield using our geocode widget
  $entity_info = entity_get_info($entity_type);
  $bundle_name = empty($entity_info['entity keys']['bundle']) ? $entity_type : $entity->{$entity_info['entity keys']['bundle']};
  foreach (field_info_instances($entity_type, $bundle_name) as $field_instance) {
    if ($field_instance['widget']['type'] === 'geofield_openlayers') {
      if (($field_value = geocoder_widget_get_field_value($entity_type, $field_instance, $entity)) !== FALSE) {
        $entity->{$field_instance['field_name']} = $field_value;
      }
    }
  }
}

Hopefully this saves someone some time.