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
20170625085052W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t046OD1w
20170625091050W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t045OD1w
20170625095501W0GC-3>APOTC1,W0GC-2*,qAR,N0QXM-1:!4444.81N/0950.05W_315/000g000t045OD1w
20170625105252W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_315/000g000t045OD1w
20170625113044W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.81N/0950.05W_315/000g000t049OD1w
20170625114733W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!4444.81N/0965005W_315/000g000t051OD1w
20170625122113W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t056OD1w
20170625123905W0GC-3>APOTC1,WIDE1-1,qAR,N0QXM-1:!4444.81N/0950.05W_315/000g000t058OD1w
20170625125141W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t058OD1w
20170625130521W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444.81N/09650.05W_315/000g000t059OD1w
20170625132315W0GC-3>APOTC1,NY0I-6,WIDE1*,qAR,N0QXM-1:!444481N/09650.05W_315/000g000t060OD1w