arwystli/getlocations_dr

for Drupal 7

Getlocations 1.x

Getlocations will provide a Google maps API version 3 enabled map on which to display markers of locations found in location-enabled content-types.

INSTALL Before installing getlocations please ensure that you have the libraries module installed

Download the file(s) and place them into your libraries folder so you have a path something like this: sites/all/libraries/getlocations/markers

The 'extra' files contain numbered and letter markers. You can optionally add these if you need them.

CONFIGURE You should configure Getlocations by visiting admin/config/services/getlocations.

USAGE Getlocations maps can be displayed per node, eg "/getlocations/node/xxx" will display all the locations associated with that node.

They can also be displayed per content-type, so if your content-type has a machine name 'venue' you can show them all with "/getlocations/type/venue".

With the above path you can add another two parameters which must be a location key/value pair, so "/getlocations/type/venue/city/london" will give you all the locations in London. The keys might typically be

lid name street additional city province postal_code country latitude longitude province_name country_name

If you need more complex things use Views.

TODO add location-enabled user ids once location handles users properly

You can display a list of location ids with something like "getlocations/lids/1,2,3,4" and a list of nodes with "getlocations/nids/1,2,3,4"

There are some Views, disabled by default. The getlocations View will provide a block that will appear when a location enabled node is being shown. The block contains a link to a map.

Automatic Panning This setting has 4 possibilities: "None" is No panning. This uses the default zoom and map center.

"Pan" keeps the markers in the Viewport. This will try to fit the markers in by panning to them but uses the default zoom.

"Pan and zoom" fits the markers to the Viewport. This zooms in as far as it can and will fit all the markers onto the map. This setting should only be used if you have less than 30 - 50 markers.

"Set Center" places the markers in the middle of the map. This is similar to "Pan" but uses averaging to define the map center.

Which of these settings is best for your usecase depends on how many markers you have and their 'spread', eg are they all in one region or spread out all over the world.

Showing more than 30 -50 markers could lead to browser crash, remember that it is the client browser not the server that is doing the work so you need to test on slow machines and basic handheld devices to determine the best settings for your site.

If you have many markers you can use MarkerClusterer to control your markers. There is also a Markermanager but it is not as reliable.

If you have the Colorbox module installed and enabled in Get Locations you can place any of the above paths in a colorbox iframe by replacing 'getlocations' with 'getlocations_box'. To enable this for a link you can use the 'colorbox-load' method, make sure that this feature has been enabled in colorbox and use a url like this: See map

or (advanced use) by adding rel="getlocationsbox" to the url, eg See map

The last method uses the settings in admin/config/services/getlocations for colorbox and uses its own colorbox event handler, see getlocations_colorbox.js. You can define your own event handlers in your theme's javascript. 'getlocations_box' has it's own template, getlocations_box.tpl.php which can be copied over to your theme's folder and tweaked there.

The InfoBubble javascript library is included and can be configured by copying js/infobubble_options.txt to js/infobubble_options.js and editing that.

Getlocations now has hook_getlocations_markerdir() from jhm http://drupal.org/user/15946 This hook allows other modules to add their own marker collections. example:

function mymodule_getlocations_markerdir() { $markers = drupal_get_path('module', 'mymodule') . '/mymarkers'; return $markers; }

The above example requires the module mymodule to have a folder mymodule/mymarkers which contains the bespoke markersets. These will be added to the available markers when the Marker Cache is regenerated.

In a Getlocations View, in Format: Getlocations | Settings, if you have selected InfoBubble or InfoWindow in the Marker action dropdown you will see a checkbox 'Replace default content' which when checked will provide a list of available fields to use instead of the default content.

Geofield and Geolocation support Getlocations provides some default Views to work with the Geofield and Geolocation modules but if you want maps you will have to do some tweaking.

Geofield: In the Getlocations view, add a block and in 'Fields' add Content: Location (or whatever you called it), Select Formatter: Latitude only Select Data options: Use full geometry Select Format: decimal degrees Under 'More' give it an Administrative title of 'latitude'

Repeat for longitude

Then add Content: Type You should now have the following in Fields: Content: Title Content: Nid (make sure this has 'Rewrite the output of this field' and 'Output this field as a link' switched off) latitude longitude Content: Type (set to Output machine name)

They should be in that order. exclude all from display except Content: Nid

Then add to Filter criteria Content: Type and select the content type(s) you want

Under Format: select Getlocations and set up the map Edit the Block title to whatever suits you Save the view, enable the block and test.

You can do much the same in 'Getlocations links' View

Geolocation: In the Getlocations view, add a block and in 'Fields' add Content: Location (or whatever you called it), Select Formatter: Latitude text-based formatter Under 'More' give it an Administrative title of 'latitude'

Repeat for longitude

They should be in that order. exclude all from display except Content: Nid

Then add to Filter criteria Content: Type and select the content type(s) you want

Under Format: select Getlocations and set up the map Edit the Block title to whatever suits you Save the view, enable the block and test.

You can do much the same in 'Getlocations links' View

Addressfield support. If the Addressfield module is supplying an address in conjunction with Geofield or Geolocation the address will be used to populate the InfoWindow or InfoBubble.

Theming. Getlocations pages can be themed by copying the relevant function to your theme's template.php, renaming it in the usual manner. eg theme_getlocations_adinfo() becomes MYTHEME_getlocations_adinfo() where MYTHEME is the name of your theme. You can edit it there to suit your needs.

These functions can be found in the file getlocations.module

Theming the content of InfoWindow or InfoBubble. This is done with function theme_getlocations_adinfo()

Theming the map display. This is done with function theme_getlocations_show()

Theming the Getlocations settings form. This is done with function theme_getlocations_settings_form()

Theming the Getlocations options form in Views. This is done with function theme_getlocations_plugin_style_map_options_form()

function template_preprocess_getlocations_box() and function template_preprocess_getlocations_marker_box() are for use in conjunction with the colorbox module and use the files getlocations_box.tpl.php and getlocations_marker_box.tpl.php respectively.

You can now categorise markers in Views by adding Content: type (output machine name) in the Fields section of a view. This will be passed on to the javascript, so you can add a button to getlocations-view-map.tpl.php (by copying this file to your theme folder) eg

and adding something like:

  // toggle location button
  if ($("#toggle_loc").is("input")) {
    $("#toggle_loc").click( function() {
      k = 'key_1';
      cat = 'location';
      $.each(getlocations_markers[k].lids, function (lid, mark) {
        if (getlocations_markers[k].cat[lid] == cat) {
          vis = mark.getVisible();
          if (vis) {
            mark.setVisible(false);
            $("#toggle_loc").val("Location on");
          }
          else {
            mark.setVisible(true);
            $("#toggle_loc").val("Location off");
          }
        }
      });
    });
  }

to your theme's javascript edit 'key_1' to whichever key your map is using edit 'location' to the machine name of your content type This will give you a button that can switch markers on/off

More information on theming can be found on http://drupal.org/documentation/theme

Polygons To use polygons on your map you will need to enable the feature either globally under admin/config/services/getlocations or per content type under Manage Display or per map in a View under Format: Getlocations | Settings. You will need to supply coordinates as a pipe (|) delimited list of lat,lon pairs minimum 3 pairs. eg 51.501579,-0.193544|51.498373,-0.144449|51.479882,-0.148054|51.484585,-0.184446

You can also have per polygon settings, here is a list of available options: strokeColor eg #0000FF strokeOpacity between 0 and 1 strokeWeight eg 3 fillColor eg #0000FF fillOpacity between 0 and 1 clickable 1 or 0 message any text

These should be in the form of key:value eg strokeColor:#0000FF

You should add these to the pipe delimited list, eg

strokeColor:#0000FF|strokeOpacity:0.8|51.501579,-0.193544|51.498373,-0.144449|51.479882,-0.148054|51.484585,-0.184446

GeoJSON Getlocations can support GeoJSON objects, see http://www.geojson.org/ for information about this format. You can download the library from https://github.com/JasonSanford/GeoJSON-to-Google-Maps. It should be installed in your libraries folder so you have a path something like this: sites/all/libraries/GeoJSON/GeoJSON.js

Once the library is installed you can enable it globally, per view or per content type

Geocoder-js The geocoder-js library provides support for the search facilities from Openstreetmap You can download the library from https://github.com/geocoder-php/geocoder-js. You should copy the file from dist/geocoder.min.js to sites/all/libraries/geocoder-js/geocoder.min.js

Once the library is installed you can enable it globally, per content type or in getlocations_search.

Drush integration for getlocations. 'drush getlocations-markers' will install the basic getlocations marker set 'drush getlocations-geojson' will install the GeoJSON javascript library 'drush getlocations-geocoder' will install the Geocoder-js javascript library 'drush getlocations-leaflet' will install the Leaflet javascript library If you want the library installed somewhere other than sites/all/libraries then provide the path after the command.

Other map tiles. Getlocations supports the use of other sources of maps besides Google, you can show maps from OpenStreetMap, OpenCycleMap, Stamen and Esri. Developers can add their own maps using hook_getlocations_map_providers(), see the function getlocations_getlocations_map_providers() for examples.

The Google Places Search service can be enabled for any map. It can be configured to provide an Autocomplete textfield or a dropdown. If you want to preselect a particular item in the dropdown you can add something like this to your theme's javascript:

var key = 'key_1'; var tp = 'grocery_or_supermarket'; $("#search_placesselect" + key).val(tp);

Content type Markers If you have selected "Enable Markers for Content types" in admin/config/services/getlocations and you wish to use these markers in a View you need to ensure that you have enabled

Getlocations Fields: Field name Content: Type (set to Output machine name)

in the view's Fields list

arwystli / getlocations_dr

readme