APRS Packet Errors for CW8264 (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
20180224182806CW8264>APRS,TCPXX*,qAX,CWOP-1:@241827z0000.00N/00000.00E_000/000g001t048r006p012P012h91b09886eCumulusDsVP
20180224183706CW8264>APRS,TCPXX*,qAX,CWOP-1:@241836z0000.00N/00000.00E_000/000g002t048r005p012P012h91b09881eCumulusDsVP
20180224184606CW8264>APRS,TCPXX*,qAX,CWOP-4:@241845z0000.00N/00000.00E_000/000g002t048r005p012P012h91b09884eCumulusDsVP
20180224185506CW8264>APRS,TCPXX*,qAX,CWOP-5:@241854z0000.00N/00000.00E_052/001g004t048r004p012P012h91b09886eCumulusDsVP
20180224190406CW8264>APRS,TCPXX*,qAX,CWOP-6:@241903z0000.00N/00000.00E_289/001g004t048r003p012P013h91b09886eCumulusDsVP
20180224191307CW8264>APRS,TCPXX*,qAX,CWOP-1:@241912z0000.00N/00000.00E_000/000g002t048r005p015P015h91b09886eCumulusDsVP
20180224192206CW8264>APRS,TCPXX*,qAX,CWOP-2:@241921z0000.00N/00000.00E_000/000g002t048r004p015P015h91b09890eCumulusDsVP
20180224193107CW8264>APRS,TCPXX*,qAX,CWOP-3:@241930z0000.00N/00000.00E_000/000g002t048r004p016P016h91b09886eCumulusDsVP
20180224194006CW8264>APRS,TCPXX*,qAX,CWOP-6:@241939z0000.00N/00000.00E_224/001g003t048r005p017P017h91b09889eCumulusDsVP
20180224194906CW8264>APRS,TCPXX*,qAX,CWOP-7:@241948z0000.00N/00000.00E_214/001g005t048r005p017P017h91b09883eCumulusDsVP