See: https://github.com/alexreisner/geocoder/issues/703

Update so opencagedata will return coordinates.

In the current opencagedata api, latitude and longitude are stored under geometry: {lat: ..., lng: ...}

Allow language to be set in geocoded_by as proc

Refactor SQL statement to prevent table join

Smartystreets is no longer free for non-profits

This should have been part of commit 47e11a41.

Get rid of extraneous "q=" in request query string.

Opencagedata: additional tests

add alternate attributes options for near_scope_options

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

Add opencagedata geocoder, incl tests and fixtures

Add support for Pointp.in ip geolocation

Allow lookup service to fully opt-out of https

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.

json coming from geocodio has changed from floats to strings

Fix CHANGELOG.md formatting

This fix adds formatting to match the other version headers.  They were previously plain text.

Date typo in changelog