https://bugs.kde.org/show_bug.cgi?id=455775
Bug ID: 455775
Summary: Improve workflow by recording accuracy in
GPSHPositioningError
Product: digikam
Version: unspecified
Platform: Other
OS: Other
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Plugin-Generic-GeolocationEdit
Assignee: digikam-bugs-n...@kde.org
Reporter: sy...@debian.org
Target Milestone: ---
Please add GPSHPositioningError as an EXIF field that can be batch edited in
Digikam via Edit Geolocation to improve photo workflows that upload to web
services making use of the field to record accuracy.
I understand that Apple iPhone cameras set this field. Unfortunately, I have
not found a GPS tracker for Android that sets it, otherwise the tracker itself
could handle this job.
I also understand that GPS DOP, while it is position related, is not something
that should be directly used to set accuracy. See discussion here:
https://forum.inaturalist.org/t/gps-accuracy-not-captured-when-uploading-photos-taken-with-a-camera-with-a-built-in-gps/18861
Details about my use case:
In order to prepare my observation photos to upload via iNaturalist web
uploader, I currently use Edit Geolocation to correlate a gpx track made on
Android with my non-GPS-capable camera photo timestamps. However, the accuracy
information must be manually added per photo in the iNaturalist web uploader
because the GPSHPositioningError is not recorded. This is not efficient. While
there are other means to add that info (e.g. running exiftool at the command
line to set that field to a reasonable default value - see
https://forum.inaturalist.org/t/geotagging-photos/66/5 ) it is an inconvenient
extra step I would like to avoid by having Digikam handle it in the geolocation
editing phase of my photo workflow.
Proposed placement in the UI:
For example, where another position-related field that can be changed in Edit
Geolocation is "DOP" in the Details pane (which iNaturalist web uploader does
not use - see the first link above), perhaps "H pos error" could be placed
beneath that, and then a user could enter a reasonable default value like 10
metres. Thus, with a few more clicks and keystrokes after performing
geolocation, a batch of photos will be ready for upload, and the accuracy
default will be set on every photo, saving that extra manual step.
Alternatively, in the GPS Correlator pane itself under "Offset of pictures
(hh:mm:ss):", add "Accuracy (in metres):" (or however you think this should be
described) that can optionally be used to set the GPSHPositioningError
directly, i.e. without a second pass in the Details pane. This would be a more
efficient alternative, though I understand it's probably a tough sell to put it
here for what might seem to you like a niche use case.
Note: while there is an iNaturalist plugin, that is not currently a part of my
workflow for various reasons. Besides, I do not consider this request limited
in scope to uploading to iNaturalist, as other platforms may also make use of
GPSHPositioningError to indicate accuracy.
--
You are receiving this mail because:
You are watching all bug changes.
