[Xastir] extract_multipoints: invalid value in (filtered) "Center of MaxConcern }d0`N M K M RAL {6JmAI": 0, -177

[Richard Polivka, N6NKO]

In checking the SPC forecasts for the next couple of days, testing 
fodder may be few and far between. Even then, stuff can still slip 
through. I can put BigBox to record all day and see what I pick up in 
the nets.

73 from 807,

Richard, N6NKO


Gerry Creager wrote:
> I watched it for a couple of more days after it last came up and it 
> started calming down.  I'll try to carve some time out on Monday.  
> What I need to identify if this is something with the latest build of 
> AWIPS or WarnGen being fed into the system.
>
> gerry
>
> Tom Russo wrote:
>> On Sat, Oct 06, 2007 at 02:12:09PM -0700, we recorded a 
>> bogon-computron collision of the <r.polivka at sbcglobal.net> flavor, 
>> containing:
>>> Here is the offending line:
>>>
>>> JSJSMW>APRS,qAS,WXSVR:;JSJM1948z*062145z1851.60NM05606.00WWCenter of 
>>> MaxConcern 
>>> }d0`N&#65533;M&#65533;K&#65533;M&#65533;R&#65533;L&#65533;{6JmAI
>>>
>>> The commas near the end were appearing as '?' but in black 
>>> (unprintable character?).
>>> Is this an issue with WXSVR or with whomever JSJ is?
>>
>> This is happening all over the place.  I see it dozens of times a 
>> day.  The
>> weather services are obviously using some new program that is generating
>> invalid characters in the multipoints.  Gerry was going to look into 
>> it, but
>> got busy.
>>
>> The wxsvr.net pages documenting the protocol haven't changed, but 
>> obviously
>> these weather sites are generating objects with multipoints that 
>> don't conform
>> to the published protocols.
>>
>