[aprssig] chewed-up APRS messages

[Andrew P.]

Greetings, all.

I've been looking at APRS messages I've been receiving, and noticing an alarming tendency towards mangled messages. It can't be just from my software not keeping up with the serial data stream, because I'm getting this on APRS-IS server connections (which, by their nature as TCP/IP connections, can't drop bytes in mid-stream). So, is there that great a frequency of garbled packets out there being forwarded by I-gates, or do we just have sloppy software (or sloppy manual data entry) putting garbaged messages out there? Here's some examples:

KA1GJU-3>APN382,UNCAN,WIDE2*,qAR,W1CLA-1:!!06 0F02 at 000-,-----(--,-- 02035 00000"7

WV9E>APW249,KC9DGP-10,N9MEA-6,K9ABC-1,WIDE3*,qAR,N9MXT-10:_113P0414c11s000g(00t032r000p0<0P000h30b09930wRS�


$GPRMC,11,A,4458.2127,N,08720.8152,W,0.000,0.0,120,2.2, W 

WA9KJE-1>APU25N,WA9+JI,AB9FX-1,K9MOT-15*,qAR,N9MXT-10:@28163z4159.74N/08741.51W_22�.<00�100t040r000P000p000h87b10173/WX Chicago-Peet2100-All Sensors Nominal

DB0DLG-1>APNU19,WIDE2-2,qAS,DB3MA-2:!4830.78N10102�222

AB9FX-1>APNW01,KA9SCF-15,K9SA*,WIDE2,qAR,N9MXT-10:/2;1412z4156.52NT08745.66W&PHG4180 wx3in1 A=650�

WX0U-1>APN382,K0SUN-13,ETULSA,CLRWTR,WIDE3*,qAR,AC0JK-5:;HAMEXAM03*111111/3824.90N\09610.88W

KY2O-4>APTT4,K4AG-6,W4NVU-4,WIDE2*,WIDE2-1,qAS,N9LCK-10:!2505.77N/08026
51W-Key Largo Fill+in Digi

OE6PWE-11>APRSOE,TRACE3-3,qAS,OE6XLR-10:!4734.11N/014�4.5

G6UIM>APWW08,TCPP*,OZ1AHV-2*,qAR,OZ1AHV-2:;G3TQ/6  *11115026.94N/00334.92Wr050.750MHz T077 1.5M GB3TQ PAIGTON G0AZX!w+G!


Any suggestions for dealing with such packets would be appreciated.

Andrew Pavlin, KA2DDO
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20111128/b69aa085/attachment.html>