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 <[email protected]>wrote: > 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 queries I tested. > > > > Anyway here is how it can be reproduced: > > > > MAPQUEST: > > session = OGRGeocodeCreateSession({"SERVICE=MAPQUEST_NOMINATIM"}); > > layer = OGRGeocode(session, "london", null, null); > > > > -> only first feature in layer has geometry > > > > > > > > GEONAMES: > > session = OGRGeocodeCreateSession({"SERVICE=GEONAMES", "USERNAME=demo"}); > > layer = OGRGeocode(session, "london", null, null); > > > > -> only first feature in layer has geometry > > > > > > > > BING: > > session = OGRGeocodeCreateSession({"SERVICE=BING", "KEY=BingMapsKey"}); > > layer = OGRGeocode(session, "london", null, null); > > > > -> layer is null and CPLGetLastErrorType does not report any error > > > > I've created http://trac.osgeo.org/gdal/ticket/5057. > > Issue confirmed (and fixed) for OSM_NOMINATIM, MAPQUEST_NOMINATIM and > GEONAMES. > But for BING, I get a non-NULL layer with my trial key... My hypothesis is > that your key is wrong ? > >
_______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
