Skip Menu |

This queue is for tickets about the Geo-Coder-OSM CPAN distribution.

Report information
The Basics
Id: 121692
Status: rejected
Priority: 0/
Queue: Geo-Coder-OSM

People
Owner: Nobody in particular
Requestors: NHORNE [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.03
Fixed in: (no value)



Subject: Can't get reverse_geocode to work
I can't see why this prints undef: #!/usr/bin/env perl use Geo::Coder::OSM; use Data::Dumper; my $geo = Geo::Coder::OSM->new(); my $location = $geo->reverse_geocode(latlng => '51.1278758,1.3134027'); print Data::Dumper->new([$location])->Dump();
Your test script works for me. If you're having issues, use the documented debug flag to narrow it down. Note this is an interface to a webservice, so if it's an issue on that end, nothing can be done. I did note some failures in the xt/live.t test script, but they were encoding issues and the mapquest source now fails without an api key, but that source is not used by default.
I've tried it at different locations and it always works for two or three times then stops with "The AppKey submitted with this request is invalid.". Looks like openstreetmap is no longer open. geocode.xyz seems to be better, so I'm going to play with that.
Ignore that - my mistake.
What is actually happening is this: curl 'http://nominatim.openstreetmap.org/?q=Wokingham,%20Berkshire,%20England&format=json&addressdetails=1&accept-language=en' gives this output [] from anywhere that I try. It works for 2 or 3 calls then does that. When you attempted to reproduce, did you only do it once, or try several times?
On Fri May 26 08:34:31 2017, NHORNE wrote: Show quoted text
> What is actually happening is this: > > curl > 'http://nominatim.openstreetmap.org/?q=Wokingham,%20Berkshire,%20England&format=json&addressdetails=1&accept- > language=en' > > gives this output > [] > > from anywhere that I try. It works for 2 or 3 calls then does that. > > When you attempted to reproduce, did you only do it once, or try > several times?
if you had tried that query on their website you're get the same result. if you want the issue fixed, file the bug report with the appropriate party.