APRS Packet Errors for EDDC-met (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
20260209100540	DK6PX>APRS,TCPIP,qAC,T2SPAIN:;EDDC-met 201218z5107.73N/01345.81E^ EDDC 090950Z AUTO 11005KT 9000 FEW008 OVC023 02/01 Q1010 TEMPO BKN011
20260209110540	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;EDDC-met 201218z5107.73N/01345.81E^ EDDC 091050Z AUTO 11006KT 9999 BKN010 BKN027 03/01 Q1010 NOSIG
20260209120539	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDC-met 201218z5107.73N/01345.81E^ EDDC 091150Z AUTO 12005KT 080V160 9999 BKN010 OVC029 04/01 Q1010 NOSIG
20260209130539	DK6PX>APRS,TCPIP,qAC,T2POLNW:;EDDC-met 201218z5107.73N/01345.81E^ EDDC 091250Z AUTO 13004KT 080V160 9999 SCT012 OVC029 04/01 Q1009 TEMPO BKN012
20260209140540	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDC-met 201218z5107.73N/01345.81E^ EDDC 091350Z AUTO 12006KT 090V150 9999 BKN013 OVC029 04/02 Q1009 TEMPO SCT013
20260209150540	DK6PX>APRS,TCPIP,qAC,T2FINLAND:;EDDC-met 201218z5107.73N/01345.81E^ EDDC 091450Z AUTO 11006KT 090V150 9999 BKN014 OVC029 04/01 Q1009 BECMG BKN015