APRS Packet Errors for WB7BKM-13 (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
20190418093946WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_247/008g t034r000p000P h64b10169KDvs
20190418103947WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_261/010g t034r000p000P h66b10170KDvs
20190418110949WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,SUNLGT,WIDE3*,qAR,SHEEP:=0000.00N/00000.00W_199/007g t035r000p000P h67b10171KDvs
20190418113950WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,SUNLGT,WIDE3*,qAR,SHEEP:=0000.00N/00000.00W_242/006g t036r000p000P h67b10170KDvs
20190418120948WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_149/006g t036r000p000P h68b10176KDvs
20190418123948WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_106/002g t036r000p000P h66b10179KDvs
20190418133949WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_323/004g t035r000p000P h67b10196KDvs
20190418140949WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_256/011g t036r000p000P h65b10200KDvs
20190418143950WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_150/003g t037r000p000P h64b10203KDvs
20190418150950WB7BKM-13>APK102,WALDEN,WIDE1,WERNER*,qAR,CEDAR:=0000.00N/00000.00W_092/002g t037r000p000P h60b10204KDvs