Gem History
=== 1.5.0 / 2009-09-21
- fixed jruby compatibility (thanks manalang)
- added country name to Google reverse geocoder (thanks joahking)
- added DependentLocalityName as district, and SubAdministrativeAreaName as province (google geocoder only)
- Google geocoder throws an error if you exceed geocoding rates (thanks drogus)
=== 1.4.1 / 2009-06-15
- Fixed Ruby 1.9.1 compat and load order (thanks Niels Ganser)
=== 1.4.0 / 2009-05-27
- Added country code/viewport biasing to GoogleGeocoder. Added Bounds#to_span method
- Added suggested_bounds (Geokit::Bounds) property to GeoLoc. (Google geocoder only)
- Added LatLng#reverse_geocode convenience method (thanks Tisho Georgiev for all three)
=== 1.3.2 / 2009-05-27
- Fixed blank address geocoding bug
=== 1.3.1 / 2009-05-21
- Support for External geocoders file (thanks dreamcat4)
- Support multiple ip geocoders, including new setting for ipproviderorder (thanks dreamcat4)
=== 1.3.0 / 2009-04-11
- Added capability to define multiple API keys for different domains that may be pointing to the same application (thanks Glenn Powell)
- Added numeric accuracy accessor for Yahoo and Google geocoders (thanks Andrew Fecheyr Lippens)
- Implement #hash and #eql? on LatLng to allow for using it as a hash key (thanks Luke Melia and Ross Kaffenberger) *
=== 1.2.6 / 2009-03-19
- misc minor fixes
=== 1.2.5 / 2009-02-25
- fixed GeoLoc.to_yaml
- fixed minor google geocoding bug
- now periodically publishing the Geokit gem to Rubyforge. Still maintaining development and managing contributions at Github
=== 1.2.4 / 2009-02-25
- Improved Google geocoder in the Gem: Support for multiple geocoding results from the Google geocoder. (thanks github/pic)
=== 1.2.3 / 2009-02-01
- Adding GeoPluginGeocoder for IP geocoding (thanks github/xjunior)
- Ruby 1.9.1 compatibility and Unicode fixes (thanks github/Nielsomat)
- various bug fixes
=== 1.2.1 / 2009-01-05
- minor bug fixes
- reverse geocoding added (Google only): res=Geokit::Geocoders::GoogleGeocoder.reverse_geocode "37.791821,-122.394679"
- nautical miles added (in addition to miles and KM)
=== 1.2.0 / 2008-12-01
- Improved Geocoder.us support -- respects authentication, and can geocode city names or zipcodes alone
- cross-meridian finds work correctly with bounds conditions
- fixed a problem with columns with "distance" in their name
- added Geonames geocoder
- the gem and plugin are now hosted at Github.
=== 1.1.1 / 2008-01-20
- fixes for distance calculation (in-memory and database) when distances are either very small or 0.
- NOTE: older versions of MySQL/Postgres may not work. See readme for more info.
=== 1.1.0 / 2007-12-07
- Geokit is now Rails 2.0 / Edge friendly.
=== 1.0.0 / 2007-07-22
- see http://earthcode.com/blog/2007/07/newgeokitrelease.html
- auto geocoding: an option to automatically geocode a model's address field on create
- in-memory sort-by-distance for arrays of location objects
- bounding box queries:
Location.find :all, :bounds=>[sw,ne] - improved performance by automatically adding a bounding box condition to radial queries
- new Bounds class for in-memory bounds-related operations
- ability to calculate heading and midpoint between two points
- ability to calculate endpoint given a point, heading, and distance
Plugin History
== 2009-10-02 / Version 1.2.0
- Overhaul the test suite to be independent of a Rails project
- Added concept of database adapter. Ported mysql/postgresql conditional code to their own adapter.
- Added SQL Server support. THANKS http://github.com/brennandunn for all the improvements in this release
== 2009-09-26 / Version 1.1.3
- documentation updates and updated to work with Geokit gem v1.5.0
- IMPORTANT: in the Geokit gem, Geokit::Geocoders::timeout became Geokit::Geocoders::request_timeout for jruby compatibility. The plugin sets this in config/initializers/geokit_config.rb. So if you've upgraded the gem to 1.5.0, you need to make the change manually from Geokit::Geocoders::timeout to Geokit::Geocoders::requesttimeout in config/initializers/geokitconfig.rb
== 2009-06-08 / Version 1.1.2
- Added support for hashes in :through. So you can do: acts_as_mappable :through => { :state => :country } (Thanks José Valim).
== 2009-05-22 / Version 1.1.1
- Support for multiple ip geocoders (Thanks dreamcat4)
- Now checks if either :origin OR :bounds is passed, and proceeds with geokit query if this is true (Thanks Glenn Powell)
- Raises a helpful error if someone uses through but the association does not exists or was not defined yet (Thanks José Valim)
== 2009-04-11 / Version 1.1.0
- Fixed :through usages so that the through model is only included in the query if there is an :origin passed in (Only if it is a geokit search) (Thanks Glenn Powell)
- Move library initialisation into lib/geokit-rails. init.rb uses lib/geokit-rails now (thanks Alban Peignier)
- Handle the case where a user passes a hash to the :conditions Finder option (thanks Adam Greene)
- Added ability to specify domain-specific API keys (Thanks Glenn Powell)
== 2009-02-20
- More powerful assosciations in the Rails Plugin:You can now specify a model as mappable "through" an associated model. In other words, that associated model is the actual mappable model with "lat" and "lng" attributes, but this "through" model can still utilize all Geokit's "find by distance" finders. Also Rails 2.3 compatibility (thanks github/glennpow)
== 2008-12-18
- Split Rails plugin from geocoder gem
- updated for Rails 2.2.2
== 2008-08-20
- Further fix of distance calculation, this time in SQL. Now uses least() function, which is available in MySQL version 3.22.5+ and postgres versions 8.1+
== 2008-01-16
- fixed the "zero-distance" bug (calculating between two points that are the same)
== 2007-11-12
- fixed a small but with queries crossing meridian, and also fixed find(:closest)
== 2007-10-11
- Fixed Rails2/Edge compatability
