Get Locations will provide Google maps API version 3 enabled maps on which to display markers of locations found in location-enabled content-types.
These 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".
The Drupal 6 version also supports paths like "/getlocations/user/xxx" and "/getlocations/users" for location-enabled users. These links have their own access permissions so control can be exercised on a per role basis.
See the README.txt for more information on what getlocations can do
Please read and follow the instructions in README.txt. You need to do this to get markers working. You will need at least the first one in the lists below.
You can download markers from Dropbox:
There are lots of icons at mapicons.nicolasmollet.com
You can use the tools at powerhut.co.uk to provide you with information to make your own ini files and icon sets.
The 6.x-2.x series supports Views 3 but is the same in all other respects.
Other features include:
- Configurable Infobubble styling
- Support for Google maps API Version 3 key
- Support for multiple maps on a page
- Markers can be defined globally, per content type, per content instance or per item
- Marker action can be either click or mouseover, configurable globally or per map
- Automatic HTTPS support
- Maps can be displayed in a Colorbox
- All output is fully themeable
- Views support for Getlocations Fields (see below) includes per item maps, All locations maps, Nearby location maps as well as lists with similar functions. Some views support exposed forms. Views developers will be able to create many other possibilities.
The 7.x series includes a submodule Getlocations Fields which can be used instead of location and location_node or location_cck.
Getlocations Fields can add an address and map to these content types:
- user with or without profile2
There can be more than one input map.
All geocoding is done clientside, before the page is submitted. There are two methods available, either with Google Places Autocomplete or without.
Support for Smart IP module. Do not enable the Smart IP submodule "Device Geolocation" as Getlocations already has this capability, just enable 'Provide Browser based geocoding option' in getlocations_fields/getlocations_search.
The Getdirections module can use Getlocations Fields locations
There are other submodules:
- Getlocations Search which uses Google Geocoding on entered search terms and shows nearby locations. The search form is fully configurable with options for setting the Search distance, Distance units, Number of locations to show and Restrict the search to a content type.
- Getlocations Blocks that works in conjunction with Views. It provides dropdowns or autocompletes for Country, Province/State, Town or Postcode. How well it works depends on how large your dataset is.
- Getlocations Location Taxonomize which supports Location Taxonomize.
- Getlocations Feeds which provides some basic support for the Feeds module.
These modules are still very much under development.
- Geolocation (Drupal 7)
- A solution to the 'duplicate markers' problem, see #1551882: MarkerCluster with InfoWindows - InfoBubbles
- 'Find current location' button for gps enabled devices
- Traffic, Bicycle, Transit, Panoramio and Weather Layers for maps
- Viewport bias option for Google Autocomplete
- Improved markers
- Getlocations Search in a page, block or Colorbox
- Configurable Maps background color (D7 and D6)
- Support for the Countries module, the Getlocations Fields input form can now be configured to only show certain Countries or Continents in the Country dropdown.
- Option to show a list of links that emulate clicking on a marker
- Maximum and Minimum zoom settings for the map
- Fullscreen option for the map
- Support for Polygons, Rectangles, Circles and Polylines. These can be global, per content type or per View
- various bug fixes
Development for Drupal 7 version:
- Support for OpenStreetMap
- Support for KML layers
Development version 7.x-2.x is now available, this is not yet suitable for production. This version attempts to use the D7 Entity type concept which in principle should allow Getlocations to work with any Entity type. Needs testing.
If updating to the latest dev or the current stable you will need to run cron or flush cache or Regenerate markers. The marker cache now resides in
Do not install the Location module or the Geofield, Addressfield or Geolocation modules at the same time as Getlocations_fields, this will not work.
If you are upgrading from an earlier version make sure you go to admin/config and save the settings as there may be new features added. Flushing the cache is probably also a good idea.
Please report any bugs on the Issues page