Bad WX multiline data, still. Re: [Xastir] Someone is sending out bad data...

[Tom Russo]

On Tue, Aug 28, 2007 at 06:35:30AM -0500, we recorded a bogon-computron collision of the <gerry.creager at tamu.edu> flavor, containing:
>  I didn't get very far with looking into this.  I had real work interfere 
>  with the important stuff.  I'll try to carve out time later this week but 
>  today's already committed.
> 
>  Let me get an on-the air station and see what's going on.
> 
>  TOM: Your local NWS station is in ABQ, correct?  I may be able to leverage 
>  that.

Yes, it's in Albuquerque.

>  Tom Russo wrote:
> > On Sun, Aug 12, 2007 at 10:26:51AM -0500, we recorded a bogon-computron 
> > collision of the <r.polivka at sbcglobal.net> flavor, containing:
> >>  This may be a repeat of a previous issue but xastir is spewing this out  
> >> today ...
> >>
> >>  extract_multipoints: invalid value in (filtered) "Center of MaxConcern 
> >> }d0df  e e e XKe {CEbAH": 24,-179
> >>  extract_multipoints: invalid value in (filtered) "Center of MaxConcern 
> >> }d0df  e e e XKe {CEbAH": 24,-179
> >>  extract_multipoints: invalid value in (filtered) "Center of MaxConcern 
> >> }d0df  e e e XKe {CEbAH": 24,-179
> >>  extract_multipoints: invalid value in (filtered) "Center of MaxConcern 
> >> }d0df  e e e XKe {CEbAH": 24,-179
> >>
> >>  Unfortunately, this is all I am getting out of it. Now, what debug level  
> >> should I turn on to find out where the bogus data is coming from?
> > This is a continuing issue, and is getting more and more common lately.
> > The issue is that these WXSVR objects are getting sent out with invalid 
> > data
> > (at least according to the published wxsvr.net multiline protocol) that 
> > xastir is choking on (because some coordinates are coming up out of range).
> > Gerry said he'd look into it, but I don't think he got back to us --- the
> > lists went down not long after this got reported here.
> > I saw the first of them from my local NWS station today --- until today I'd
> > only seen them in APRS-IS feeds from more distant stations.  Here's a 
> > packet
> > that I got today yanked from my TNC log file:
> > # 1188253815  Mon Aug 27 16:30:15 MDT 2007
> > K5MJE-2>APJI23,CEDRO,RAVEN*,WIDE3-1:}ABQSVR>APRS,TCPIP,K5MJE-2*:;ABQS2131z_272230z3458.80NS09553.40WWCenter 
> > of MaxConcern }d0dV?V?V?S?S?U?V??V{RLVAK
> > There are non-printable characters in there that may or may not make it 
> > through
> > in this email.  Gerry, wassup with this?  Are you aware of a change to the
> > WXSVR multiline protocol that we need to code up?  The multiline protocol
> > documentation page at 
> > http://home.earthlink.net/~kg5qd/APRS_Multiline_Protocol.html
> > is not responding anymore, and the cached version on google just shows
> > the protocol we are already supporting.
> 
>  -- 
>  Gerry Creager -- gerry.creager at tamu.edu
>  Texas Mesonet -- AATLT, Texas A&M University	
>  Cell: 979.229.5301 Office: 979.458.4020 FAX: 979.862.3983
>  Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843
>  _______________________________________________
>  Xastir mailing list
>  Xastir at xastir.org
>  http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick