Bug 40882 - geonames backend doesn't work anymore due to service changes
Summary: geonames backend doesn't work anymore due to service changes
Status: RESOLVED WONTFIX
Alias: None
Product: GeoClue
Classification: Unclassified
Component: Backends (obsolete) (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Geoclue Bugs
QA Contact: Geoclue Bugs
URL:
Whiteboard:
Keywords:
: 45004 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-09-14 08:49 UTC by Laurent Bigonville
Modified: 2012-02-22 11:13 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Laurent Bigonville 2011-09-14 08:49:24 UTC
Hi,

It seems that the geonames backend is not working anymore. When using it, the server is answering me:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<geonames>
<status message="the deprecated ws.geonames.org servers are currently overloaded with requests please use the api.geonames.org domain." value="22"/>
</geonames>


Recompiling the backend to update the hostname, I get:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<geonames>
<status message="Please add a username to each call in order for geonames to be able to identify the calling application and count the credits usage." value="10"/>
</geonames>


The backend call this URL on the server:

GET /findNearby?lat=-51&lng=4.2000000000000002&featureCode=PPL&featureCode=PPLA&featureCode=PPLC&featureCode=PPLG&featureCode=PPLL&featureCode=PPLR&featureCode=PPLS&maxRows=1&style=FULL HTTP/1.0
Comment 1 Javier Jardón 2012-02-22 10:55:10 UTC
You can use geocode-glib to access this service (Its already using the new
Placefinder API). The plan is to remove geocoding and reverse geocoding from
geoclue:
https://mail.gnome.org/archives/desktop-devel-list/2011-May/msg00072.html

http://git.gnome.org/browse/geocode-glib
Comment 2 Bastien Nocera 2012-02-22 11:13:17 UTC
*** Bug 45004 has been marked as a duplicate of this bug. ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.