APRS Packet Errors for EW5954 (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
20170622231719EW5954>APRS,TCPXX*,qAX,CWOP-4:@222317z0000.00N/00000.00E_013/000g004t079P012h74b10064ws31
20170622232719EW5954>APRS,TCPXX*,qAX,CWOP-5:@222327z0000.00N/00000.00E_079/000g003t079P012h75b10064ws31
20170623035719EW5954>APRS,TCPXX*,qAX,CWOP-7:@230357z0000.00N/00000.00E_193/000g006t073P012h85b10050ws31
20170623040720EW5954>APRS,TCPXX*,qAX,CWOP-5:@230407z0000.00N/00000.00E_340/001g003t072P000h86b10049ws31
20170623041719EW5954>APRS,TCPXX*,qAX,CWOP-1:@230417z0000.00N/00000.00E_269/001g006t072P000h87b10048ws31
20170623042720EW5954>APRS,TCPXX*,qAX,CWOP-6:@230427z0000.00N/00000.00E_352/003g006t072P000h87b10048ws31
20170623043719EW5954>APRS,TCPXX*,qAX,CWOP-4:@230437z0000.00N/00000.00E_281/001g007t072P000h86b10047ws31
20170623044720EW5954>APRS,TCPXX*,qAX,CWOP-5:@230447z0000.00N/00000.00E_356/000g004t073P000h86b10046ws31
20170623045719EW5954>APRS,TCPXX*,qAX,CWOP-4:@230457z0000.00N/00000.00E_268/000g006t073P000h86b10045ws31
20170623050719EW5954>APRS,TCPXX*,qAX,CWOP-6:@230507z0000.00N/00000.00E_328/000g006t073P000h86b10046ws31