APRS Packet Errors for DW4782 (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
20181210134008DW4782>APRS,TCPXX*,qAX,CWOP-5:@101340z0000.00N/00000.00E_085/008g013t050r000p034P034h77b10037eCumulusDsVP
20181210135009DW4782>APRS,TCPXX*,qAX,CWOP-2:@101350z0000.00N/00000.00E_252/004g012t048r000p034P034h79b10041eCumulusDsVP
20181210140010DW4782>APRS,TCPXX*,qAX,CWOP-5:@101400z0000.00N/00000.00E_194/005g010t047r000p034P034h81b10041eCumulusDsVP
20181210141012DW4782>APRS,TCPXX*,qAX,CWOP-7:@101410z0000.00N/00000.00E_204/006g008t047r000p034P034h81b10043eCumulusDsVP
20181210142014DW4782>APRS,TCPXX*,qAX,CWOP-1:@101420z0000.00N/00000.00E_273/001g003t047r000p034P034h83b10043eCumulusDsVP
20181210143016DW4782>APRS,TCPXX*,qAX,CWOP-1:@101430z0000.00N/00000.00E_266/002g005t047r000p034P034h85b10045eCumulusDsVP
20181210144017DW4782>APRS,TCPXX*,qAX,CWOP-4:@101440z0000.00N/00000.00E_292/001g003t047r000p034P034h86b10046eCumulusDsVP
20181210145018DW4782>APRS,TCPXX*,qAX,CWOP-4:@101450z0000.00N/00000.00E_263/003g007t046r000p034P034h86b10049eCumulusDsVP