0000400: Time zone problem when camera clock set to UTC - GeoSetter - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0000400	GeoSetter	User Interface	public	2010-01-24 21:30	2010-01-25 20:07

Reporter	brendt	Assigned To	Friedemann
Priority	normal	Severity	feature	Reproducibility	always
Status	assigned	Resolution	open
Product Version	3.2.6 release
Target Version		Fixed in Version

Summary	0000400: Time zone problem when camera clock set to UTC
Description	I'm trying to synchronise some digital images with NMEA track data, but am experiencing some difficulty because the camera clock was set to UTC rather than the local time zone. Under "Synchronize with GPS Data Files", the only possible option was to select "Use Time Zone", with the time zone set to (UTC) Europe/London (or equivalent). While this does indeed result in the correct (i.e. zero) offset being applied to the camera clock when matching with UPS data, after synchronization, the time zone can be correctly set by using "Get from Web" to set the time zone, but this merely sets the correct time zone as a postfix to the UTC time, instead of adding the UTC offset to the UTC time to obtain the local time. Since setting the camera clock is a useful approach (having the advantage of not having to constantly change the clock as one changes time zones, or with the start or end of daylight savings time), it seems reasonable to support this choice. One way of doing so would be to allow the user to specify two time zones: one for the camera clock, and another for the local time zone, but there could well be a better approach.
Tags	No tags attached.

Date Modified	Username	Field	Change
2010-01-24 21:30	brendt	New Issue
2010-01-25 20:07	Friedemann	Status	new => assigned
2010-01-25 20:07	Friedemann	Assigned To	=> Friedemann