Hi, i just realized that we are talking about completely different things when we say "geotagged". I am relating to GPS positions. You seem to relate to place names. I just learned that the n900 does not write GPS tags. Correct?
Unfortunately that completely spoils the idea to use maep to display these. Converting GPS positions into place names and back to coordinates will likely cause most images to show up pretty far from their real location and even worse will make them all show up at the same place. Is there a way to enable real GPS tagging? Is there any reason why this isn't happending? It's so obvious that just i didn't expect this not to be there. Till Am Montag 11 Januar 2010 schrieb Ivan Frade: > Hi, > > El vie, 08-01-2010 a las 20:45 +0100, ext Till Harbaum / Lists escribió: > > Hi, > > > > Am Freitag 08 Januar 2010 schrieb Ivan Frade: > > > > see it when i arrive there). This will be supported in tracker 0.7 > > > (ready to play with on desktop), but not in 0.6/fremantle. > > Using tracker 0.6 limited to images is a start. Do you have example > > code somewhere? I have never worked with tracker before. > > We have some (basic) documentation here: > http://live.gnome.org/Tracker/Documentation/RDF-Query > > Tracker is a daemon visible in DBus. In python, connect to the daemon > directly (an example in my own pet-project [1]). In C, use > libtracker-client (some examples in MAFW's tracker backend). > > There should be some libtracker-client gtk-doc documentation, but it > looks like library.gnome.org only contains the last unstable version > (0.7). This is useless for you, the API in 0.7 is _completely_ different > from 0.6 API. Don't get confused with that. > > The properties you can use in your queries are defined here: > http://git.gnome.org/browse/tracker/tree/data/services?h=tracker-0.6 > > You can also monitor dbus while using the image-viewer to see some > queries flying. > > Regards, > > Ivan > > [1] > https://garage.maemo.org/plugins/ggit/browse.php/?p=mussorgsky;a=blob;f=src/tracker_backend.py;h=e956f38668066423fa9538a1cb69a4082f776fa8;hb=9d71d07b572bdf50114484b28a0e188d742fcdfc > > > _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
