| Summary: | Feature Request (KGeoTag): Extract and Write view direction into EXIF data | ||
|---|---|---|---|
| Product: | [Applications] kgeotag | Reporter: | BOF <bugs_kde_org.5.kuru> |
| Component: | General | Assignee: | Tobias Leupold <tl> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | tl |
| Priority: | NOR | ||
| Version First Reported In: | 1.3.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | All | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
BOF
2023-01-04 21:06:13 UTC
Hi BOF, thanks for the request! Sounds essentially like a good idea. I'll have to investigate this closer. But: You can't derive the view direction from a GPX track though, so this would have to be done by hand, for each and every picture taken, no? If there's a standardized Exif header for that, this could be doable. The problem to implement this is that KGeoTag doesn't mess with the Exif headers directly (which is, as you might have already thought, not so easy ;-), but uses KExiv2 to do the "dirty work". So, as long as KExiv2 doesn't support setting such information, the only thing we could do is to implement our own Exif header writer (and I'm pretty sure I don't want to do that :-P). So I think you should ask the KExiv2 guys to add the respective functionality first (or implement it yourself and create a MR of course!). As soon as KExiv2 support this, we can think about how to use it in KGeoTag. Cheers, Tobias No, you would not be able to get the view direction directly from a GPS track. However, as far as I know about this feature from a different application it positions images along the track based on their time. So it's to add GPS info to files that were taken with a device that does not have a build in GPS receiver (like an old DSLR camera) or was not turned on at the time (like in the settings of your smartphone) I'm not sure if it's what you mean by 'header', but there already is a standard entry for the view direction in the EXIF data. The company smartphone I got saved the view direction alongside the image in already mentioned 'GPS Img Direction' tag. I guess KExiv2 sound like a fork of Exiv2. So everything that Exiv2 can do should be able possible for KExiv2 as well (as long as the latest changes are transfered to the fork). I tried to test around with exiv2 today (on Windows) and it told me that "ligcc_s_seh-1.dll" was missing. After I got that one an error box told me that the application can not run with bug code "0xc00000007b". I remember this tool to be rather simple to use (just /path/to/file/application.exe "path/to/file/filename.jpg" and the application will display the contained EXIF data. So it will may take some time to check f Exiv2 can do that. KExiv2 is not a fork, it's a Qt/KDE wrapper using exiv2 that makes your life much easier when developing a Qt/KDE app, and, as said, it's the library that KGeoTag uses to do the Exif tagging. If exif2 can write the respective Exif header, KExiv2 would be able to also do so – if somebody adds the respective functionality (but this is not the case by now). |