Test suite failed because railtie wasn't loaded (because
Rails/ActiveRecord are stubbed out in test env). This initializes
it explicitly in test_helper before any models get defined

GeoLite2 is a free version of a product called GeoIP2. Both use the same
format.

Handle responses that only have one component in the Location field, assume this is a county and so return blank city

Add PostcodeAnywhere API error handling; Map key limit exceeded, invalid key to Geocode errors and call all others as just Error

This should have been part of commit 47e11a41.

No longer documented. Removing to avoid confusion.
See: http://notes.ericjiang.com/posts/741

If you have an address geocoding service that you want to use HTTPS with
and then attempt to use an ip_geocoder that does not support HTTPS (e.g.
Telize) then the ip_geocoder lookups will fail because
Geocoder::Lookups::Base#make_api_request turns on opts[:use_ssl] based
on that single configuration value.

Rather than allowing for per-provider HTTPS configuration I have just
refactored Geocoder::Lookups::Base call a private `use_ssl?` method
which can be overridden by individual lookup provider implementations.
The default implementation of `use_ssl?` simply returns the value from
the config thus preserving the existing behavior but this allows
subclasses, like Telize, to override `use_ssl?` completely to return
false and thus fully opt-out of HTTPS regardless of what the
configuration was.

Use correct fixtures in tests and make required changes so tests pass.