<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-GB link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Thanks Bob (and others who have responded).<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Monitoring 1.7m beacons last night I found 1500 that were duff, so happy to just reject the 0.1% that don’t conform.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>What is noticeable is there seems a common theme amongst the bad packets, in that they are being generated by a few buggy bits of software (specifically a radiosonde system and a MMDVM repeater), or are manually entered.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Jim<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Robert Bruninga <bruninga@usna.edu> <br><b>Sent:</b> 23 March 2019 13:38<br><b>To:</b> Jim (List) <jim.list@stuckinthemud.org><br><b>Cc:</b> TAPR APRS Mailing List <aprssig@lists.tapr.org><br><b>Subject:</b> Re: [aprssig] Beacon parsing help<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>I think your thinking is correct. These are bad packets. No new position report formats have been added in morethan a decade.<o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'>There are plenty and they work fine.<o:p></o:p></p></div><div><p class=MsoNormal>Bob, WB4APR<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Fri, Mar 22, 2019 at 5:14 PM Jim (List) <<a href="mailto:jim.list@stuckinthemud.org">jim.list@stuckinthemud.org</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>Looking for help from someone experienced in parsing ARPS beacons to assist<br>in understanding differences in the position beacons I'm seeing from various<br>stations.<br><br>I'm dusting off some code I wrote a few years ago to parse APRS beacons,<br>which at the time was decoding everything perfectly and was used on various<br>activities.<br><br>However, monitoring positional data today it's picking up beacons with<br>differences that do not appear in the specification.<br><br>Are these differences recent changes to the APRS spec, or are they clients<br>that are just sending bad data?<br><br>Monitored beacons are listed below, with a note of what I'm seeing wrong.<br><br>K3NAL-1>BEACON,qAR,KK4ZWW-1:!146.64-000000z3812.05n/07623.07WrT146 R25 NetTu<br>1930 Mtg 4th Th<br>*** Appears to have a frequency, a dash and a time inserted before the Lat,<br>plus the Lat letter is in lower case <br><br>W9GO-3>BEACON,qAR,KC9MWQ-1:!146.91-4028.82N/08609.33W# Kokomo Repeater Club<br>*** Another with what looks like a frequency and a dash before the Lat<br><br>SV1GCB-3>APMI06,SV3ISZ-11*,SOUTH2-1,qAR,SV3IRM-10:!222024S3704.18N/02225.79E<br>#QTH T=18.5C, U=13.2V, WX3in1Plus2.0<br>*** Has "222024S" inserted before Lat<br><br>WB5OER-2>APTT4,WX5II-3,WIDE1*,WIDE2-1,qAO,KG5YOV:!2847.0333N/09729.2666W#PHG<br>71304/ 13.0V<br>*** Too many digits after the decimal in both Lat and Long<br><br>W3EPE-3>APTT4,WIDE1-1,WIDE2-1,qAO,BEARCK:!4048.31N07531.34W#PHG51304/ W1 <br>*** No symbol table ID<br><br>POINT6>APN382,qAR,N6MLD-1:!4702.46NS11359.W#PHG5860/ 11,22,21,33 harc's pt6<br>thanks mso wx.<br>*** No digits after the Long decimal<br><br>OE3FRE-15>APNL51,TCPIP*,qAI,OE3FRE-15,SQ6KXY-2,T2DENMARK,T2HUB5,T2CAEAST:!48<br>04.66NN/01618.46EE`Radiosondetracker<br>*** Lat N/S and Long E/W duplicated<br><br>DC1SK-15>APNL51,TCPIP*,qAI,DC1SK-15,SQ6KXY-1,T2BIO,T2HUB5,T2CAEAST:!5112.018<br>N/01117.042E`Radiosonde Tracker - Based on kxyTrack 1.0-1805<br>*** Too many digits after the decimal in both Lat and Long<br><br>DO2ATR-10>APGW1K,TCPIP*,qAC,T2KA:!5005.05N/007 0.07E#DO2ATR iGate APRS<br>432.500 JO30MU<br>*** Spaces in the Long that don't conform to position ambiguity<br><br><br><br>Jim, G1HUL<br><br><br><br>_______________________________________________<br>aprssig mailing list<br><a href="mailto:aprssig@lists.tapr.org" target="_blank">aprssig@lists.tapr.org</a><br><a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><o:p></o:p></p></blockquote></div></div></div></body></html>