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
20190322040615WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,WIDE2*,qAR,CEDAR:=0000.00N/00000.00W_141/003g t033r000p000P h62b10186KDvs
20190322043613WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,WIDE2*,qAR,CEDAR:=0000.00N/00000.00W_142/003g t032r000p000P h64b10189KDvs
20190322050613WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,WIDE2*,qAR,CEDAR:=0000.00N/00000.00W_240/005g t034r000p000P h58b10193KDvs
20190322053614WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,WIDE2*,qAR,CEDAR:=0000.00N/00000.00W_225/005g t035r000p000P h58b10190KDvs
20190322060615WB7BKM-13>APK102,WALDEN,WIDE1,ERIDGE,WIDE2*,qAR,CEDAR:=0000.00N/00000.00W_222/002g t034r000p000P h63b10182KDvs