APRS Packet Errors for EW8932 (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
20170622231816EW8932>APRS,TCPXX*,qAX,CWOP-4:@222318z0000.00N/00000.00E_341/006g023t101P000h12b09972L107ws31
20170622232816EW8932>APRS,TCPXX*,qAX,CWOP-1:@222328z0000.00N/00000.00E_314/006g017t101P000h12b09972L524ws31
20170623035816EW8932>APRS,TCPXX*,qAX,CWOP-3:@230358z0000.00N/00000.00E_294/005g013t090P000h19b09993L000ws31
20170623040816EW8932>APRS,TCPXX*,qAX,CWOP-7:@230408z0000.00N/00000.00E_315/000g011t090P000h19b09996L000ws31
20170623041816EW8932>APRS,TCPXX*,qAX,CWOP-6:@230418z0000.00N/00000.00E_360/002g008t089P000h19b09997L000ws31
20170623042816EW8932>APRS,TCPXX*,qAX,CWOP-7:@230428z0000.00N/00000.00E_360/000g006t089P000h19b09999L000ws31
20170623043816EW8932>APRS,TCPXX*,qAX,CWOP-3:@230438z0000.00N/00000.00E_360/005g006t088P000h20b10000L000ws31
20170623044816EW8932>APRS,TCPXX*,qAX,CWOP-4:@230448z0000.00N/00000.00E_258/002g011t087P000h21b10001L000ws31
20170623045816EW8932>APRS,TCPXX*,qAX,CWOP-6:@230458z0000.00N/00000.00E_360/003g009t087P000h22b10003L000ws31
20170623050816EW8932>APRS,TCPXX*,qAX,CWOP-4:@230508z0000.00N/00000.00E_288/002g008t087P000h21b10003L000ws31