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
20170625132315W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_315/000g000t060OD1w
20170625143031W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.81N/0650.05W_315/000g000t063OD1w
20170625143753W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_315/000g000t063OD1w
20170625145649W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_315/000g000t062OD1w
20170625152718W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_297/000g000t063OD1w
20170625155953W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t063OD1w
20170625161952W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t066OD1w
20170625163332W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t066OD1w
20170625163538W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t066OD1w
20170625175223W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_318/000g000t067OD1w
20170625175533W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.8N/09650.05W_327/000g000t067OD1w