Almost one year passed since the last release of KGeoTag, the KDE/Linux standalone geotagging program. Which doesn't mean that the development stalled, quite the opposite :-) It seems like the feature set KGeoTag now has is slowly but surely suitable to do it's one job: To geotag photos in a convenient, graphical way.
However, there are two alterations, and thus, it's time to finally make a new release:
It's now possible to find the chronologically closest track point for an unassigned image and center the map there. If an image has been taken in the time between two tracks, one can find the last or first coordinates of the track recorded before or afterwards (whichever is closer) and use them as a basis for manual tagging.
I'm pleased to anncounce the new 1.4.0 release of KGeoTag, the stand-alone geotagging program!
The most "visible" change of this release is: KGeoTag now supports handling of some TIFF-based RAW image formats (cr2, nef and dng). By default, XMP sidecar files are created for those (regardless of the global setting). Additionally, there's a new option for enabling direct Exif header changes for RAW files.
Thanks a lot to Angel Lopez to bring this up and help to implement this properly!
Additionally, some minimum depencency version bumps have been done (KF 5.68.0 and Qt 5.12.0). Those should be fine with older (LTS) distributions. The dependency bump to Marble 21.12.0 broke the compatibility with (at least) Ubuntu LTS 20.04 and Debian Bullseye. As KGeoTag could always be compiled against Marble from the beginning, the required Marble version is now omitted again, until >= 21.12.0 hits LTS distros (the first Marble version to have decent versioning).
TL;DR: KGeoTag can now be built (again) on Ubuntu LTS 20.04 and Debian Bullseye – without any manual changes.
Last but not least, the timezones data files have been updated to the 2022g release of Timezone Boundary Builder. Due to some changes to the script creating the timezones map KGeoTag uses from it, we now 1. have much less changes to the timezones.json file on changes to the underlying data and 2. much nicer colors in timezones.png ;-)
Due to a problem with releaseme's tarme.rb script, the release tarball for KGeoTag 1.3.0 didn't contain any translation data. Alas, I noticed this not before the tarball already spread the mirrors, so we had to withdraw it an create a new one, with a bumped version number.
Anyway, I jumped at the chance: There's one additional feature compared to 1.3.0 now. Strictly speaking, this would have required a minor version bump, not only a bugfix one, but I already wanted to release this with 1.3.0 – but I simply couldn't get it to work. Now I figured out how to do it. So let's not be too particular with this, pretend is was added to 1.3.0 but didn't work and call it a bugfix:
Now, when using the split images list view and tagging images manually, the "assigned" image list scrolls to the last (or only) tagged image and highlights it, so that it's immediately accessible for e.g. further corrections. Which is really nice when dropping images to the map and fiddling with their exact position by dropping them a few more times.
I'm happy to announce the new release 1.3.0 of KGeoTag, the standalone KDE geotagging program!
The ChangeLog contains the following changes:
New (Bug #458537): Allow setting coordinates directly from the clipboard. As of now, Google Maps' format as well as OpenStreetMap's Geo URI scheme is supported.
New: It is now possible to open an image with the system's default image viewer (for closer inspection), either from the image list(s), or from the preview widget.
Bugfix (#457020): Use "Folder", not "Directory" according to KDE's style/vocabulary guidelines.
New: Files and/or directories given on the command line are now loaded after startup (which can e.g. also be triggered via "Open with" from a file manager like Dolphin).
Update: Updated the timezones data files to 2021c (cf. Timezone Boundary Builder's Release Announcement.
Change: As Marble now has a decent versioning scheme (at least since the KDE Apps release 21.12.3), KGeoTag now has a defined dependecy for Marble: It now depends on at least Marble 21.12.0. It actually can be built against older versions as well, but due to the lack of proper version bumps, there was no way to define a definitive version to depend on until now.
New/Bugfix (#452534): Added a handbook stub.
Notice to the packagers
Just to say it again: If you're packaging KGeoTag for your distribution, and Marble 21.12.0 is not available yet, you can still build KGeoTag if you were able to build it before. The dependecy has only been added because it's the first Marble version we can rely on (cf. the ChangeLog above).
In this case, simply remove the version from CMakeFiles.txt and you're done. The following patch does the trick: