From: Grant Kier <grant.kier@bi...> - 2005-11-14 00:48:20
In an effort to flee the bitter cold of an early Montana winter, my
Garmin (Forerunner 301) makes frequent, and very quick, trips to the
Gulf of Guinea (Lat 0.000, Lon 0.000) in the middle of my otherwise
uneventful bike rides through narrow mountain canyons. The result is
track data that is very difficult to plot on a map and somewhat
misleading with respect to my total trip mileage. I don't see a track
filter that is equivalent to the radius point filter, but is there a
single filter or combination of filters that might work in a similar
way to get rid of intermittent zero lat-lon values in a gpx track file?
Bitter Root Land Trust
117 North Fourth Street, Suite A2
Hamilton, Montana 59840
406/ 375-0956 | office
406/ 375-0925 | fax
From: Robert Lipe <robertlipe@us...> - 2005-11-14 14:39:58
Grant Kier wrote:
> In an effort to flee the bitter cold of an early Montana winter, my
> Garmin (Forerunner 301) makes frequent, and very quick, trips to the
> Gulf of Guinea (Lat 0.000, Lon 0.000) in the middle of my otherwise
> uneventful bike rides through narrow mountain canyons. The result is
We don't have such a filter. Let's focus instead on why you're getting
so many frequent flier miles during your bike ride.
Are we really reading 0/0 trackpoints from the 301? Is the 301 sending
us 0/0's (though the Garmin isn't *supposed* do to that on lost lock, I
wouldn't fake shock if it did) or did we bozo the read somehow?
If you turn on protocol debugging (and there'll be a mountain of it) does
anything catch your eye?
gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx
Get latest updates about Open Source Projects, Conferences and News.