Frontend Geocoder Failover Infinite Loop

[jmfield2]

For a limited degree of failover, we define two geocoder URLs in the config.js (one matches the current hostname (maps), and the last is hard-coded as mobullity. On error, the geocoder will find the "next" URL in the list and try that one. This seemed to work OK, but on mobullity, that means if the mobullity geocoder has an error, the failover loop will never end and continuously hit the mobullity geocoder endpoint until the browser is closed before looking for the mobullity URL will always return the "next" value to try.

One solution that I worked on is to use index values - starting at 0 - and incrementing on error until it reaches the end of the list (currently 2). I also added an alert message if it reaches the end so that the user can be aware of a problem instead of waiting indefinitely for results that would never come.