trailblazing / gpicsync

Automatically exported from code.google.com/p/gpicsync
Other
0 stars 0 forks source link

Adjust time by minutes between GPS LOG and Photos #8

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Camera time should be a few minutes faster or slower than the GPS
2. Take photos while moving on a boat / car / plane...
3. Geocoding the photos will find trackpoints in the log at the EXIF time 
but the Lat/Long will be incorrect.

What is the expected output? What do you see instead?
I would like to lat / long to represent the accurate location where the 
photo was taken. Instead the position on the map can be way out if the 
time is not accurate between the devices.

What version of the product are you using? On what operating system?
0.9 / win XP SP2

Please provide any additional information below.
My camera seems to gain time. I have lots of photos that I'd like to 
geocode where the time is a bit out but where for example I was on a boat 
taking photos while we were moving past Cape Point, the map places these 
photos of Cape Point a few km off which make things very confusing.
It would be great if I could use the UTC offset in hours and minutes. 
Currently I find I can only use integers eg +2 - I'd like to be able too 
do +2:09 to correct for the 9 mins.

Original issue reported on code.google.com by chris.nu...@gmail.com on 24 Apr 2007 at 10:28

GoogleCodeExporter commented 9 years ago
Hello chris.nursey,

Did you see the "local time correction" in options menu ? (you can add here an
additional offset between your camera and GPS to the second).

Tell me if you think it's not sufficient.

Don't hesitate also to use the GPicSync group:
http://groups.google.com/group/gpicsync

thanks

francois 

Original comment by francois...@gmail.com on 25 Apr 2007 at 6:55

GoogleCodeExporter commented 9 years ago
Hi Francois,

Thanks, The time difference I entered in the menu was 2 min. The geocode only 
if 
track point is .. was 120 sec. I confused the two. I thought the difference 
calculated from the menu was filled in to that setting on the screen. Am I 
right to 
assume that the "local time correction" is only valid for the nest Sync or is 
it 
valid until you close the program?

Anyway the problem is solved.
Thanks!
Chris

Original comment by chris.nu...@gmail.com on 25 Apr 2007 at 8:55

GoogleCodeExporter commented 9 years ago

Original comment by francois...@gmail.com on 25 Apr 2007 at 10:08