[aprssig] Generic APRS Digipeater Path?

[Randy Love]

So, as an example.. if this packet were sent as:

 KE8YNU-5 <https://aprs.fi/?c=raw&limit=&call=KE8YNU-5>>APN000*-2*
,TCPIP*,qAC,W8FSM-MI:=4237.98N\08251.11Wkke8ynu at gmail.com
instead of :

 KE8YNU-5 <https://aprs.fi/?c=raw&limit=&call=KE8YNU-5>
>APN000,TCPIP*,qAC,W8FSM-MI:=4237.98N\08251.11Wkke8ynu at gmail.com

Then a digi should treat that the same as if were sent as:
 KE8YNU-5 <https://aprs.fi/?c=raw&limit=&call=KE8YNU-5>
>APN000,WIDE2-2,TCPIP*,qAC,W8FSM-MI:=4237.98N\08251.11Wkke8ynu at gmail.com

Can't say as I've even seen this concept used much less implemented
anywhere... First I've heard of it!

Seems that the digi would need some extra buffer and processing power to
figure out which digi's are N,S,E and W for this special routing via SSID
on the destination...
Ouch... making my brain hurt...

73,
Randy
WF5X
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20240627/66f6f4a0/attachment.htm>