From 0b6c6e1add6a5094f5ef866e54cad1e3f2e67623 Mon Sep 17 00:00:00 2001
From: Christopher Manning <c@christophermanning.org>
Date: Sat, 19 Nov 2011 12:50:15 -0600
Subject: [PATCH] Change lat and lon configurations in README to latitude and
longitude so it matches the gem's defaults and the generate migration
instructions
---
README.rdoc | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/README.rdoc b/README.rdoc
index 0280f482..883788e5 100644
--- a/README.rdoc
+++ b/README.rdoc
@@ -50,7 +50,7 @@ Next, your model must tell Geocoder which method returns your object's geocodabl
For reverse geocoding, tell Geocoder which attributes store latitude and longitude:
- reverse_geocoded_by :lat, :lon
+ reverse_geocoded_by :latitude, :longitude
after_validation :reverse_geocode # auto-fetch address
=== Mongoid
@@ -190,7 +190,7 @@ If your model has +street+, +city+, +state+, and +country+ attributes you might
For reverse geocoding you can also specify an alternate name attribute where the address will be stored, for example:
- reverse_geocoded_by :lat, :lon, :address => :location # ActiveRecord
+ reverse_geocoded_by :latitude, :longitude, :address => :location # ActiveRecord
reverse_geocoded_by :coordinates, :address => :loc # MongoDB
@@ -198,7 +198,7 @@ For reverse geocoding you can also specify an alternate name attribute where the
So far we have looked at shortcuts for assigning geocoding results to object attributes. However, if you need to do something fancy you can skip the auto-assignment by providing a block (takes the object to be geocoded and an array of <tt>Geocoder::Result</tt> objects) in which you handle the parsed geocoding result any way you like, for example:
- reverse_geocoded_by :lat, :lon do |obj,results|
+ reverse_geocoded_by :latitude, :longitude do |obj,results|
if geo = results.first
obj.city = geo.city
obj.zipcode = geo.postal_code
--
GitLab