APRS Packet Errors for EW0236 (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
20190117003532EW0236>APRS,TCPXX*,qAX,CWOP-3:@170035z0000.00N/00000.00E_278/002g005t037r000p017P000h90b09826eCumulusFO
20190117004432EW0236>APRS,TCPXX*,qAX,CWOP-2:@170044z0000.00N/00000.00E_268/000g005t036r000p017P000h90b09825eCumulusFO
20190117005332EW0236>APRS,TCPXX*,qAX,CWOP-3:@170053z0000.00N/00000.00E_279/000g003t036r000p017P000h89b09826eCumulusFO
20190117010232EW0236>APRS,TCPXX*,qAX,CWOP-2:@170102z0000.00N/00000.00E_285/000g004t036r000p017P000h89b09826eCumulusFO
20190117011132EW0236>APRS,TCPXX*,qAX,CWOP-6:@170111z0000.00N/00000.00E_298/002g004t036r000p017P000h89b09828eCumulusFO