APRS Packet Errors for ED7YAL-3 (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
20170428233546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429000546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429003546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429010546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429013546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429020546ED7YAL-3>APRS,RELAY,WIDE1-1,WIDE2-1,qAR,ED7ZAD-3:!3744.02N/00331.07W
20170429023546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429030546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429033546ED7YAL-3>APRS,RELAY,WIDE1-1,WIDE2-1,qAR,ED7ZAD-3:!3744.02N/00331.07W
20170429040546ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170429043546ED7YAL-3>APRS,RELAY,WIDE1-1,WIDE2-1,qAR,ED7ZAD-3:!3744.02N/00331.07W
20170429050546ED7YAL-3>APRS,RELAY,WIDE1-1,WIDE2-1,qAR,ED7ZAD-3:!3744.02N/00331.07W