[aprssig] Long messages

[VE7GDH]

Scott N1VG wrote...

> I've been reworking my old APRS IS parser, and I'm finding a lot of
> overly long messages, like this one:
>
> KD5YOV-14>APU25N,TCPIP*,qAC,AHUBSWE::KC4JGC   :5.3 miles northeast of
> Norfolk, VA --- Report received 15 minutes 59 seconds ago {21
>
> The spec gives a maximum length of 67 characters for a message. That one
> is 81 characters, counting the trailing space.  Was the spec revised at
> some point, or do clients just ignore it?  Makes it hard to know how big
> a database field is required to store it...

Looking at http://map.findu.com/KD5YOV-14 and
http://www.findu.com/cgi-bin/raw.cgi?call=KD5YOV-14&time=1

There's something odd going on. First, Bryan KD5YOV is asking over on the
UI-View list why he seen sometimes moving at fantastic speeds and showing up
off the coast of Africa. He is using a D700, sometimes with UI-View and
sometimes with the D700 "stand-alone" and apparently at other times using
"something else" as well that is beaconing to "GPS" with NMEA $GPRMC
sentences and also sometimes to "APK101"...

20070126015731,KD5YOV-14>APK101,WIDE1-1,KB4TOH-4,WIDE2*,qAo,KG7SB-3::KC4JGC
:SORRY I ONLY RESPOND WHEN UI-VIEW IS ON, AT THIS TIME IT IS OFF.

What sends to "APK101"? That might help track what down is sending the long
messages.

I hadn't noticed it before, but yes, that's a whole lot of characters. He
isn't having a UI-View problem in my opinion, so he might be better off
asking over on this list. I posted a reply to the UI-View list with my
observations a while back, but it hasn't been echoed back to me by the
list yet.

73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"