This isn't an answer to your question, but... you might end up finding
working with the Google reverse geocoder and Refine a pain as its data
structure isn't particularly conducive in some ways to pulling out the
data.
Say you wanted to turn a lat,long into a nearest city name, you'll
have to iterate through its address_components and compare on types.
At least as far as I'm able with Refine, that's much more work than
say, parseJson(cells['address resources'].value)[0]['address']
Bing & Yahoo have a more Refine-friendly results structure, but you'll
have to sign up for an API key (about five minutes' work)
YMMV!
Paul
> This isn't an answer to your question, but... you might end up finding
> working with the Google reverse geocoder and Refine a pain as its data
> structure isn't particularly conducive in some ways to pulling out the
> data.
You probably also want to review the Terms of Service for the Google
Geocoder API, particularly the part about only using the results in
conjunction with displaying a location on a Google Map, and not saving
them.
Tom