search

1001WordsPhoto / gpicsync

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

Error during sync and/or gpx inspection #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start a sync then exit, or;
2. Start a inspection then exit

What is the expected output? What do you see instead?
I expected to have jpg files with included GPS data. I got an error.

What version of the product are you using? On what operating system?
I'm using version 1.06 of GPicSync running on Windows Vista Ultimate 64bit
and Windows XP Pro.

Please provide any additional information below.
When trying to synchronise gps data GPicSync generates this message:

------
Beginning synchronization with UTC Offset =2 hours and maximum time
difference = 300 seconds

and then it doesn't do anything. When I press stop and then quit the
program I get an error dialog with the log file location. There is no gps
data in the photo's. Same happens when inspecting the gpx file. The gpx is
fine and opens without errors in OziExplorer and GPSBabel

I tried it on Windows Vista and XP both with the same result. I've attached
the log and the gpx file.

Kind regards,

Sebastiaan Schimmel

Original issue reported on code.google.com by s.schim...@gmail.com on 8 Jul 2007 at 5:54

Attachments:

GoogleCodeExporter commented 9 years ago 
Hello,

The XML parser I use (python elementtree) doen't like this elements in each
trackpoints of your GPX file:

"""
<rmc:course>15.45</rmc:course>
<rmc:speed>0.03</rmc:speed>
"""

It is the first time I see stuff like that in a GPX. Do you have an idea where 
that
come from? I've seen the file was generated with GPSbabel. What was the original
format and what GPSBabel command did you use (maybe you could also send me the
original file)?

If you manage to generate a GPX without this elements it will work fine 
otherwise
I'll have to find a way around it.

francois

Original comment by francois...@gmail.com on 8 Jul 2007 at 7:18

GoogleCodeExporter commented 9 years ago 
Hi,

I don't know if it's something special or not. The gpx was created with 
Trekbuddy on
my Nokia N95 http://www.trekbuddy.net/ as a gpx in raw format (according to
trekbuddy). As the original file generated the same error I tried converting it 
with
GPSBabel (using the GUI without any options) to check if there where any errors 
in
the GPX itself. As it turned out they created the same error.

I've attached the original GPX created by Trekbuddy for comparison but it has 
the
same elements in it. I deleted all the <extension> elements and Gpicsync works 
fine.
I can use this for the time being.

I think the rmc:course is the direction I was walking and rmc:speed the speed I 
was
walking at.

Thanks a lot :-)

Kind regards,

Sebastiaan

Original comment by s.schim...@gmail.com on 9 Jul 2007 at 6:27

Attachments:

GoogleCodeExporter commented 9 years ago 
I'm having similar problems - it's stopping after printing:

Beginning synchronization with UTC Offset =8 hours and maximum time difference 
= 300
seconds

Creating an 'originals-backup' folder.

Starting to generate a Google Earth file (doc.kml) in the picture folder ... 

(Found DSC_0001.JPG ...

I'm using an NMEA log recorded by my GPS. I've tried having gpicsync create the 
GPX
file, and I've made the GPX file myself using GPSBabel. The GPX reader function 
shows
the location information correctly, so I'm not sure what's wrong.

Mike
khelmar@gmail.com

Original comment by khel...@gmail.com on 17 Jul 2007 at 8:57

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi Khelmar,

Your GPX seems fine to me. I suspect that the date of the GPX and the date of 
your
camera is not the same. Can you uncheck "Dates must match" to see (for me it 
works).
If it is the problem I'll have to add a warning message.

You also said you had a problem with the nmea. Can you send it to me with a 
picture
for tests? Thanks

If you don't want your data to be public here you can send it to my gmail 
address:
http://francois.schnell.free.fr/mygmail.png

thanks

Original comment by francois...@gmail.com on 17 Jul 2007 at 9:19

GoogleCodeExporter commented 9 years ago

Original comment by francois...@gmail.com on 22 Jul 2007 at 8:43

GoogleCodeExporter commented 9 years ago 
For information I've ditched the library I was using and use only regular 
expressions
search now (so it should works for any GPX). Version 1.20 released today have 
this
change.
Thanks again for your bug report.

Original comment by francois...@gmail.com on 13 Oct 2007 at 5:26