geocode-glib: Geocoding, reverse geocoding library
Quikee
quikee at gmail.com
Thu Apr 21 14:39:49 PDT 2011
On Thu, Apr 21, 2011 at 23:05, Bastien Nocera <hadess at hadess.net> wrote:
> Heya,
>
> Last night, I pushed the first version of geocode-glib, a simple helper
> API on top of Yahoo!'s Place Finder (the old Yahoo API in Geoclue is due
> to be switched off, or should have been for a little while).
>
> The current code is LGPLv2.1+, and there are probably some things to be
> sorted out with regards to API keys, etc.
>
> The current code uses json-glib, libsoup, and gvfs (for HTTP), though I
> can remove the gvfs requirement if MeeGo/KDE people are interested in
> the code.
>
> There's async and sync APIs, and I will be adding code to support
> Telepathy's own attributes (which don't quite match the Place Finder API
> attributes).
>
> Code:
> http://git.gnome.org/browse/geocode-glib
>
> Opinions, comments? Is somebody interested in working on a Nominatim
> backend? (does anybody know how well it works?)
>
> I would also be interested in ideas on how to export the bounding boxes
> for matches.
>
> Cheers
>
> _______________________________________________
> GeoClue mailing list
> GeoClue at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/geoclue
>
Hi,
I was already making a library that does various geo-services like
routing, POI and other geo-information (pictures, wikipedia). I also
experimented with geocoding/reverse geocoding using Nominatim and
GeoNames. I was wondering if we could combine all this and make a
general library for geo-services for example called
"geoclue-services". I will try to put the my code up during the
weekend and then we can see what can be done with this. I am using
Vala for this - using C is to verbose for such things.
So what do you think?
Regards, Tomaž
More information about the GeoClue
mailing list