On 25 Feb, 08:37, Terry Pinnell <terrypinDEL...@THESEdial.pipex.com
wrote:
"claudegps" <claud...@gmail.com> wrote:
On 21 Feb, 10:14, Terry Pinnell <terrypinDEL...@THESEdial.pipex.com
wrote:
OK, thanks Claude, I'll take a look at the program again in a week or
two.
The new version with the promised fixes is ready to be donwloaded.
Claude
www.claudegps.altervista.org
Thanks Claude. That seems to convert OK now. I used the same file I
sent you as a test previously:http://www.terrypin.dial.pipex.com/Images/17Oct06Nuthurst.plt
Pleased to see the browse default now retains last folder used.
But one immediately obvious flaw is that it doesn't warn you of
over-writing a previous KML.
Hi Terry!
Overwrite is one of things on the 'ToDo-list' from long time... I'm
just lazy...
It' will be added... sooner or later
More importantly, I'm not sure whether I'm using it correctly, or
because the PLT file is deficient in some way, but I don't see any
track displayed in Google. I have Opacity at 50% and Track Width = 3.
Also, the only graph produced is Speed. Of the six others, which are
blank, the two involving altitude are obviously because my ancient GPS
12 doesn't download that! I don't know what 'HDOP' and 'Geoidal
Separation' are, but I'd have expected maybe to see something for the
remaining two: Acceleration and Number of Satellites.
Perhaps you could run it and let me have your comments please.
I tried to convert your file.
I think to have discovered why you don't see the track: the altitude
setting.
Into your file, the altitude is set to 0. If you have terrain enable
in Google Earth, you track goes below the terrain(that is > 0)!
To avoid this, just select "Ignore(ground)" in "Track Altitude"
options. In this way, Google earth will "glue" your track to the
terrain.
Unfortunately PLT is very poor of informations...
There is Lat/Lon, altitude, speed and time. And Altitude and Speed are
not always present!
Speed/heading can be reconstructed using position and Time, but the
program can't recover other informations like N. of satellites used,
geoidal separation (an altitude parameter),HDOP (parameter that tell
you how good is your positioning based
on satellites position) and so on...
That is why you have emtpy graph: there are not enough informations in
the PLT file to fill them!
The Acceleration graph is reconstructed starting from the
reconstructed speed...and... it's wrong...
In your file, the positions are not stored each second, but the
acceleration is calculated supposing that the measurements are done
each second!
The speed is calculated in the right way, taking into account the
delta times, but the acceleration is not...
...Ehm...You pointed out a bug...

Now it's fixed (will be ok in
the next release)
It looks a useful tool, but unless you add support for GPS Utility
files it will unfortunately be of no real practical value for me.
When you say "GPS utility" file format what do you mean?