[Xastir] A minor miracle.....and another issue with gpsd....

[Richard E. Polivka]

It seems that when I forced the leading zero, xastir decoded correctly. 
I had tried using %08.4f but no joy. I could use the 0%8.4f as long as 
longitude is less than 100 and then use a different sentence structure 
%8.4f when >= 100.0000. Nasty hack - Nasty hack - probably non-portable.

On a new front, while driving and testing, xgps and xastir were reporting me traving at supersonic speed. I wish but I doubt my jeep could handle that. The speed was a factor of 60 too high. So I have hacked libgpsd_core.c to divide the speed signal by 60 to see if that is where the issue is. This may not be correct but others can point out more appropriate solutions. 

Now to wait for my batteries in the laptop to recharge so I can test things again. Don't have a 12 volt cord for the Dell...yet.

73,

---
Richard E. Polivka, N6NKO

*** Never meddle in the affairs of wizards, for they
*** are easily angered, and you are crunchy and taste
*** good with lemon sauce.



Henk de Groot wrote:

> Richard E. Polivka schreef:
>
>> Now for the C wiz's: I used 0%8.4f to supply the leading zero. I 
>> doubt this is correct. What would be correct to make 88.0102 print 
>> out as 088.0102?
>
>
> Well, this is not correct, unless you want 100.0102 to appear like 
> 0100.0102 :-).
>
> I would assume %08.4f would do the trick, the 0 indicates to prefix 
> the number with zeros unitl the length is 8 positions. I'm not sure 
> however if this is portable, i.e. if all *printf/*scanf 
> implementations support it.
>
> Kind regards,
>
> Henk.
>
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> https://lists.xastir.org/mailman/listinfo/xastir
>