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
20260208130541	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;EDDS 201218z4841.33N/00912.00E^ EDDS 081250Z AUTO 09007KT 060V130 9999 BKN016 07/03 Q1007 NOSIG
20260208140542	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDS 201218z4841.33N/00912.00E^ EDDS 081350Z AUTO 10005KT 060V140 9999 OVC016 07/03 Q1006 NOSIG
20260208150541	DK6PX>APRS,TCPIP,qAC,T2CZECH:;EDDS 201218z4841.33N/00912.00E^ EDDS 081450Z AUTO 11004KT 070V160 9999 BKN018 07/03 Q1006 NOSIG
20260208160557	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;EDDS 201218z4841.33N/00912.00E^ EDDS 081550Z AUTO VRB02KT 9999 FEW020 06/03 Q1006 NOSIG
20260208170542	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDDS 201218z4841.33N/00912.00E^ EDDS 081650Z AUTO 18001KT 9999 BKN023 05/02 Q1006 NOSIG
20260208180541	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDDS 201218z4841.33N/00912.00E^ EDDS 081750Z AUTO VRB02KT 9999 OVC024 05/02 Q1007 NOSIG