https://bugs.kde.org/show_bug.cgi?id=400579
evren.kuzucuo...@gmail.com changed:
What|Removed |Added
CC||evren.kuzucuo...@gmail.com
--- Comment #15 from evren.kuzucuo...@gmail.com ---
I wouldn't change or delete the GPS timestamp. In my opinion that's the main
field that shouldn't be deleted when GPS information is modified, because when
it exists it is likely to be the most accurate indication of exactly when the
picture was taken in UTC (since the camera clock might or might not be set
properly), so it's pretty valuable information.
I have this issue for a GPS-enabled camera I used for years (a Canon PowerShot
A520). Very often when the picture was taken just after the camera was turned
on, the camera received enough satellite data to get a timestamp (you just need
one satellite for that) but not the location (requires 3 satellites) or
altitude (requires 4 satellites). As a result I have these pictures with GPS
timestamps but no GPS location. When adding GPS location, I lose the GPS
timestamp... It's a shame to lose valuable data this way.
You could also argue that GPS Image Direction isn't made invalid when changing
the GPS location because it potentially comes from a completely different
sensor (a compass).
There's also another major issue with this behaviour, which is that GPS data is
entirely overwritten when running the pictures through the Batch Queue Manager
(or maybe just specifically the User Shell Script, that's the main one I use)!
So even if I'm not modifying the GPS information, I'm still losing Altitude,
Speed, Direction and Timestamps from my geolocalized pictures... Of course I
can disable the writing of GPS info in settings but then I can't set the GPS in
the metadata anymore in the main app...
--
You are receiving this mail because:
You are watching all bug changes.
