APRS Packet Errors for EDTL (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
20260208130703	DK6PX>APRS,TCPIP,qAC,T2CSNGRAD:;EDTL 201218z4821.56N/00749.54E^ EDTL 081250Z 03006KT 350V060 1100 R21/1600U BR OVC002 02/02 Q1007
20260208140608	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDTL 201218z4821.56N/00749.54E^ EDTL 081350Z 36007KT 1300 R21/P2000D BR OVC002 03/03 Q1007
20260208150632	DK6PX>APRS,TCPIP,qAC,T2CZECH:;EDTL 201218z4821.56N/00749.54E^ EDTL 081450Z 36005KT 310V040 0900 R21/1100N FG OVC001 02/02 Q1007
20260208160632	DK6PX>APRS,TCPIP,qAC,T2FRANCE:;EDTL 201218z4821.56N/00749.54E^ EDTL 081550Z VRB03KT 0600 R21/0800N FG OVC001 03/03 Q1007
20260208170649	DK6PX>APRS,TCPIP,qAC,T2ROMANIA:;EDTL 201218z4821.56N/00749.54E^ EDTL 081650Z 00000KT 0550 R21/0700N FG OVC000 03/03 Q1008
20260208180608	DK6PX>APRS,TCPIP,qAC,T2DENMARK:;EDTL 201218z4821.56N/00749.54E^ EDTL 081750Z AUTO 16002KT 0700 R21/0900N // VV/// 03/03 Q1008