Thanks for the reminder about that issue. Given that: 1) the search pkg already supports looking for a location, and that it looks for either a permanode based location, or a file based location 2) there currently is no way for a user to effectively set a location on a permanode (because the indexer will ignore it)
then I think the most urgent item is to let a user set a (GPS coordinates) location on a permanode as simply as possible, isn't it? I may be missing a point that was made in https://github.com/camlistore/camlistore/issues/778 against, and if so, please point me to it. Attila, if you agree with the above, do you think https://camlistore-review.googlesource.com/6456 could become the implementation for it? In any case, I'll have another look at it tonight. On 24 July 2016 at 22:49, Attila Tajti <[email protected]> wrote: > After being stuck with the issues mentioned by Matthieu and seeing the > problem with time values in Exif spec itself (no timezone) I decided to > experiment with file metadata formats instead. > > In the end I started my own Exif package which can also write exif metadata, > not just read it like github.com/rwcarlsen/goexif does. With it one could > embed GPS location in the jpeg file, perhaps based on location attributes of > its permanode in camlistore. > > The function indexEXIF pkg/index/receive.go stores all Exif tags in their > original, close to raw format. Perhaps some fields should have special > processing: > - GPSLatitude/Longitude in float instead of rational array > - GPSTimeStamp (rational) recorded together with GPSDateStamp in RFC3339 > - time stamps (DateTimeOriginal and DateTimeDigitized) should use RFC3339 > (without TZ when missing from exif) > > These could then be returned similar to media tags in search.Describe. One > problem is that there are at least 117 exif tags I found in the spec (see > github.com/tajtiattila/metadata/blob/master/exif/exiftag/name.csv). Perhaps > we should just store (and implement query and describe for) selected tags > instead, like it is done for audio files. > > > On Wednesday, July 13, 2016 at 12:23:45 PM UTC+2, mpl wrote: >> >> I believe this is pretty much >> https://github.com/camlistore/camlistore/issues/778 and related to >> https://github.com/camlistore/camlistore/issues/777 >> >> >> On 12 July 2016 at 16:44, <[email protected]> wrote: >> > I understand (and see) how photos with GPS data are parsed and you can >> > search for location... no problem there. >> > >> > What about photos that don't have GPS data? I could add it via EXIF >> > before >> > import, but I would think it could be nice to add as a parameter (that >> > is >> > then recognized) inside of Camlistore. >> > >> > Actually, I would (ideally) be able to assign locations to things beside >> > pictures (files, notes, whatever) and search them the same way... >> > >> > Not implemented, or am I missing the obvious? >> > >> > :-) >> > >> > Thanks all... >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups >> > "Camlistore" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> > an >> > email to [email protected]. >> > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Camlistore" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Camlistore" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
