search

GoogleCodeArchives / gpicsync

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

"WARNING: DIDN'T GEOCODE, no track point below the maximum time range ( 30 s)" #88

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set the Pictures Folder to the Folder containing the Pics
2. Set the GPS File to the File of the GPX
3. Click "Synchronise"

What is the expected output? What do you see instead?
GPicSync Should have added the GPS Info...I get an error instead. :(

What version of the product are you using? On what operating system?
1.28 2008
Windows XP Pro

Please provide any additional information below.
My Pics have timestamps in their file info.  There are many points in the
GPX file that are within a few seconds of the pics' timestamps.  For some
reason I keep getting that same error. I changed the 300s to 30s to get
more accurate GPS info onto the Pic file, but I was getting that same error
when it was preset @ 300s.

Original issue reported on code.google.com by 559J...@gmail.com on 23 Jun 2009 at 7:49

GoogleCodeExporter commented 9 years ago 
I forgot to mention, the details show that the time difference (different from 
file
to file) is between ~99,000 & 35 seconds...mostly over 1000 seconds...it DID 
sync
about 5% of the pics with the GPS...but I don't know Y it didn't sync the other 
95%.

Original comment by 559J...@gmail.com on 23 Jun 2009 at 8:01

GoogleCodeExporter commented 9 years ago 
A couple of details that I failed to mention:

1) The 11% (not 5% as I 1st stated) of the pics that were Updated by GPicSync 
were
sporadic (almost random).  All of the 200+ aforementioned pics were taken over 
the
course of 2 days...the same 2 days that I was on my JMT Hike thru Yosemite.

2) My Garmin GPSmap 60CSx & my Sony DSC-W55 were within 1' of eachother during 
every
photo & have their times synced to about 1/10th of a second.

3) I reviewed the info of the GPX File on Garmin MapSource & there are 
corresponding
Waypoints/Tracks to the times of the pics...furthermore, there are 5 GPX files 
on my
Garmin and I attempted to run this program using not only the obvious file, but 
all
5, one at a time.  No difference in results other than the time differences.

Original comment by 559J...@gmail.com on 23 Jun 2009 at 9:57

GoogleCodeExporter commented 9 years ago 
Hi Josh,

Did you give the good value in the UTC offset field ? 
It depends of the state you live in and there's maybe a summer time shift of 
one hour.

So try to play with this field.

If it doesn't work send me the gpx + one or two picture which don't sync for 
testing.

PS: in the next version it will be easier to select your time zone.

Original comment by francois...@gmail.com on 23 Jun 2009 at 4:25

GoogleCodeExporter commented 9 years ago 
I did NOT play with the UTC Field as all of the settings appeared to be 
correct.  I'm
located in Fresno, CA, USA (PST Zone) so I'm not certain that the UTC Field 
would
apply to me.  Besides that fact, it doesn't make logical sense that that field 
would
be the problem considering that some of the pics WERE 'Updated' by the program 
and
others were not.

I have attached the GPX Files & 1 pic (20090621 and/or 22 are the most 
applicable GPX
files.  Not sure Y my 60CSx made more than one GPX).  I'd send more pics but 
since
they are so large I want to be sure that you get them.

Thanks in advance,
Josh

Original comment by 559J...@gmail.com on 23 Jun 2009 at 10:38

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
It's been over a WEEK now & I'm still waiting for some resolution.

Original comment by 559J...@gmail.com on 1 Jul 2009 at 9:20

GoogleCodeExporter commented 9 years ago 
Hello 559Josh and sorry for my late reply.

If I asked you if you gave the good value for the UTC field before it's because 
it's
necessary for gpicsync as you can see in the "Gettintg started page":
http://code.google.com/p/gpicsync/wiki/GettingStarted

This is because the GPSr receive time in UTC format and that people usually set 
the
time of their camera to local time.

I just looked at california timezone:
http://www.timetemperature.com/tzus/california_time_zone.shtml

If you give -7 as the value for the offset and take the 20090621.gpx file it 
should
work for this picture.

Original comment by francois...@gmail.com on 1 Jul 2009 at 10:18