Re: [gpsd-users] JSON output

[IT1 Stuart Blake Tener, USNR]

Eric,

I was exchanging posts with Gary a few days back and had mentioned  
that the first 3 lines of output on a "gpspipe -r" were JSON and that  
I had to use grep "{" to dispose of them. He then very quickly stated  
that I had located a bug, which I did not even realize it was. Either  
way, that bug is easily surmountable with a grep, but if it was a bug  
I'd not mind to try to research it and apparently Gary was going to do  
so also (I did not rush so far to look at it, as he did mention he was  
going to also).

I had presumed that the JSON output was there to enunciate the type of  
device and such. But then, I realized, that probably there is a NMEA  
sentence way of doing that and maybe that output was a bug. I also  
then noticed that the JSON was spitting out when you request binary  
output too, and that certainly made no sense (to have ASCII JSON when  
binary is expected for everything else).

By the way Eric, with all your technical capabilities you would be a  
wonderful addition to the Amateur Radio Community should you decide to  
use the open source "hamexam" software to study for the license. :)


V/R and 73,

Stuart, N3GWG
Computer Scientist


--

IT1 Stuart Blake Tener, USNR, N3GWG (Extra), MROP
NR N-NC JTF EAST DET UIC 84245

Las Vegas, NV / Boulder, CO / Philadelphia, PA / Beverly Hills, CA

(310) 358-0202 Mobile Phone
(215) 338-6005 Google Voice

e-mail: address@hidden



Quoting "Eric S. Raymond" <address@hidden>:

> IT1 Stuart Blake Tener, USNR <address@hidden>:
> > Just curious if there was any success on the remediation of the code
> > segment responsible for generation of JSON during NMEA output on
> > gpspipe?
>
> To what problem are you referring?
> --
>                 <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>