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 :-)
I'm delighted to announce a new release of KGeoTag, the KDE stand-alone photo geotagging program!
To improve the workflow, there's a new main menu entry called "Assign images to GPS data". This one triggers a configurable action, like "(Re)Assign all images" from the "Automatic assignment" dock. One now can load images and GPX tracks, assign them and save the coordinates without having to mark all images and having to use the context menu of the images list or using the "Automatic assignment" dock.
Additionally, some bugs have been fixed:
The date and time displayed for a waypoint when walking along a track is now calculated correctly for the system timezone. Until now, the correct timezone was only displayed, but the time was actually displayed in UTC.
I also learned that some GPS devices (in this case my mobile phone) do store milliseconds for a waypoint's timestamp. Maybe, also some cameras do this for the EXIF data. This lead to the matching algorithm not finding any exact matches, although there should have been some (caused by the way the lookup is done, see the ChangeLog for details). The exact matching now also works for GPX files and/or images containing times including milliseconds.
This is the first post on KGeoTag's brand new homepage, https://kgeotag.kde.org/! From now on, there's a "real" homepage for the project, besides the KDE Invent page and the (auto-generated) KDE Apps entry.
Now, the project has a central place for posting news about KGeoTag, release announcements, and so on :-)
Big thanks (as always) to KDE's Sysadmin Ben Cooksley for setting up the needed infrastructure, and of course also big thanks to the whole KDE Project for hosting the site and making all this possible!
Notice: This blog post was added after KGeoTag's homepage was set up. Originally, it had been posted on nasauber.de.
Just to also announce this somewhere in a weblog (as KGeoTag currently lacks a "real" homepage other than the GitLab one): Some days ago, I did the first official release of KGeoTag, the new KDE/Linux geotagging program!