APRS Packet Errors for EW66880 (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
20170529134218EW66880>APRS,TCPXX*,qAX,CWOP-7:@291342z0000.00N/00000.00E_298/000g001t080P000h67b10140ws31
20170529144218EW66880>APRS,TCPXX*,qAX,CWOP-6:@291442z0000.00N/00000.00E_289/000g006t082P000h65b10144ws31
20170529154219EW66880>APRS,TCPXX*,qAX,CWOP-5:@291542z0000.00N/00000.00E_357/000g006t084P000h54b10151ws31
20170529164219EW66880>APRS,TCPXX*,qAX,CWOP-5:@291642z0000.00N/00000.00E_344/001g007t085P000h50b10151ws31
20170529174219EW66880>APRS,TCPXX*,qAX,CWOP-4:@291742z0000.00N/00000.00E_344/000g006t087P000h47b10147ws31
20170529184219EW66880>APRS,TCPXX*,qAX,CWOP-5:@291842z0000.00N/00000.00E_279/002g007t088P000h49b10146ws31