APRS Packet Errors for EDTY (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
20260208150712	DK6PX>APRS,TCPIP,qAC,T2CZECH:;EDTY 010113z4907.05N/00946.77E^ EDTY 081450Z 09005KT 9999 OVC012 05/04 Q1007
20260208160727	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;EDTY 010113z4907.05N/00946.77E^ EDTY 081550Z 07003KT 9999 FEW017 05/03 Q1007
20260208170800	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDTY 010113z4907.05N/00946.77E^ EDTY 081650Z 04003KT 9999 BKN020 03/02 Q1007
20260208180703	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDTY 010113z4907.05N/00946.77E^ EDTY 081750Z AUTO 09002KT 9999 // SCT021/// 02/02 Q1008
20260208190707	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDTY 010113z4907.05N/00946.77E^ EDTY 081850Z AUTO 06008KT 0700 0650 R10/1600D // VV/// 01/01 Q1008
20260208200741	DK6PX>APRS,TCPIP,qAC,T2UKRAINE:;EDTY 010113z4907.05N/00946.77E^ EDTY 081950Z AUTO 07006KT 0800 R10/1200U // VV/// 01/01 Q1009