[aprssig] FW: Echolink objects to APRS

Robert Bruninga bruninga at usna.edu
Tue Jul 21 08:34:18 CDT 2009

Well, The echolink objects issue is further clarified below:

Looks like we need an APRS author to go get the EchoLink data
and then inject it into the APRS-IS.  This is a good approach
since it lets us control formatting at one central location.  Do
we have a volunteer? 

I got this from the EchoLink folks.


> The data collected from the RF Info tab 
> is sent to the central EchoLink servers and 
> displayed in summary form on the Link 
> Status page (http://www.echolink.org/links.jsp).  
> It is also available in XML format at 
> http://www.echolink.org/node_location.xml .   
> About 50% of the EchoLink "sysop" nodes 
> worldwide have elected to provide this data.  
> It isn't being injected by EchoLink directly 
> into APRS-IS... but someone could certainly 
> do so by pulling down the XML periodically.  

Anyway, so it looks like EchoLink author did his side of the
objective by getting position info, and providing an operator
selection for putting out the data, and all we need is to grab
it and insert it.  Then local Igates add their local EchoLink
object names to the pass-to-RF function and we have achieved the

That is, open-echolink nodes appearing on APRS for the mobile
operator with Frequencys so that the mobile operator can use
EchoLink easily from anywhere at anytime.



More information about the aprssig mailing list