KGeoTag 1.4.0 released

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 ;-)

Have a lot of fun with KGeoTag!

– Tobias

Hotfix: KGeoTag 1.3.1

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.

On top, KGeoTag now ships translations again ;-)

– Tobias

KGeoTag 1.3.0 released

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:

--- CMakeLists.txt.orig 2022-09-04 14:27:25.729672632 +0200
+++ CMakeLists.txt      2022-09-04 14:27:52.961403115 +0200
@@ -8,7 +8,7 @@
 set(QT_MIN_VERSION "5.11.0")
 set(KF5_MIN_VERSION "5.44.0")
 set(KExiv2_MIN_VERSION "5.0.0")
-set(Marble_MIN_VERSION "21.12.0")
+set(Marble_MIN_VERSION "")


Have a lot of fun with KGeoTag :-)

– Tobias

KGeoTag 1.2 released

KGeoTag 1.2 is out now! Basically, this is only a bugfix release:

Bugs fixed

The main reason for this release is, that – at least here on my Gentoo box – the MIME type for GPX files has changed. I'm not sure which update caused this, but until lately, QMimeDatabase::mimeTypeForFile reported application/x-gpx+xml as the MIME type for GPX files, but now, I get application/xml+gpx.

This caused KGeoTag to refuse loading GPX files and thus broke a main functionality. Fixing this was quite trivial however: Now, both MIME types are accepted for GPX files.

Additionally, Bug #445023 has been fixed. All images in a list can now be selected via CTRL+A again.

CMake dependency bumped

… BUT: The reason why we have to call this "1.2.0" and not "1.1.1" is that a small compilation warning also has been fixed. Just after releasing version 1.1.0, KDE's Extra CMake Modules told me "Your project should require at least CMake 3.16.0 to use FindKF5.cmake". So I bumped the dependency from 3.8.0 to 3.16.0.

This should be no problem. Even Debian Stable ("Bullseye") has CMake 3.18.4, there's also a backport for Buster (on Gentoo, we're at 3.20.5 to be stable). Technically, this is a depencency change however, and thus, according to Semantic Versioning, we need a minor release and not just a bugfix one.

Everbody is encouraged to update! Have a lot of fun with KGeoTag :-)

– Tobias