My Professional Blog

Comment by Bill Eisenhauer

July 9, 2007 @ 4:24 am

Hey There,

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

Comment by vince

July 9, 2007 @ 10:26 am

Hi Bill,

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

Comment by carlivar

July 23, 2007 @ 11:35 pm

First just FYI per last comment, I am using the latest GeoKit successfully with the latest will_paginate.

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…

Comment by Evgeny

September 26, 2007 @ 9:44 am

Are you using PostgreSQL geometry functions if those are available?
Like I have a method in my cities model that finds by radius, and is using PostgreSQL for that. See here : http://pastie.caboo.se/pastes/101087

Comment by Bill Eisenhauer

September 26, 2007 @ 10:15 am

Nope, not using those functions. We are using primitive trig functions that are common to both MySQL and Postres.

Comment by Gary P

October 2, 2007 @ 4:51 pm

Just starting on a site using GeoKit and I noticed an “oddity” about an address.. When using the Google Maps web site I get one set of Long/Lat but using GeoKit (thru Google Maps) I get a different set (slightly off by about 1/4 mile). For instance google gives: -71.119759 while Geokit gives: -71.124938

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.

Comment by Bill Eisenhauer

October 2, 2007 @ 5:43 pm

My guess is that Google Maps does not geocode exactly the same as the Google Geocoder. I haven’t heard any similar complaints, so I wouldn’t be too worried.

Comment by John Bachir

June 27, 2007 @ 10:17 am

Great to hear. GeoKit is an amazing tool. Do these changes comprise an upcoming release?

Comment by vince

July 8, 2007 @ 12:24 pm

Howdy Bill,
I’m having some issues using geokit with the will_paginate plugin (pagination is being yanked out of rails 2.0) Do you have any suggestions on how to get geokit to play nice with pagination calls? Currently, with will_paginate, I get an Unknown key(s): origin when doing my finds.


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