You are here

README.txt in Get Locations 6

Same filename and directory in other branches
  1. 6.2 README.txt
  2. 7.2 README.txt
  3. 7 README.txt
for Drupal 6
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 location and
libraries modules installed

You can fetch markers from dropbox:
As tarballs:
http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers.tar.gz
http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers-extra.tar.gz

As zipfles:
http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers.zip
http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers-extra.zip

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/settings/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.

You can show all the location enabled users with a path
"/getlocations/users"
and you can show a single user with
"getlocations/user/xxx" where "xxx" is the user uid

The getlocations user features have their own permissions so you can restrict
access according to your needs.

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.

getlocations_user View does the same for users.

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 hundreds of markers make sure that the markermanager is enabled and
that the markers are not all in the viewport at once, at least not on the map
as it is initially set up.
This applies especially to the
"/getlocations/type/zzz"
map which shows all the markers (of a given content-type)

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:
<a href="/getlocations_box/node/xxx?width=700&height=600&iframe=true" class="colorbox-load">See map</a>

or (advanced use) by adding rel="getlocationsbox" to the url, eg
<a href="/getlocations_box/node/xxx" rel="getlocationsbox">See map</a>

The last method uses the settings in administration/settings/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.

File

README.txt
View source
  1. for Drupal 6
  2. Getlocations will provide a Google maps API version 3 enabled map on which to
  3. display markers of locations found in location-enabled content-types.
  4. INSTALL
  5. Before installing getlocations please ensure that you have location and
  6. libraries modules installed
  7. You can fetch markers from dropbox:
  8. As tarballs:
  9. http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers.tar.gz
  10. http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers-extra.tar.gz
  11. As zipfles:
  12. http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers.zip
  13. http://dl.dropbox.com/u/41489105/Drupal/getlocations/getlocations-markers-extra.zip
  14. Download the file(s) and place them into your libraries folder so you have
  15. a path something like this:
  16. sites/all/libraries/getlocations/markers
  17. The 'extra' files contain numbered and letter markers.
  18. You can optionally add these if you need them.
  19. CONFIGURE
  20. You should configure Getlocations by visiting admin/settings/getlocations.
  21. USAGE
  22. Getlocations maps can be displayed per node, eg "/getlocations/node/xxx"
  23. will display all the locations associated with that node.
  24. They can also be displayed per content-type, so if your content-type
  25. has a machine name 'venue' you can show them all with
  26. "/getlocations/type/venue".
  27. With the above path you can add another two parameters which must be a
  28. location key/value pair, so "/getlocations/type/venue/city/london" will
  29. give you all the locations in London. The keys might typically be
  30. lid
  31. name
  32. street
  33. additional
  34. city
  35. province
  36. postal_code
  37. country
  38. latitude
  39. longitude
  40. province_name
  41. country_name
  42. If you need more complex things use Views.
  43. You can show all the location enabled users with a path
  44. "/getlocations/users"
  45. and you can show a single user with
  46. "getlocations/user/xxx" where "xxx" is the user uid
  47. The getlocations user features have their own permissions so you can restrict
  48. access according to your needs.
  49. You can display a list of location ids with something like
  50. "getlocations/lids/1,2,3,4"
  51. and a list of nodes with
  52. "getlocations/nids/1,2,3,4"
  53. There are some Views, disabled by default.
  54. The getlocations View will provide a block that will appear when a location
  55. enabled node is being shown. The block contains a link to a map.
  56. getlocations_user View does the same for users.
  57. Automatic Panning
  58. This setting has 4 possibilities:
  59. "None" is No panning.
  60. This uses the default zoom and map center.
  61. "Pan" keeps the markers in the Viewport.
  62. This will try to fit the markers in by panning to them but uses
  63. the default zoom.
  64. "Pan and zoom" fits the markers to the Viewport.
  65. This zooms in as far as it can and will fit all the markers onto the map.
  66. This setting should only be used if you have less than 30 - 50 markers.
  67. "Set Center" places the markers in the middle of the map.
  68. This is similar to "Pan" but uses averaging to define the map center.
  69. Which of these settings is best for your usecase depends on how many markers
  70. you have and their 'spread', eg are they all in one region or spread out all
  71. over the world.
  72. Showing more than 30 -50 markers could lead to browser crash, remember that
  73. it is the client browser not the server that is doing the work so you need to
  74. test on slow machines and basic handheld devices to determine the best
  75. settings for your site.
  76. If you have hundreds of markers make sure that the markermanager is enabled and
  77. that the markers are not all in the viewport at once, at least not on the map
  78. as it is initially set up.
  79. This applies especially to the
  80. "/getlocations/type/zzz"
  81. map which shows all the markers (of a given content-type)
  82. If you have the Colorbox module installed and enabled in Get Locations
  83. you can place any of the above paths in a colorbox iframe by replacing
  84. 'getlocations' with 'getlocations_box'.
  85. To enable this for a link you can use the 'colorbox-load' method,
  86. make sure that this feature has been enabled in colorbox
  87. and use a url like this:
  88. See map
  89. or (advanced use) by adding rel="getlocationsbox" to the url, eg
  90. See map
  91. The last method uses the settings in administration/settings/getlocations for colorbox
  92. and uses its own colorbox event handler, see getlocations_colorbox.js. You can define your own
  93. event handlers in your theme's javascript.
  94. 'getlocations_box' has it's own template, getlocations_box.tpl.php which can be
  95. copied over to your theme's folder and tweaked there.
  96. The InfoBubble javascript library is included and can be configured by copying
  97. js/infobubble_options.txt to js/infobubble_options.js and editing that.