Don't reverse geocode coordinates before making a Directions request.

[lxbarth]

There's something janky going on when clicking to set origin / destination. I assume the code reverse geocodes a location and then updates the location returned? This leads to very weird behavior in areas where our geocoding locations are sparse:

[tristen]

The error is being compounded with this UI one in #36

[tristen]

This is a bit of a blunder on my end. The data that supports the geocoder doesn't have address data for South Korea. Because directions/geocoding data don't share parity (i.e this request always returns Seoul and not the address) I shouldn't be piping coordinates to the geocoder first and making a Directions request from the reverse geocoded result of origin and destination.

This is going to take some refactoring but its top priority for v1.1.0