- Nov 30, 2018
-
-
Andrew Kane authored
-
- Sep 11, 2018
-
-
Ignatius Reza authored
-
- Sep 08, 2018
-
-
Anders Eriksson authored
-
Anders Eriksson authored
-
- Jul 27, 2018
-
-
Alex Reisner authored
-
ip2location authored
-
ip2location authored
-
Alex Reisner authored
-
- Jun 18, 2018
-
-
Alex Reisner authored
Appears to be defunct.
-
- Jun 17, 2018
-
-
Alex Reisner authored
No longer seems to exist.
-
- May 14, 2018
-
-
Heath Attig authored
* Update initializer template to use ipinfo_io * Implement ipstack lookup * Add Ipstack readme documentation * Add post-install message * Remove DSL from ipstack lookup * Remove unnecessary logging * Update post-install message
-
- Apr 10, 2018
-
-
Scott Wenborne authored
-
- Apr 04, 2018
-
-
David authored
-
- Mar 13, 2018
-
-
Jordan Moncharmont authored
some google geocoding requests have bounds within the result. add a helper to extract these. * Add tests to cover results with no bounds In this case, calling .bounds should return nil. Oddly, calling viewport on a result with no viewport causes the current code to `fail`. I have preserved this behavior even though I think it to be a little odd.
-
- Jan 16, 2018
-
-
German Velasco authored
Bing returns the status codes within the json response. When a request is forbidden, it will return a 403. If there is an internal server error, it will return a 500. And if the service is unavailable for some other reason, it will return a 503. That information was obtained from bing's [Status Codes and Error Handling](https://msdn.microsoft.com/en-us/library/ff701703.aspx) documentation. We handle those three status codes here to raise `Geocoder::RequestDenied` (for 403) and `Geocoder::ServiceUnavailable` (for 500 and 503). This allows for the users of the Geocoder to handle those errors in their applications.
-
- Jan 10, 2018
-
-
Robert Schaefer authored
Remove silly check for HTML tags Add test case for invalid json
-
Robert Schaefer authored
-
- Nov 17, 2017
-
-
Carlos Villela authored
* Handle Geocoder::OverQueryLimitError gracefully. Geocoder::OverQueryLimitError errors were not being generated correctly, and the response was coming back empty but with no indication. This changes the behavior slightly so that unknown errors are also returned. * Add error handling tests * Remove unnecessary config in tests
-
- Sep 25, 2017
-
-
Carlos Villela authored
* Add support for DB-IP.com geocoding service * Added support for https with paid accounts * Use `use_https` to distinguish between paid/unpaid API usage * Clean rubocop warnings
-
Srihari Thalla authored
* Update LocationIQ geocoding provider with limits and handle errors * Correct syntax errors * Update over limit fixture * Set HTTPS as the assertion for the URL * Add missing fixtures for unit tests * Correct the mistakes in doc * Let users decide SSL usage * Revert incorrectly asserted URL without https * Remove use_ssl from lookup subclass * Update the assertion of the URL to HTTP and not HTTPS
-
- Jun 28, 2017
-
-
Vladimir Kalinkin authored
-
Yuri Veremeyenko authored
-
- May 04, 2017
-
-
vyrak bunleang authored
-
- Apr 25, 2017
-
-
http://lbs.amap.comLeon Guan authored
* Added support for AMap, aka AutoNavi Map, 高德地图 * Try to include amap error info if failed * Get correct result from amap response * Fix result error in amap return * Refactor codes for AMap handling * Refactor codes for amap result handling * Refactor amap handling codes * Fixed coordinates handling error * Added tests * Fixded amap result handling and tests * Lock webmock on 2.3.2 for ruby 1.9.3 support
-
- Feb 25, 2017
-
-
Roy Lee authored
Update smarty streets results coordinates method to return nil when both latitude and longitude do not exist
-
- Jan 31, 2017
-
-
Taufiq Muhammadi authored
-
- Dec 09, 2016
-
-
Dzmitry authored
In the sea for example [Fix #1131]
-
- Nov 30, 2016
-
-
Julian Nacci authored
add new lookup to lookup.rb add new lookup file ban_data_gouv_fr.rb add new results file ban_data_gouv_fr.rb update README with new lookup create fixtures to test new lookup create unit test file for new lookup update test helper default fixture for new lookup remove invalid multibyte char (US-ASCII) 'ç' from lookup name Revert "remove invalid multibyte char (US-ASCII) 'ç' from lookup name" This reverts commit 7dbfcab4dc4bcb9473edc43651e7d53884f0e24d. Add '# encoding: utf-8' to files containing special chars Add '# encoding: utf-8' to files containing special chars Add '# encoding: utf-8' to files containing special chars remove useless Geocoder.config from test methods refacto of ban lookup results method change city serach param to fit naming conventions in ban lookup test renamed no results ban lookup fixture to fit tests removed no search results unnecessary test remove useless commented code add alias method to handle state and state_code + move from department to region name as state refacto results method
-
- Nov 15, 2016
-
-
sputnik82 authored
-
- Sep 09, 2016
-
-
aleem uddin authored
LocationIq # for classes location_iq # for config
-
- Sep 05, 2016
-
-
Ryan Boland authored
-
Ryan Boland authored
-
- Aug 31, 2016
-
-
Greg Signal 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
-
- Apr 12, 2016
-
-
Alex Reisner authored
-
- Apr 04, 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
-
- Mar 15, 2016
-
-
Gil Raphaelli and Nic Cavigliano authored
-
- Mar 12, 2016
-
-
unit authored
-
- Mar 07, 2016
-
-
Evan Marks authored
-
- Feb 20, 2016
-
-
Galia authored
The Yahoo BOSS Placefinder API is being discontinued. https://developer.yahoo.com/boss/placefinder/
-