Bug 271647 - Unwished GPS localisation provided to Google photo
Summary: Unwished GPS localisation provided to Google photo
Status: RESOLVED DUPLICATE of bug 297290
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Google (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-24 21:44 UTC by christian
Modified: 2022-01-07 05:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description christian 2011-04-24 21:44:25 UTC
Version:           1.8.0 (using KDE 4.5.4) 
OS:                Linux

Each time I need to do export to internet (picasa included), I do a batch queue suppressing all tags (exif, iptc, xmp). 
This activity is aiming to avoid any information discloser to internet web site.

Unfortunately, even having done this activity, GPS localisation has been publish to picasa.
I have check the picture tags. Actually they don't have any tag. Nevertheless, it seems that some pcitures has GPS information in digikam database (shown in geolocalisation tool). 

Could it be any way to avoid disclosing any information but the picture itself to picasa ?

Thanks.
Christian.

Reproducible: Didn't try

Steps to Reproduce:
get gps information in picture. Supress all tags by batch. Do export to picasa.

Actual Results:  
picasa know my picture location

Expected Results:  
no localisation provided (no information provided  if possible)

OS: Linux (i686) release 2.6.34.7-56.fc13.i686.PAE
Compiler: gcc
Comment 1 christian 2011-04-24 21:52:37 UTC
it may help:

digiKam version 1.8.0 (rev.: 1211277)
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.21
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.5.4 (KDE 4.5.4)
LibKExiv2: 1.2.0
LibKdcraw: 1.2.0
LibLCMS: 119
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.09.44 - internal library
LibPNG: 1.2.44
LibQt: 4.6.3
LibRaw: 0.11.0
LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble widget: 0.10.3
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.8
LibKipi: 1.2.0
Comment 2 christian 2011-04-24 22:12:46 UTC
the same issue exists on caption as it is published even after having clean up all tags by batch queue.
Comment 3 caulier.gilles 2011-12-20 17:24:01 UTC
Christian,

This file still valid using kipi-plugins 2.4 ?

Gilles Caulier
Comment 4 christian 2011-12-20 21:08:59 UTC
Hi Gilles,
   I now use the standard Ubuntu Digikam release. At this time this is 2.1.1 with the below component list.

I'm not sure the kipi is different but I ll give a try on this and come back to you. I may upgrade later but it will take a big while.

Christian.


digiKam version 2.1.1
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.21.1
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.7.2 (4.7.2)
LibKExiv2: 2.0.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.0.0
LibLCMS: 119
LibPGF: 6.11.24 - internal library
LibPNG: 1.2.46
LibQt: 4.7.4
LibRaw: 0.13.5
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.12.0 (stable release)
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibKface: 2.0.0
LibKipi: 1.2.0
LibOpenCV: 2.1.0
Libface: 0.2
Comment 5 caulier.gilles 2011-12-22 10:04:10 UTC
Christian, 

This file still valid using kipi-plugins 2.4 ?

Gilles Caulier
Comment 6 caulier.gilles 2015-05-19 13:47:58 UTC

*** This bug has been marked as a duplicate of bug 297290 ***