> > > GPS data is stored in tracker for images only. Till wants GPS data > > > for > > > *all* file types. > > > I really REALLY think tracker is the only useful way to deal with > > geotags especially in a mobile device where indexing may really be > > expensive with respect to CPU power and battery. > > We have two problems: > 1) Who set the location information? Responsibility of applications. > 2) Where should that information be stored? In tracker. > > but ... > 1) No application is really setting location information > except the image viewer (and only for images) > 2) Tracker 0.6 cannot store efficiently that information. We > could try to add a File:Location property, so you could set > location for everything known by tracker, but it is going to > be very very inefficient. This will be fixed in 0.7 .
It would be preferable to also store the lat/lon information so that applications could use that if they see fit (e.g. map apps) as well as the pre-reverse geocoded location name, otherwise there's additional overhead and severe inaccuracy of the geocoding. >From a quick websearch I can see that video can and is geocoded at least (either once uploaded, or for e.g. some Sony camcorder with a built-in GPS), so adding support for geocoded videos would be nice. I can also envision other files adding geocoding metadata about themselves to the tracker database, even if the file itself doesn't support internal geocoding metadata (is that possible, I guess it should be?) so adding a geotag field (or fields I hope for name and lat/lon) would be a nice, cool and future proof thing to do (but yeah it will waste some space for files that don't use it, but probably not much, though I've not looked at the db so I don't know for sure). Anyway I think it's a shame we don't make more use of our geo-information and the ability to enable it in general on the N900 - the IM app doesn't report actual location data which is a real shame (and hence my interest in using Google's Latitude instead), contacts can contain addresses but not more accurate lat/lon, etc. Cheers, Simon _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
