due to changes in v.in.ascii the script v.in.garmin is currently broken.
Changing the string "catcol" to "cat" in v.in.garmin fixes the biggest
problems and the script can at least be used to import Waypoints/Tracks and
Routes as POINTs.
There's still another bug lurking: track/route-vectors are being created,
but the geometry is garbled, which makes 'em unusable.
due to changes in v.in.ascii the script v.in.garmin is currently
broken. Changing the string "catcol" to "cat" in v.in.garmin fixes the
biggest problems and the script can at least be used to import
Waypoints/Tracks and Routes as POINTs.
There's still another bug lurking: track/route-vectors are being
created, but the geometry is garbled, which makes 'em unusable.
due to changes in v.in.ascii the script v.in.garmin is currently
broken. Changing the string "catcol" to "cat" in v.in.garmin fixes the
biggest problems and the script can at least be used to import
Waypoints/Tracks and Routes as POINTs.
fixed in cvs.
There's still another bug lurking: track/route-vectors are being
created, but the geometry is garbled, which makes 'em unusable.
works for me.
G61> v.in.garmin -v -t out=t_trk
[...]
G61> v.build t_trk
Building topology ...
12 primitives registered
Building areas: 100%
0 areas built
0 isles built
Attaching islands:
Attaching centroids: 100%
Topology was built.
Number of nodes : 24
Number of primitives: 12
Number of points : 0
Number of lines : 12
Number of boundaries: 0
Number of centroids : 0
Number of areas : 0
Number of isles : 0
[no errors there..]
G61> d.vect t_trk
[looks fine]
Could you explain more about "geometry is garbled" ?
Are there any error messages in the v.in.garmin output?
Are you using DBF database?
I tried the same command sequence you suggested (on a UTM zone 32
location, import of GPS_points (track|route|waypoint) works
fine), this is an excerpt of the error printout:
---------------------
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()
ERROR: Error while executing: "INSERT INTO t1_trk VALUES (135,
'03/27/2005
11:31:52', 49,0000000, 9,0000000, '03/27/2005 11:33:00',
49,0000000,
9,0000000)
"
DBMI-DBF driver error:
Incompatible value type.
Error in db_execute_immediate()
ahh ok, I see the problem.
49,0000000
Awk is using the comma as a decimal place instead of a period, and so
the third column is read as 000000 not 9.0000.
see these threads, same problem but with r.fillnulls.