APRS Packet Errors for XE2SI-9 (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
20171020054453XE2SI-9>APT311,XE2GF-10,WIDE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/054448h3231.52N/)1700.21W(062/000/A=000249
20171020062949XE2SI-9>APL311,XE2GF-10,WIDE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/062944h3231.6)N/11700.20W(223/000/A=000305
20171020064447XE2SI-9>APT311,XE2GF-10,WIDE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/064442h3231.61N/11700.207(014/000/A=000446
20171020071914XE2SI-9>APT311,XE2GF-10,WIHE1,KF6ILA-10,WIDE2*,qAR,WD6DRI-1:/071909h3231.6)N/)1700.20W(195/000/A=000305
20171020073542XE2SI-9>A0T311,XE2GF-10,WIDE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/073537h323).61N/11700.21W(201/000/A=000396
20171020085035XE2SI-9>APT311,XE2GF-10,WIDE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/085030h323.61N/11700.21W(132/000/A=000403
20171020092930XE2SI-9>APT311,XE2GF-10,WIBE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/092926h32+1.61N/11700.20W(206/000/A=000383
20171020095927XE2SI-9>APT311,XE2GF-10,WIDE1,KF6ILA-10,WIDE2*,qAR,AG6IF-1:/095923h323).62N/11700.21W(332/000/A=000485