Bug 214210

Summary:	dont take the correct position from geolocation file
Product:	[Applications] digikam	Reporter:	Marc Collin <marc.collin>
Component:	Geolocation-Correlator	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, mike, rjwgnr27
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	0.9.0
Sentry Crash Report:
Attachments:	Fix timezone behavior and allow an offset in seconds Screenshot of new timezone handling and seconds offset.

Description Marc Collin 2009-11-12 01:35:48 UTC

Version:           0.10.0 (using 4.3.3 (KDE 4.3.3) "release 1", KDE:43 / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.5-0.1-desktop

i tried to do a correlation from a gpx file to some photo

i have a photo the date and time is: 2008:10:24 12:35:04

a part of my gpx file

<trkpt lat="41.903110000" lon="12.466303333">
  <ele>-13.600000</ele>
<time>2008-10-24T12:35:03Z</time>
  <course>170.059998</course>
  <speed>0.861111</speed>
  <fix>3d</fix>
  <sat>5</sat>
  <hdop>1.700000</hdop>
  <vdop>1.000000</vdop>
  <pdop>2.000000</pdop>
</trkpt>
<trkpt lat="41.903095000" lon="12.466296667">
  <ele>-8.600000</ele>
<time>2008-10-24T12:35:04Z</time>
  <course>200.020004</course>
  <speed>0.694444</speed>
  <fix>3d</fix>
  <sat>5</sat>
  <hdop>1.700000</hdop>
  <vdop>1.000000</vdop>
  <pdop>2.000000</pdop>
</trkpt>
<trkpt lat="41.903081667" lon="12.466278333">
  <ele>-4.300000</ele>
<time>2008-10-24T12:35:05Z</time>

so the latitude value should be 41.903095000 and the longitude should be 12.466296667

it was in rome italy this summer, so i need to put gmt value to: GMT+2:00

digikam don't find this value... it' like 41.900615 and 12.465328... if i check this value in my gpx file theses value are found at 14:35:04

so i tried to put GMT+00:00 but i was value found a 16:35:05... so to get the correct value i put gmt to 04:00... don't think it's normal

Comment 1 caulier.gilles 2009-11-17 22:19:58 UTC

Which kipi-plugins version you use ?

Gilles Caulier

Comment 2 Marc Collin 2009-11-18 00:41:14 UTC

libkipi show me 0.4

Comment 3 caulier.gilles 2009-11-18 06:15:45 UTC

I don't talk about libkipi there, but kipi-plugins. Go to Help button from GPSSync tool dialog and look About information

Gilles Caulier

Comment 4 Marc Collin 2009-11-18 13:55:16 UTC

0.8-30

Comment 5 Michael G. Hansen 2009-11-26 16:28:46 UTC

I can reproduce your problem. Looks like there is an implicit time zone stored in the QDateTimes that we use. I will look into it.

Michael

Comment 6 Michael G. Hansen 2009-11-26 19:20:33 UTC

*** Bug 193732 has been marked as a duplicate of this bug. ***

Comment 7 Michael G. Hansen 2009-11-26 19:23:50 UTC

Created attachment 38614 [details]
Fix timezone behavior and allow an offset in seconds

This patch fixes the timezone misbehavior. It also allows the user to specify whether the camera is in the same timezone as the system, or in a manually specified timezone.

This patch includes the patch for specifying an offset in seconds from bug #199189 from Johannes Wienke.

Comment 8 Michael G. Hansen 2009-11-26 19:25:39 UTC

Created attachment 38615 [details]
Screenshot of new timezone handling and seconds offset.

Comment 9 caulier.gilles 2009-11-30 10:55:07 UTC

Let's go Michael to apply this patch before to release 0.9.0...

Gilles Caulier

Comment 10 Michael G. Hansen 2009-11-30 11:20:33 UTC

SVN commit 1056472 by mghansen:

Fix handling of timezones for the camera time. Handle timezones automatically if the timezone of the camera is the same as the timezone of the system.

Also, add the possibility to adjust the camera time offset in seconds for now using the patch by Johannes Wienke.

BUG: 214210
CCBUG: 199189



 M  +2 -1      NEWS  
 M  +22 -12    gpssync/gpsdataparser.cpp  
 M  +4 -3      gpssync/gpsdataparser.h  
 M  +130 -20   gpssync/gpssyncdialog.cpp  
 M  +1 -0      gpssync/gpssyncdialog.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1056472