Il giorno lun, 04/12/2006 alle 16.26 +0100, Leonardo Lami ha scritto:
Hi all,
I'm testing v.in.gpsbabel but I found a not corrspondence between tha datas
associated to the point in gps and the datas associated to the new vector.
If I use a gps Garmin 12 (not Etrex) the label associated to the points
(second column in the file
gps.csv, download by gpstrans) is not present in the table associated to
the vector (gpsbabel.dbf).
If I use gps Garmin 12 Etrex it works well (gpsbabel_etrex.dbf).
Does someone know this bug?
Thank you for help
Regards
Leonardo
Hi all,
I think that the field is not correctly recognized by gpsbabel, the
script make only textual manipulation on his output...
It can be that gpsbabel download the column with a different tag from
the other garmin gps, and this tag is not included in csv stylesheet...
If the problem is only on one gps receiver model, I think it his hard to
fix (we had to download a meaningless column for all others gps
receivers), but if it is common problem, we had to fix it.
Leonardo, please try watching on temporary files to see if I'm right.
PS Please report if it happens on other receivers...
Leonardo:
> Hi all,
> I'm testing v.in.gpsbabel but I found a not corrspondence between
> tha datas associated to the point in gps and the datas associated
> to the new vector.
>
> If I use a gps Garmin 12 (not Etrex) the label associated to the
> points (second column in the file
> gps.csv, download by gpstrans) is not present in the table
> associated to the vector (gpsbabel.dbf).
>
> If I use gps Garmin 12 Etrex it works well (gpsbabel_etrex.dbf).
Davide:
I think that the field is not correctly recognized by gpsbabel, the
script make only textual manipulation on his output...
It can be that gpsbabel download the column with a different tag from
the other garmin gps, and this tag is not included in csv
stylesheet... If the problem is only on one gps receiver model, I
think it his hard to fix (we had to download a meaningless column for
all others gps receivers), but if it is common problem, we had to fix
it.
Leonardo, please try watching on temporary files to see if I'm right.
PS Please report if it happens on other receivers...
All our Garmins are currently out in the field. I can help test whenever
they get back.
Note that "date" column is really just the comments field. It so happens
that the default comment when you make a new waypoint is the current
time and date. As the user can change it to anything, v.in.gpsbabel
should not treat that field as a timestamp, just as a string comment.
Il giorno mar, 05/12/2006 alle 14.53 +0100, Leonardo Lami ha scritto:
Hi
I make some tests and I send you the gpsbabel output files.
For every type of gps (garmin 12, garmin 12xl and garmin 12 etrex) I make two
file:
a gpx file create from gpsbabel by "gpsbabel -w -i garmin -f /dev/ttyUSB0 -o
gpx -F *.gpx"
a csv file create from v.in.gpsbabel using grass_write_ascii.style like in the
script
You can see that for "garmin 12" and "garmin 12xl" v.in.gpsbabel does not
transfer the field "name" (present in the gpx files) in the csv files.
Regards
Leonardo
Hi all,
the data is not downloaded because in the grass_write_ascii.style I did
not put a field for that data (I believed that was only a progressive ID
for the waypoint...)