address front end problem of issue 920; geocoding in javascript

Tested on:

mac os x 10.9.2 mavericks in: 
* chrome 33.0.1750.152
* firefox 27.0.1
* safari 7.0.3 (9537.75.14)

Windows
* windows 8 chrome
* windows 7 chrome 33.0.1750.154
* windows 7 internet explorer 10.0.9200.16736

No errors in javascript consoles from any code added. Geolocation worked from 2 different cities.

Ran tests via manage.py 370 tests run, 52 skipped all OK, no failures.

The backend will still need to be updated as it contains the original reverse geocoding code. Issue 920 will still be reproducible if the geolocation database isn't found or if there is a location entered that is not recognized when run from a cloned repo. This code will continue working with the old backend as it is just passing one string through the post.