opensoul.org - Graticule can failover Comments

Comment on 'Graticule can failover' by Eliot

2008-10-29T20:00:44Z

Hi Brandon, just want to say how great acts_as_geocodable and graticule are – the source has more or less taught me geocoding, which is just fantastic, so sincerely thank you.

I understand from the acts_as_geocodable page that contributions are welcome, so I’m making some minor changes I’m using on a project.

These changes will be on github in case they are of use to anyone else (at time of writing I’ve not committed these): http://github.com/eliotsykes/acts_as_geocodable_extra/tree/master

Comment on 'Graticule can failover' by Brandon

2008-03-04T04:08:12Z

nathan:

This is actually a limitation in ActiveRecord with using :select (which graticule uses to perform distance calculations) and :include in a find. I believe there are some workarounds somewhere, but I haven’t looked into them.

Comment on 'Graticule can failover' by nathan

2008-02-26T17:51:43Z

Ok so i modified Graticule gem by adding a new geocoder(http://plasmicpeach.com/articles/2007/09/12/uk-geocoding-with-google-and-graticule) so i can use UK google service. acts_as_geocode works fine with it but i’m trying to find a way to utilise :include with :origin and :order => distance. Duplex on railsforum suggested

 location = Location.find :all, :origin => postal_code,
                             :order => "distance asc",
                             :include => :listings, #eager-loading for performance
                             :conditions => "state = 'published'" 
    list = location.listings

but it cuases SQL errors about distance.

anyone got any ideas?

great plugin but unless i can find someway of using it with has_many belongs_to relationships then it’s not going to be suitable for my project.

cheers Nathan

Comment on 'Graticule can failover' by Andrew Selder

2007-10-19T19:13:50Z

Very nice.

I’d love to see MapQuest added as a geocoding service

Comment on 'Graticule can failover' by Matt King

2007-09-15T16:22:25Z

This is awesome! I’ll be updating the gem and trying it out on my development box. I was going to mention adding in precision checking but I see that’s already in there. :-)