Thanks for your help.
I found a link to Python, PHP, and Pascal code to do this. Looks like I have to 
stop being lazy and do some math. I’m ok with converting the code to xTalk. I 
should be able to figure it out myself. I’ll share when I get something done. 
It may be a bit because I’ve got some other tasks pulling at me.


Best wishes and thanks again for helping me in this search,
Bill P

> On Apr 28, 2017, at 5:23 PM, Mike Bonner via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> I'll poke around more. Maybe I'll get lucky (boatloads of no in that
> phrase) and find a solution.
> On Fri, Apr 28, 2017 at 5:55 PM, William Prothero via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>> Ok, its a bit more complicated. After my initial high at thinking the
>> problem was solved (rushing to a haircut appointment before looking
>> carefully), I noticed that the returned data from Mike’s reverse geocoding
>> URL didn’t change with the zoom level. So apparently, it’s only applied to
>> the stated location. The reverse geo lookup finds a city or address and the
>> “bounds” elements don’t give the lat/lon values at the corner of the image.
>> I’m fiddling with this, and I’ve got the link (somewhat incomplete
>> derivation) of how to calculate the corner lat/lons, so I’ll try that next.
>> I wish there was a google call I could make that would give me this info,
>> but I can’t find it.
>> Best,
>> Bill

use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription 

Reply via email to