September 09, 2010
Summary of mapping modules in Drupal
First off, here is how I'm currently mapping in Drupal:
The Location module supplies the ability to associate locations with nodes in (at least) two ways: 1) Node Location (similar to a Node Title) and 2) CCK Location Field. I use the CCK Location Field. Location also offers Views integration.
The GMap module (maintained by the same team as Location) adds Google Map interface capabilities to the Location and Views module.
I use GMap and Location to georeference nodes of the Institution and Research Site content types. Examples are here:
A View of the sites comprising our research site gazetteer. Note, I am using Jef Poskanzer's Clusterer to group sites.
Here is an example of a research site. The GMap shown is a View modified from that listed above. Basically, I added an NID argument (taken from the URL) to show only the given research site and a tiny GMap macro that autozooms and resizes the map.
I also associate an Institution with nodes of the Person content type and map them here. This is less functional, but it is cool to see where our visitors (researchers, faculty, students, others) come from.
GMap Addons Module - allows overlay support for KML and other layers. Also, more baselayers. Same maintainer as GMap and Location (bdragon.)
Geo Module - similar to Location but with support for lines and polygons. Perhaps more advanced in terms of loyalty to GIS principals?
Notes: there's an uncommitted patch for GMap to support polygons.
OpenLayers Module - the non-proprietary version of the GMap Module? Seems to standalone (don't need Geo or Location.) In fact, integration with Location may not work. This video indicates that OpenLayers is more powerful but harder to use than Gmap. Can create polygons and lines via point and click map interface.
Posted by kkwaiser at September 9, 2010 09:42 AM