Re: [web2py] geocode() return value

2013-10-09 Thread Manuele Pesenti
Il 24/09/13 15:44, Ricardo Cárdenas ha scritto: > Hi Manuele, > > Thanks for your email. (0,0) in effect represents two possible > outcomes: "/I could not geocode this address/" and also "/please try > again later/". How can I know if it makes sense to retry later? > > best regards -Ricardo Hi Rica

Re: [web2py] geocode() return value

2013-09-25 Thread Manuele Pesenti
Il 24/09/13 15:44, Ricardo Cárdenas ha scritto: > Hi Manuele, > > Thanks for your email. (0,0) in effect represents two possible > outcomes: "/I could not geocode this address/" and also "/please try > again later/". How can I know if it makes sense to retry later? > good quest... another solution

Re: [web2py] geocode() return value

2013-09-24 Thread Ricardo Cárdenas
Hi Manuele, Thanks for your email. (0,0) in effect represents two possible outcomes: "*I could not geocode this address*" and also "*please try again later*". How can I know if it makes sense to retry later? best regards -Ricardo On Tuesday, September 24, 2013 8:26:38 AM UTC-5, Manuele wrote

Re: [web2py] geocode() return value

2013-09-24 Thread Manuele Pesenti
Il 24/09/13 15:13, Ricardo Cárdenas ha scritto: > The gluon.tools geocode() function is great. > > A minor suggestion. Right now it returns (0,0) on any execption. It > would be nice if the function distinguished between /unable to geocode > this address/ and other problems (such as quota reached).

[web2py] geocode() return value

2013-09-24 Thread Ricardo Cárdenas
Hi, The gluon.tools geocode() function is great. A minor suggestion. Right now it returns (0,0) on any execption. It would be nice if the function distinguished between *unable to geocode this address* and other problems (such as quota reached). Use case: I geocode addresses as they come in a