Documentation and/or consistency issue

Hi @alexreisner,

first off: thank you, amazing work 💯

I'm a little confused by the following:

1. Using Geocoder.search leads to @data containing "lat" and "lon".
2. The documentation suggests stubbing "coordinates".
3. When using Model.geocode, it is expected that the coordinates are present within @data in "latitude" and "longitude"

My questions:

• Is there a reason for this deviation?
• Is stubbing coordinates maybe deprecated?
• What are the arguments against either using the short form (lat) or the long form (latitude) consistently?

Cheers,

Finn

Start with the README testing section and lib/geocoder/results/base.rb, then compare the documented coordinates stub with the lat/lon data returned by Geocoder.search and the latitude/longitude expectations of Model.geocode. Done means the project has a decided, consistent convention and documentation for these coordinate keys.