APRS Packet Errors for EW7252 (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
20190615215747EW7252>APRS,TCPXX*,qAX,CWOP-3:/152157z000.00N/0000.00E_229/015g022t082P000b09779h58cwMServer
20190615220427EW7252>APRS,TCPXX*,qAX,CWOP-4:/152204z000.00N/0000.00E_227/012g022t082P000b09779h59cwMServer
20190615221747EW7252>APRS,TCPXX*,qAX,CWOP-5:/152217z000.00N/0000.00E_225/011g019t083P000b09779h60cwMServer
20190615223107EW7252>APRS,TCPXX*,qAX,CWOP-3:/152231z000.00N/0000.00E_228/014g026t082P000b09775h59cwMServer
20190615224427EW7252>APRS,TCPXX*,qAX,CWOP-5:/152244z000.00N/0000.00E_223/013g022t082P000b09775h59cwMServer
20190615230427EW7252>APRS,TCPXX*,qAX,CWOP-4:/152304z000.00N/0000.00E_225/012g019t082P000b09775h60cwMServer
20190615231747EW7252>APRS,TCPXX*,qAX,CWOP-3:/152317z000.00N/0000.00E_214/007g020t081P000b09775h61cwMServer