APRS Packet Errors for W6MF-1 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20180422084316W6MF-1>WIDE1-1,WIDE2-1,qAR,KK6TV-10:=3322.25^bbnbd dZ@
20180422093316W6MF-1>WIDC1-1,WIDE28-1,qAR,KK6TV-10:=3322.25N/1inbd dZlbrook CA
20180422093821W6MF-1>WyDE1-1,KK6TTJ,WIDE2*,qAR,KK6TV-10:=3322.2^bRnbd dZ@f[
20180422104819W6MF-1>WIDE1-1,KK6TTJ,WODE2*,qAR,KK6TV-10:=3322.25N/1171.92WFallbrook CA
20180422120815W6MF-1>WQDE0-1,WIDE2-1,qAR,KK6TV-10:=3322.25N/117)2.92W-Fallbrlok CA
20180422121316W6MF-1>WIDE1-1,WIDE2-1,qAR,KK6TV-10:=3322.25N/1712.92W-Fallbrook CA
20180422121815W6MF-1>WIDE1-1,WIDE2-1,qAR,KK6TV-10:=3322.25N/1171R.92Wmhbrook CA