"invalid longitude" from gpsbabel invoked by geo-found
Date: January 13, 2010 01:40PM
From the output of "geo-found -n 5 -D 10":
gpsbabel -i xcsv,style=/tmp/geo.newstyle -f /tmp/geo.merge -o gpsdrive -F /tmp/geo.way
Invalid longitude 19700101.000000 in waypoint .
geo-found: gpsbabel returned error code [4]
Has something changed in the past few days that might produce such an effect?
Keeping the /tmp files for further reference...