issue in order aprs string

[pd9mwo]

look like there is an issue with the order to send to APRS-IS

PD9MWO-4>APRS,TCPIP*:@171407z5216.39N/00437.37E_110/004t049g012P000h83b10256L063Xaprs-weather-submit/1.4
but must be
PD9MWO-4>APRS,TCPIP*:@171407z5216.39N/00437.37E_110/004g012t049P000h83b10256L063Xaprs-weather-submit/1.4

the raw packets on aprs.fi
GOOD
2022-01-17 15:09:09 CET: PD9MWO-4>APRS,TCPIP*,qAC,T2EDM:@171408z5216.39N/00437.37E_049/004g012t049P000h83b10256L062Xaprs-weather-submit/1.4

ISSUE
2022-01-17 15:11:31 CET: PD9MWO-4>APRS,TCPIP*,qAC,T2EDM:@171411z5216.39N/00437.37E_084/007t049g002P000h83b10256L061Xaprs-weather-submit/1.4

the order is wrong here
can you please fix this ??

many thanks in advance
menno
pd9mwo

[pd9mwo]

changes these lines in the aprs-wx.c file ( version 1.4 )

look like its working now
but can you please fix it ???

212         else {
213                 /*                    header_________ timestamp____pos__wc_ s_t__*/
214                 snprintf(result, 61, "%s>APRS,TCPIP*:@%.2d%.2d%.2dz%s/%s_%s/%s",
215                         p->callsign, now->tm_mday, now->tm_hour, now->tm_min,
216                         p->latitude, p->longitude, p->windDirection, p->windSpeed);
217         }
218
219         if (notNull(p->gust)) {
220                 strncat(result, "g", 1);
221                 strncat(result, p->gust, 3);
222         }
223
224         if (notNull(p->temperature)) {
225                 strncat(result, "t", 1);
226                 strncat(result, p->temperature, 3);
 227         }

[rhymeswithmogul]

It seems odd that APRS.fi would ignore the gust speed if it comes after the temperature -- but that wouldn't be the first time I've had to deviate from the specification to make that (wonderful) site happy. Could you link me to a raw packet that was not processed correctly?

[pd9mwo]

Thx the raw item thats in my first port menno

…

On Tue, Jan 18, 2022 at 1:39 PM Colin Cogle ***@***.***> wrote: It seems odd that APRS.fi would ignore the gust speed if it comes after the temperature -- but that wouldn't be the first time I've had to deviate from the specification to make that (wonderful) site happy. Could you link me to a raw packet that was not processed correctly? — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVZQQRN7O74MKGPDF3T7FQTUWVNRJANCNFSM5MEZIB5Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[rhymeswithmogul]

APRS.fi is not following the specification correctly, but I suppose I can switch the g parameter to be first.

[pd9mwo]

APRS.fi is not following the specification correctly, but I suppose I can switch the g parameter to be first.

or use my solution in the second post ;-)

[rhymeswithmogul]

Sorry, @pd9mwo. I could have sworn that I worked around this in version 1.5. It's fixed now.