<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",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;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
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-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Bob, this seems to be a “cart before the horse” problem.<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The APRS specification should drive the equipment used in APRS, not the other way around. Granted, an installed base of 10,000 APRS devices is a concern. But, there has to be a better reason to deprecate part of the spec than just lack of support by one type of APRS client.<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Also, the TM-D700 has been out of production about 9 years, I believe. While many of them may still be in use, they will gradually disappear from active use in APRS.<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Bob…<o:p></o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></font></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><font size=2 face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;font-weight:bold'>From:</span></font></b><font size=2 face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> aprssig [mailto:aprssig-bounces@tapr.org] <b><span style='font-weight:bold'>On Behalf Of </span></b>Robert Bruninga via aprssig<br><b><span style='font-weight:bold'>Sent:</span></b> Monday, March 14, 2016 8:36 PM<br><b><span style='font-weight:bold'>To:</span></b> TAPR APRS Mailing List <aprssig@tapr.org><br><b><span style='font-weight:bold'>Subject:</span></b> Re: [aprssig] APRS SPEC Addendum 1.2 Proposals (compressed items & objects)<o:p></o:p></span></font></p></div></div><p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:12.0pt'><o:p> </o:p></span></font></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>The reason the compressed objects were depricated is because there were about ten thousand APRS radios (D700’s) out there that could not decode them. (Problem is, I lost my notes on what does and does not work… argh!)</span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>But, if the idea is to have consistent performance and end-to-end communication in a tactical real-time network, it did not seem to be a good idea to have a built-in, known failure mode in a standard.</span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Also, the compressed format has no more precision than a regular object. Its still to the nearest 60 feet. Only the !DAO! protocol has increased precision.</span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>If anyone has the exact list of what the D700’s or any other radio for that matter, do or do not decode, then maybe it is time to re-look at this.</span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Bob, WB4APR</span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><font size=2 color="#1f497d" face=Calibri><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'> </span></font><o:p></o:p></p><p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif;font-weight:bold'>From:</span></font></b><font size=2 face=Tahoma><span style='font-size:10.0pt;font-family:"Tahoma",sans-serif'> aprssig [mailto:<a href="mailto:aprssig-bounces@tapr.org">aprssig-bounces@tapr.org</a>] <b><span style='font-weight:bold'>On Behalf Of </span></b>Curt Mills via aprssig<br><b><span style='font-weight:bold'>Subject:</span></b> [aprssig] APRS SPEC Addendum 1.2 Proposals</span></font><o:p></o:p></p><p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:12.0pt'> <o:p></o:p></span></font></p><div><div><div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Regarding this web page:<font color="#1f497d"><span style='color:#1F497D'> </span></font> <a href="http://www.aprs.org/aprs12.html">http://www.aprs.org/aprs12.html</a><br>"Formats no longer recommended: Compressed-Objects, ITEM Format, Raw Weather Formats,"<o:p></o:p></span></font></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>I'd like to put in my thumbs-up for both Compressed Objects, and both Compressed and Non-compressed Items.<o:p></o:p></span></font></p></div><p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>We've implemented these in Xastir and I find them of use in SAR. Compressed format gives much better precision in placing and/or recovering objects, precision you cannot get with non-compressed APRS formats. Items are useful for placing positions when you have no timestamp, as well as providing a shorter packet than APRS Object format.<o:p></o:p></span></font></p></div><p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>In short, I see no advantage to removing formats that are currently used to good effect and already implemented in APRS programs.<br clear=all><br>-- <o:p></o:p></span></font></p><div><div><div><div><div><div><p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:12.0pt'>Curt, WE7U<br><a href="http://wetnet.net/~we7u" target="_blank">http://wetnet.net/~we7u</a><br><a href="http://www.sarguydigital.com" target="_blank">http://www.sarguydigital.com</a><o:p></o:p></span></font></p></div></div></div></div></div></div></div></div></div></body></html>