<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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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 style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>I think, a little detail is missing in the packet without position – that’s temperature. There is a need in the APRS standard to have a temperature field, at least t…<o:p></o:p></p><p class=MsoNormal>73<o:p></o:p></p><p class=MsoNormal>Andrew AB9FX<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b>From:</b> aprssig <aprssig-bounces@lists.tapr.org> <b>On Behalf Of </b>John Gorkos<br><b>Sent:</b> Saturday, October 23, 2021 15:11<br><b>To:</b> aprssig@lists.tapr.org<br><b>Subject:</b> Re: [aprssig] APRS Object & Weather format<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>APRS Spec 1.01: 29 AUG 2000, bottom of page 65 (curse the editor that didn't put Table #s), "Complete Weather Format -- With Lat/Long position, No Timestamp" indicates that it should be valid. HOWEVER, on the previous page, under the "Positionless Weather Data" heading, you'll see:<br>"NOTE: The weather report must include at least the MDHM date/timestamp, wind direction, wind speed, gust and temperature..."<o:p></o:p></p><p>Ambiguity aside (I think a "Positionless Weather Report" requires the timestamp), it is valid to have a weather report without timestamp. Just assume time=now().<o:p></o:p></p><p>John Gorkos<br>AB0OO<o:p></o:p></p><div><p class=MsoNormal>On 10/23/21 10:48 AM, Matthew Adair wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal style='margin-bottom:12.0pt'>I've been going over the APRS 101 specification and teasing it apart using Heikki's excellent Ham::APRS::FAP library.<o:p></o:p></p><div><p class=MsoNormal>Page 66 of the APRS101 document gives two example weather report formats as objects:<o:p></o:p></p></div><div><p class=MsoNormal># Complete Weather Report Format — with Object and Lat/Long position<o:p></o:p></p></div><p class=MsoNormal>;BRENDA *4903.50N/07201.75W_220/004g005t077r000p000P000h50b09900wRSW<o:p></o:p></p><div><p class=MsoNormal>;BRENDA *092345z4903.50N/07201.75W_220/004g005b0990<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>The second object parses correctly. The first one does not.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>From what I can figure out, the reason is because the first object doesn't have a valid time stamp. The 101 spec seems to indicate that Objects require a time stamp. So, is the first object truly invalid, or is a weather object without a timestamp a valid exception?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- Matt, N8SHA<o:p></o:p></p></div></div><p class=MsoNormal><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>aprssig mailing list<o:p></o:p></pre><pre><a href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a><o:p></o:p></pre><pre><a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><o:p></o:p></pre></blockquote></div></body></html>