APRS Packet Errors for DW8263 (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
20170622230449DW8263>APRS,TCPXX*,qAX,CWOP-5:@222304z0000.00N/00000.00E_071/000g001t043P000h86b10100ws31
20170622231449DW8263>APRS,TCPXX*,qAX,CWOP-5:@222314z0000.00N/00000.00E_071/000g001t043P000h86b10100ws31
20170622232449DW8263>APRS,TCPXX*,qAX,CWOP-5:@222324z0000.00N/00000.00E_068/000g001t043P000h85b10100ws31
20170623035449DW8263>APRS,TCPXX*,qAX,CWOP-5:@230354z0000.00N/00000.00E_092/000g003t045P000h81b10096ws31
20170623040450DW8263>APRS,TCPXX*,qAX,CWOP-5:@230404z0000.00N/00000.00E_109/000g003t045P000h80b10095ws31
20170623041449DW8263>APRS,TCPXX*,qAX,CWOP-5:@230414z0000.00N/00000.00E_103/001g004t045P000h80b10095ws31
20170623042449DW8263>APRS,TCPXX*,qAX,CWOP-5:@230424z0000.00N/00000.00E_102/001g003t045P000h79b10095ws31
20170623043449DW8263>APRS,TCPXX*,qAX,CWOP-5:@230434z0000.00N/00000.00E_081/000g003t045P000h78b10095ws31
20170623044450DW8263>APRS,TCPXX*,qAX,CWOP-5:@230444z0000.00N/00000.00E_053/001g003t045P000h78b10095ws31
20170623045449DW8263>APRS,TCPXX*,qAX,CWOP-5:@230454z0000.00N/00000.00E_073/001g004t045P000h78b10095ws31