22869Re: [aprsisce] Object Paths
- May 10, 2013On 5/10/2013 1:16 PM, Robert Bruninga wrote:
>>> I cannot see the paths used for these objects, because the APRS-ISNot based on what I'm seeing from
>>> strips the path when heard by an IGate, but if they are anything other
>> Please educate me Bob. How does "the APRS-IS strip the path
>> when heard by an IGate"?
> I thought that everything after the last-digipeated-used was stripped. So
> that if a packet had 4 hops and was heard on the first one, that all the
> path after the first one was stripped, then the QAR construct and callsign
> of the IGATE was inserted?
station that routine travels from Canada to El Paso criss-crossing the
2013-05-07 05:38:44 EDT: VA3CC-14>S6UT2Q,WIDE1-1,WIDE2-2,qAR,KG4LVA-1:`r60!6<0x1f>u/]"5U}Heading to El Pas
2013-05-07 01:57:44 EDT: VA3CC-14>T0QU6P,WA4ZKO-15,WIDE1*,WIDE2-2,qAR,WA4ZKO-2:`p&<0x7f>!?ku/]"7#}Heading to El Paso
2013-05-07 01:59:00 EDT: VA3CC-14>T0QU6P,WA4ZKO-15,WIDE1,KB9GYO-3,W8BLV,WIDE2*,qAR,W8GUC:`p&<0x7f>!?ku/]"7#}Heading to El Paso
> Maybe things have changed... (above my overly protective rock ;-)Been that way for as long as I've been into APRS. I'm very familiar
with that because I started out with path analysis from simply the
global APRS-IS feed. At least, provided that all of the involved
digipeaters are properly configured and WIDEn-N capable.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
- << Previous post in topic Next post in topic >>