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
20171122043630EW7252>APRS,TCPXX*,qAX,CWOP-7:/220452z000.00N/0000.00E_359/006g010t044P000b09894h40cwMServer
20171122044950EW7252>APRS,TCPXX*,qAX,CWOP-7:/220505z000.00N/0000.00E_021/008g013t044P000b09894h39cwMServer
20171122045630EW7252>APRS,TCPXX*,qAX,CWOP-4:/220512z000.00N/0000.00E_011/008g014t043P000b09894h39cwMServer
20171122050310EW7252>APRS,TCPXX*,qAX,CWOP-7:/220518z000.00N/0000.00E_005/009g014t043P000b09894h38cwMServer
20171122050950EW7252>APRS,TCPXX*,qAX,CWOP-4:/220525z000.00N/0000.00E_014/006g013t043P000b09897h38cwMServer
20171122051631EW7252>APRS,TCPXX*,qAX,CWOP-5:/220532z000.00N/0000.00E_007/006g011t042P000b09901h39cwMServer
20171122052310EW7252>APRS,TCPXX*,qAX,CWOP-5:/220538z000.00N/0000.00E_354/006g010t042P000b09901h40cwMServer
20171122052950EW7252>APRS,TCPXX*,qAX,CWOP-7:/220545z000.00N/0000.00E_007/005g010t042P000b09904h40cwMServer