Sad to read that there will be NO sessions about this subject http://cph2010.drupal.org/news/initial-program. I had really hoped someone would have made such but I think it's because that there still not is any map module that really do the job. A lot of you have been struggling to make such modules and I wish I were good enough understanding Drupal and PHP to make such too but I'm not (at the moment). :-(
That's why I have made my site without any map module and it's functioning great but don't know if I will get any problems in the future but hope not?
http://www.tinemuller.dk/test_drupal/ with radius and for only ONE city http://www.tinemuller.dk/test_drupal/node/6. There will be a map for each city and all this info is saved in the same content type and table. At the moment there will be 98 citites.
Comments
OpenLayers
Zzolo and I are presenting on OpenLayers (http://cph2010.drupal.org/sessions/mapping-drupal-openlayers)
OpenLayers includes Google Maps (as well as many other mapping APIs). It's a different approach than the GMap & Location module approach, but I've been really impressed by it. It's much easier to extend and customize, and the documentation is improving too (definitely check out the handbook pages and the README files in the module).
I'm also presenting on OpenLayers this weekend at Drupal Camp NYC, so I'll post my slides afterwards.
http://www.thomasturnbull.com
http://twitter.com/thomasturnbull
Thanks for your feedback. I
Thanks for your feedback. I will join this session but don't think that a site like mine can be made with this, right? Your name is not mentioned at the session.
Hi tinem: The OpenLayers
Hi tinem:
The OpenLayers module is written so that there are frameworks in place to do things like your site - one could write behaviors that create the filters required, and there are views plugins that provide radius search capabilities. It's a route that requires serious Drupal familiarity, but is more sustainable - after behaviors are written, maps using them can be exported and included in features, and the same behaviors can be included on new maps without any coding. For one-off sites, your approach works well, and may be faster. However, as far as creating and maintaining module infrastructure, the goal is flexibility and sustainability over immediate feature-richness.
Thanks a lot for your
Thanks a lot for your respons. I have earlier ask'ed for help to understanding and writing my FIRST module using Google Maps API but no one wanted to help or maybe they don't have the time or maybe they can't figure out this too. My post can be seen here http://groups.drupal.org/node/79804