Here’s my code:
results = Geocoding::get(params[:searchField])
if results.status == Geocoding::GEO_SUCCESS
coord = results[0].latlon
RAILS_DEFAULT_LOGGER.error(coord);

(email me and I’ll send more details)

Thanks,
Gary

PS. Complete RoR newbie.. So could easily be my mistake.

Also I want to make sure to say: I LOVE THIS PLUGIN! So a huge thank you.

Since you asked for input, the big problem for me is that eager loading (:include) doesn’t work. This is already talked about here:

http://jystewart.net/process/2007/03/select-and-include-in-activerecord-queries/

I’m a bit stumped how to get around the problem without going from one database query to possibly hundreds (and even then not very well). I think I might have to add duplicate lat/lng data to the model that my mappable model has_many of. However with my data I will get dupe parents, so I’ll need to select distinct (if that works with GeoKit) or just filter dupes on the app layer. Kind of a bummer about the dupe lat/lng data though (DRY).

Anyway, seems like a tricky problem. I’m trying to avoid monkey-patching Rails…

Thanks very much. FWIW, I opened a ticket on it a few minutes ago: http://err.lighthouseapp.com/projects/466/tickets/59-will_paginate-doesn-t-play-nicely-with-geokit

-Vince

I will have to look at it in more detail. I quickly inspected the Will Paginate code and on the surface, it seemed like it was playing with the finder options just like we are in GeoKit. In both cases, we add options to the finder, use them, and then strip them out seamlessly. I’ll have to create a test case to follow it exactly.

Bill


@places = Address.paginate :per_page => 10,
:page => params[:page],
:include => [:place], rigin => @location,
:conditions =>['distance