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:
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.