APRS Packet Errors for EDDS (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
20260209130541DK6PX>APRS,TCPIP*,qAC,T2POLNW:;EDDS *201218z4841.33N/00912.00E^ EDDS 091250Z AUTO 09006KT 050V120 9999 OVC018 05/01 Q1005 NOSIG
20260209140543DK6PX>APRS,TCPIP*,qAC,T2ROMANIA:;EDDS *201218z4841.33N/00912.00E^ EDDS 091350Z AUTO 08007KT 050V110 9999 OVC019 05/01 Q1005 NOSIG
20260209150541DK6PX>APRS,TCPIP*,qAC,T2FINLAND:;EDDS *201218z4841.33N/00912.00E^ EDDS 091450Z AUTO 08007KT CAVOK 05/01 Q1005 NOSIG
20260209160557DK6PX>APRS,TCPIP*,qAC,T2CSNGRAD:;EDDS *201218z4841.33N/00912.00E^ EDDS 091550Z AUTO 07007KT 9999 FEW029 04/01 Q1005 NOSIG
20260209170541DK6PX>APRS,TCPIP*,qAC,T2SWEDEN:;EDDS *201218z4841.33N/00912.00E^ EDDS 091650Z AUTO 08005KT CAVOK 03/00 Q1005 NOSIG
20260209180541DK6PX>APRS,TCPIP*,qAC,T2ERFURT:;EDDS *201218z4841.33N/00912.00E^ EDDS 091750Z AUTO 09004KT CAVOK 01/M00 Q1004 NOSIG