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
20170626081552W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_022/000g000t047OD1w
20170626090515W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_022/000g000t047OD1w
20170626091857W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_022/000g000t047OD1w
20170626093238W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_022/000g000t046OD1w
20170626101603W0GC-3>APOTC1,W0GC-2*,qAR,N0QXM-1:!4444.81N/09650.05_022/000g000t047OD1w
20170626102104W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.8N/09650.05W_022/000g000t047OD1w
20170626111549W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.81/09650.05W_022/000g000t050OD1w
20170626113240W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_022/000g000t052OD1w
20170626122625W0GC-3>APOTC1,KD0MC-2,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_022/000g000t058OD1w
20170626132523W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_022/000g000t062OD1w
20170626133038W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.1N/09650.05W_022/000g000t062OD1w