APRS Packet Errors for W0GC-3 (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
20170819043006W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t058OD1w
20170819045213W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t058OD1w
20170819052801W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_000/000g000t058OD1w
20170819054350W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t058OD1w
20170819055316W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.1N/09650.05W_000/000g000t058OD1w
20170819055836W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t058OD1w
20170819061528W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_000/000g000t058OD1w
20170819062703W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t058OD1w
20170819063641W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_000/000g000t058OD1w
20170819070049W0GC-3>APOTC1,WIDE1-1,qAR,N0QXM-1:!4444.81N/0950.05W_000/000g000t057OD1w
20170819075029W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t057OD1w
20170819083042W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t055OD1w
20170819091051W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_000/000g000t057OD1w