APRS Packet Errors for CDS (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
20180814093153CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814094153CDS>BEACON,qAR,KE5PL-1:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814095153CDS>BEACON,qAR,BIGROK:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814100153CDS>BEACON,qAR,KE5PL-1:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814101153CDS>BEACON,qAR,KE5PL-1:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814102154CDS>BEACON,qAR,KG5BQX-10:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814103153CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814104153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814105153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814111153CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814112154CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814113153CDS>BEACON,qAR,BIGROK:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814114153CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814115153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814120153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814121156CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814123153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814124153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814125154CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814131153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814132153CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814135153CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814140154CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814141153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814142153CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814143154CDS>BEACON,qAR,KE5KUL:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814145154CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net
20180814150154CDS>BEACON,qAR,N5LEA:;146.52a*3426.19n/10013.37w/Childress TX de NL7C nl7c@arrl.net