| 1 |
********************************************************************
|
| 2 |
D R U P A L M O D U L E
|
| 3 |
********************************************************************
|
| 4 |
Name: geonames_cck
|
| 5 |
Initial Authors: Peter Brownell and Russell Blakeborough
|
| 6 |
Sponsors: Code Positive [www.codepositive.com]
|
| 7 |
and school of everything [www.schoolofeverything.com]
|
| 8 |
Drupal: 5.0.x
|
| 9 |
********************************************************************
|
| 10 |
DESCRIPTION:
|
| 11 |
|
| 12 |
The geonames_cck module implements a CCK field type that uses geonames
|
| 13 |
(http://www.geonames.org) to translate location names into their longditude
|
| 14 |
and latitude coordinates.
|
| 15 |
|
| 16 |
This module was designed to work with the geomap (http://drupal.org/project/geomap)
|
| 17 |
module. Locations are output using Geo microformats, and the geomap
|
| 18 |
module will display any geo data on a google map.
|
| 19 |
|
| 20 |
We use the geonames web service module (http://drupal.org/project/geonames)
|
| 21 |
to handle the actual communication with geonames.
|
| 22 |
|
| 23 |
-- Limitations
|
| 24 |
We have built this version of the module to handle basic name lookups and
|
| 25 |
disambigation. There are all sorts of things it does not do.
|
| 26 |
|
| 27 |
-- No Multiple Values
|
| 28 |
Although a lot of work has been done, working multivalue support was out of
|
| 29 |
scope for our initial release.
|
| 30 |
|
| 31 |
-- No Locations Module Integration
|
| 32 |
The current implementation of this module does not integrate with the standard locations system. There are a few reasons for this, but the first was simply implmentation scope. As a result of this lack of integration, we do not currently have working proximity search functionality.
|
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
********************************************************************
|
| 37 |
INSTALLATION:
|
| 38 |
|
| 39 |
Note: It is assumed that you have Drupal up and running. Be sure to
|
| 40 |
check the Drupal web site if you need assistance. If you run into
|
| 41 |
problems, you should always read the INSTALL.txt that comes with the
|
| 42 |
Drupal package and read the online documentation.
|
| 43 |
|
| 44 |
1. Place the module directory in to Drupal
|
| 45 |
modules/directory.
|
| 46 |
|
| 47 |
2. Enable the module by navigating to:
|
| 48 |
|
| 49 |
Administer > Site building > Modules
|
| 50 |
|
| 51 |
Click the 'Save configuration' button at the bottom to commit your
|
| 52 |
changes.
|
| 53 |
|
| 54 |
|
| 55 |
|
| 56 |
********************************************************************
|
| 57 |
CONFIGURATION
|
| 58 |
|
| 59 |
Geonames CCK fields will now appear as a new field type for CCK
|
| 60 |
nodes. Once assigned to a content type, you may want to set the
|
| 61 |
display settings for the field.
|
| 62 |
|
| 63 |
Locations data can be set to hidden so that it is not visible to
|
| 64 |
users, but is still plotted on a map.
|
| 65 |
|
| 66 |
|
| 67 |
|
| 68 |
|
| 69 |
********************************************************************
|
| 70 |
ACKNOWLEDGEMENTS
|
| 71 |
|
| 72 |
Thanks to Geonames for a great open resource.
|
| 73 |
|