<html><head></head><body><div class="ydpa2698a55yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div>See embedded comments below<br></div><div><br></div>
</div><div id="ydpaa47cdeeyahoo_quoted_3349810837" class="ydpaa47cdeeyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, March 22, 2019, 5:14:50 PM EDT, Jim (List) <jim.list@stuckinthemud.org> wrote:
</div>
<div><div dir="ltr">>Looking for help from someone experienced in parsing ARPS beacons to assist<br></div><div dir="ltr">>in understanding differences in the position beacons I'm seeing from various<br></div><div dir="ltr">>stations.<br></div><div dir="ltr">><br></div>>Are these differences recent changes to the APRS spec, or are they clients<br><div dir="ltr">>that are just sending bad data?<br></div><div dir="ltr"><br></div><div dir="ltr">From looking at your examples (and similar ones I have seen), they all look like</div><div dir="ltr">typos from hand-creating beacon messages.</div><div dir="ltr"><br></div><div dir="ltr">>Monitored beacons are listed below, with a note of what I'm seeing wrong.<br></div><div dir="ltr">><br></div><div dir="ltr">>K3NAL-1>BEACON,qAR,KK4ZWW-1:!146.64-000000z3812.05n/07623.07WrT146 R25 NetTu<br></div><div dir="ltr">>1930 Mtg 4th Th<br></div><div dir="ltr">>*** Appears to have a frequency, a dash and a time inserted before the Lat,<br></div><div dir="ltr">>plus the Lat letter is in lower case <br></div><div dir="ltr"><br></div><div dir="ltr"><div>This looks like someone is trying to send an Item (timestamped non-station Object) for a repeater</div><div>rather than a self-beacon, but they used the prefix character "!" for a self-beacon rather than<br></div><div>")" for an Item, and they're missing the "!" between the Item name and the latitude to indicate</div><div>this is a live Item (or an "_" to indicate it's a dead Item).<br></div></div><div dir="ltr"><br></div><div dir="ltr">>W9GO-3>BEACON,qAR,KC9MWQ-1:!146.91-4028.82N/08609.33W# Kokomo Repeater Club<br></div><div dir="ltr">>*** Another with what looks like a frequency and a dash before the Lat<br></div><div dir="ltr"><br></div><div dir="ltr">Same as above, except they should have used ";" instead of "!" to indicate a non-timestamped</div><div dir="ltr">Object. Also the Object name (between the ";" and the latitude digits) is missing the extra space</div><div dir="ltr"> characters to pad the Object name out to 9 characters, plus the "*" character to indicate a live</div><div dir="ltr">Object or "_" to indicate a dead (out-of-service) Object.</div><div dir="ltr"><br></div><div dir="ltr">>SV1GCB-3>APMI06,SV3ISZ-11*,SOUTH2-1,qAR,SV3IRM-10:!222024S3704.18N/02225.79E<br></div><div dir="ltr">>#QTH T=18.5C, U=13.2V, WX3in1Plus2.0<br></div><div dir="ltr">>*** Has "222024S" inserted before Lat</div><div dir="ltr"><br></div><div dir="ltr">Looks like a timestamped Position Report for a digipeater, but they used the wrong prefix</div><div dir="ltr">character (should have been "@" or "/" for a timestamped position) and didn't use a standard</div><div dir="ltr"> time zone character on the end of the 6-digit timestamp; the allowed characters are</div><div dir="ltr"> 'z' or 'Z' (for UTC time in day-of-month, 24-hour, minute) or "/" or "l" (for site-local time, same format)</div><div dir="ltr">or "h" (for UTC time in hours/minutes/seconds).<br></div><div dir="ltr"><br></div><div dir="ltr">>WB5OER-2>APTT4,WX5II-3,WIDE1*,WIDE2-1,qAO,KG5YOV:!2847.0333N/09729.2666W#PHG<br></div><div dir="ltr">>71304/ 13.0V<br></div><div dir="ltr">>*** Too many digits after the decimal in both Lat and Long<br></div><div dir="ltr"><br></div><div dir="ltr">Indeed. There is a different format where the extra digits of precision go in an encoding in the</div><div dir="ltr">free-text comment, but they aren't supported here.</div><div dir="ltr"><br></div><div dir="ltr">>W3EPE-3>APTT4,WIDE1-1,WIDE2-1,qAO,BEARCK:!4048.31N07531.34W#PHG51304/ W1 <br></div><div dir="ltr">>*** No symbol table ID<br></div><div dir="ltr"><br></div><div dir="ltr">Correct analysis; the symbol table ID character (after the "N") is missing.</div><div dir="ltr"><br></div><div dir="ltr">>POINT6>APN382,qAR,N6MLD-1:!4702.46NS11359.W#PHG5860/ 11,22,21,33 harc's pt6<br></div><div dir="ltr">>thanks mso wx.<br></div><div dir="ltr">>*** No digits after the Long decimal<br></div><div dir="ltr"><br></div><div dir="ltr">Correct analysis; the digits need to either be present or replaced with blanks for position</div><div dir="ltr">ambiguity.</div><div dir="ltr"><br></div><div dir="ltr">>OE3FRE-15>APNL51,TCPIP*,qAI,OE3FRE-15,SQ6KXY-2,T2DENMARK,T2HUB5,T2CAEAST:!48<br></div><div dir="ltr">>04.66NN/01618.46EE`Radiosondetracker<br></div><div dir="ltr">>*** Lat N/S and Long E/W duplicated<br></div><div dir="ltr"><br></div><div dir="ltr">Never seen the APRS-IS backbone report _all_ the servers the packet was relayed through before.</div><div dir="ltr">Analysis correct; why they doubled those characters, who knows?</div><div dir="ltr"><br></div><div dir="ltr">>DC1SK-15>APNL51,TCPIP*,qAI,DC1SK-15,SQ6KXY-1,T2BIO,T2HUB5,T2CAEAST:!5112.018<br></div><div dir="ltr">>N/01117.042E`Radiosonde Tracker - Based on kxyTrack 1.0-1805<br></div><div dir="ltr">>*** Too many digits after the decimal in both Lat and Long<br></div><div dir="ltr"><br></div><div dir="ltr">Again, correct analysis; they should use compressed-mode position or the extended-precision</div><div dir="ltr">token in the free-text comment if they want more digits of precision.</div><div dir="ltr"><br></div><div dir="ltr">>DO2ATR-10>APGW1K,TCPIP*,qAC,T2KA:!5005.05N/007 0.07E#DO2ATR iGate APRS<br></div><div dir="ltr">>432.500 JO30MU<br></div><div dir="ltr">>*** Spaces in the Long that don't conform to position ambiguity<br></div><div dir="ltr"><br></div><div dir="ltr">Correct analysis.</div><div dir="ltr"><br></div><div dir="ltr">>Jim, G1HUL<br></div><div><br></div><div>Amazing, the amount of bends you need to put into parsing code to handle the non-standard</div><div>formats.</div><div><br></div><div>Andrew, KA2DDO</div><div>author of YAAC ("Yet Another APRS Client"), which has to do all of that parsing<br></div></div>
</div>
</div></body></html>