APRS Packet Errors for dw6699 (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
20171215154100dw6699>APRS,TCPXX*,qAX,CWOP-5:@151540z3239.86N/09810.100W_028/000g000t043P000h61b10201ws31
20171215155100dw6699>APRS,TCPXX*,qAX,CWOP-5:@151550z3239.86N/09810.100W_005/002g000t044P000h59b10203ws31
20171215160100dw6699>APRS,TCPXX*,qAX,CWOP-5:@151601z3239.86N/09810.100W_037/000g000t045P000h58b10202ws31
20171215161100dw6699>APRS,TCPXX*,qAX,CWOP-5:@151611z3239.86N/09810.100W_360/000g000t046P000h56b10201ws31
20171215162059dw6699>APRS,TCPXX*,qAX,CWOP-5:@151620z3239.86N/09810.100W_355/000g000t047P000h53b10199ws31
20171215200100dw6699>APRS,TCPXX*,qAX,CWOP-4:@152001z3239.86N/09810.100W_332/004g000t056P000h32b10165ws31
20171215201100dw6699>APRS,TCPXX*,qAX,CWOP-4:@152011z3239.86N/09810.100W_336/000g000t055P000h32b10163ws31
20171215202101dw6699>APRS,TCPXX*,qAX,CWOP-4:@152021z3239.86N/09810.100W_022/000g000t056P000h32b10164ws31
20171215203100dw6699>APRS,TCPXX*,qAX,CWOP-4:@152031z3239.86N/09810.100W_011/000g000t056P000h31b10163ws31
20171215204101dw6699>APRS,TCPXX*,qAX,CWOP-4:@152041z3239.86N/09810.100W_360/000g000t057P000h31b10161ws31
20171215205100dw6699>APRS,TCPXX*,qAX,CWOP-4:@152051z3239.86N/09810.100W_360/000g000t055P000h31b10159ws31
20171215210100dw6699>APRS,TCPXX*,qAX,CWOP-4:@152100z3239.86N/09810.100W_360/000g000t056P000h31b10158ws31