The APRS spec would likely contain the specification for any and all data strings. Looking at Bruninga's site I see that they are working on v1.2; I have been reading v1.0.1.
http://www.tapr.org/aprs_working_group.html http://eng.usna.navy.mil/~bruninga/aprs/aprs11.html My guess is that anything xastir writes to APR-IS (igate or not) would be within APRS spec "tolerances". I have been working on a packet decoder in c to help me understand actual data strings better. You are welcome to it if interested (though I am sure that something similar is already in xastir). It is more "human readable" than "machine optimized" since it is a learning endeavor... Though I may be completely wrong ;) Greg On 2/11/07 9:13 AM, "David Daniel Clark" <[EMAIL PROTECTED]> wrote: > Good morning, > > Can some one point me to the place in the xastir where data gets written > to the APRS-IS. I am interested in how objects, posits, messages etc > are written and not necessarily IGate-ing, but it may be the same code. > Pseudo code would be good too. I have an idea for some SAR specific > messaging stuff and am trying to understand how the APRS-IS works. I > have not had much luck looking at the documentation on > http://www.aprs-is.net > > Thanks es 73, > Dave _______________________________________________ Xastir-dev mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
