Re: [gdal-dev] 1.10 Issues with Geocing API and OSM Driver

2013-04-18 Thread Dennis Gocke
Great work Even. Yes, you are right with the BING service. I did not use the correct key. But perhaps it would be good to have some kind of error message in this case. Cheers, Dennis On Thu, Apr 18, 2013 at 9:19 PM, Even Rouault wrote: > Le jeudi 18 avril 2013 16:04:50, Dennis Gocke a écrit :

Re: [gdal-dev] 1.10 Issues with Geocing API and OSM Driver

2013-04-18 Thread Even Rouault
Le jeudi 18 avril 2013 16:04:50, Dennis Gocke a écrit : > Thanks for the information Even. > > I have created two tickets related to the OSM Driver issues. > > > Regarding the problems with the geocoding services. > It isn't really query dependant. A specific service behaves the same for > all q

Re: [gdal-dev] 1.10 Issues with Geocing API and OSM Driver

2013-04-18 Thread Dennis Gocke
Thanks for the information Even. I have created two tickets related to the OSM Driver issues. Regarding the problems with the geocoding services. It isn't really query dependant. A specific service behaves the same for all queries I tested. Anyway here is how it can be reproduced: MAPQUEST: se

Re: [gdal-dev] 1.10 Issues with Geocing API and OSM Driver

2013-04-18 Thread Even Rouault
Selon Dennis Gocke : > Hi, > > I’ve encountered some issues. My tests are done with the latest 1.10 > version. > > The first issue is related to the new Geocoding API. Great work btw. > > When using the MAPQUEST_NOMINATIM or GEONAMES service only the first > feature in the resulting layer gets a g

[gdal-dev] 1.10 Issues with Geocing API and OSM Driver

2013-04-18 Thread Dennis Gocke
Hi, I’ve encountered some issues. My tests are done with the latest 1.10 version. The first issue is related to the new Geocoding API. Great work btw. When using the MAPQUEST_NOMINATIM or GEONAMES service only the first feature in the resulting layer gets a geometry. The other features only repo