- Sep 09, 2016
-
-
aleem uddin authored
LocationIq # for classes location_iq # for config
-
- Sep 08, 2016
-
-
Alex Reisner authored
-
Alex Reisner authored
No escaping should be necessary, according to the MaxMind docs: http://dev.maxmind.com/geoip/geoip2/web-services/
-
- Sep 06, 2016
-
-
Ryan Boland authored
-
- Sep 05, 2016
-
-
Ryan Boland authored
-
Ryan Boland authored
-
toydi authored
-
toydi authored
-
- Aug 31, 2016
-
-
Greg Signal authored
-
- Aug 25, 2016
-
-
aleem uddin authored
-
- Aug 19, 2016
-
-
Will Jordan authored
-
- Jul 27, 2016
-
-
Paul Cantrell authored
In Rails 5, `rake geocode:all` crashes: ``` $ rake geocode:all CLASS=Whatzit rake aborted! ArgumentError: comparison of Fixnum with nil failed /Users/paul/.rvm/gems/ruby-2.2.2/gems/activerecord-5.0.0/lib/active_record/relation/batches.rb:217:in `<' /Users/paul/.rvm/gems/ruby-2.2.2/gems/activerecord-5.0.0/lib/active_record/relation/batches.rb:217:in `block in in_batches' /Users/paul/.rvm/gems/ruby-2.2.2/gems/activerecord-5.0.0/lib/active_record/relation/batches.rb:198:in `loop' /Users/paul/.rvm/gems/ruby-2.2.2/gems/activerecord-5.0.0/lib/active_record/relation/batches.rb:198:in `in_batches' /Users/paul/.rvm/gems/ruby-2.2.2/gems/activerecord-5.0.0/lib/active_record/relation/batches.rb:120:in `find_in_batches' /Users/paul/.rvm/gems/ruby-2.2.2/gems/activerecord-5.0.0/lib/active_record/relation/batches.rb:58:in `find_each' /Users/paul/.rvm/gems/ruby-2.2.2/gems/geocoder-1.2.2/lib/tasks/geocoder.rake:11:in `block (2 levels) in <top (required)>' /Users/paul/.rvm/gems/ruby-2.2.2/gems/rake-11.2.2/exe/rake:27:in `<top (required)>' /Users/paul/.rvm/gems/ruby-2.2.2/bin/ruby_executable_hooks:15:in `eval' /Users/paul/.rvm/gems/ruby-2.2.2/bin/ruby_executable_hooks:15:in `<main>' Tasks: TOP => geocode:all (See full trace by running task with --trace) ``` The problem seems to be that `find_each` used to default the `batch:` param when it was explicitly set to nil, but now passes an explicit nil on through. This patch fixes the issue by defaulting the batch size in the rake task.
-
- Jun 27, 2016
-
-
Steve Jorgensen authored
-
Steve Jorgensen authored
-
Steve Jorgensen authored
-
- Jun 26, 2016
-
-
Steve Jorgensen authored
-
- Jun 09, 2016
-
-
Alex Reisner authored
-
Eric Bouchut authored
Was causing: NoMethodError: private method `include' called for ActionDispatch::Request:Class
-
- Jun 07, 2016
-
-
Hassanin Ahmed authored
* handles unreachable network exception * adds network error class * tests unreachable host exception handling
-
- Jun 02, 2016
-
-
Jeffects authored
SmartyStreets is permanently changing their ZIP Code API endpoint by June 22 at 9am Mountain Time. The legacy API endpoint is available until the 22nd. This change basically changes the API endpoint and updated the tests to reflect the change.
-
- May 31, 2016
-
-
Alex Reisner authored
-
Alessandro Lepore authored
-
- May 27, 2016
-
-
Alex Reisner authored
-
- May 26, 2016
-
-
Alex Reisner authored
Intended to fix #1048.
-
- May 25, 2016
-
-
Aaron Parecki authored
-
Alex Reisner authored
ESRI lookup now uses this method.
-
Alex Reisner authored
-
Aaron Parecki authored
-
Alex Reisner authored
This should improve readability and make testing easier as it separates the various tasks into separate methods.
-
Alex Reisner authored
-
- May 24, 2016
-
-
Shinya Kitamura authored
-
- May 20, 2016
-
-
Alessandro Lepore authored
-
- May 17, 2016
-
-
Aaron Parecki authored
-
- May 06, 2016
-
-
jlhonora authored
-
Jason Waldrip authored
* Support for a custom telize endpoint * fix path
-
- May 02, 2016
-
-
jlhonora authored
-
- Apr 28, 2016
-
-
Han Loong Liauw authored
-
- Apr 17, 2016
-
-
Alex Reisner authored
The #latitude and #longitude methods are defined in the Base lookup. The intention is that subclasses implement #coordinates only, as it results in less code duplication.
-
Alex Reisner authored
-
- Apr 16, 2016
-
-
Piotr Górecki authored
* Add ip-api.com (ip lookup) support This service returns better coordinates for Europe than other free ip lookup services available in geocoder. * Clean the results class Remove default responses for fields. * Remove checking fields in url query API already handles unknown fields, so this check is unnecessary. * Add a test for using parameters directly in search method * Use proper domain name Use pro.ip-api.com domain in case when api key is in use, otherwise just ip-api.com. * Handle invalid api key * Add forsaken fixture * Make uniform an invalid key handler with the other geocoder lookups
-