APRS Packet Errors for NOCJN (last 24 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
20180919041419NOCJN>APK102,N0AGI-1,WIDE1,N0HOY-10*,WIDE2,qAR,N0TOR-10:=4517.72/0936.4802g t060r00p00P h8Kvs
20180919052417NOCJN>APK102,N0HOY-10*,WIDE2-1,qAR,N0TOR-10:=4517.72N/093644W7/ 0000P h04KDvs
20180919062431NOCJN>APK102,N0AGI-1,WIDE1,N0HOY-10*,WIDE2,qAR,N0TOR-10:=517.72N/09336.44W_070/004g t059r000p000P h67b10147KDvs
20180919133450NOCJN>APK102,N0AGI-1,WIDE1,N0HOY-10*,WIDE2,qAR,N0TOR-10:=4517.72N09336.44W_038/003g t055r004p006P h71b10158KDvs
20180919163507NOCJN>APK102,N0AGI-1,WIDE1,N0HOY-10*,WIDE2,qAR,N0TOR-10:=4517.72N/09336.44W_05/06P h71b10151KDvs