Oct 01 2012
Oct 01

Setting up geo-location data on a Drupal site is startlingly straightforward these days: pop in Geofield or Geolocation module and start adding latitude and longitude data to your nodes. Once you have the data, setting up maps and other complex geographically-aware content listings is easy. Unfortunately, it's that "getting the data" part that can be thorny. If users are willing to type in exact street addresses or latitude/longitude pairs themselves, there are more than a few options. If you need to transform other kinds of data into useful location data, though, Geocoder might just do the trick.

Geocoder Google options

Geocoder provides as a custom field editing widget for several popular location storage fields (Geofield, Geolocation, and Location module). Rather than offering a custom input form, however, it lets the site administrator pick another field on the content type that contains some geographical information.

Are you creating nodes whose titles are city names? Tell Geocoder to send that title to Google's geocoding service and store the resulting data in the Geofield. Are your site's users uploading photos with location information from a camera phone? Tell Geocoder to use the image field as its source, and the location data will be extracted automatically. The actual location storage fields -- the ones that hold latitude and longitude values -- are kept hidden from users and editors entirely.

Geocoder EXIF data extraction

Geocoder supports an impressive array of encoding APIs and data extraction mechanisms, from uploaded .KML files to Mapquest-parsed street addresses. It's an excellent swiss army knife for sites that need user-entered geo data, and a great addition to any site builder's arsenal.

*/
Apr 01 2008
Apr 01

What is GeoLocation module?
For OSCMS, over a year ago, I wrote a module called geolocation as an example CCK field. It has languished in CVS for quite a while, I finally set up a project for it today, and I'm looking for a co-maintainer.

Why do you need help?
I don't have time right now. I'm in the midst of major upgrades on the image* modules I maintain, doing new development on filefield and other media related modules, trying to keep up with my day job, and preparing to do 6.x ports of the modules I maintain.

Ok, so what do you need?
I need someone who would like to run with the module and implement a few necessary features for it. I want to stay involved because I want to play with different proximity searching techniques and would like a free hand to do it.
This would be a great role for an aspiring developer who already has some basic CCK and Views skills and wants a chance to expand them, and work on a module with a lot of potential.

What is the condition of GeoLocation?
GeoLocation is currently functional as a field module and works with Drupal 5.x. It has a basic text widget as well as yahoo maps integration that hasn't been tested since OSCMS. (I did yahoo maps since we were on their turf.)

What does GeoLocation need?

  • Improve the views integrations by adding filters for longitude, latitude, and proximity.
  • Google Maps input widget
  • Gmap Module integration

If you're interested please contact me @ http://drupal.org/user/22202 and I will be happy to discuss in further detail what I'm looking for in a co-maintainer and the direction of the module.

About Drupal Sun

Drupal Sun is an Evolving Web project. It allows you to:

  • Do full-text search on all the articles in Drupal Planet (thanks to Apache Solr)
  • Facet based on tags, author, or feed
  • Flip through articles quickly (with j/k or arrow keys) to find what you're interested in
  • View the entire article text inline, or in the context of the site where it was created

See the blog post at Evolving Web

Evolving Web