APRS Packet Errors for EW6247 (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
20190615214253EW6247>APRS,TCPXX*,qAX,CWOP-5:@152142z0000.00N/00000.00E_129/001g002t069r054p061P061h93b10075eCumulusDsVP
20190615215152EW6247>APRS,TCPXX*,qAX,CWOP-7:@152151z0000.00N/00000.00E_157/000g002t070r052p061P061h94b10076eCumulusDsVP
20190615220053EW6247>APRS,TCPXX*,qAX,CWOP-2:@152200z0000.00N/00000.00E_157/000g001t070r050p061P061h95b10074eCumulusDsVP
20190615220953EW6247>APRS,TCPXX*,qAX,CWOP-2:@152209z0000.00N/00000.00E_110/001g003t070r040p061P061h95b10072eCumulusDsVP
20190615221853EW6247>APRS,TCPXX*,qAX,CWOP-2:@152218z0000.00N/00000.00E_055/001g003t070r012p061P061h95b10072eCumulusDsVP
20190615222753EW6247>APRS,TCPXX*,qAX,CWOP-5:@152227z0000.00N/00000.00E_052/001g002t071r002p061P061h94b10070eCumulusDsVP
20190615223653EW6247>APRS,TCPXX*,qAX,CWOP-3:@152236z0000.00N/00000.00E_050/001g002t071r000p061P061h94b10069eCumulusDsVP
20190615224553EW6247>APRS,TCPXX*,qAX,CWOP-3:@152245z0000.00N/00000.00E_054/001g003t071r000p061P061h94b10066eCumulusDsVP